folks what is a good practice of issue resolution when you get a vendor msi that does not accept a transform, usuallly these msi's have no dialogs either.
i assume a recapture of the vendor msi is the last resort but usually the only option.
any ideas, opinion??
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
What are you using to transform? Sometimes Wise cannot transform InstallShield MSIs.
Answered 01/10/2006 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
0
good point, mainly wise, if your statement arises how do you proceed, create the mst with IS not doubt, what if that does not work.
Answered 01/10/2006 by: misk
Orange Senior Belt

Please log in to comment
0
This is true, i have had some applications who did not take the MST file from WISE because of the InstallShield Nature.
When the MST is created with the InstallShield Tuner is probably will work Correctly.

Regards,

The Packeteer
Answered 01/11/2006 by: The Packeteer
Senior Yellow Belt

Please log in to comment
1
When I run into issues creating a transform from a vendor tool it is always easy to follow the steps below:

Download and install the MSI SDK
Locate the MSITRAN exe file and add to your path statement
Make a copy of the existing MSI file, rename to T_filename.msi
Edit the T_filename.msi to add all your changes using your favorite editor (ORCA, Wise, InstallShield)
On the command line type MSITRAN /g filename.msi T_filename.msi transformname.mst, putting in the correct paths where necessary.

This should create a perfectly useable transform.
Answered 01/11/2006 by: TomB
Orange Belt

Please log in to comment
0
very clever indeed. cheers TomB. does msitran always work? can the created transforms be applied without hassle, even if the msi has no dialogs?
Answered 01/11/2006 by: misk
Orange Senior Belt

Please log in to comment
0
Yes using MSITRAN.EXE as Tom suggests will always create an MST based on the differences between 2 MSI files (it's -g not /g though)

You can then verify your MST by applying it to the original base MSI in Orca to verify the changes and ensure you haven't introduced and new validation errors.

You should always be able to apply the MST to your install via MSIEXEC command line - if you are running setup.exe though you may have problems unless is supports passing switches to MSIEXEC - e.g. /V is the standard one for InstallShield. I hate InstallShield setups [:'(]

Cheers,
Rob.
Answered 01/11/2006 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
ORIGINAL: MSIPackager
I hate InstallShield setups [:'(]


Yeah, me too. And I'm an IS user. Go figure. [X(]

Luckily, if setup.exe is a simple launcher for a "Basic MSI Project", you can usually just extract the MSI, and then throw the garbage out.
Answered 01/11/2006 by: williamp
Orange Belt

Please log in to comment
0
Do you see any specific errors when you enable logging during the install?
Answered 01/12/2006 by: xythex
Orange Senior Belt

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