Silent Installation and uniinstaller Common Characteristics

Silent installation and uniinstaller command are based on the same three steps:

  1. Checking the content of the response file: the procedure checks if all dialogs exist with a response value (but the value is not checked at this stage).
    This step is recorded in the InstallShield silent log file (default name setup.log, iss_setup.log when launched by uniinstaller). At the end of this step, the ResultCode is written and the file is closed.
    Example of the InstallShield silent log file:

    [InstallShield Silent]

    Version=v7.00

    File=Log File

    [ResponseResult]

    ResultCode=0

    If this check is successful then the ResultCode is 0 and the next step will begin. If a dialog or a value is missing, the procedure aborts with a ResultCode -3.

    In the above two cases, a report file is created that contains the record of successful dialogs.

    Other ResultCode values are generally system problems: setup is not launched and the report file is not created.

  2. Checking the values: before installing the product, the procedure checks if all values are correct. If an invalid value is detected (bad syntax, already existing directory …), the procedure aborts and the report file (%TEMP%\DUAS_6_ISS_installation.log) contains the detailed error.

  3. Installing the software: if no error is detected, the installation begins. If the installation fails for any reason, the report file contains the detailed error.

Possible ResultCode values are listed below:

In case of a -3 or 0 ResultCode, the report file (%TEMP%\DUAS_6_ISS_installation.log) is created.

As of version 6.10.41, documentation new updates are posted on the Broadcom Techdocs Portal.
Look for Dollar Universe.