I use a secret file to hold installation info, such as demo, reg #, etc.

I call the file winagr.dll. It is encrypted. I store it in the Windows System
folder.

If the user were to double click on it and open with Notepad, it would appear
as unreadable gibberish.



>The app will be downloaded. There is an evaluation period. The goal is to prevent the user from uninstalling and requesting (or getting away with) downloading a "fresh" evaluation and aquiring another evaluation license.
>
>I have an inocuous (how is that spelled?:) enough, yet important sounding name for the file. I may even assign "important sounding" properties to it.
>
>The file will be created at first run. The systems will be home-office XPs.
>
>My question is what folder can I depend on (or should be used) to test the desktop for an attempt to reinstall over an expired evaluation license?
>
>Is there a better way? System configuration was one thought.
>
>Thanks