Didn't want to mark it as a bug just yet in case it is something wrong with what I am doing that I just am not seeing.
I have the following code in my launcher.ini for Pencil Project dev test 4:
[Launch]
ProgramExecutable=Pencil\pencil.exe
DirectoryMoveOK=yes
WaitForEXE1=xulrunner.exe
RunAsAdmin=force
RunAsAdmin2000=none
RunAsAdminXP=none
RunAsAdmin2003=none
But on XP I am getting an error when running it as follows:
Error: invalid value 'none' for [Launch]:RunAsAdminXP. Please refer to the Manual for valid values.
As far as I can tell, I am doing everything right there in reference to the launcher.ini docs, so is this a bug or have the docs not been updated with a change from 2.1 to 2.2?
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
See the styling in the [Launch]:RunAsAdminXP documentation:
Note the difference between "
force", "try" and "none".forceandtryare values, but none signifies the omission of any value. (Sorry, it has always seemed to me to be clear in the documentation, but apparently it is not so. Perhaps it should be made italic.) As it stands, there is no way to override for a specific value, specifying no value.I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
Thanks for that.
I had semi-noticed the styling difference but had not equated it to actually meaning something different.
As for overriding, the last paragraph under RunAsAdmin states that for apps requiring admin on modern Windows, you should specify RunAsAdmin=force and then override for 2000, XP and 2003 with none. Are the docs incorrect regarding this?
I took a look at PAL's source, and it looks like the docs are indeed incorrect.
With that said, I think I've got a way to enable what you want. I'll test it, then send it to Chris or Aluisio for adding to PAL.
Thanks, although it may not be necessary. The issue can be worked around by setting the older OSes to 'try', it just depends on how much of a time/resource hit it is to check for admin privileges with 'try' as opposed to not checking at all.
Did I really do that?
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
Maybe a change in documentation is needed for this case, and any others that are similar?
Something like:
Values: force / try
Default: not set
Optional
That should make it more obvious.
Previously known as kAlug.
Here's a patch file for the changes.
http://caswellaquatics.ca/files/GordPALdocsClarification.patch