mgillespie
19th November 2004 09:15 UTC

Any know problems with rebooting in NSIS 2.02?
I have noticed a couple of times that after installing my test app on NT4, and selecting reboot, it does not reboot, just appears to exit the install (as if I selected reboot later). On all the machines I noticed this on, there is a temp file still showing in task manager that prevents the reboot happening (even shutdown from the host operating system does not work, until I end the temp process).

It does seem a bit intermittant, even when testing on a fresh re-ghost of the same OS setup, on the same hardware.

Anyone seen this behaviour?

jonnebonne
19th November 2004 09:31 UTC

..
Never heared or seen it :(

kichik
19th November 2004 11:54 UTC

Rebooting code has changed in 2.02. But it shouldn't cause any troubles like this. The code was simply moved somewhere else. As NSIS itself doesn't run any processes with temporary names (unless it's the uninstaller and you're talking about A~NSISu.exe), I think it's something else your installer runs that is causing this. I don't have any idea as to why NSIS is waiting for it though.

What is the name of that process? Are you using nsExec? Have you declared .onRebootFailed?

mgillespie
1st December 2004 15:30 UTC

Noticed this also exhibits this problem on EmbeddedXP. Am looking into it further, as I do launch several 3rd party installers silently during install (Jet4, ODBC, MDAC)

mgillespie
1st December 2004 15:48 UTC

False alarm, as kichik said, NSIS is not to blame here, it's a crappy Microsoft installer for JET that uses some 16bit process to install (running under ntvdm)...