Skip to main content

Command-line Parameters for Process Runner Setup

This topic describes the command-line parameters that system administrators can use while installing Process Runner. The command-line parameters are as follows:

  • /SILENT: Instructs the setup to be silent. When Setup is silent, the wizard and the background window are not displayed but the installation progress window is displayed. Everything else is normal. For example, error messages during installation are displayed and the start-up prompt, if you have not disabled it with DisableStartupPrompt or the /SP-command-line option.

    If a restart is necessary and the /NORESTART command is not used and Setup is silent, it displays a Reboot now? message.

  • /VERYSILENT: Instructs the setup to be very silent. When setup is very silent the wizard, the background window, and installation progress window are not displayed. Everything else is normal. For example, error messages during installation are displayed and the start-up prompt, if you have not disabled it with DisableStartupPrompt or the /SP- command-line option.

    If a restart is necessary and the /NORESTART command is not used and the setup is very silent, it reboots without asking.

  • /SUPPRESSMSGBOXES: Instructs the setup to suppress message boxes when used with /SILENTor /VERYSILENT. The default response in situations where there's a choice is:
    • Yes in a 'Keep newer file?' situation.
    • No in a 'File exists, confirm overwrite.' situation.
    • Abort in Abort/Retry situations.
    • Cancel in Retry/Cancel situations.
    • Yes (=continue) in a DiskSpaceWarning/DirExists/DirDoesntExist/NoUninstallWarning/ExitSetupMessage/ConfirmUninstall situation.
    • Yes (=restart) in a FinishedRestartMessage/UninstalledAndNeedsRestart situation.
  • The following five message boxes are not suppressible:
    • The About Setup message box.
    • The Exit Setup? message box.
    • The FileNotInDir2 message box displayed when the setup requires a new disk to be inserted and the disk was not found.
    • Any (error) message box displayed before setup (or Uninstall) could read the command-line parameters.
    • Any message box displayed by [Code] support function MsgBox.
  • /LOG: Causes Setup to create a log file in the user's TEMP directory detailing file installation and the Run actions taken during the installation process. This can be a helpful debugging aid. For example, if you suspect a file is not being replaced when you believe it should be, the log file tells you if the file was skipped, and why.

    The log file is created with a unique name based on the current date; it does not overwrite or append to existing files.

    The information contained in the log file is technical in nature, and therefore not intended to be understandable by end-users. Nor is it designed to be machine-parseable; the format of the file is subject to change without notice.

  • /LOG="filename": Same as /LOG, except that it allows you to specify a fixed path or file name to use for the log file. If a file with the specified name already exists, it is overwritten. If the file cannot be created, the setup aborts with an error message
  • /NOCANCEL: Prevents the user from canceling during the installation process, by disabling the Cancel button and ignoring clicks on the Close button. Useful with /SILENT or /VERYSILENT.
  • /NORESTART: Prevents the setup from restarting the system following a successful installation, or after a preparing to install failure that requests a restart. Typically used with /SILENT or /VERYSILENT.
  • /RESTARTEXITCODE=exit code: Specifies a custom exit code that the setup is to return when the system needs to be restarted following a successful installation. By default, 0 is returned in this case. Typically, used with /NORESTART.
  • /CLOSEAPPLICATIONS: Instructs the setup to close applications using files that must be updated by the setup if possible.
  • /NOCLOSEAPPLICATIONS: Prevents the setup from closing applications using files that need to be updated by the setup. If /CLOSEAPPLICATIONS was also used, this command-line parameter is ignored.
  • /RESTARTAPPLICATIONS: Instructs the setup to restart applications if possible. If the setup did not close these applications, for example, because /NOCLOSEAPPLICATIONS was used, this command-line parameter is ignored.
  • /NORESTARTAPPLICATIONS: Prevents the setup from restarting applications. If /RESTARTAPPLICATIONS was also used, this command-line parameter is ignored.
  • /DIR="x:\dirname": Overrides the default directory name displayed on the Select Destination Location wizard page. A fully-qualified path name must be specified. May include an expand: prefix that instructs the setup to expand any constants in the name. For example, DIR=expand:{pf}\My Program expands the constants in the name.
  • /GROUP="folder name": Overrides the default folder name displayed on the Select Start Menu Folder wizard page. May include an expand: prefix. If the [Setup] section directive DisableProgramGroupPage was set to yes, this command-line parameter is ignored.
  • /NOICONS: Instructs the setup to initially check the Don't create a Start Menu folder checkbox on the Select Start Menu Folder wizard page.
  • /TYPE="typename": Overrides the default type of the setup. There are two types of installation of Process Runner: Full Installation and Express Installation. Express Installation skips the installation of local sample Process files and offline video tutorials. If this parameter is not implemented, it proceeds with the Full Installation, which is the default type.
    • /TYPE=full: Leads to Full Installation of Process Runner.
    • /TYPE=exp: Leads to Express Installation of Process Runner.

Was this article helpful?

We're sorry to hear that.