Yes Thank you.
I have an exe file(Main.exe) that extracts when it is run.After extraction it runs a setup.exe file which it has extracted.
I am using ExecWait "Main.exe" to run that exe.But the problem is after the setup.exe is launched the nsis installed is ended.I want the nsis installer to end after the setup.exe file has completed the installaton.
Waiting for external setup
8 posts
Originally Posted by Mohamaed View PostYes Thank you.
I have an exe file(Main.exe) that extracts when it is run.After extraction it runs a setup.exe file which it has extracted.
I am using ExecWait "Main.exe" to run that exe.But the problem is after the setup.exe is launched the nsis installed is ended.I want the nsis installer to end after the setup.exe file has completed the installaton.
Sounds to me like setup.exe needs a switch to wait. Who created setup.exe and where did you get it from?
This is in the installation part.
When the main exe is run it extracts some files.One of the file is the setup.exe.This is automatically made to run after the extraction.
When the main exe is run it extracts some files.One of the file is the setup.exe.This is automatically made to run after the extraction.
We cannot help you when you ignore questions and don't provide details about 3rd-party programs...Originally Posted by Anders View PostWho created setup.exe and where did you get it from?
It is a Visa Run time Engine 5.3
When I run that exe ,it extracts itself creating a setup.exe file .
The setup file provides a window to install Visa runtime.By that time the Nsis installer has finished its installation.But I want the nsis installer to wait for the installation of Visa runtime engine.
When I run that exe ,it extracts itself creating a setup.exe file .
The setup file provides a window to install Visa runtime.By that time the Nsis installer has finished its installation.But I want the nsis installer to wait for the installation of Visa runtime engine.
Automating the Installation of NI Products?
This is not really a NSIS issue, please contact the vendor of that software if you have further questions...
This is not really a NSIS issue, please contact the vendor of that software if you have further questions...
Some "Setup.exe" programs extract the actual installation files to some "temp" directory, then they launch the actual installer executable from there and then they exit. It means the "Setup.exe" is only a wrapper around the actual installer. So what you see running is the actual installer, located in the "temp" directory, while the initial "Setup.exe" has long terminated! The problem here is that ExecWait only waits for the process it has created, e.g. the initial "Setup.exe" in this case. It does not wait for any child processes of that process! If the "Setup.exe" does not offer some kind of "/wait" switch, you could try extracting the "Setup.exe" yourself (instead of launching it). Then, what you run with ExecWait (and thus wait for) would be the actual installer executable - in other words: The wrapper "Setup.exe" is skipped completely.
Ya.I got the point.Thanks a lot.