Mimer SQL Documentation PREV

Mimer Developer Site

www.mimer.com/developer


7.1 setup.exe


setup.exe is the main setup executable; it performs setup initialization and launches the appropriate setup engine file on the target system.

Once you have built your setup, you can rename setup.exe to any valid file name, such as install.exe.

Syntax
Setup [switches] 
Switches

These switches are optional. They are not case sensitive; upper- or lowercase letters can be used.

/c and -c -
Examples:
/c<path\RebootFile> 

or

-c<path\RebootFile> 

This is a Mimer SQL specific switch which specifies location and name of a reboot indicator log file.

"RebootNeeded=1" is inserted into the file if reboot is required to complete the installation.

"RebootNeeded=0" is inserted into the file if reboot is not required.

It is recommended that the reboot indicator log file and the log file are the same file.

/f and -f
Examples:
/f<path\CompiledScript> 

or

-f<path\CompiledScript> 

Specifies an alternate compiled script.

Unless the compiled script (.ins file) also resides in the same directory as that of setup.exe, the full path to the compiled script must be specified.

_setup.dll must also reside in the same directory as your .ins file. For example, setup -ftest.ins will launch setup using Test.ins instead of Setup.ins.

/f1 and -f1
Examples:
/f1<path\ResponseFile>  

or

-f1<path\ResponseFile> 

Specifies an alternate location and name of the response file (.iss file).

If this option is used when running InstallShield Silent, the response file is read from the folder/file specified by <path\ResponseFile>.

If this option is used along with the -r option, the response file is written to the
folder/file specified by <path\ResponseFile>.

If an alternate compiled script is specified using the -f switch, the -f1 switch entry must follow the -f switch entry.

/f2 and -f2
Examples:
/f2<path\LogFile>  

or

-f2<path\LogFile> 

Specifies an alternate location and name of the log file created by InstallShield Silent.

By default, Setup.log log file is created and stored in the same directory as that of Setup.ins.

If an alternate compiled script is specified using the -f switch, the -f2 switch entry must follow the -f switch entry.

/r or -r
Examples:
/r  

or

-r 

Causes setup.exe to automatically generate a silent setup file (.iss file), which is a record of the setup input, in the Windows folder.

/s or -s
Examples:
/s  

or

-s 

Runs InstallShield Silent to execute a silent setup.

/z or -z
Examples:

/z or -z

Prevents setup.exe from checking the available memory during initialization.

This switch is necessary when running a setup on a machine with more than 256 MB of disk space; if it is not used, setup.exe reports insufficient memory and exits.

Comments
Errors

setup.exe may produce error messages if it cannot start properly. In most cases you'll encounter these messages when a severe error occurs. Rarely will your end users see these messages.

Error messages are displayed in message boxes. Every error message has a number. These are InstallShield system error messages and there is no way to suppress them in your script.

7.1.1 setup.exe Error Codes

The following table explains setup.exe error codes:

Error No.
Message
101
Setup is unable to find a hard disk location to store temporary files. Make at least 500KB of free disk space available and then try the setup again.
102
Setup is unable to find a compressed library file required to proceed with the setup. Check to make sure all required files are located with the Setup program.
103
Setup is unable to find _setup.dll, which is needed to complete the setup. Restart your system and try again.
104
Setup is unable to find the language section in the Lang.dat file, or Lang.dat could not be found.
105
Setup.lid cannot be found or it has an invalid format.
106
The language dialog box cannot be created.
107
Setup is unable to locate the script file <%s> which is needed to complete the setup.
110
Setup was started with a command line argument that contained an incomplete parameter bad_parameter.
111
Insufficient memory available to run Setup. Close all other applications to make more memory available and try to run Setup again.
112
Setup is unable to locate the layout file '...\Layout.bin' which is needed to complete the setup.
201
Setup is unable to initialize the setup program (Install.exe).
202
Setup is unable to initialize the setup program.
301
Setup was unable to start up the setup program.
401
String variable is not large enough for string. Please check string declarations.
420
Setup is unable to copy the setup support file <filename> to a temporary location.
421
Setup is unable to copy the setup support file _user1.cab to a temporary location. Make more space available and try again.
422
Setup is unable to expand the setup support file <filename>.
423
Setup is unable to load the setup script file.
424
Setup has encountered an internal stack overflow error. Close all applications, restart the system and try the setup again.
425
Setup has encountered an incomplete return statement in the script. Check your script for unmatched return statements.
426
Setup is unable to find the setup script file: script_filename.
427
Setup is unable to load the setup script file: script_filename. The script may be from a previous version or corrupted.
432
Setup has detected that the uninstaller is in use. Please close the uninstaller and restart setup.
440
Setup has detected a possible infinite loop in the script with function function_name. Make sure you are handling the error return codes properly.
502
Setup is unable to initialize the setup program. The script file may be bad.
701
A division by zero error was detected in the script. Setup will continue.
702
An internal error has occurred. Insufficient memory to allocate buffer.
703
An internal read error has occurred on script_filename. Unable to load setup instructions.
704
Script_filename file has become corrupted. Unable to load setup instructions.
30xx
Error messages ranging from 3000 to 3021 are internal memory-related error conditions.

7.1.2 Setup Runtime Errors

When copying the installation files the following errors may occur. These error numbers will occur in the ResultCode in the response file.

Code
Description
0
Success.
-1
General error.
-2
Invalid mode.
-3
Required data not found in the Setup.iss file.
-4
Not enough memory available.
-5
File does not exist.
-6
Cannot write to the response file.
-7
Unable to write to the log file.
-8
Invalid path to the InstallShield Silent response file.
-9
Not a valid list type (string or number).
-10
Data type is invalid.
-11
Unknown error during setup.
-12
Dialog boxes are out of order.
-51
Cannot create the specified folder.
-52
Cannot access the specified file or folder.
-53
Invalid option selected.

