Jon,
Not sure if this is specific to the beta, but your licensing says per computer (Each license purchased is only valid for one computer).
I notice that on my test machine that the code is regisitered in HKCU not HKLM and therefore is per user not machine.
Is this how it should be? In the options you can set :start DF when Windows starts but this is not correct again it is HKCU.
Either you need to change your license page to per user or fix it so that it does truely work per machine.
I suspect there may be legal issues here so be careful.
I think it would be best if it could be per machine as then it may scale in a work environment where multiple users may work on a machine; although you may need to offer both options - the licens code you produce could then determine how it runs HKCM or HKCU.
Pete

"In the options you can set :start DF when Windows starts but this is not correct again it is HKCU."
As it should be I guess? If my machine was used by 3 people (it's not, but just as an example) every user can configure DFP to run on start-up or not. It's a user's choice, so 'current user' seems to be fine? Or am I missing something here?

"Either you need to change your license page to per user or fix it so that it does truely work per machine."
He doesn't have to do squad, what's wrong with 'I suggest you...'
As far as I understand, if you want DFP to run for multiple users on the same machine, just apply the code for every user who wants DFP installed in the first place as the license clearly says 'per machine'.

But this is not good programming; if it is indeed per machine the system code should be written to HKLM and individual user settings should go in HKCU. The start functions should be either when WIndows starts or at logon; again the settings would be in their respective places.
Your comment "He doesn't have to do squad" is simplistic and unhelpful to the discussion.
Pete

Jon,
I can see where the problems stem from. The issue is that users can run in freeware mode.
I think you will have a better and more saleable app if you re-code the license to HKLM.
However can you not elevate the UI with a button on the License Key area so the code is written to HKLM? Linked to this, if the code is presented at install time then it is already elevated.
Last change the description "run at Windows startup" to "run at logon".

Otherwise B9 is good for me!
Pete

Jon,

Couldn't you borrow from the Installer's Elevation to do this? If you allow the user to run DF immediately after elevation, I believe it runs DF as admin, as it is inheriting the permissions from the installer, which had to also elevate to install in Vista / 7. So, instead of having to write a separate routing just for elevation if a user decides to enter a code, couldn't you have the options page simply present the user with a button if there is no code, that would then call the installer back up to gain the elevation required to write to the appropriate reg key?

Or would this be out of the scope of the installer / not permissible based upon the licensing you have with the installer?

Just a thought - I ran into similar issues with numerous programs when I helped Beta test them in Vista, and there were a couple of workarounds until the issues were resolved used by different applications - but IIRC one of them did something very similar to what I said....

Ahh, good call on not running it as admin post-install. Hopefully you can get this sorted out to make the license stick to the computer.....

I am gonna have to buy another license for the heck of it - man, you are putting your literal blood sweat and tears into this thing, eh?