wrong location for start in folder for shortcuts?

The start-in folder of the shortcut the instaler creates is set to the start menu
directory where the mushclient icons are installed. As a result of this, the prefs.sqlite
and mushclient.ini get created in the start menu, and things like saving plugin states doesn't work
since the state directory isn't in .\worlds\plugins\state where the client expects to find it. I've
verified this by removing mushclient, deleting the start menu folder and the program files folder, and reinstalling.
I'm using Windows XP if that matters.

Hello Tyler,

I've also seen this behavior. I'm running Win 7 under VMware Fusion.

I've seen this too, actually. I believe it happened to me on Vista. It was a few months ago, and I think I just changed the shortcut target to point to the right location, or something.

The installer needs work for Windows 7.

Meanwhile see the helpful tips here:

http://www.gammon.com.au/forum/?id=9842

Well, Tspivey said he was using XP, which is interesting because nobody's reported this rather hard-to-miss issue before, and XP has been around for quite a while. It's hard for me to believe that this is just a W7 issue.

The techniques described in that thread would also apply to earlier versions - you can put MUSHclient manually somewhere and avoid all the installer issues. Well picked up, though, that I skimmed the original problem. I think I picked up on Coderunner's comment about Windows 7.

I wonder... Nick, would it be possible to create a separate installer designed for the later versions of Windows, so we can dodge these inconsistencies altogether?

I think I found the problem. In the NSIS docs
for CreateShortCut, it says:
$OUTDIR is used for the working directory.
You can change it by using SetOutPath before creating the Shortcut.

Currently, you have:


I think it will work if you use:

The first SetOutPath will create the MUSHclient directory in the start menu, and the second will reset it to $INSTDIR so that
the start in field will be set correctly.
I tried testing this by copying the relevant binaries to the correct locations so the installer could find them to rebuild,
and on my system, it seems to work - all the shortcuts
have the start in field set to the directory containing mushclient.exe.

Look strange, but I'll try it.

The semicolon should be a comment character. You shouldn't need to SetOutPath twice.

Yes, but I think he's saying it will create the directory, and then move back. Don't know if this is right.

That's what it does, gathering from the documentation.
You might be able to use CreateDirectory "$SMPROGRAMS\MUSHclient"
to make it more clear, but what you have now in latest git should work.

On line 114 of the nsi script, you're doing:



Does



not work?