Title

Message

Confirm

Want to earn a free DisplayFusion Pro license? We're looking for DisplayFusion translators!
<< DiscussionsReply

Licensing

Avatar from Gravatar.com
PGomersall
194 discussion posts
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
Jul 30, 2009  • #1
Avatar from Gravatar.com
PeterDackers
44 discussion posts
"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'. :)
Jul 31, 2009  • #2
Avatar from Gravatar.com
PGomersall
194 discussion posts
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
Jul 31, 2009  • #3
Jon Tackabury (BFS)'s profile on WallpaperFusion.com
@PGomersall: This is an excellent point, and one I've never really considered. The main issue is that writing to HKLM in Vista/Win7 is a really pain. You have to fire up a separate process as an admin, which generates a UAC prompt. As for the startup settings, this is and should be a per-user setting, which is why it is in HKCU. The only setting I can see being moved to HKLM is the license key setting, but that will require more thought on my end. It is (unfortunately) a larger change than it should be, because of UAC. I'll it add it to my list of things to investigate for version 3.2 Thanks!
Jul 31, 2009  • #4
Avatar from Gravatar.com
PGomersall
194 discussion posts
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
Jul 31, 2009  • #5
Jon Tackabury (BFS)'s profile on WallpaperFusion.com
I appreciate this feedback, I never would have thought of this myself. I have added this to my to-do list for a future release, as it does make sense. However, reading/writing to the reg in Vista/Win7 is a pain and not something I want to add to this release, this close to the end. Thanks!
Aug 12, 2009  • #6
John L. Galt's profile on WallpaperFusion.com
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....
I am I.
Aug 15, 2009  • #7
Jon Tackabury (BFS)'s profile on WallpaperFusion.com
DisplayFusion isn't being run as an admin after the installation, because of the way the installer does the elevation. I know how to elevate a process to do this (I've done it in FileSeek) but it's very messy. Hopefully I can come up with a better way for DF in the future. Thanks!
Aug 17, 2009  • #8
John L. Galt's profile on WallpaperFusion.com
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 I.
Aug 19, 2009  • #9
Jon Tackabury (BFS)'s profile on WallpaperFusion.com
I've got it on my list of things for version 3.2.
Aug 19, 2009  • #10
John L. Galt's profile on WallpaperFusion.com
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?
I am I.
Aug 19, 2009  • #11
Jon Tackabury (BFS)'s profile on WallpaperFusion.com
Everything takes time, that's why every release can't have every feature right away.
Aug 20, 2009  • #12
Was this helpful?  Login to Vote  Login to Vote
<< DiscussionsReply