1. You'd have to look at the MSI (open it with InstallShield or ORCA) to see what it's looking for. Very likely there is a Launch Condition (InstallShield calls them Install Conditions) that is testing for a property being set by the setup launcher. If so, you could set the property yourself on the command line, author the property into the Property Manager, or remove the Launch Condition.
2. When the MSI is running (say stopped on a dialog box), do a Start | Run... and type %temp% in the open box. Then sort the entries by date and start opening the folders with GUID names down the list from most recent to oldest until you find the MSI file.
Hi Thanks for the reply. I just have a simple MSI. I have opened the MSI using IS2008 but launch condition is empty. Is there any custom action that is running..
For (1), perhaps it's an InstallScript MSI package, which in InstallShield 2008 and earlier requires setup.exe?
(As an aside, InstallShield 2009 introduced InstallScript as an embedded UI handler, which means that InstallScript MSI packages can be launched from the MSI database.)
