congtak
27th November 2007 00:23 UTC

Hi,
I need an urgent help with nsExec.
I used nsExec::exec in my installer which works brilliantly on my PC. But my installer doesn't work on my supervisor's PC, and I'm not sure why. I used nsexec::exec to launch a java program that our company developed, the java launched and closed just fine on my PC and I can continue installation normally. But on my supervisor's PC the java app was launched but when we close it, the installer hangs.
I think this is caused because the installer still waits for the process application to end.. because when i use the exec /TIMEOUT I can still get back to the installer. Is nsexec depends on some windows setting? perhaps CMD prompt setting or something?

kichik
27th November 2007 00:40 UTC

It only depends on the executed application's life. Once it's completely terminated (make sure there are no more java.exe or javaw.exe instances in the Task Manager), nsExec will return control.

congtak
27th November 2007 03:47 UTC

hi kichik,
I tried to do this on my own PC by running the tool manually so i have a java.exe in my task manager, then i run the installer I still can terminate the tool in my installer without a problem. Do you have any other suggestion ?

congtak
27th November 2007 04:34 UTC

Sorry i forgot to mention that i use the execDos::exec no the nsExec::exec. But nsExec has the same problem, that's the reason i changed to execDos.

Takhir
27th November 2007 06:04 UTC

The only situation I remember is Win98 bat files excution - see remark at the end of http://nsis.sourceforge.net/ExecDos_plug-in page.
To debug situation you can change nsexec/execdos call to ExecWait and check what happens in DOS window. Use bat file with pause to see app's output if window closes too fast.