MSI with InstallShield Dependencies
Some newbie questions with regards an MSI application that I believe was developed using InstallShield.
A number of questions/problems, I'm after some guidance on my approach and some pointers to a good reference before I start trawling the InstallShield site for a novice guide:
The application has a Setup.exe and Setup.ini, the application complains if launched using the MSI, needs to be run from Setup.exe. I presume the Setup.exe is a standard as can be generated by WPS. Checked the Setup.ini and it has references to the application MSI and the InstallShield Scripting Engine MSI (ISSCRIPT).
I'd be grateful for any tips/guidance, many thanks!
A number of questions/problems, I'm after some guidance on my approach and some pointers to a good reference before I start trawling the InstallShield site for a novice guide:
The application has a Setup.exe and Setup.ini, the application complains if launched using the MSI, needs to be run from Setup.exe. I presume the Setup.exe is a standard as can be generated by WPS. Checked the Setup.ini and it has references to the application MSI and the InstallShield Scripting Engine MSI (ISSCRIPT).
- So my approach was to ensure any dependent components were separate and delivered appropriately; MDAC, ISSCRIPT and dongle driver MSI's (pre-reqs).
- Then I wanted to create an MST in order to reference any changes but I couldn't because it complains about being run from Setup.exe in WPS InstallTailor. However it was OK using ORCA so I decided to use that.
- Then I added the ISSCRIPTDRIVEN property and removed the CA for the OnCheckSilentInstall as recommended, to remove the Setup.exe dependence.
- The application now appears to install and will run however some critical components are missing as parts of the application are missing (not available) - parts that are available using the install launched via Setup.exe. I'm assuming the setup.exe is doing something/setting some properties which I'm not aware of but I'm not sure how to track or debug this.
- I've noticed that a). the application is littered with InstallScript CA's but I don't really understand what each one does or how the sequence works. b). If I open the project in WPS I can only small portion of the files/etc. in the Installation Expert & Table views, however the remainder are available through the feature/component views?. However if I open the project in an AdminStudio demo I can see the entire contents through their GUI view?
I'd be grateful for any tips/guidance, many thanks!
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
viswakar
18 years ago
Hi ,
I believe the vendor MSI is installing less features compared to the setup.exe. I suggest you to check the INSTALLLEVEL property value set in the msi. if it is more than the value given in the feature table then that particular feature wont get installed. Try installing the msi and setup.exe with the log, Do a comparison of those logs..Check for the property INSTALLLEVEL !!
Cheers..
I believe the vendor MSI is installing less features compared to the setup.exe. I suggest you to check the INSTALLLEVEL property value set in the msi. if it is more than the value given in the feature table then that particular feature wont get installed. Try installing the msi and setup.exe with the log, Do a comparison of those logs..Check for the property INSTALLLEVEL !!
Cheers..
Posted by:
aogilmor
18 years ago
hi, i think your approach is basically sound - make sure all components are in place, install isscript separately, etc. But sometimes, as you've seen, these installshield installations can be very stubborn. it's almost as if the authors are trying to thwart your attempts to silence the installations. Here are a a couple of things I've gotten to work:
* Try it with ALL of the media and files are in place. Sometimes the MSI will look outside its parent directory, if it comes stored on a CD.
* Just edit the INI and run setup.exe /s /v/qn (or something similar). You can create a wrapper or some other script to move the files and shortcuts the way you like. The bad thing about this is you can't use a transform.
Good luck!
* Try it with ALL of the media and files are in place. Sometimes the MSI will look outside its parent directory, if it comes stored on a CD.
* Just edit the INI and run setup.exe /s /v/qn (or something similar). You can create a wrapper or some other script to move the files and shortcuts the way you like. The bad thing about this is you can't use a transform.
Good luck!
Posted by:
kkaminsk
18 years ago
One thing I also suggest is when running the setup using setup.exe make sure to turn on MSI logging so you can see all the properties that Setup.exe is passing the MSI. Sometimes you can find some really useful information there.
Posted by:
aogilmor
18 years ago
Hi kkaminsk, is it possible to turn on verbose logging for ALL msi's at the system level? I had a case where this would have been useful but the eXE didn't have a way to expressly turn on logging. it just didn't recognize any kind of windows installer command line input. TIA, O.G.
Posted by:
kkaminsk
18 years ago
I'll grab my memory key for work tomorrow and post the reg hack I use but here is where you can set the logging system wide with MSIEXEC.
http://www.winguides.com/registry/display.php/1127/
The logs will be written to %TEMP% but my reg hack also has something special for InstallShield Script logging too. I happened to come accross the InstallShield script logging when I had an application that would not uninstall when Altiris called the uninstall.
http://www.winguides.com/registry/display.php/1127/
The logs will be written to %TEMP% but my reg hack also has something special for InstallShield Script logging too. I happened to come accross the InstallShield script logging when I had an application that would not uninstall when Altiris called the uninstall.
Posted by:
kkaminsk
18 years ago
Here it is!
REGEDIT4
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer]
"Logging"="viwearucmo"
"Debug"=dword:7
[HKEY_CURRENT_USER\Software\InstallShield\ISWI\3.0\SetupExeLog]
"VerboseLogFileName"="C:\\is.log"
This is the best documentation I could Google up on the InstallShield logging.
http://installsite.org/pages/en/msifaq/a/1022.htm
REGEDIT4
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer]
"Logging"="viwearucmo"
"Debug"=dword:7
[HKEY_CURRENT_USER\Software\InstallShield\ISWI\3.0\SetupExeLog]
"VerboseLogFileName"="C:\\is.log"
This is the best documentation I could Google up on the InstallShield logging.
http://installsite.org/pages/en/msifaq/a/1022.htm
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.