Hi,
When we run our installer in silent mode (BCWSetup.exe /s), we immediately get back the DOS command prompt, although the installation itself has only just begun. Is there any way to make the silent execution behave like a normal console application, where you don't get the prompt back until the application finishes?
TIA,
pokr
Silent install command returns before app is fully installed
Re: Silent install command returns before app is fully insta
In the Run Program command, there's a check box to "Hide Program Window". Run Program As also has an option to control window behavior.
Andy Mills
InstallAware
Other Help:
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Product Guides - http://www.installaware.com/publication ... guides.htm
InstallAware Help - Press F1 in the InstallAware IDE.
InstallAware
Other Help:
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Product Guides - http://www.installaware.com/publication ... guides.htm
InstallAware Help - Press F1 in the InstallAware IDE.
Re: Silent install command returns before app is fully insta
Hi Andy,
Thanks for your answer.
I'm not asking about launching an app from an installer, but about launching the installer itself from a command line prompt and having it to terminate before the prompt returns.
BTW, I've tried to create a new installer that just launches the original one specifying the 'Wait for Program to Finish' option in the Run As command, but it does not wait either...
Txs, regards,
pokr
Thanks for your answer.
I'm not asking about launching an app from an installer, but about launching the installer itself from a command line prompt and having it to terminate before the prompt returns.
BTW, I've tried to create a new installer that just launches the original one specifying the 'Wait for Program to Finish' option in the Run As command, but it does not wait either...
Txs, regards,
pokr
Re: Silent install command returns before app is fully insta
InstallAware setups, Wise setups, and some others don't return until they have finished execution. InstallShield setups tend to return immediately after launching a separate setup process. They don't wait, and because the process has already returned, we have no way to tell that the actual setup is still ongoing. InstallShield used to have a command line parameter to prevent such premature returns, I believe it is /sms. Try to add that to your command line parameters and see if that helps.

