mtconleyuk
1st May 2007 14:36 UTC

Directory Constants on Japanese XP
I have an installer that I'm attempting to run on a Japanese system, but the predefined constants $SMPROGRAMS, $DESKTOP, $STARTMENU, and $SMSTARTUP (and possibly some others) all wind up pointing to the wrong location: the user's folder in the Documents and Settings folder.

I'm not doing anything special, and I have a test script that just calls SetShellVarContext current, followed by a DetailPrint of each string, so I can see what they're supposed to be.

Any idea why this should be happening? Does anyone else have this problem?

dienjd
1st May 2007 15:27 UTC

I just tried this on a Japanese system, and the constant values were correct for me. Are you running a true Japanese OS or another OS that has been set to Japanese?

mtconleyuk
1st May 2007 15:32 UTC

I'm running Japanese Windows XP, installed from an MSDN developer disc.

mtconleyuk
1st May 2007 15:44 UTC

Here's the test script I've been using, by the way.

[Bogus test script deleted]

mtconleyuk
1st May 2007 15:53 UTC

Sorry about that last post; here's a cleaned-up version of the script.

dienjd
1st May 2007 15:55 UTC

I compiled and ran, and it displayed correctly for me. I'm testing on a Japanese XP VPC image. I had to comment out this:
!include "CMSLIb.nsh" ; CrystalMaker functions.
!insertmacro GetContextDocsFolder

Unless that is causing the issue, it could be your instance of a Japanese system. NSIS has had multi-lingual support for a while now. VPC is now free, so if you confirm that it's your system causing the problem, you could install VPC to do your development and testing.

mtconleyuk
1st May 2007 16:02 UTC

You don't have to compile the thing on the Japanese system itself, do you? I built mine on a stock English system and copied the binary over.

dienjd
1st May 2007 16:05 UTC

Correct, you can compile on an English system. My last comment was confusing. I meant you could use VPC to test with, not to actually do your script development on.

mtconleyuk
1st May 2007 16:17 UTC

Right. Well, I'm going to assume my system is corrupt and reinstall and see what happens. Thanks.

mtconleyuk
2nd May 2007 10:17 UTC

I ran a repair from the installation DVD and now everything works fine. My guess is the problem occurred when I tried to install a video driver for this laptop awhile ago and the installation failed.

Thanks for the script testing!