GabrielBarbu wrote:Hello,
If the packages you are trying to install are .msi's then you could look into using
Chained Packages. Otherwise the only way to conditionally launch the installers would be during InstallFinalize by using a "Launch File or Open URL" or an "Attached Custom Action". This is because two msi based installs can not run at the same time.
Regards,
Gabriel
Hi,
Maybe I'm not doing something right.
I made the acrobat setup a prerequisite and it works fine, I think.
The other is an Install Shield setup with an ini file and compiled script.
It is a set of drivers for a piece of USB hardware that my app needs. It's provided by a third party.
I added all of these files to my Application Folder. (Which is actually a nice feature in case the user has to rerun the driver setup.)
However, when I use the "Launch File or Open URL" action it doesn't run. I spent a couple hours trying to figure out why and only came up with the action was returning a "1".
But I recalled that earlier I was able to run a .bat file so I poked around and tried to remeber how I did that. What I came up with was the "EXE with working directory". That action is able to launch the setup.exe for the drivers and it seems to run ok. The path is [#setup.exe] and I have this as my expression: (&Drivers = 3) AND NOT (!Drivers = 3) Everything else is default.
Is that how I want to do this?
This all (not only this piece but the whole setup, it's only copying files to certain places and running a couple third party packages.) seems like it should be so simple. I'm amazed that it has taken so long to get working. Might have been easier, but not so elegant, to use a .bat file.
Gary