>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

Terry,
These kind of things never publicly published < bg >. Some ideas that served me well but only superficially - imagination:)
A file at least occupies 512 bytes but copy and alike only copy its visible content.
Always there is usable space in frequently used files.
Filetimes have a millisecond component.
If you can write to win32\system, it is well crowded and only few would dare to check and change files there.
Registry is yet another place.
List goes on...
Cetin