Nov 4, 2011 at 1:37 PM
Edited Nov 4, 2011 at 1:47 PM
I would be completely satisfied if either of the possibilities below worked as described:
Just my 2 cents:
Best Scenario: Regardless of where the files are saved, With UAC in its default setting, Go into the properties of terminal.exe compatibility tab, Choose Run as Administrator.
If you can Run terminals at that point without a elevation prompt on Windows x64 I would consider the issue fixed for 95 percent of those users that the program terminals.
Not as bad... but still not ideal:
Same as above, but with UAC relaxed by one position.
In the above sceanarios Terminals will still run as an Administrator, just not as an "elevated"? administrator.
Would this allow the funtionality that you were discussing previously to be enabled, or does that have more to do with writing files to the protected areas of the OS? One last thought, I believe the idea of storing the configuration info in the
user profile is a good idea.
After re-reading another users comments I would like to add, that I believe that if you place the configuration files as suggested in the user profile and allow the user to run the program with reduced funtionality when not using the "run as administrator"
thi may also be acceptable, with the intention of the program to have full funtionality when "run as a administrator" option is choosen or enabled. This suggestion may serve both positions and requests.