Command Syntax

/NewPrerequisite <display_name>
                 -prereq_type {FileBased|UrlBased|OpenSite}
                 -prereq_path <prereq_path>
                 [-cmd_line <cmd_line>]
                 [-extract_folder <extract_folder>]
                 [-64bit]
                 [-lzma_compresion]
                 [-size <prereq_file_size>]
                 [-md5 <prereq_file_md5>]
                 [-target_os {Win9x|WinNT|Win64}]
                 [-force_install]
                 -search_type {FileVersion|RegSubKeyEnum|RegValue}
                 -search_path <search_path>
                 [-search_depth <search_depth>]
                 [-minversion <minimum_version>]
                 [-maxversion <maximum_version>]
                 [-aditionalfiles <aditional_files>]
                 [-builds <builds_list>]

This command will add a new prerequisite for your package. Its equivalent UI option is the [ New... ] button from Prerequisites page Prerequisite Software tab.

Parameters:

• <display_name>
• The name of the prerequisite. This string will be visible to the user.
• -prereq_type {FileBased|UrlBased|OpenSite}
• Where the setup file for the prerequisite is located.
• -prereq_path <prereq_path>
• The exact path or URL to the prerequisite setup file.
• [-cmd_line <cmd_line>]
• An optional command line for launching the prerequisite. This parameter cannot be used with "OpenSite" option.
• [-extract_folder <extract_folder>]
• The location where the prerequisite files will be extracted or downloaded. This parameter cannot be used with "OpenSite" option.
• [-64bit]
• Specify whether your prerequisite is on 64 bits.
• [-lzma_compresion]
• Specify LZMA Compression for your prerequisites files. To use this option your prerequisite files must be included in the EXE bootstrapper. This parameter can be used only with "FileBased" option.
• [-size <prereq_file_size>]
• The exact size of the prerequisite setup file. This parameter can be used only with "UrlBased" option.
• [-md5 <prereq_file_md5>]
• This field contains the MD5 "fingerprint" of the prerequisite file. This parameter can be used only with "UrlBased" option.
• [-target_os {Win9x|WinNT|Win64}]
• Which Operating System is required for this prerequisite to run. Don't specify this parameter if the prerequisite is for all type of OS.
• [-force_install]
• Will not allow installation of the product until the prerequisite is installed.
• -search_type {FileVersion|RegSubKeyEnum|RegValue}
• A value specifing how to obtain the installed prerequisite's version.
• -search_path <search_path>
• Path to a file or registry value from where to get the prerequisite version.
• [-search_depth <search_depth>]
• How deep to search for a file in the subdirectories. This parameter can be used only with "FileVersion" option.
• [-minversion <minimum_version>]
• The minimum version necessary for the installed prerequisite to be accepted.
• [-maxversion <maximum_version>]
• The minimum version necessary for the installed prerequisite to be accepted.
• [-aditionalfiles <aditional_files>]
• A list with additional files for your prerequisite. The files are separated by "|". If you have more than one file include this parameter into quotes. Those files need to by placed next to the file specified in the prereq_path parameter. This parameter can be used only with "FileBased" option.
• [-builds <builds_list>]
• A list of builds to which this prerequisite should be added. If no build is specified, the prerequisite will be added to all the defined builds.

Example:

AdvancedInstaller.com /edit MyProject.aip 
    /NewPrerequisite DirectX -prereq_type FileBased
    -prereq_path C:\Setup.exe -search_type RegValue 
    -search_path HKLM\Software\Microsoft\DirectX\Version
    -minversion 9.0 -aditionalfiles "file.txt|file1.txt"