Software Deployment

You can't use the .iss file with a .msi file, as .iss is only for [:@]InstallShield[:@] MSI's.

You could attempt to use the InstallTailor utility, or search for the log file when installing the setup.exe (with .iss file). The log file should have the neccessary properties in it that you need to author into the MSI (or preferably a transform file).

Brent,

Firstly, thanks for your help.

This is an installshield supplied MSI. I've applied a transform to it. I need to know how I get my transformed package to pick up the setup.iss on install.

Is this even possible?

No, like I said; MSIs don't use .iss files.

.iss files are only for InstallShield, ie: when using in conjunction with an InstalShield setup.exe.

You basically need to convert the settings in your .iss file to a transform file. This can be no easy task. Thats why I suggested you to use InstallTailor.

Do you know of InstallTailor? I believe its an InstallShield utility, that allows you to run through your normal setup, and it will create a transform file for you.

Wich software you use to wrap your MSI.

I successfully did a wrapped MSI for firefox, with everything I wanted (silent install-uninstall, shortcut, profile, etc). Wrapped MSI are very usefull if you compare them to repackaged MSI.

I might help you but I need to know what you are using.

I've tried WIWW and ScriptLogic (formely Masai) and ScriptLogic is way much easier.

Good luck

I'm trying to do install a wrapped MSI. The setup.exe that runs this file installs extra features which I'm trying to include in my package. Also, there are no dialogs in the MSI (all in the setup.exe install) so I can't use a response transform or InstallTailor!

Here is a tool to extract the content of a MSI

http://blogs.pingpoet.com/overflow/archive/2005/06/02/2449.aspx

Hi RichardRS,

Here are the two ways I think to extract the wrapped MSI if you don't want to use any tool.

1. Go to Run and type the name and path of your setup.exe. Example: C:\setup.exe /a
When the option for the location, choose your convenient path. This will extract the files in the wrapped MSI.

1.A. After that, you should be able to see the MSI extension which you will be used to create your TRANSFORMS file. You can use Install Tailor (I think from WIse) or ORK Tools' Custom Installation Wizard or other same tools.

You command line should be like this after you have created your MST:
C:\setup.exe /s /v"TRANSFORMS={PATH AND NAME OF MST} /QB"

2. Run your setup.exe file and when the Welcome dialog appears, check out the folder under C:\WINDOWS\Installer for your MSI file. If it's not there, you can do a search for MSI extensions. Follow step 1.A for the next steps.

Let us know if you need help again..

send me beers then! [:)]

ORIGINAL: dj_xest

Hi RichardRS,

Here are the two ways I think to extract the wrapped MSI if you don't want to use any tool.

1. Go to Run and type the name and path of your setup.exe. Example: C:\setup.exe /a
When the option for the location, choose your convenient path. This will extract the files in the wrapped MSI.

1.A. After that, you should be able to see the MSI extension which you will be used to create your TRANSFORMS file. You can use Install Tailor (I think from WIse) or ORK Tools' Custom Installation Wizard or other same tools.

You command line should be like this after you have created your MST:
C:\setup.exe /s /v"TRANSFORMS={PATH AND NAME OF MST} /QB"

2. Run your setup.exe file and when the Welcome dialog appears, check out the folder under C:\WINDOWS\Installer for your MSI file. If it's not there, you can do a search for MSI extensions. Follow step 1.A for the next steps.


an addendum to point 2: in my environment, the msi file is usually extracted to a new folder in C:\WINDOWS\TEMP\ The new folder is usually named something like "_is###".

If you have the ISS file already why can't you run "setup.exe /s /f1[path to iss]"? I would think the ISS file would make the MST unnecessary. Of course I don't know the specifics of the program, or how it is being installed so I could be wrong.