Good Moring guru's.
I am currently trying to package an installshield bootstrap compressed exe. I can run a setup.exe /b to extract the compressed MSI file with a setup.ini and a setup.isn and a 0x0409.ini. If I run setup.exe /a I get an uncompressed MSI(which doesn't work. I get error 2920). The compressed MSI will install if I add the property ISSETUPDRIVEN=2 but there are no shortcuts, user dialogs, or configuration properties (licesnse info) installed. I have a process monitor that shows me what processes are called with what switches during the install but that doesn't help because there are no useful switches displayed. I need to know how to get the licesnse server setup into the MSI.

I know you are never suppose to capture an MSI, so what if I install the MSI first then run setup capture with WISE, and then run setup.exe. Will the setup capture do what I need it to do, and not capture any MSI changes?

Also I perfer to have my install work under one MSI, but as a worst case senario I can use the install shield exe to create a setup.iss file and use setup.exe /s to install my package. Does anyone know what the downsides might be to using the setup.exe /s with the setup.iss instead of compling the whole thing into one MSI?

Any help is sincerely appreciated!
0 Comments   [ + ] Show 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.


Hi kj,
what app are we talking about here?
With some versions of Installshield, you see all kinds of crippled MSI's (like early versions of Quicktime7 or CorelDraw9 and others).
Biggest advantage of an MSI over the other setup formats is IMHO its changeability with properties, transforms etc.
Another one is, that it is embedded into the system and it runs in system context, no need for extra accounts and stuff.
Regards, Nick
Answered 09/04/2007 by: nheim
Tenth Degree Black Belt

Please log in to comment
First enable verbose logging using policy or the command line.
Execute the setup.exe then search in the log file for "command line" to see what parameters (public properties) the setup.exe passes to the MSI. You then need to investigate what more you have to do, like setting other properties fromout any dialog changes while running this setup.exe.
Answered 09/04/2007 by: AngelD
Red Belt

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