Announcement

Collapse
No announcement yet.

Wait for program to finish before continuing

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Wait for program to finish before continuing

    Even though I tick this box, it doesn't seem to work.
    During my installation I have to run a program, which on completion continues with the SUF6 installation, using values from the program just run, however the installation just continues on.

    I actually want to install a named instance of MSDE 2000, and read the instance version, but it is trying to read it before it is written, instead of waiting for the exe to finish running first.

    We are having a similar issue installing Crystal Runtimes, instead of waiting for the exe to finish running, we get a message saying installation complete, when it is still being installed.

    One of our installation needs to detect if MDAC is installed, and if not install it and then the MSDE engine if that is not installed, instead of waiting for MDAC to finish, it jumps into the MSDE install.

    How can I make SUF6 wait until an exe finishes before continuing.

    This is quite urgent, especially as the Comapny are considering trying another install program!

    JohnD

  • #2
    Re: Wait for program to finish before continuing

    When launching a Setup Factory installation, certain contents are extracted to a temporary directory where a secondary executable is launched. When that secondary executable is launched, control is passed back to the calling process and the installation proceeds even though, the second executable is not finished running. This is very common in installers and many will have a command line argument that can be passed with the install to force it to wait until the entire process is finished. For Setup Factory installs (only), we have the command line argument /W that can be passed along with checking the "Wait for program to finish before continuing" checkbox.

    Therefore the answer will depend upon what installation program was used to create those particular installs and what command line arguments they have available. Try taking a look at the documentation for those installs to see what command line arguments are availble. Chances are they will have a similar one that can be passed.

    Hope that helps.

    Comment

    Working...
    X