Time bombing

[RichP]

About to release a new version of our software on CD, want to send out about 500 or so copies, want to either timebomb it for 90day or so or limit users. Never done it before so I don't know how. The user limit I think I can set in the code before compiling but then the issue is to change it to an 'unrestricted' on the fly if they buy it so I would prefer not to. Any suggestions. Oh, it runs on windoze but was mostly for more powerful *nix systems.

[old_man]

Time bomb is tough. The problem is that you can't modify the CD, so in theory you are going to have to set a fixed date. All that has to be done to get past that is to set the date on the computer back to before the date. Most software uses a hidden registry entry or hidden file that holds the install date. Even when you uninstall, it leaves the entry or file behind. If you know the entry or file, you can just nuke it. The best would be to serialize each copy. Have it check in with a server you run and then keep track of the date and serial number on each install.

[RTicUL8]

Another option:
Set a counter to allow X number of starts.
Program a message box to say something like: This program will run X more times before registration is required.

If you hide X in a data file kept in the program folder, they can bypass registration by simply deleting and re-installing the program.

Instead:
Research methods for programming and hiding a registry key for X.