You download the demo version. It is the full blown
product, no bleeps ,restrictions what so ever.
The only thing it got is a big "DEMO" sign in the
user interface.
When you buy the product you´ll get access to download the real version without the "DEMO" sign.
That´s it! And here is how it works:
----------------------------------------------------
The bitmap part with the demo sign is encrypted in the dll file and placed in position using a small
code routine. This would prevent the "normal" user
to go into the file using any standard way to view
the resources and modify where he would need a patch
from a cracker to free up the space in the otherwise
normal bitmap.
-The cracker-
The cracker would realize quite quickly that there
isn´t any real challange to do this. Just find the
code that will access this bitmap space,remove it
and replace with the proper bitmap portion and re-save.
His work will be a standard move where the developer
do not do anything to hide the decrypter code ect.
Sooner or later the crackers would loose interest.
What happens then is that all the "wannabee" crackers
will start producing patches to show that they were
first. And in this battle they would sooner or later
start to add their own "tag" into this bitmap to
show "who made it".
-The crack user-
The crack user would go through all this trouble just to cover the fact that he didn´t pay for the software where the moral justification will get
even more stupid. He can of course use it by himself
but if he shows his stuff to anyone the "demo" sign
will create questions. Friends with the same
attitude will not bother but then again they were
never the target buyer group in the first place.
So he goes out on the net and tries to download a patch where he soon discovers that it is almost impossible to find a real patch that does not include a nasty tag or anything else.
And here the developer adds his own spam attacks
where he flood the internet with fake patches
to his own product since this will not harm the product itself since it is fully functional from
the start.
-Conclution-
The end result would be that it would be a mess to
get a "clean looking" software where the only reason
you do this is to show off to your paying friend
that always could ask for a proof anyway.
The developer can more activly prevent spreading
of cracks by spamming since it will not harm the product.
Crackers will loose interest and create an "anti movement" among themselves.
In the end the customer knows that the only place to
download the real version is from the true product page and all he needs is to pay.
any thoughts?
//Daniel
