Cyrille
18th February 2010 18:08 UTC

Windows7 - Desktop and QuickLaunch shortcut
Dear all,

I am currently experiencing problem with my installation package created with NSIS Compiler V2.3. The problem has been identified only by a user with Windows 7. If the desktop and QuickLaunch shortcuts are well created, he has also noticed that the shortcut to the application is also created in:

c:\users\Administrator.WIN-XXX\Desktop\
and :
c:\users\Administrator.WIN-XXX\AppData\Roaming\Microsoft\Internet Explorer\Quick Launch\

where XXX is the real name of his Windows account.

To create the short cut, I have used the following code:

CreateShortCut "$DESKTOP\my_app.lnk" "$INSTDIR\my_app.exe"
CreateShortCut "$QUICKLAUNCH\my_app.lnk" "$INSTDIR\my_app.exe"

Is it a bug with my code or something normal with Windows 7?

Thank you very much for your kind support
Best regards,
Cyrille

Anders
18th February 2010 18:25 UTC

Those paths looks correct to me, what is the actual problem? (Also, 2.3 is kind of old, you might want to upgrade so you can use RequestExecutionLevel)

Yathosho
18th February 2010 21:17 UTC

afaik there is no more quicklaunch in win7

pengyou
18th February 2010 21:53 UTC

Windows 7 still supports QuickLaunch - all you have to do is enable it. The first hit in a Google search gave me step-by-step instructions for enabling it.

Yathosho
18th February 2010 22:39 UTC

support yes, but with taskbar pinning nobody has a reason to go back to quicklaunch. there already is a discussion that suggests not to pin programs here.

pengyou
19th February 2010 00:21 UTC

Originally posted by Yathosho
with taskbar pinning nobody has a reason to go back to quicklaunch.

Sorry, I disagree. I find QuickLaunch very useful in Windows 7.

Cyrille
19th February 2010 13:47 UTC

Originally posted by Anders
Those paths looks correct to me, what is the actual problem? (Also, 2.3 is kind of old, you might want to upgrade so you can use RequestExecutionLevel)

In fact, the correct path should be \XXX\ (i.e. without the administrator.WIN). However, the person informed me that these shorcuts were created from a previous installer. The last one do not create these shortcuts. Everything is fine thus. Thank you very much and sorry.

I am going to check the forum about the use of RequestExecutionLevel. Thanks again :)

Cyrille

Anders
19th February 2010 15:53 UTC

I'm guessing the Administrator.WIN prefix could have been added by windows itself during a reinstall or account name change, either way, NSIS just uses what windows tells it to use as the shell path

Cyrille
19th February 2010 17:43 UTC

I would bet on the account kept from an updated from a previous version of Windows :)

Cyrille
19th February 2010 17:53 UTC

Originally posted by Anders
Those paths looks correct to me, what is the actual problem? (Also, 2.3 is kind of old, you might want to upgrade so you can use RequestExecutionLevel)

Probably a stupid question: I would like to know if RequestExecutionLevel defines the requested execution level of the install package (and thus the choice depends on the NSIS script) or of the .exe file of the installed application?

Thank you very much
Cyrille

Anders
19th February 2010 18:46 UTC

Originally posted by Cyrille
Probably a stupid question: I would like to know if RequestExecutionLevel defines the requested execution level of the install package (and thus the choice depends on the NSIS script) or of the .exe file of the installed application?


Cyrille

Installer and Uninstaller

Cyrille
20th February 2010 19:19 UTC

Ok, so I suppose the admin rights are only necessary when the installer writes in the registry. Is it correct?

Anders
20th February 2010 20:04 UTC

Its necessary if you want to do admin things (DOH) like writing to HKLM or $programfiles/$windir etc

Cyrille
21st February 2010 13:02 UTC

Ok, thank you very much Anders. It is very clear now :)