I have a Medical Application by McKessen. It uses Install Shield. It uses Setup.exe which installs a lot of files in C:\WinNt\Profiles\Username\LocalFiles\Temp (the usual place) for use during the install. However the MSI etc, is not one of them. This is called from the original location. I need to have the items that Setup.exe run as well as the MSI. The MSI will not run if these items are not installed. Manually installing the ISSsript.MSI has no bearing. How do I get a transform of the MSI when it will not install unless the item from the EXE are done first? I deed to capture the things done by Setup.exe as well as create a transform for the MSI. Is there a way to still create a transform for the MSI when SETTUP.exe is executed? My packaging tool is WISE 5.5 and or 5.1 I am wondering if the solution lies with the Setup.ini but do not know where to start.

Thank You.

Jim wiser
Jim_wiser@cdh.org
630-933-4737
0 Comments   [ + ] Show Comments

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.

Answers

0
This link might be useful?

http://documentation.installshield.com/robo/projects/helplib/IHelpSetup_EXECmdLine.htm

You might be able to create an unattended install using the "/r" option, and then specify the name of your transform in the "iss" file.

Otherwise, you might be able to pass the name of the transform to the "setup.exe" using the "TRANSFORMS" property on the command line (/v"TRANSFORMS=mytransform.mst").
Answered 02/17/2005 by: WiseUser
Fourth Degree Brown Belt

Please log in to comment
0
The problem I am having is I can not get the MSI to run so I can make an MST. It will not run outside of the context of the SETUP.exe. My Tool for creating a MST is WISE install Tailor. It needs a MSI to run to creat the MST. Any suggetions?
Answered 02/17/2005 by: wiser
Senior Yellow Belt

Please log in to comment
0
You may be able to determine the command line passed to the MSI by the setup.exe using one of the following methods:

1) Switch on logging through the registry, and check the log file in the %temp% folder.

2) Using the SysInternals Process Explorer:

http://www.sysinternals.com/ntw2k/freeware/procexp.shtml

This tool allows you to check the command line used to launch an application - you can check the main "Msiexec.exe" process.
Answered 02/17/2005 by: WiseUser
Fourth Degree Brown Belt

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