Files created in Application Data and System32 directories

[thor222]

I've been running two programs (FARR and ProcessTamer) and I've noticed that each has created a file in the WINDOWS\System32 directory:

DonationCoder_findrunrobot_InstallInfo.dat
DonationCoder_processtamer_InstallInfo.dat

They look harmless and are duplicates of files created in the Application Data\DonationCoder\Keys directory in my Documents and Settings directory.

My question: what are these files and why are they written to the System32 directory?

Thanks,
Shawn

[mouser]

it is from the donationcoder license key system. the files tell it when you installed the program so it knows when to complain and tell you to visit the site after 6 months to download a new license key.  if you delete it it will be recreated.  kind of annoying i know

[thor222]

Ah. Thanks for the info! A little annoying, yes, but manageable. Just out of curiosity, why create them in the System32 directory and not just the Application Data folder?

[mouser]

it's me being sneaky.. they are created in the app dir and system dir, if one is deleted and the other exists it will be recreated from the other location

[thor222]

OK. Thanks!

[lanux128]

thor222, you are really thorough.

mouser, why not get the date from the folder (date created) of the installed programs. that way there'll be no tell-tale signs.

[f0dder]

mouser: you really shouldn't be dropping stuff in SYSTEM32 though - shame on you

[justice]

yeah I thought the fonts folder is where you put files you don't want to be seen 

[thor222]

This brings up an issue: on the main page for FARR, it claims that FARR is "fully portable and runnable from a USB thumbdrive, and doesn't mess with your registry" (emphasis not mine). I would have to partially disagree with that statement To me, fully portable means "leaves no traces" behind on the host system.

[mouser]

yes, i need to make a switch that stops this behavior when run portably, i agree 100% and it is planned for very near future.

[jgpaiva]

Mouser: Another way to do it would be to add the time information to the key itself, so that it only lasts for some time.
This also spares having different expiration dates for each program you install.

[lanux128]

or designate a different set of keys for portable versions. since those looking for portable versions are tinkerers by nature (myself included), they will back for an updated version.