as far as all this is concerned
one thing seems to be a good idea to me...
* whatever demo you give out, be sure to not just 'disable
functionality', but make sure that some functional piece of code never
finds it's way into whatever demo you distribute freely from your web
site
(these are accessible to all, and quite easy to pirate if some pirate
gives out some universal patch program or something)
It's pretty hard to enable functionality that isn't there. You simply
cannot patch, nop, or jump over a piece of code that doens't exist.
Never mind CRC checks or whatever, if you distibute a demo that is
missing some key functionality, (#ifdef it out!) it's pretty hard to
enable what isn't there if you are a hacker.
* Now you are down to people who actually buy your software.... at least
one copy of it anyway
maybe I'm totally wrong here, but I'm actually more worried about the
companies who buy one copy and distribute to the entire organization
than I am about those personal users who pick up a pirated copy ...
which is at least a little bit harder if your demo is as above?
so, at least in my mind, I'm down to worrying about small orgs buying
one copy and using for 50 or 100
(I say small, cause large companies seem to not be bothered with taking
the chance on this... where smaller companies I think do)
no, I don't know the answer to this problem.... but just some
thoughts...
just a thought,
Mark
Actual Software
Horace Ho wrote:
> a) develop a really cool regcode system (uncrackable).
> b) keep your software cheap.
> c) maybe give periodic changes to the regCodes.. (this is bad)
>
> d) Periodic rearrange the binary code (change object link order)
> and so patches won't work.
>
> Regards
> horace
