Page 1 of 1

Run Program not properly waiting for command to finish

Posted: Fri Jan 30, 2009 9:34 am
by ZviZemel
Hello,

I'm having a problem with the Run Program command. I use it to execute another installer that needs to run silently after my product has been installed. I set the Run Program command to "wait for program to finish".

This used to work, and my msiscript would pause until the other installer completed, but it does not wait anymore, and I can't figure out why.

The other installer is build with Installshield. I have read in another forum post here that those installers return before the installation is finished. Again though, this used to work, and has now stopped.

Worse, if I copy/paste the line to execute the installer right to the very top of my script and place a Messagebox command after it, it will always wait for the second installer to finish before displaying the messagebox, but the original line further down the script (after my Apply Changes command to install my application) will not wait.

What could be going on here?

Any help would be appreciated.

Posted: Fri Jan 30, 2009 10:16 am
by MichaelNesmith
Are you able to reproduce this with a minimum project on all computers? If so, send us the project and we'll be able to take a better look at it here under the microscope.

Posted: Fri Jan 30, 2009 1:13 pm
by ZviZemel
Unfortunately, I am not able to reproduce this with a minimum project.

As I mentioned, if I launch the second installer at the start of my install project, it will properly wait for completion. It is only when I launch the second installer deep inside the installaware script that Run Program seems to not work properly.

It might be an issue with the second installer. I just can't figure out why it is sometimes returning right away, and sometimes only when the installer is done.

Any thoughts on this?

Posted: Fri Jan 30, 2009 2:37 pm
by MichaelNesmith
Well, first you need to figure out where the fault lies: Is it with the InstallShield installer, that is acting unpredictably (sometimes returning right away and sometimes returning after completion); or is it with InstallAware (sometimes waiting for return and sometimes returning immediately)?

Then on the basis of that information we can figure out a strategy for resolution of the issue.

Please note that InstallShield setups require a command line parameter to have their launcher wait for completion if I recall correctly from my days there. You should be able to find this from your InstallShield documentation.

Posted: Fri Jan 30, 2009 3:45 pm
by ZviZemel
Thanks for the help. It turns out the issue is with the installshield product. For some reason it returns right away if launched from CD, but returns after the install is finished if launched from local hard drive, but I can't figure out why.