Community Forums
Page 1 of 4 123 ... LastLast
Results 1 to 5 of 18

Thread: Silent install /r not recording

  1. #1
    Join Date
    Jan 2012
    Posts
    8

    Silent install /r not recording

    I am trying to built a ISS file to make a silent installation.

    My install is very simple - no custom dialog boxes.

    But when I do "setup /r" there is no ISS file recorded anywhere on the hard drive.

    I tried "setup /r /f1"C:\users\xxx\desktop\setup.iss" just in case this was a windows 7 security issue. Still no luck.

    Any ideas? Is this a limitation the express edition?

  2. #2
    Join Date
    Jan 2004
    Posts
    2,074
    The silent response file is applicable to InstallScript projects in the Premier and Professional editions of InstallShield. Express projects (or Basic MSI projects in the Premier or Professional editions) do not create or read response files.

    To run an Express installation silently, all you need to do is type the following at the command line:
    msiexec /i Product.msi /qn

    If your release settings include Setup.exe, you can run the following command:
    Setup.exe /s /v"/qn"

    I hope that helps.

  3. #3
    Join Date
    Jan 2012
    Posts
    8
    Thanks Debbie. They should put a table somewhere with the differences between products...

    My build is a single setup.exe

    The Setup.exe /s /v"/qn" command makes the windows cursor flash a little, but no install takes place. IS there a log file somewhere that can help tell me what is happening? Is there a flag or another setting in Installshield I need to set?

  4. #4
    Join Date
    Jan 2004
    Posts
    2,074
    To log the installation, use something like this at the command line:
    setup.exe /s /v"/l*v \"c:\My Log File.txt\" /qn"

    For more information on logging and the available command-line parameters, see the "Setup.exe" help topic in the InstallShield Express Help Library (available when you press F1 from within the InstallShield Express Edition). It's available in the Reference section of the help (Reference > Command-Line Tools > Setup.exe).

    I'm not sure where you found out about the response files for silent InstallScript installations, but it is not documented in the InstallShield Express Edition Help Library. That help system does have a help topic called "Upgrading to the Premier or Professional Editions of InstallShield"; it lists functionality that is not available in the Express edition, but is available in the Premier edition or is available in both the Premier and Professional editions. Although that help topic doesn't list silent response files specifically, it does list that InstallScript support is available only in the Premier and Professional editions.

    I hope that helps.
    Last edited by DebbieL; 01-06-2012 at 10:56 AM. Reason: Corrected the command line

  5. #5
    Join Date
    Jan 2012
    Posts
    8
    I cut&pasted that statement into my command line windows and I just get a dialog box that pops up labeled "windows installer" and this text.


    Windows ® Installer. V 5.0.7601.17514

    msiexec /Option <Required Parameter> [Optional Parameter]

    Install Options
    </package | /i> <Product.msi>
    Installs or configures a product
    /a <Product.msi>
    Administrative install - Installs a product on the network
    /j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
    Advertises a product - m to all users, u to current user
    </uninstall | /x> <Product.msi | ProductCode>
    Uninstalls the product
    Display Options
    /quiet
    Quiet mode, no user interaction
    /passive
    Unattended mode - progress bar only
    /q[n|b|r|f]
    Sets user interface level
    n - No UI
    b - Basic UI
    r - Reduced UI
    f - Full UI (default)
    /help
    Help information
    Restart Options
    /norestart
    Do not restart after the installation is complete
    /promptrestart
    Prompts the user for restart if necessary
    /forcerestart
    Always restart the computer after installation
    Logging Options
    /l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
    i - Status messages
    w - Nonfatal warnings
    e - All error messages
    a - Start up of actions
    r - Action-specific records
    u - User requests
    c - Initial UI parameters
    m - Out-of-memory or fatal exit information
    o - Out-of-disk-space messages
    p - Terminal properties
    v - Verbose output
    x - Extra debugging information
    + - Append to existing log file
    ! - Flush each line to the log
    * - Log all information, except for v and x options
    /log <LogFile>
    Equivalent of /l* <LogFile>
    Update Options
    /update <Update1.msp>[;Update2.msp]
    Applies update(s)
    /uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi | ProductCode>
    Remove update(s) for a product
    Repair Options
    /f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
    Repairs a product
    p - only if file is missing
    o - if file is missing or an older version is installed (default)
    e - if file is missing or an equal or older version is installed
    d - if file is missing or a different version is installed
    c - if file is missing or checksum does not match the calculated value
    a - forces all files to be reinstalled
    u - all required user-specific registry entries (default)
    m - all required computer-specific registry entries (default)
    s - all existing shortcuts (default)
    v - runs from source and recaches local package
    Setting Public Properties
    [PROPERTY=PropertyValue]

    Consult the Windows ® Installer SDK for additional documentation on the
    command line syntax.

    Copyright © Microsoft Corporation. All rights reserved.
    Portions of this software are based in part on the work of the Independent JPEG Group.

Page 1 of 4 123 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •