> so... technically... :) their patch should work for the current
> session (of running the program).. but when they exit, and come
> back in.. the InitApplication routine should redefine the
> variable 'registered'..
>
> but... strangely.. it doesnt! :)
YES!!! *big huge grin*
it was a compiler optimization! :) *grin grin grin*.. sometimes
you have to hate your compiler for being too smart!
i made a little modifcation to the code, changed the offsets
so that their patch would still work.. and it now does as i
expected..
ie: enter in a bogus code and then when you restart.. it is
not longer registered.
so.. from an ethical point of view.. if, as a developer, you
can detect that a fake code has been entered.. (or possibly
do a CRC check on the code).. would it be ethical to format
the users device? or possibly throw a FATAL EXCEPTION?
:> *grin*..
once people know that a hacked version of your software can
do bad things.. maybe they wont use the cracked versions?
does anyone know how to actually get a reference to the
memory used by the '.prc' file and then perform a CRC check on
it?
cheers.
az.
--
Aaron Ardiri
Lecturer http://www.hig.se/~ardiri/
University-College i G�vle mailto:[EMAIL PROTECTED]
SE 801 76 G�vle SWEDEN
Tel: +46 26 64 87 38 Fax: +46 26 64 87 88
Mob: +46 70 352 8192 A/H: +46 26 10 16 11
