Setup.iss incomplete
Hello all,
I have a vendor supplied Setup.exe that calls multiple child installations, several of which are MSI's.
When I attempt to generate the setup.iss file, the .iss file is created and is only populated with half of the dialog information needed. No other processes are kicked off that I can see in the Task Manager/Processes view. I've also monitored using ProcMon and the original Setup.exe is the only install running.
Here's a sample from the .iss file:
[{FBC51784-0430-4D7B-BCE5-22A0D5D0A290}-DlgOrder]
Dlg0={FBC51784-0430-4D7B-BCE5-22A0D5D0A290}-SdLicenseRtf-0
Count=10
Dlg1={FBC51784-0430-4D7B-BCE5-22A0D5D0A290}-SdWelcome-0
Dlg2={FBC51784-0430-4D7B-BCE5-22A0D5D0A290}-AskOptions-0
Dlg3={FBC51784-0430-4D7B-BCE5-22A0D5D0A290}-AskYesNo-0
Dlg4={FBC51784-0430-4D7B-BCE5-22A0D5D0A290}-AskYesNo-1
Dlg5={FBC51784-0430-4D7B-BCE5-22A0D5D0A290}-SdAskDestPath-0
Dlg6={FBC51784-0430-4D7B-BCE5-22A0D5D0A290}-SdShowDlgEdit1-0
Dlg7={FBC51784-0430-4D7B-BCE5-22A0D5D0A290}-SetupType-0
Dlg8={FBC51784-0430-4D7B-BCE5-22A0D5D0A290}-SdSelectFolder-0
Dlg9={FBC51784-0430-4D7B-BCE5-22A0D5D0A290}-SdFinish-0
There are an additional five forms that require user input.
Interestingly enough...the product code listed above, {FBC51784-0430-4D7B-BCE5-22A0D5D0A290}, is the product code for one of the child MSI's.
There is no Dialog information that I can find in the MSI. I grabbed the MSI from the %temp% directory and attempted to generate a transform. However, when running the MSI no dialogs are presented.
Any ideas or direction would be greatly appreciated!
I have a vendor supplied Setup.exe that calls multiple child installations, several of which are MSI's.
When I attempt to generate the setup.iss file, the .iss file is created and is only populated with half of the dialog information needed. No other processes are kicked off that I can see in the Task Manager/Processes view. I've also monitored using ProcMon and the original Setup.exe is the only install running.
Here's a sample from the .iss file:
[{FBC51784-0430-4D7B-BCE5-22A0D5D0A290}-DlgOrder]
Dlg0={FBC51784-0430-4D7B-BCE5-22A0D5D0A290}-SdLicenseRtf-0
Count=10
Dlg1={FBC51784-0430-4D7B-BCE5-22A0D5D0A290}-SdWelcome-0
Dlg2={FBC51784-0430-4D7B-BCE5-22A0D5D0A290}-AskOptions-0
Dlg3={FBC51784-0430-4D7B-BCE5-22A0D5D0A290}-AskYesNo-0
Dlg4={FBC51784-0430-4D7B-BCE5-22A0D5D0A290}-AskYesNo-1
Dlg5={FBC51784-0430-4D7B-BCE5-22A0D5D0A290}-SdAskDestPath-0
Dlg6={FBC51784-0430-4D7B-BCE5-22A0D5D0A290}-SdShowDlgEdit1-0
Dlg7={FBC51784-0430-4D7B-BCE5-22A0D5D0A290}-SetupType-0
Dlg8={FBC51784-0430-4D7B-BCE5-22A0D5D0A290}-SdSelectFolder-0
Dlg9={FBC51784-0430-4D7B-BCE5-22A0D5D0A290}-SdFinish-0
There are an additional five forms that require user input.
Interestingly enough...the product code listed above, {FBC51784-0430-4D7B-BCE5-22A0D5D0A290}, is the product code for one of the child MSI's.
There is no Dialog information that I can find in the MSI. I grabbed the MSI from the %temp% directory and attempted to generate a transform. However, when running the MSI no dialogs are presented.
Any ideas or direction would be greatly appreciated!
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
dunnpy
13 years ago
It would to be prudent to enable MSI Logging in the registry to see how the extracted MSI files are being run.
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer
Reg_SZ: Logging
Value: voicewarmup
You'll find any log files in %Temp% with MSIxxxx.log file name.
I suspect that the setup.exe is building a commandline, based on your installation choices, that is then being passed to the MSI files for the installation. This would explain the lack of dialogues too.
Once you have identified which MSI files are run, and the commandlines from the logs, you can create an MST for each one to configure the installation.
Then you need to identify if the setup.exe is actually performing any installation actions, but just a stub for calling the MSI files.
Use your favourite light-weight snapshot tool (InControl, InstallRite, PictureTaker, et al) to capture a setup.exe installation and then just the MSI files installation and compare the two.
If setup.exe does perform some configuration you could either create a new MSI for this config, or incorporate into the MST of one of the other MSI files.
Hope that helps,
Dunnpy
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer
Reg_SZ: Logging
Value: voicewarmup
You'll find any log files in %Temp% with MSIxxxx.log file name.
I suspect that the setup.exe is building a commandline, based on your installation choices, that is then being passed to the MSI files for the installation. This would explain the lack of dialogues too.
Once you have identified which MSI files are run, and the commandlines from the logs, you can create an MST for each one to configure the installation.
Then you need to identify if the setup.exe is actually performing any installation actions, but just a stub for calling the MSI files.
Use your favourite light-weight snapshot tool (InControl, InstallRite, PictureTaker, et al) to capture a setup.exe installation and then just the MSI files installation and compare the two.
If setup.exe does perform some configuration you could either create a new MSI for this config, or incorporate into the MST of one of the other MSI files.
Hope that helps,
Dunnpy
Posted by:
jmaclaurin
13 years ago
ORIGINAL: dunnpy
If setup.exe does perform some configuration you could either create a new MSI for this config, or incorporate into the MST of one of the other MSI files.
Other things to watch for are if the MSI's are configured to be run silent by being called specifically from the setup.exe, the MSI's are configured to not be editable (as in create an MST), and/or the MSI's will not permit them being called without the setup.exe (sounds like the first, but slightly different). I came across an installer that would not permit any type of direct intereaction either with the MSI's or the setup.exe unless called from a silent.bat file, and it had to be called silent.bat and had to be called from the same folder structure as the setup.exe.
And worse case, contact the vendor and see what they have to say about a silent install.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.