When I was on the Watergate beta team, I met the developer
in person, and was working on some new code with him. He said that
his registration scheme used three distinct places in the binary file
combined to set 1 bit in another place in the file, which then was
used to enable or disable registration. I'm sure there was more to it
than that, but it was quite complex. He had offered anyone a full
complete key to anyone that could crack it.
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 6/15/99, 3:10:16 PM, "Michael S. Davis" <[EMAIL PROTECTED]> wrote
regarding Crack Prevention (or rather Reg Protection):
> Just curious. What is the concensus on this point I
> am about to make?
> Something that bugs me is developers who have a Reg
> Scheme that relies on leaving hidden data on my Palm,
> in order to know if an app has been previously installed.
> Seems to me this is only possible by leaving some hidden
> data on my palm. Even if I decide to not keep the product,
> I'm stuck with the garbage left hanging around.
> With storage kind of limited, does this seem like a bad idea?
> Or, am I wrong; is it possible to know if an app has
> been previously installed without leaving some hidden garbage (data)
on my
> palm?
> ----------------------------------------------------
> Shoot-to-Win
> Protect the 2nd Amendment
> ----------------------------------------------------
