Install Shield Command Line Parameters
If You're using a Software Deployment System (Softwareverteilung
- Wikipedia) like Microsoft SMS, Enteo NetInstall, Matrix 42 Empirum Pro,
Baramundi, Managesoft etc.. You run sometimes in trouble using correct
commandline parameters.
Here is some help to make Your life easier
- to create Responsefile:
setup.exe -r
(setup.iss will be created under <windowsFolder>\setup.iss)
- to run Silent Installation:
setup.exe -f1c:\temp\setup.iss -s
|
Parameter
|
Description
|
|
-d
|
Runs setup in debug mode. The -d switch
also includes a <pathonly> option for specifying the path of the
Setup.rul file. For more information, refer to the Visual Debugger help
file.
|
|
-f<path\CompiledScript>
|
Specifies an alternate compiled script.
Unless the compiled script (.ins file) also resides in the same
directory as that of Setup.exe, the full path to the compiled script
must be specified. _setup.dll must also reside in the same directory as
your .ins file. For example, setup -ftest.ins will launch setup using
Test.ins instead of Setup.ins.
|
|
-f1<path\ResponseFile>
|
Specifies an alternate location and name
of the response file (.iss file). If this option is used when running
InstallShield Silent, the response file is read from the folder/file
specified by<path\ResponseFile>. If this option is used along with
the -r option, the response file is written to the folder/file specified
by<path\ResponseFile>. If an alternate compiled script is
specified using the -f switch, the -f1 switch entry must follow the -f
switch entry.
|
|
-f2<path\LogFile>
|
Specifies an alternate location and name
of the log file created by InstallShield Silent. By default, Setup.log
log file is created and stored in the same directory as that of
Setup.ins. If an alternate compiled script is specified using the -f
switch, the -f2 switch entry must follow the -f switch entry.
|
|
-m<filename>
|
Causes Setup.exe to generate a Management
Information Format (.mif) file automatically at the end of the setup. Do
not include a path - the .mif file is always placed in the Windows
folder. <filename> is optional. If you do not specify a filename,
the resulting file will be called Status.mif.
|
|
-m1<serial number>
|
Tells setup to place the indicated serial
number in the created .mif file.
|
|
-m2<locale string>
|
Tells setup to place the indicated locale
in the .mif file. English (ENU) is the default; refer to Microsoft
documentation for a complete listing of locale strings.
|
|
-r
|
Causes Setup.exe automatically to
generate a silent setup file (.iss file), which is a record of the setup
input, in the Windows folder.
|
|
-s
|
Runs InstallShield Silent to execute a
silent setup.
|
|
-SMS
|
Prevents a network connection and
Setup.exe from closing before the setup is complete. This switch works
with setups originating from a Windows NT server over a network. Please
note that SMS must be uppercase; this is a case-sensitive switch.
|
|
-z
|
Prevents Setup.exe from checking the
available memory during initialization. This switch is necessary when
running a setup on a machine with more than 256 MB of memory; if it is
not used, Setup.exe reports insufficient memory and exits.
|
Installshield Setup.log [ResponseResult]
Using
"Silent Installation" with InstallShield there is only one chance to
analyze the reason for cancelling an Installation.
Locate
the File setup.log, usually in <WindowsFolder>, jump to the
Paragraph [ResponseResult]
ResultCode
contains a Value
| 0 |
Success |
| -1 |
General error |
| -2 |
Invalid mode |
| -3 |
Required data not found in
setup.iss |
| -4 |
Not enough memory available |
| -5 |
File does not exist (setup.iss
-- try -f1.\setup.iss ) |
| -6 |
Cannot write to the response
file |
| -7 |
Unable to 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 |
Dialogs are out of order
(Version prior 6, evtl. it is -3)) |
| -51 |
Cannot create the specified
folder |
| -52 |
Cannot access the specified file
or folder |
| -53 |
Invalid option selected |
| |
|
Selbstextrahierende
Installshield Setups (Package for the Web) können entweder ausgepackt werden
oder über den zusätzlichen Schalter /a automatisiert werden.
Nach
dem Schalter /a folgen die Befehle, die an das ausgepackte Setup übergeben
werden. Hier ist das Auffinden der Setup.iss am kritischsten, da z.B. bei der
Angabe /f1.\setup.iss die setup.iss-Datei im Pfad der ausgepackten Setup-Dateien
gesucht werden würde und nicht im Verzeichnis, in dem sich das gepackte Setup
befindet. Eine Angabe eines absoluten Pfads ist hier unumgänglich, z.B
setup.iss nach %Temp kopieren.
InstallShield IDriver.exe Commandline Parameters
to uninstall a Installshield Product via Idriver.exe there
are two ways to handle:
Make the simple way to silent uninstall InstallShield package
go to Your Registry Uninst Section
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\InstallShield
Uninstall Info\{YOUR_GUID}
--> look which GUID is Your package..
go one branch up
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\[InstallShiels_]{YOUR_GUID}
-- locate the GUID
Get the Value of the "UninstallString" (....\IDriver.exe
/M{YOUR_GUID})
append to that Value /uninst --> \IDriver.exe
/M{YOUR_GUID} /uninst
| 