7.1.3 Component Error Codes

The following table describes the error codes returned by ComponentError:

Code
Description
Cause
-101
Cannot add component.
ComponentAddItem was unable to add a component to the script-created component set.
-102
Specified component already exists.
ComponentAddItem was called twice with the same media name and component name.
-104
Specified component name is not valid.
The value passed in the second parameter of ComponentInitialize is not valid.
-105
Specified component cannot be found in the media.
An attempt was made to access a component that does not exist in the named media. This error occurs when a component name is specified incorrectly in call to a component function. Component names must be specified exactly as they appear in the Components Pane or in the call to ComponentAddItem. Case is sensitive.
-106
Unable to decompress a file.
An internal error occurred. Contact technical support.
-107
Disk ID specified in call to ComponentMoveData is not valid.
ComponentMoveData has already been called to transfer files and has not been re-initialized. To re-initialize ComponentMoveData, call that function with a null string in the first parameter.
-108
Out of disk space.
The target disk or directory has insufficient free space; the disk space cannot be determined because TARGETDIR is invalid; or a script-defined folder of a component has not been set.
-109
EnterDisk function called failed.
Internal error occurred. Contact technical support.
-112
Specified file cannot be found.
To determine which file is missing, check the value returned by ComponentError in the parameter svFile.
-107
Disk ID specified in call to ComponentMoveData is not valid.
ComponentMoveData has already been called to transfer files and has not been re-initialized. To re-initialize ComponentMoveData, call that function with a null string in the first parameter.
-113
Specified file cannot be opened as read-only.
The file Data1.cab (or one of the other data cab files) is missing or corrupted; or an uncompressed data file is missing from a CD-ROM, Data As Files build.
-114
Specified file cannot be opened as read/write.
Unable to append to split file. Contact technical support.
-115
Specified file cannot be opened as write.
An attempt was made to overwrite a locked file belonging to a file group that does not have the Potentially Locked or Shared property set to Yes or the path to the target folder is invalid.
-117
Cannot read the specified file.
A data cab file or an uncompressed data file may be corrupt.
-118
Attempted operation not allowed with script-created component sets.
A script-created component set name was passed to a component function (for example, ComponentFileInfo), that operates only on file media.
-119
Unable to self-register a file properly.
This error has many possible causes. For details, refer to article Q101538 in the InstallShield Knowledge Base.
-120
Unable to update a shared file in ComponentMoveData.
Internal error. Contact technical support.
-121
Unable to write to a file.
Internal error. Contact technical support.
-123
Unable to find a file group.
The specified file group could not be found. The name of the missing file group is returned by ComponentError in the parameter svFileGroup.
-125
The list specified in the component function is not valid.
When calling ComponentListItems, or ComponentSetupTypeEnum, verify that the list you are passing to the function is valid.
-126
Attempted operation not allowed with file media library.
A file media name was passed to a component function (for example, ComponentAddItem), that operates only on script-created component sets.
-127
Media is already initialized.
ComponentInitialize was called to initialize a media that was already initialized.
-128
The specified file media library was not generated by the InstallShield Media Wizard.
The file Data1.cab is corrupt, or the file specified in a call to ComponentInitialize is not an InstallShield-generated cabinet file.
-132
The specified media cannot be found.
The media has been declared but it not associated with any components. Make sure that either script-created components or file media components are associated with the media.
-133
An error occurred with the specified media.
ComponentMoveData has already been called to transfer files and has not been re-initialized. If your script calls ComponentMoveData more than once, you must re-initialize it after each call by calling it again with a null string in its first parameter.
-136
Unable to allocate memory.
Insufficient memory is available to the setup. Display a message to the end user to close down all other applications or to cancel the setup, reboot the system, and restart the setup.
-137
Specified option is not valid.
An invalid option has been specified for a component function, for example, by specifying only a file group when both a file group and file name are required.
-139
Specified password does not match.
The specified password does not match the password stored in the specified file media library or component.
-141
Specified password cannot be found.
ComponentValidate was called to validate a component or a file media library for which no password has been set.
-142
The media or the component password was not validated.
ComponentValidate was not called to validate the components and/or the file media library before transferring those components with ComponentMoveData.
-145
Target path for the component cannot be found.
The target directory for a script-defined folder has not been set or is invalid.
-147
Invalid value passed to a component-related function.
One of the values passed to a component function is invalid. This error can be caused, for example, by passing an empty string in the second parameter of ComponentAddItem.
-148
Data cannot be read from the internet.
This error occurs when using InstallFromTheWeb in conjunction with InstallShield5. InstallShield is unable to read the data from the Internet because the files are corrupt or the Internet connection has been lost and cannot be reestablished by InstallFromTheWeb.
-149
Internet has been disconnected.
This error occurs when using InstallFromTheWeb in conjunction with InstallShield5. The Internet connection has been lost and cannot be reestablished by InstallFromTheWeb.
-150
Cabinet file generated by an older version of InstallShield5.
Verify that the project was built with your most recent version of InstallShield5. Verify that you are not using mismatched cabinet files generated by different versions of InstallShield5.
-620
Error with third-party shell.
Consult the documentation for the shell in question to determine whether it is 100% Explorer shell compatible.
-623
Error renaming a file.
An attempt was made to transfer an executable file (an .exe or .com file) over a locked file without setting the Potentially Locked property to Yes.



Upright Database Technology AB
Voice: +46 18 780 92 00
Fax: +46 18 780 92 40
dbtechnology@upright.se
Mimer SQL Documentation PREV