ErikET
27th September 2009 22:08 UTC

NSIS_CONFIG_LOG_STDOUT and ExecWait
Hi,

I was wondering if the following is a bug or by design:

I compiled NSIS 2.45 from the source with the NSIS_CONFIG_LOG_STDOUT and NSIS_CONFIG_LOG and I created a installer that uses ExecWait to execute a VBScript. All script output is neatly sent to stdout.

Now the problem: when you press CTRL-BREAK during execution of the VBScript via the ExecWait statement, the entire installation is being aborted, which results in $INSTDIR being left with a partial installation.

I first thought this was normal behaviour, however when creating the installer without a custom compiled NSIS (i.e. without NSIS_CONFIG_LOG_STDOUT) a CTRL-BREAK during the VBscript execution results in a cleanup of $INSTDIR.

Any thoughts on this?

ErikET
29th September 2009 11:09 UTC

Anybody?

kichik
29th September 2009 11:51 UTC

That's kinda funny. I guess we should add some kind of handler for that in NSIS and ignore it. I think MakeNSISw has a function that sends Ctrl+C to makensis.exe. It should be easy to find its counterpart from there. Submit a bug report or a patch for this.

You can also probably set a break handler in your VB script as a quick fix.