CyberInstaller
Studio - 11. Adding
an external application CyberInstaller
Studio - 11. Adding
an external application
Clicking on the Add button in the step 8 - "External Applications" opens a window through which you can specify all the parameters of the executable file that you want to run during the installation process of the package.
Note: The
application can be incorporated in the package, or you can refer to a
location on your system if you are sure that the application exists
(for example, "|$SystemPath$|
\ calc.exe") or if the executable file you just installed (like if you
want to run the installed application after installation, then the
reference will be "|$AppPath$|
\ MiaApplicazione.exe). encasing the application package sizes it will
grow accordingly.
CyberInstaller
Studio - 11.1 General Parameters application
Description application
[field] - Example:
"Setup Microsoft Data Access Components"
Descriptive text that is displayed to the user,
usually used to insert the expanded title of the application (it will
appear to the user during the installation process to inform the
application that is started).
Package [button]
Allows you to open the Browse
dialog box package through which to select an executable
belonging to the current package. Utulizzando this button all other
fields are automatically filled in properly.
This procedure is useful, for
example, if you want to start the installed application after
installation (which is why the applications available from the package
should always be performed after
the actual installation).
Path local executable application [field] - Example: "F:\My Documents\MDAC_TYP.EXE"
The full path to your local disk where the file is executable. If your application package will be included in this parameter will be used to CyberInstaller only designed to know where to copy the files in the package, otherwise it will serve to indicate the name alone CyberInstaller executable file (the path of this field is irrelevant if you do not encompasses the application in the package).
Includes in the package [checkbox] - Default: No
If checked, CyberInstaller Studio will copy the executable file mentioned in "Local path" in the current package (by increasing the packet size accordingly). Otherwise, the file mentioned in "Local path" will only start being installed on the value of the "Startup folder".
Browse [button]
Opens the Open dialog box/Select Files by which to select the executable file. Using this window will not need to type the path and file name manually.
Folder start application during the installation [field] - Example: "|AppsToRunPath|"
Folder to start the
application. If it is not "|$AppsToRunPath$|" (the pattern that tells CyberInstaller
to look in the folder of the package used to contain the external
application) the application will not be
incorporated in the package, otherwise you (thus checking the check box
"It embeds in the package" this field will take this value). Also in
the event that is not "|$AppsToRunPath$|"
during the installation CyberInstaller
will seek to launch the executable from the folder specified in this
field (it is highly recommended to use patterns
of system), then you need to enter a location to which you
are certain that the executable content is specified (eg: "|$WinPath$|" to the Windows
folder or "|$AppPath$|" for
the destination folder chosen by the user, which will install the
software to be distributed).
Note: you should always
incorporate the external application in the package, unless it is:
- Distributed applications
always in Windows (calculator, notepad, etc.).
- Newly installed
application (reference is usually at the startup folder using
the pattern |$AppPath$|). In
this case the external application should be launched later.
Command line parameters to pass to the application [field] - Example: "/silent/showgui"
Here you can specify various parameters by which the application should be initiated.
CyberInstaller
Studio - 11.2. Conditional execution
Condition [field] - [Optional] - Example: "|OS_WinXP|"
Optional condition
that, if met, will prevent or permit the application starts. The fact
that inhibit/enable the execution is the same condition, which can be:
- A file (inhibit:
if present, the application will not run)
- A folder (inhibit:
if present, the application will not run)
- A key/value
registry (inhibit: if present, the application will
not run)
- Identification
operating system (allows: the application will run
only if you are installing the operating system specified).
It's possible leave this field blank. In this case the application will run forever.
Browse [button]
Allows you to open the Open dialog box/Select Files by which to select a file whose existence will prevent the application runs.
Special Folders [button]
Allows you to open the dialog "special folder system" through which to select a pattern that represents a folder on the target user's system. The existence of this folder will prevent the application runs.
Registry Editor [button]
Allows you to open the registry editor in Windows to copy the name of a key or value, and then paste it in the "Condition". The existence of this key/value to the user's system will inhibit the implementation of the application.
Operating System [list]
Allows you to select an identifier of the operating system. The application will run only if the user's system is shown. This is the only condition that can be verified if the application is running.
CyberInstaller
Studio - 11.3. Implementing
Rules
It's possible select a mode of execution in relation to the installation process:
Synchronous
[box
option] - Default: Yes
The installation process will continue until after the application starts or ends is closed by the user. Utile nei casi in cui bisogna installare più pacchetti ed è necessario attendere il completamento del precedente prima di continuare (es. MDAC, DirectX, ecc.). Useful in cases where you have to install multiple packages and you must wait for the completion of the previous before continuing (eg MDAC, DirectX, etc.)..
Asynchronous
[box
option] - Default: No
The installation process will continue immediately after starting the application (without waiting for closing) and returning immediately to the user. Useful in cases where you want to start the application you just installed and finish the installation process itself.
CyInstaller
Studio - 11.4. Ask the user
It's possible choose
whether the application should be performed immediately or through user
confirmation:
Yes,
requires confirmation [box option] - Default:
No
The application will performed only if the user confirms it.
No, start
immediately [box option] - Default:
Yes
The application will run immediately, without prompting the user
CyberInstaller
Studio - 11.5. Examples
Example 1:
You want to run the installer for Microsoft Data Access (MDAC). This executable is
present on our hard drive in C:\Documents\Software and is called
MDAC_TYP.EXE.
In this example it is right to incorporate such application in the package, as part of all that is necessary in our package to be installed correctly. Also you want the application to run only if the MDAC components that are not already going to install on the target system (in this case will be the registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Classes\MDACVer.Version\CurVer"). The application must be done synchronously wait for its completion before advancing to the main installation.
The
values of the parameters will be:
Application description = "Installer for Microsoft data access"
Local application executable file path = "C:\Documents\Software\MDAC_TYP.exe"
Incorporates the current packet = Yes
Startup folder during the installation application = "|$AppsToRunPath$|"
Condition = "HKEY_LOCAL_MACHINE\SOFTWARE\Classes\MDACVer.Version\CurVer"
Mode of execution = synchronous
Example 2: You want
to run the installed application (main executable: "NetCounter 2.exe").
This example does not make sense to incorporate
this application package, because after installation will be present on
your system. Also you want the installation process will continue even
without waiting for the end application.
The
values of the parameters will be:
Application description = "Silver Cybertech NetCounter 2"
Local application executable file path = "C:\Documents\Silver Black\Software\NC2\ NetCounter 2.exe"
Incorporates the current packet = No
Startup folder during the installation application = "|$AppPath$|"
Condition = [no value added]
Methods of execution = async
Example 3: you want to run the installer of a driver. This driver is diverse: there is a version for Windows XP and Windows 95. The executables are present on our hard drive in C:\Documents\Software and are named SetupDriverWinXP and SetupDriverWin95 respectively.
In this example it is right to incorporate such applications in the package, as this is part of all that is necessary in our package to be installed correctly. Furthermore you will, of course, that it will only run the installer properly, according to the operating system. The application must be done synchronously wait for its completion before advancing to the main installation.
The values of the parameters for
SetupDriverWinXP will be:
Application description = "Driver Installer Microsoft Windows Vista"
Local application executable file path = "C:\Documents\Software\SetupDriverWinVista.exe"
Incorporates the current packet = Yes
Startup folder during the installation application = "|$AppsToRunPath$|"
Condition = "|%OS_WinVista%|"
Mode = synchronous execution
The values of the parameters for SetupDriverWin95 will be:
Application description = "Driver Installer Microsoft Windows XP"
Local application executable file path = "C:\Documents\Software\SetupDriverWinXP.exe"
Incorporates the current packet = Yes
Startup folder during the installation application = "|$AppsToRunPath$|"
Condition = "|%OS_WinXP_SP2%|"
Mode = synchronous execution
See
also ...
