The best copy protection is the one you've already used successfully:
Put out regular updates, which rearrange your code a bit.
That way the crack that worked on the last vesion won't work on the new
one.
All you have to do is rearrange your code a bit, and make a habit of
regularly checking http://astalavista.box.sk to see when you need to
put up a "new" version.
--- Alistair George <[EMAIL PROTECTED]> wrote:
> Thanks J. that gives me food for thought on this registration code I
> was
> working on. Maybe I will enhance it a bit. But any other thoughts on
> how to
> 'crack the crackers' would be interesting working on the basis of
> what
> Jeremy has just said.
> My immediate thoughts are to quit a boolean check in the EXE, maybe
> feedback
> from the reg code setting an integer to a regcode compatible #. (eg
> regOK:=isregok:boolean; change to regok:=isregok:integer;) And use
> the regOK
> integer to do something in the EXE.
> Ta.
> Al+
>
>
---------------------------------------------------------------------------
> New Zealand Delphi Users group - Offtopic List -
> [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
>
>
_______________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com.au address at http://mail.yahoo.com.au
---------------------------------------------------------------------------
New Zealand Delphi Users group - Offtopic List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
