not a valid win32 application

ptzNovember 20, 2011 at 2:13 PM#

I'm compiling and running the following test script:

OutFile "hello_world.exe"
InstallDir $DESKTOP\hello_world
RequestExecutionLevel user

Page directory
Page instfiles

section ""
SetOutPath $INSTDIR
#File hello_world.nsi
messageBox MB_OK "Hello world!"
sectionEnd

If I uncomment the line "File hello_world.nsi" everything is OK, but as is it produces a "... is not a valid Win32 application" error in runtime. I am a complete beginner both in NSIS and in Windows, and would like to know why this happens. Or at least how to stay away from this problem.

Thanks.

YathoshoNovember 20, 2011 at 2:43 PM#

tried the full path to hello_world.nsi?

AndersNovember 20, 2011 at 2:50 PM#

NSIS version?
Unicode NSIS? (I have seen this happen with the latest unicode version)

ptzNovember 20, 2011 at 4:07 PM#

Yes, Unicode NSIS, latest version (2.46.3). May it be safer to revert to an older release (reverting to ANSI isn't an option).

Afrow UKNovember 20, 2011 at 10:06 PM#

Or just extract an empty file to $PLUGINSDIR or something.

Stu

T.SlappyNovember 21, 2011 at 3:47 AM#

Is your script called hello_world.nsi and you want to include it in the installer?
It looks like recursion -> file hello_world.nsi is being read by NSIS compiler and also being packed into .resulting exe file.
Try to include some other file like "readme.txt" (create it)

MSGNovember 21, 2011 at 6:36 AM#

Originally Posted by T.Slappy View Post

Is your script called hello_world.nsi and you want to include it in the installer?
It looks like recursion.

There is no recursion. Including the script is a perfectly legal command.

ptzNovember 24, 2011 at 11:52 AM#

So yeah, works fine in unicode 2.46.

AndersNovember 24, 2011 at 6:28 PM#

Originally Posted by ptz View Post

So yeah, works fine in unicode 2.46.

You mean 2.46.2 or .1? I only tested .3...