I want to install two executables to a temporary folder, launch one .exe, and then immediately launch the second .exe.

I created a Wise package that copies the two .exe's to a temp folder. From the Execute Immediate tab, after InstallFinalize, I inserted the action Execute Program From Installed Files for both .exe's. I set both as Asynch, No wait.

When I run the compiled .msi, the two files are copied to the temp folder. Then the first .exe launches, but the second .exe does not launch (unless I cancel the first install or let it complete).

Is there a setting that I'm missing or can I not execute two programs at the same time?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
I want to install two executables to a temporary folder, launch one .exe, and then immediately launch the second .exe.

Is there a setting that I'm missing or can I not execute two programs at the same time?


what is the logic here you can only run one exe at a time then wait and run the other exe
I take it you created 2 CA's and sequenced both after installfinalize
2 actions , 2 different sequenced numbers in the installexecutesequence table
why do you want to run both exe's at the same time
Answered 07/16/2009 by: cygan
Fifth Degree Brown Belt

Please log in to comment
0
Two separate CA's, two actions, two different sequenced numbers in the installexecutesequence table.

The first .exe is a setup routine to install an application. The second .exe is a compiled AutoIt3 script that answers the setup routine questions/screens (Next, Next, Finish, etc.). The second .exe must kick-off shortly after the first one begins, so it will be running when the various setup screens appear.
Answered 07/16/2009 by: Ron Duca
Senior Yellow Belt

Please log in to comment
0
The application executable (first .exe) is a self-extracting file that unzips the setup files to a temporary location, and then automatically launches the install. When the AutoIt3 script (second .exe) launches, it sits in wait of specific application setup screens to appear and performs certain functions depending on the screen. The functions really just "press" the Next button a few times, and then the Finish button.

I can manually kickoff the application installation, and then immediately manually kickoff the answer script, and it works fine. I just can't get it to works in WPS. I used to do this all of the time using Wise 9.
Answered 07/16/2009 by: Ron Duca
Senior Yellow Belt

Please log in to comment
0
I resolved my issue by removing the CA that kicks off the application install. I now just have one CA that kicks off the application install and answers all of the install screens.
Answered 07/17/2009 by: Ron Duca
Senior Yellow Belt

Please log in to comment
0
Hi Ron,

Why would you be using Wise to create and install that launches and setup routine and then an AutoIt script to answer all of the screens, when the whole point of Wise Packaging Studio is to give you the ability to to capture this installation into a MSI, where you can install it with a single click and no user interaction ?
Answered 07/17/2009 by: michaelnowell
Second Degree Blue Belt

Please log in to comment
0
The application in question performs a rather convoluted install. It includes an installation of SQL Server Client and during the installation, no less than six command prompts open and close while it performs various file installations and configurations. Two of us have attempted to capture the installation of this application at least a half a dozen times. It does not capture everything, but the install is so bizarre that we're unable to determine what's missing. I spoke with the vendor about a silent installation and was told that one is not available. My last resort was using AutoIt.
Answered 07/17/2009 by: Ron Duca
Senior Yellow Belt

Please log in to comment
0
It includes an installation of SQL Server Client ...which is comprised of a bunch of MSIs in the end. It would be much simpler to separate those out, install them as a pre-req, then capture the actual stuff you need.

Once you have an MSI, you would jump through the VBScab-patented "Did I get everything?" hoops:
- install your MSI
- use a lightweight snapshot tool e.g. InstallWatch to create a 'Before' snapshot
- remove any flags (registry or otehrwise) which the vendor install uses to determine its installed state (we want a new install , not a re-install/repair/fix)
- run the vendor install over the top of yours, ensuring you choose the same options as for your captured MSI
- take an 'After' snapshot
- add any relevant changes to your package.
Answered 07/20/2009 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity