Insofar as watching Windows Explorer would reveal, I see no evidence of the Setup.inx file being created. I suspected some kind of Windows file protection problem, but peculiarly, the larger tree in which this problem occurs has uniform protections, and I can make other installers within other parts of the tree without any difficulty.
InstallShield 2015
Project: This information applies to the following project types:
| • | Basic MSI |
| • | InstallScript |
| • | InstallScript MSI |
Summary Failed to extract file setup.inx. Error = 0 Intermittent errors known to occur with a Basic msi using a.rul file for custom actions Symptoms. The run-time behavior for InstallShield 12 and later InstallScript MSI projects is much different than the behavior for InstallShield 11.5 and earlier because of some architecture enhancements. For more information about the enhancements, see Upgrading Projects from InstallShield 11.5 or Earlier. InstallShield Command-Line Parameters. InstallShield uses setup.exe as the bootstrap loader to call the Microsoft Windows Installer service. Setup.exe can accept command-line parameters that allow you to perform administrative installations, run silent installations, and complete other administrative tasks. Setup.inx is the compiled file; replace the one built by InstallShield. Run built installer setup.exe with /d flag on remote machine: setup /d When prompting for the script folder, locate to My Project Script Files folder which contains.rul and.h files. The.ism project file and other files are not needed at all. Keyboard Shortcuts of.
| • | InstallScript Object |
| • | Merge Module |
If you want to pass numerous parameters during a command-line build, or if you consistently pass the same parameters, it might be convenient to use an .ini file. The following statement illustrates running ISCmdBld.exe to build a release with parameters as specified in the MySetup.ini file.
ISCmdBld.exe -i 'C:InstallShield 2015 ProjectsMySetup.ini'
You need to include the same information in the .ini file as you would if you were passing the parameters at the command line. There are four sections for this file:
| • | [Project]—In this section, include entries for the path to the project file (.ism), as well as the name of the product configuration. If you are building a patch, include an entry for the name of the patch configuration that you are building. |
| • | [Release]—In this section, include entries for release configuration information such as the compression type (compressed or uncompressed), build flags, Setup.exe settings, and the release name. |
| • | [Mode]—In this section, include any of the available optional entries, such as the Silent=yes entry if you want to build your release while suppressing any build errors or warning messages. This section also lets you indicate whether a log file should be created. |
| • | [BuildLocation]—In this section, you can optionally specify the release output location. |
Not all sections are required. As with passing parameters directly from the command line, parameters for requirements such as silent build and build location are optional. In the example .ini file below, these parameters are in the [Mode] and [BuildLocation] sections. You can omit these entries from your .ini file if you want to accept the defaults. By default, no log file is created, the installation is not run in silent mode, and your release is created in the project location that is specified on the File Locations tab of the Options dialog box.
Sample .ini File
The following tables contain sample entries from each of the four sections in a sample .ini file. The first column of each table shows a sample entry. The other columns provide the corresponding command-line parameter and description.
Entries in the [Project] Section
Entry | Corresponding ISCmdBld.exe Command-Line Parameter | Description |
Name='C:InstallShield 2015 ProjectsOthello.ism' | -p | Path to the .ism file. |
BuildLabel=Label1 | -a | Name of the product configuration for the release that you are building. If it does not exist, it is created. |
Product=Othello | Name of your product. This entry lets you override the value that is specified in the General Information view. | |
PatchConfigName=“Version 1.2” | -patch_config | Name of the patch configuration in the Patch Design view that you want to build. |
CompileScript=no | -n | Ensures that Setup.rul is not compiled as part of the build process. Note: CompileOnly should not be used with CompileScript. |
Entries in the [Release] Section
Entry | Corresponding ISCmdBld.exe Command-Line Parameter | Description |
BuildFlags=flags | -f | Release flags to be included in the installation, separated by commas. |
Configuration=COMP | -c | Compressed vs. uncompressed. |
Name=Othello Beta | -r | Release name. |
SetupEXE=yes | -e | Creates a Setup.exe file. |
Entries in the [Mode] Section
Installshield Setup.inx
Entry | Corresponding ISCmdBld.exe Command-Line Parameter | Description |
CubFile='C:Program FilesInstallShield2015SupportValidationMyValidation.cub' | -m | Validate the installation or merge module package after it is built using the specified .cub file. Include the full path and name to the .cub file. To use multiple .cub files, separate each path with a semicolon (;). Enclose long file names in quotation marks. For example, the following entry indicates that validation should be performed with the InstallShield Validation Suite for Windows 8 (ISWin8.cub) and the Full MSI Validation Suite (darice.cub): CubFile='C:Program FilesInstallShield2015SupportValidationISWin8.cub;C:Program FilesInstallShield2015SupportValidationdarice.cub' |
Silent=yes | -s | Runs in silent mode. |
StopOnFirstError=yes | -x | Aborts the build when the first error is encountered. |
CompileOnly=no | -q3 | Compiles only Setup.rul and streams Setup.inx into the Binary table of the .msi file, if one was previously built. Note: The entries CompileOnly, BuildTablesRefreshFiles, and BuildTablesOnly are mutually exclusive. Only one can be set to yes. CompileOnly should not be used with CompileScript. |
BuildTablesRefreshFiles=no | -q2 | Builds the Windows Installer tables and refreshes files. Note: The entries CompileOnly, BuildTablesRefreshFiles, and BuildTablesOnly are mutually exclusive. Only one can be set to yes. |
BuildTablesOnly=yes | -q1 | Builds only the Windows Installer tables for your release. Note: The entries CompileOnly, BuildTablesRefreshFiles, and BuildTablesOnly are mutually exclusive. Only one can be set to yes. |
UpgradeOnly=no | -u | Allows you to upgrade—but not build—your release. |
Verbose=yes | -v | Generates an engine log file. |
WarningAsError=yes | -w | Treats any build warnings as build errors. |
MSIVersion=2.0 | -g | Version of Windows Installer required on target system. Note: This entry applies to the Standalone Build only. |
DotNetVersion= | -j | Minimum version of Microsoft .NET Framework required on the target system. This parameter is optional and defaults to the latest version of the .NET Framework supported by InstallShield. Note: This entry applies to the Standalone Build only. |
DotNetPath='C:...' | -t | Path to the Microsoft .NET Framework on the build machine. Note: This entry applies to the Standalone Build only. |
SkipValidators=yes | -h | Enables you to turn off the upgrade validators that normally run at the end of the build. Note: This entry applies to the Standalone Build only. |
MergeModulePath='C:...' | -o | Search path for merge modules (.msm files). For more information, see Specifying the Directories that Contain Merge Modules. Note: This entry applies to the Standalone Build only. |
PrerequisitePath='C:...' | -prqpath | Search path for InstallShield prerequisite files (.prq). For more information, see Specifying the Directories that Contain InstallShield Prerequisites. Note: This entry applies to the Standalone Build only. |
Decompile Installshield Setup.inx
Entries in the [BuildLocation] Section
Entry | Corresponding ISCmdBld.exe Command-Line Parameter | Description |
Path='C:InstallShield 2015 ProjectsOthello' | -b | Release output location. |
For more information about the .ini file entries, see Building a Release from the Command Line.
See Also
InstallShield 2015 Help LibraryJune 2015 | Copyright Information | Contact Us |
I'm attempting to put a batch file together to push a COP17 install silently to campus labs. The problem I'm encountering is with the Python extension in ChemScript and the Activate program. I'm using the admin activation guide provided by PerkinElmer which lists all the individual install packages required, but it provides no unattended setup information for the Phyton extension (which does not use MSI). The rest does. Furthermore, the activate.exe program continutes to prompt for user activation - wanting an activation code to be provided. I've created the necessary activate.ini file according to the guide's instructions but it doesn't seem to recognize it when I drop it into the script folder. I've put it in the same folder as the Activate.exe program as well as with the install.exe (which is mentioned in the guide). Here's the batch script I'm using - it is run from the same location as the extracted install folders/files. I've bolded the two problem areas. I appreciate anyone willing to put another set of eyes on this and tell me what I'm missing.
Installshield Setup Inxs
%~dp0WindowsThirdPartyMicrosoftVCRedistvcredist_x86.exe /q /norestart
%~dp0WindowsPerkinElmerChemOfficePerkinElmer_ChemOffice_Professional_2017.msi /qn /norestart
%~dp0WindowsThirdPartyMicrosoftVCRedistvcredist_x64.exe /q /norestart
%~dp0WindowsPerkinElmerChemOfficePerkinElmer_ChemOffice_64-bit_Support_17.0.msi /qn /norestart
%~dp0WindowsPerkinElmerChemScriptPerkinElmer_ChemScript_17.0.msi /qn /norestart
%~dp0WindowsThirdPartyPythonpython-3.2.2.msi /qn /norestart
%~dp0WindowsThirdPartyPythonExtpywin32-217.win32-py3.2.exe
%WINDIR%System32REG ADD HKLMSOFTWAREPerkinElmerInformatics17.0 /v FNOServer /d https://perkinelmer.flexnetoperations.com/control/prkl/deviceservices /f /reg:32
%~dp0WindowsPerkinElmerActivationActivate.exe ChemBioOffice Ultra 17.0 IsInstaller