This is a strange bug, I don't know if its Windows' or
NSIS's fault...
Im using a german WinXP, latest patches.
Look at the following script:
----
OutFile "Test.exe"
Function .onInit
MessageBox MB_OK $SMPROGRAMS
Quit
FunctionEnd
Section -test
SectionEnd
----
When compiled and started as non-privileged user,
SMPROGRAMS is correct. Also if started as Administrator
using "Run as..."
However, if the file is _renamed_ to Setup.exe,
SMPROGRAMS is empty if "Run as" Administrator via the
Popup-Menu. If I _log in_ as Administrator and execute
it, SMPROGRAMS is correct. The error only occurs if an
unprivileged user executes Setup.exe as Administrator.
If the file is given any Name other then Setup.exe, all
works as expected.
(NSIS 2.0rc4)
Logged In: YES
user_id=26932
Just FYI: Windows Version is
5.1 (Build 2600.xpsp2.030422-1633:Service Pack 1)
Logged In: YES
user_id=584402
Works fine for me... Have you changed group policies?
Change permissions in Documents and Settings? Have you
done anything out of the ordinary?
Logged In: YES
user_id=26932
I checked it under a different account on the same machine
-> no problems. I can't remember having done something weird
to the other account, though.
However, I'll close this bug, as it is most propably not
NSIS' fault, if I find out more, I will reopen it, if neccesary.
Logged In: YES
user_id=584402
Are there any more constants that come up empty or is it
just $SMPROGRAMS?