2.0a7 Bug - Won't work on XP

okapi
12th September 2002 20:55 UTC

2.0a7 Bug - Won't work on XP
I have an installer built from this version. When I run it on a 2000 machine, it installs fine. When I run it on an XP machine, the installer says it ran fine but it actually did not copy the files to the install directory. I have admin rights on both machines. Anyone aware of this problem? Someone else using this same installer was having this problem on NT, but I have not tried to reproduce it on NT personally.

Thanks,
Steve

Joost Verburg
12th September 2002 21:24 UTC

I got no problemes at all on Windows XP. Are you using the latest CVS version? Or maybe post a script?

okapi
12th September 2002 22:46 UTC

Tracked down the problem. In the 2.0a7 (and probably in other v2.x but not the v1.x) you need to specify CreateDirectory for the installation directory on XP (and NT it would seem according to the problem). However, in W2K it will make the directory without specifically specifying for it to be made. Whether this is a bug in XP that it doesn't create the directory and should or it's one in W2K as it does create the directory (and maybe shouldn't unless creation is specified), I don't know. One way or the other, there's an inconsistency bug.

Steve

rainwater
12th September 2002 23:08 UTC

Sounds like you are not doing SetOutPath before you do File x.x?

okapi
12th September 2002 23:55 UTC

No, I do have a SetOutPath. However in 1.x and 2.x on W2K it creates the install directory but (or the output path) but on W2K and NT it does not do this.

rainwater
13th September 2002 00:48 UTC

Originally posted by okapi
No, I do have a SetOutPath. However in 1.x and 2.x on W2K it creates the install directory but (or the output path) but on W2K and NT it does not do this.

I cannot reproduce this on XP. Everytime I use SetOutPath the directory is created as it should. Do you have a script?

Dick4
13th September 2002 03:43 UTC

same here...I can't reproduce it either..

okapi
13th September 2002 05:24 UTC

Here's the config (it's split in 2 files for certain reasons).

Steve

kichik
13th September 2002 10:21 UTC

Works here too. Make sure your $INSTDIR is really what you think it is.

okapi
13th September 2002 15:37 UTC

Ooops... the ZIP I posted had the CreateDirectory line in there and thus worked. Attached is one that does not have that and thus does not create the install directory on XP (and NT?).

Steve

Yathosho
13th September 2002 16:18 UTC

i'm also having a bug since i have updated to alpha 7.

Processing script file: "C:\Programme\NSIS\makensis.exe"
Invalid command: MZ
Error in script "C:\Programme\NSIS\makensis.exe" on line 1 -- aborting creation process

i had this error on my code, which is why i tried compiling the example by joost.

the odd thing is, that "MZ" doesnt appear in the whole code!

kichik
13th September 2002 16:24 UTC

Make sure you run SetCVSShellCommands.exe before you start using the latest version of MakeNSISw from the CVS.

Sunjammer
13th September 2002 19:27 UTC

Originally posted by killahbite the odd thing is, that "MZ" doesnt appear in the whole code!

Can I just explain something, the error message you get with this problem actually tells you what is going wrong, you're just not reading it :)

It says Processing script file: "C:\Programme\NSIS\makensis.exe" and Error in script "C:\Programme\NSIS\makensis.exe". Both of these errors tell you that it is trying and unsuprisingly failing to compile makensis.exe... makensis.EXE *not* the script file you intended... the MZ stuff is because it tries to read a BINARY file, makensis.exe!!! This was all because makensisw used to need the path to makensis.exe as an argument but no longer does, however the old right mouse button menus installed by 2.0a6 still supply the path to makensis.exe as an argument which gets mistakenly interpreted as the name of the script to compile :D