This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Must specify a console launcher
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
‎Jul 17, 2008
08:38 PM
how to stop Windows silent command from running in background
Using an .exe, is there a way to have the command stay on the command line (not run in the background) when running
.exe -silent. Is there some parameter/option, to be able to do this?
(3) Replies
‎Aug 06, 2008
04:58 PM
Is there a way to do this ^ ?
Or is it just working as designed and the minute you kick off silent install you get the command line back ??
My main concerned is, how does the user know if silent install finished ??
Or is it just working as designed and the minute you kick off silent install you get the command line back ??
My main concerned is, how does the user know if silent install finished ??
‎Aug 15, 2008
02:13 PM
You have to create a console launcher. You specify this under "Distributions". We ship 2 launchers for our product, and doc that the console launcher should be used for silent installations.
This is from the docs under "Installation Exit Codes":
"There is no way to check the exit code for a Windows GUI-based launcher (for example, setup.exe) because the command prompt returns before the wizard actually exits. To have the ability to check the exit code of a Windows installation, create a Windows Console Launcher—either Windows Console Launcher, Windows IA64 Console Launcher, or Windows AMD64 Console Launcher (Premier Edition) in the Releases/Distributions view. These launchers enable you to test the exit code of a Windows installation because control does not return until the Java process has completed."
This is from the docs under "Installation Exit Codes":
"There is no way to check the exit code for a Windows GUI-based launcher (for example, setup.exe) because the command prompt returns before the wizard actually exits. To have the ability to check the exit code of a Windows installation, create a Windows Console Launcher—either Windows Console Launcher, Windows IA64 Console Launcher, or Windows AMD64 Console Launcher (Premier Edition) in the Releases/Distributions view. These launchers enable you to test the exit code of a Windows installation because control does not return until the Java process has completed."