MAKEMSI quickly and reliably creates MSI files in a non-programmatic way\Building or Updating MSIsRepackaging - Converting an EXE to MSIWrap Existing InstallersInstallShieldInstallShield Version 7.00

---

InstallShield Version 7.00

• To capture install or uninstall ".ISS" files use the "/r" option. It created a file called "setup.iss" in "c:\winnt" (on my syetem) which records the dialogs and actions you performed.

• To invoke the "I sometimes do it successfully silently" (if I feel like it) option use the "/s" switch.

• The exact order of switches is critical, experiment if it fails...

• Supply name of the ISS file in the format: /f1"C:\some Place\Install.ISS" ("normal" quoting will cause failure).

• The return code from "setup.exe" is meaningless.

• There is no log as such (so no details about any failure). There is a "/verbose" switch which does nothing!

• The one piece of information that is available is a return code produced in "setup.log" (default name). Override the "log" filename with the "/f2" switch and I suggest supplying this as part of the 3rd parameter of the VbsCaRunSync() routine when used.

  Common errors are:

  • 0 - Success.
  • -1 - General error.
  • -2 - Invalid mode.

  • -3 - Required data not found in the Setup.iss file.
    This can occur if InstallShield wants to display a dialog that didn't display during capture (with "/r" switch). To diagnose, run manually on failing box with "/r" switch and use "WinMerge.EXE" to compare response files.

  • -4 - Not enough memory available.
  • -5 - File does not exist.
  • -6 - Cannot write to the response file.
  • -7 - Cannot write to the log file.
  • -8 - Invalid path to the InstallShield Silent response file.
  • -9 - Not a valid list type (string or number).
  • -10 - Data type is invalid.
  • -11 - Unknown error during setup.

  • -12 - Dialog boxes are out of order.
    Apparently this can also occur if a new dialog wants to popup (see -3 for help diagnosing).

  • -51 - Cannot create the specified folder.
  • -52 - Cannot access the specified file or folder.
  • -53 - Invalid option selected.

  • NONE - IT HANGS - Not Uncommon (thanks for nothing IS)...
    I recommend that all wrapped installs use "RunProcess.EXE" with a timeout and handle this error appropriately. Be sure to watch with "PROCESS EXPLORER" to ensure all tasks cleaned up or you will need to use a tool like "PV.EXE" to terminate the rest. You should probably change the ".iss" response file to generate a hang to test how your installer handles it.

    To diagnose hangs start "PROCESS EXPLORER" and sort by "Startup Time" (adding this column if required). Have a look at the process you started plus any child processes and right click on these and choose the "WindowBring to Front" option. This will hopefully make a dialog visible.

    If a file is missing from the image (perhaps you are trying to limit the size of the image) you will probably get a "Setup needs next disk" dialog.

    The funny things about an unexplained hang, I've never seen one that didn't go away on a retry or after a reboot!

• The "setup.exe" program will spawn another copy of "setup.exe". To clear a hang, I don't feel comfortable killing a process with such a "generic" name, however I have noticed that if I rename the "setup.exe" to "DistinctiveName-Setup.exe" the secondary process also has the same name and so can be safely killed without the small risk that you are killing some other "setup.exe" task! As "RunProcess.exe only terminates the first copy on timeout you need to follow up by terminating any other copies with "PV.EXE".

EXAMPLE

;----------------------------------------------------------------------------
;--- "SETUP-I.ISS" points here! ---------------------------------------------
;----------------------------------------------------------------------------
<$DirectoryTree Key="PRODUCTDIR" Dir="c:\Program Files\WrappedProducGoesHere">


;----------------------------------------------------------------------------
;--- Install the CD-IMAGE here ----------------------------------------------
;----------------------------------------------------------------------------
<$DirectoryTree Key="INSTALLDIR" Dir="[PRODUCTDIR]\MsiSource (wrapper)" CHANGE="\">


;----------------------------------------------------------------------------
;--- Set up the response file created with "setup.exe /r" (created in "c:\winnt" dir) ---
;----------------------------------------------------------------------------
#(
    #define AddResponseFile
    <$File Source="{$ISS}" Destination="[INSTALLDIR]\{$ISS}" Comment=^Response file for {$FOR} (renamed "setup.iss" file). Generated by manual {$FOR} of product using "setup.exe /r".^>
    <$SourceFile FileName="{$ISS}" HTML="Y">
#)
<$AddResponseFile ISS="setup-I.iss"  FOR="installation">
<$AddResponseFile ISS="setup-UI.iss" FOR="uninstallation">


;----------------------------------------------------------------------------
;--- Install InstallShield based Installer ----------------------------------
;----------------------------------------------------------------------------
#(
    <$WrapInstall
        ;--- Where is the CD Image? -----------------------------------------
        CdImage=".\CD-IMAGE"

        ;--- INSTALL --------------------------------------------------------
         EXE="[INSTALLDIR]setup.exe"
        Args='/s /f1"[INSTALLDIR]setup-I.iss" /f2"[INSTALLDIR]setup-I-<$ProductVersion>.log"'

        ;--- UNINSTALL ------------------------------------------------------
         UninstallExe="[INSTALLDIR]setup.exe"
        UninstallArgs='/s /f1"[INSTALLDIR]setup-UI.iss" /f2"[INSTALLDIR]setup-UI-<$ProductVersion>.log"'

        ;--- VALIDATION -----------------------------------------------------
        UninstallKey="{149511F11-4375-4557-5541-8F9217A15480}"
    >
#)

Please email me any feedback, additional information or corrections. See this page online (look for updates) MAKEMSI© is (C)opyright Dennis Bareis 2003-2008 (All rights reserved). Saturday December 27 2008 at 3:15pm Visit MAKEMSI's Home Page