🚀 go-pugleaf

A tip :
It doesn't matter what you use, so take it easy on yourself.
If you go with any simple thing, a cracker who is handy with softice or
turbo debugger will wipe it out.

If you go with encryption, crc checks or special keys or serials, some
maniac math genius will puzzle it out.

And, if you get past those, the third or fourth legimate user will copy
whatever is necessary to run his copy of the program, and you're finished
anyway.

What you have to think in terms of is a deterrent, and one that doesn't
annoy legit users. so forget doc checks, and go with a simple key file and
maybe some crc checks and encryption (my method, is as follows)
1. Basic protection is a file created in the root directory marked hidden
system and named something innocent, like " win32krn.sys" or "dosio.sys"
(people will not screw with things that look important, unless they know
better, in which case you've already lost."

2. do overlayed crc checks (take an arbitary section of code, and crc it,
(just make sure it contains your protection scheme (completely, including
any variables stored elsewhere, do another crc on them) this gives code
changers fits because it's easy to defeat a crc on a whole file, (you just
generate a crc for the file, find that value, make your changes and generate
a new crc, replace old with new, tada) but if it's just a section....

3. (if you do this, do it before you add crc's (duh) ) do a basic xor
encrypt on the file.

That would be best to limit unwanted copying.
the best encryption code can be found with virus programming, crc code is
everwhere, and the key file is simple. good luck

--

- Bishop

Henry Gray wrote in message <36123bdf.0@145.227.194.253>...
>The serial numbers of disks are stored in their boot sector. If you read
the
>boot sector of the floppy disk (which you can do via a DOS or BIOS
>interrupt - I forget which) then you can read the serial number of the
disk.
>
>
>
>