CyberInstaller - 3. Script Installation

A package, as well as by the script, is also defined by the folder structure.

Note: To avoid having to manually perform these tedious, it is highly recommended (though not essential) to use CyberInstaller Studio, which through an easy interface cards, will create the installation package and all the technical details in our place , in a completely automatic, transparent, and above all without possibility of error. The use of CyberInstaller Studio is also essential for the creation of the self-extracting executable package.

 CyberInstaller - 3. Syntax and description sections

The installation script is the file INSTALL.DAT and should be compulsory in the same folder (same level) is located in Setup.exe (the main file CyberInstaller).

To compile the script properly, it should follow the instructions contained in the same file in the form of comments (lines preceded by ";"). The script is divided into sections, usually corresponding to the steps of package creation of CyberInstaller Studio, and everyone deals with a very specific aspect of the installation process. Changing a section is necessary to follow carefully the notes at the start of each, which lists the possible parameters to use any special commands, and sample code.

Do not change the lines that indicate the sections, ie those preceded by ">". The lines preceded by ";" comments, and may be modified/removed/added at will at any point in the script, outside and inside sections. The only limitation is to reside in rows reserved for them, that is not next to commands. The character "<" indicates the end section and must be inserted.
The order of the sections is not fixed: it can be defined as desired.

Files and commands can be added to taste after the line of section, with due care and respecting the syntax (see the comment that precedes it).

The commands enclosed in "|" are reserved words and should not be changed. Their meanings are very precise and explained below.
Use the following commands to refer to special system paths:

General (recommended):

Note: attention to the difference between users for the following commands! If you use the commands related to the current user or all users the value of the section ChooseUserSpecialPath not be taken into account (not recommended).

Related to the selected user at installation (recommended). Itineraries SPA pursuant to section ChooseUserSpecialPath or the user's choice (we recommend you use these commands in order to give the user more control over 'installation):

Current user (whatever the user selected at installation) (not recommended):

All users (whatever the user selected at installation) (not recommended):

Other special commands:

Commands to identify the operating system (for use only in sections that allow them):

All controls, as well as the section names, are case-sensitive. So they must be scripted respecting the exact sequence of upper/lower case, because they are recognized correctly.

Section: Look & Feel - Customization CyberInstaller   

(Corresponds to step CyberInstaller Studio: 2)

Separate the names of the parameters from the command with an equal [=] with no spaces.
Parameter List:

• TransparentForms = <TRUE|FALSE>: toggles transparencies for the windows not in the foreground. Set it to TRUE to have the maximum flexibility and the soothing effect, to FALSE for maximum display speed or if crashes CyberInstaller. Scelta consigliata: FALSE. Recommended: FALSE.
  
  
• MoveableForms = <TRUE|FALSE>: Enables/disables the ability to move windows by dragging the title bar. Set it to TRUE to have the maximum flexibility and how to use the same standard Windows interface to FALSE to prevent the user can move windows CyberInstaller. Recommended: TRUE.
  
  
• ShowBackground = <TRUE|FALSE>: Enables/disables the display of the background. Set it to TRUE to display the background so that will cover the Windows desktop and other applications that are open, but will display name, producer and logo, FALSE to make the interface less intrusive as possible, but without the possibility of display the logo (if set). Recommended: TRUE.
  
  
• TransparentBackground = <TRUE|FALSE>: enables/disables the transparency of the background. WARNING: is taken into account if TransparentForms and ShowBackground = TRUE = TRUE. It's useful if you want to maintain a non-transparent background (default FALSE) while enabling the transparency of the windows. Instead set it to TRUE to get a nice effect of jamming the desktops of Windows. Recommended: FALSE.
  
  
• ShowBackgroundTitles = <TRUE|FALSE>: Enables/disables the display of writing in the background. WARNING: is taken into account only if ShowBackground = TRUE. Set it to TRUE to display name of the application to install and author, as well as a possible logo, background, FALSE for the background more attractive, as in the case of transparent background. Recommended: TRUE.
  
  
• BackgroundAppTitleFontSize = <TRUE|FALSE>: sets the font size which is written the name of the application to be installed in the background. WARNING: is taken into account only if ShowBackground and ShowBackgroundTitles = TRUE = TRUE. Recommended: 24.
  
  
• BackgroundCompanyTitleSize = <TRUE|FALSE>: sets the font size which is written the name of the application to be installed in the background. WARNING: is taken into account if ShowBackground = TRUE and ShowBackgroundTitles = TRUE. Recommended: 12.
• BackgroundColor = code> colore>: color to give the background. It's possible use any color.
• BackgroundTitlesColor = code> colore>: color of the securities in the background. It's possible use any color.
• TitleImageFile = <name .gif, .bmp .jpg file in the folder containing Setup.exe>: image that appears on the title bar of the main window. It's to enter only the file name, without path, because the file must be placed at the same level as Setup.exe and you can refer to any folder. If not entered or the file does not exist the image will not appear. Maximum dimensions (W x H) = 150 x 50 pixels.
• TitleImagePosition = <|TOP_SX |, |TOP_DX|>: position of the logo on the title bar of the main window.
• WelcomeImageFile = <name .gif, .bmp .jpg file in the folder containing Setup.exe>: image that appears on the title bar of the main window. It's to enter only the file name, without path, because the file must be placed at the same level as Setup.exe and you can refer to any folder. If not entered or the file does not exist the image will not appear. Maximum dimensions (W x H) = 162 x 312 pixels.
  

   

  
  

Section: MinimumRequirements - Minimum Regulatory Requirements  

(Corresponds to step CyberInstaller Studio: 14)

Separate the names of the parameters from the command with an equal [=] with no spaces.
Parameter List:

• Identifier = <pattern OSVersion SO> / <pattern identifier SO> / ...: Indicates the version of the minimal operating system in order to proceed with the installation
  es.: OSVersion=|%OS_WinXP_SP2%|/|%OS_WinXP%|/|%OS_Win2000%|/|%BLOCKING%| -> (Windows XP SP2 + WinXP + Win2000, bloccante) es.: OSVersion = |% OS_WinXP_SP2 %|/|% OS_WinXP %|/|% OS_Win2000 %|/|% BLOCKING% | -> (Windows XP SP2 + WinXP + Win2000, blocking)
  
  
• MinPhysicalRAM <da = 0 to 922337203685477>: indicates the minimum amount of RAM in order to proceed with the installation
  es.: MinPhysicalRam=268435456/|%BLOCKING%| -> (256 MB di RAM fisica, bloccante) es.: MinPhysicalRam = 268435456/|%BLOCKING%| -> (256 MB of physical RAM, blocking)

• MinDestDiskSpace <da = 0 to 922337203685477> ...: indicates the minimum amount of disk space to be able to proceed with the installation
  es.: MinDestDiskSpace = 20971520/|%BLOCKING%| -> (20 MB of space on the partition of installation, blocking)

• MinWinDiskSpace <da = 0 to 922337203685477> : Indicates the minimum amount of disk space on the partition where Windows is installed, in order to proceed with the installation
  es.: MinWinDiskSpace = 536870912/|%BLOCKING%| -> (512 MB of space on the Windows partition, blocking)

•  MinCPUSpeed <da = 0 to 32767>: indicates the processor speed (MHz) to proceed with the installation
   es.: MinCPUSpeed = 1200/|%BLOCKING%| -> (1/2 GHz processor speed, blocking)
 


• LoggedUserName = <name user connesso>: Indicates the user logged
  es.: LoggedUserName = Administrator/|%BLOCKING%| -> (the user logged on must be the administrator, blocking) 



• MinVideoResolution <da = 0 to x 32767> <da 0 to 32767>: Indicates the video resolution
  es.: MinVideoResolution = 1024x768/|%BLOCKING%| -> (minimum resolution 1024x768, blocking) 



• MinVideoColorDepth <da = 0 to 32767>: Indicates the color depth (bits - usually the values are: 8/16/24/32)
  es.: MinVideoColorDepth = 16/|%BLOCKING%| -> (the depth of color must be minimum 16-bit, blocking)

Section: ReadOnlyInstall - Perform a read-only, ie without the user being able to change anything? <TRUE|FALSE>

(Corresponds to step CyberInstaller Studio: 1)

•  specifyng TRUE user will not be given the opportunity to change the parameters of the installation, even the basic ones (eg the target folder, etc..) to complete the installation, but used only data read from this script installation. will show up any readme files and licenses, as well as the summary and the monitor setup.
• specifying TRUE override any decision on the components already in the system will be made automatically based on the version of the file (the file will be overwritten only if older than you are installing) and you will not be asked to confirm
  specifyng FALSE  you will be given the opportunity to change some installation parameters (such as the destination folder) fundamental WARNING: If SilentInstall = TRUE parameters are not modified by the user anyway.
•  specifyng FALSE will ask the user when overwriting an existing component, unless otherwise specified in Section COMPONENTS. WARNING: is taken into account only if SilentInstall = false the default, if no command is specified (TRUE|FALSE) is FALSE.

Section: SilentInstall - Perform a silent installation, ie without requiring user information? <TRUE|FALSE> <TRUE|FALSE>

(Corresponds to step CyberInstaller Studio: 1)

• specifying TRUE you will not be asked any information (eg the target folder, etc..) to complete the installation, but used only the data read from this script installation. Will show up any readme files and licenses, as well as the monitor setup.
• specifying TRUE override any decision on the components already in the system will be made automatically based on the version of the file (the file will be overwritten only if older than you are installing) and you will not be asked to confirm.
• specifyng FALSE you will be given the opportunity to change some installation parameters (such as the destination folder) fundamental. WARNING: is taken into account only if ReadOnlyInstall = FALSE, otherwise the parameters will only appear, but will not be editable.
• specifyng FALSE will ask the user when overwriting an existing component, unless otherwise specified in Section COMPONENTS. WARNING: is taken into account only if ReadOnlyInstall = FALSE.
• the default, if no command is specified (TRUE|FALSE) is FALSE.

Section: MinimumInteractionInstall - Perform a minimum of interaction, ie minimizing requests to the user? <TRUE|FALSE>

(Corresponds to step CyberInstaller Studio: 1)

• specifying TRUE user is offered only strictly necessary steps to complete the installation: pre-installation notes (if any), license to accept (if any) and destination folder. Then start the installation process itself, which will be completed only by the settings of the same script.
• specifying TRUE override any decision on the components already in the system will be made automatically based on the version of the file (the file will be overwritten only if older than you are installing) and you will not be asked to confirm.
• specify true in the setting section to hide the details (hidedetails) will be bypassed (the details are always hidden.)
• Specify false to you, showing you the steps to reach the greatest number of customization of the installation process.
• silent installation takes precedence over this setting.
  

Section: UpdateInstall - Perform an upgrade rather than opens a full installation of the package? <TRUE|FALSE>

(Corresponds to step CyberInstaller Studio: 1)

• TRUE will be executed by specifying a simple software upgrade rather than opens a fresh installation, this implies that as the destination folder will be used the same as before (at first installation), and will add a new reference in the Control Panel/Add or Remove Programs. Also will add the relevant information about the removal of the main package, so removing this will also remove all changes also applied to the system by the update.
• TRUE indicating the Roll-Back will be disabled and you can not select a group folder for links (the default is used).
• Specify false it will do a fresh install.
  

Section: Rollback - Activate the system roll-back? <TRUE|FALSE>

(Corresponds to step CyberInstaller Studio: 1)

• specifying TRUE system roll-back will be enabled by default.
• Specify false system roll-back will be turned off by default.
• you have the option to choose whether or not to enable this option.
• the default, if no command is specified (TRUE | FALSE) is false.

Section: hidedetails - Hiding the details of installation? <TRUE|FALSE>

(Corresponds to step CyberInstaller Studio: 1)

• specifyng TRUE the summary of installation will not be displayed
• TRUE specifying the monitor installation will be displayed only on request
• default is FALSE.
  

Section: AppToInstallTitle - Name of application to be installed

(Corresponds to step CyberInstaller Studio: 1)

Section: CompanyName - manufacturer or author

(Corresponds to step CyberInstaller Studio: 1)

• can omit if you do not want it to appear.
• entering the pattern "[*]" at the end of the manufacturer are not shown.
• author information of CyberInstaller (the pattern will not be displayed).

Section: Credits - Credits author package (will be displayed in a separate window by clicking on "?")

(Corresponds to step CyberInstaller Studio: 3)

• UseCustomCredits = <TRUE|FALSE>: if TRUE indicates that we must use credits personalized (parameters later). If FALSE, but the pattern is "[*]" the end of the manufacturer in the "CompanyName", the button "?" not be displayed. Considered only if there is such a pattern.
  
• LogoImage = <name .gif, .bmp .jpg file in the folder containing Setup.exe>: image that is displayed at the top of the window of the claims. Is's to enter only the file name, without path, because the file must be placed at the same level as Setup.exe and you can refer to any folder. Dimensions (WxH): 393x53 pixels. If not entered or the file does not exist the image will not appear.
  Eg: "SS.jpg.
  
• MainTitle = <string>: main title (usually the name of the package) that appears in bold type below the image of the logo.
  Eg: "CyberInstaller 3.0".
  
• Copyright = <string>: text copyright that appears below the main title.
  Eg: "SilverCyberTech Copyright 2003-2006. All rights reserved.."
  
• WebDescr = <string>: descriptive text before the website.
  Eg: "Website:".
  
• Web = <IP cliccabile>: address of website where the user can click to navigate to the site immediately.
  Eg: "http://www.silvercybertech.com.
  
• EMailDescr = <string>: first descriptive text of the email address.
  Eg: "Technical Support".
  
• EmailAddress = <IP cliccabile>: email address on which the user can click to instantly send an email.
  Eg: "support@silvercybertech.com.
  
• EMailSubj = <object EMAIL> the message: the subject of default to be set automatically to the email message to send if left blank will contain the name of the package (the "AppToInstallTitle).
  Eg: "Request for Help for CyberInstaller."
  
• EMailBody = <text EMAIL> message: default text to be set automatically to the email you send.
  Eg: "I got hold of your software and would aid in this regard."
  
• Notes = <string> : Additional notes displayed in small text at the bottom.
  Eg: "CyberInstaller Free edition is distributed free."
  

Section: Logo - File containing the application logo

(Corresponds to step CyberInstaller Studio: 2)

• ImageFile = <name .gif, .bmp .jpg file in the folder containing Setup.exe>: image that appears in the background. It's to enter only the file name, without path, because the file must be placed at the same level as Setup.exe and you can refer to any folder.
  If not entered or the file does not exist the image will not appear.
  es. "SS.gif"

• Position = <|TOP_SX|,|TOP_DX|,|BOTTOM_SX|,|BOTTOM_DX|,|CENTER|>: position of the logo in the background.
  es.: |TOP_DX|
  

Section: License - A file containing the license to appear before installation

(Corresponds to step CyberInstaller Studio: 3)

• must be contained in the data folder (you can refer to any)

Section: ReadmeFileBefore - File containing notes Preinstallation to appear before installation

(Corresponds to step CyberInstaller Studio: 3)

• must be present in the data folder (you can refer to any)

Eg:

Note.txt

Section: DefaultDestinationFolder - Destination Folder default
<path> / [<path read registro: key\value name>]

(Corresponds to step CyberInstaller Studio: 5)

• need not exist or is added in Section FoldersToCreate will be created automatically.
• is also used (the last part) for the group folder by default be created in the Start menu (if the user does not specify otherwise).
• you can specify a registry key to read from the folder that will be used as a destination, in this case, leave this parameter blank <path>, if alternative (if there are both values), the registry key is ignored
  

Eg:

|ProgramsPath|\CyberInstaller Suite /HKEY_CURRENT_USER\Software\Corel\Paint Shop Pro\10\Browser\Browsed

Section: ExtraDestinationFolder - Destination folder extra to give the custom pattern "|$UserPatternPath_001$|"
<description>/<Windows (percorso absolute or pattern)>/[<registry key\value name>]/<visibile TRUE|FALSE>/[<Only reading TRUE|FALSE>]

(Corresponds to step CyberInstaller Studio: 5)

• useful to create your own custom pattern to use as a route into other sections of the script
• need not exist or is added in Section FoldersToCreate automatically created
• the pattern in which the path will always be assigned "| $ UserPatternPath_001 $ |"
• the folder associated with the pattern will be selected by the user or read from a registry key
• you can set to TRUE, the optional parameter "read only" so as not to change the folder you
• the description may not contain the "/" character, used to separate parameters
• If this parameter "folder" can not be present "key log"
• If this parameter "registry key" may not be present "folder" in this case we'll use the parameter "key log" as "folder"
• If both these parameters "folder" and "key log" will be taken into account and displayed to the user (if "visible" is TRUE) the first
• whether the parameter "folder" that "key log" does not return paths exist on the target system, the field will appear empty to you

Eg:

Folder on the server: /G:\USER_FOLDER\Test / / TRUE
Folder on the server: //HKEY_LOCAL_MACHINE\Software\SilverCyberTech\dbpath / TRUE / FALSE
Folder on the server: /G:\USER_FOLDER\Test/HKEY_LOCAL_MACHINE\Software\SilverCyberTech\dbpath / TRUE / FALSE
Folder on the server: //HKEY_CURRENT_USER\Software\Corel\Paint Shop Pro\10\Browser\Browsed / TRUE / FALSE

Section: FoldersToCreate - Files/directories to be created (if not already exist)
 <complete path>

(Corresponds to step CyberInstaller Studio: 5)

• Use this section to create folders outside of the target folder: all folders and subfolders in the folder date will be recreated faithfully respecting the hierarchical structure if it contains at least one file. If the Data folder contains folders that in turn contain only other sub-folders (and no files), you must create by this section such
  folders without files.
• Include here also any special folders that you want to create in the Start Menu

 Example

If the data folder contains a subfolder AddIns which in turn contains only folders
(and no files), or is completely empty, you must create it:
|AppPath|\AddIns

to make sure that the folder "Dao" exists in its usual position and
If not create it, put these four lines:
|ProgramsPath|
|CommonPath|
|CommonPath|\Microsoft Shared
|CommonPath|\Microsoft Shared\Dao

to create the folder "Tools" in the Start Menu enter:
|StartMenuPath|\Tools

to create the folder "Tools" folder in the Start Menu Programs include:
|StartProgPath|\Tools

to create the folder "Tools" folder of the Start Menu group chosen by the user (wherever it is) to include:
|UserMenuFolder|\Tools

Section: AppsToRunBefore - Applications to be executed before the installation itself
<description estesa>/<blank of comando: executable |{parametri}|>/<sincrona TRUE|FALSE>/<conferma execution TRUE|FALSE>/|<condition>|

(Corresponds to step CyberInstaller Studio 8)

• You can use the pattern |$AppsToRunPath$| to run existing applications in the apps of the distribution media.
• The command line includes the full path + executable any parameters to pass. These parameters must be enclosed in braces and can contain pattern system.
  
• By setting the 3rd parameter to TRUE applications are executed synchronously, ie before launching an application CyberInstaller wait until the end of the previous one and also you can not continue installation if the first does not close the application with the flag to TRUE. In contrast with the 3rd parameter to FALSE applications will not run in sequence, but without waiting for the end of the execution before and you can also continue to install them while running in the background.
• By setting the 4th parameter to TRUE will ask the user before starting the application, and will be shown a window indicating the executable and any parameters.
  
• The last parameter can be a folder, file, registry key or value, the existence of which, if verified, will not run the application on.
  If instead that the item does not exist, the application will run normally. If this parameter is omitted the application will run
  however.
• The last parameter can also be an identification of the operating system. In this way the specified application is executed only if the operating system is indicated (see notes at the beginning of this file for valid IDs).

Eg:

EasyBudget 1.7/|$AppsToRunPath$|\EasyBudget\EasyBudget.exe/FALSE/TRUE
Microsoft MDAC 3.5/|$AppsToRunPath$|\MDAC.exe/TRUE/FALSE/HKEY_LOCAL_MACHINE\SOFTWARE\Classes\MDACVer.Version\CurVer
Notepad/|$WinPath$|\Notepad.exe/TRUE/TRUE
Setup DirectX/|$AppsToRunPath$|\DX\Setup.exe/TRUE/FALSE/|SystemPath$|\DirectX
Driver XP/|$AppsToRunPath$|\Drivers\WinXP\Setup.exe/TRUE/TRUE/|%OS_WinXP%|
Setup DirectX/|$AppsToRunPath$|\DX\Setup.exe {/silent /c -copy |$AppPath$|}/TRUE/FALSE/|SystemPath$|\DirectX
Notepad/|$WinPath$|\Notepad.exe/TRUE/FALSE/|%OS_WinXP%|
Notepad/|$WinPath$|\Notepad.exe {|$WinPath$|\dasetup.log}/TRUE/FALSE
Notepad/|$WinPath$|\Notepad.exe {|$WinPath$|\dasetup.log}/TRUE/FALSE/|%OS_WinXP%|

Section: Components - List data package (components) to be copied to the specified folder
<filename> / <path destinazione> / <to register: (one line) <filename> / <path destinazione> / <da registrare: TRUE|FALSE> / <copy mode: [|%% AutoConfirmation |] [|% AlwaysOverwrite %|][|% NeverOverwrite %|]>/
<Side-by-Side: TRUE|FALSE> / <eseguibile associated with Side-by-Side> / <categoria> / removal: TRUE | FALSE>

(Corresponds to step CyberInstaller Studio: 6)

• target directory must exist (in the event create a special section).
• COMPONENTS is the source folder (you can refer to any other).
• If the file does not require registration and the flag is still the place to TRUE, it will generate an error.
• copy mode: The command |%AutoConfirmation%| will ensure that prompting the user before overwriting a component already installed on your system, but the decision will be made automatically based on file versions (the component will be installed overwritten only if older than you are installing). If this command |%AlwaysOverwrite%| any files with the same name in the destination path will be overwritten anytime, in any case. If this command |%NeverOverwrite%| any files with the same name in the destination path will be maintained (will not be overwritten in any case). If not provided any command, you will be prompted for confirmation via a dialog box with details of the two files, so that the user can decide what to do. Warning: this parameter is taken into consideration only if the SilentInstallation section contains the value FALSE, if TRUE the automatic confirmation will be performed on each component without the possibility of intervention.
• Side-by-Side: how to install special ability to install the components in the same folder as the executable (|$AppPath$|) without interfering with any other versions (lower / higher) already available in shared folders of the system. Only works on systems Win98SE or higher.
• executable associated with the Side-by-Side:. exe files associated with the component. It is assumed that this executable will use the component in question. The component will be installed in the same folder as the executable. <Side-by-Side> If the parameter is FALSE, this parameter will not be taken into account.
• Category: Installation Group membership of the component (for custom installations).
• Removal: If TRUE the compo will be uninstalled with the removal of software, otherwise it will remain on the destination system.
  

Section: Fonts - List fonts to be installed
<name font> / <filename>

• fonts are installed in the Fonts folder system.
• We do not require system reboot after installation.
• fonts will be immediately available to applications and the system after installation

Section: REGKEYS - keys / values to be created in the Windows registry
<key> / [<value name>] / [<value>]

 (Corresponds to step CyberInstaller Studio: 10)

• If you omit the parameters name> valore> <value> and will create a section (subkey)
• if you want to create a value, you must first create the section
• if you want to create a section (subkey), the key to the previous layer must already exist. If not, create it as described in the first note
• you can change the default value for a key first creating the key and immediately after a value with name> valore> = | default_value |
• You can enter the pattern of the system (| $ AppPath $ |, | $ WinPath $ |, etc.).
• you can enter the license key entered by the user via the command |% SERIALCODE_VALUE%| value added as
• you can insert the boot path of Setup.exe (drive + + full path name file.exe) via the command |%SETUP_PATH%| value added as
  

Section: ExtensionsToAssociate - Extensions to associate
<extends> / <Fully executable file that will trigger l'estensione> / [<conferma>]

(Corresponds to step CyberInstaller Studio: 11)

• If this optional parameter "|%AskConfirm%|" will ask the user before the extension is associated
  

Eg:

associate the. EBB application "EasyBudget"
EBB / |$AppPath$|\ EasyBudget.exe

associate the. CSP application "CyberInstaller Studio":
CSP / |$AppPath$| \ CyberInstaller Studio.eXe

associate the. BMP application "NewPaint" Prompt the user:
BMP / |$AppPath$| \ NewPaint.exe / |%AskConfirm%|

Section: AttribsToSet - Attributes to be set
<Fully file/cartella> / <N(normale)|H(nascosto)|S(sistema)|R(sola lettura)|A(archivio)>

(Corresponds to step CyberInstaller Studio: 12)

• attribute N (normal) reset every other attribute set
• attributes can only add. It's possible still circumvent this restriction by setting the attribute Normal first and possibly only then adding the attributes that affect
• makes no sense to set up more than 4 attributes for a time, then any other characters will be ignored

Eg:

|AppPath| \ EasyBudget.exe / N
|AppPath| \ Init.ini / HRSA
|AppPath| / HR

Section: ChooseUserSpecialPath - Select users to whom you refer special routes:
<How selection username>/[|Locked |]

(Corresponds to step CyberInstaller Studio: 1)

Allowable values are two:
- |%CurrentUser%| to select the path of the user currently logged
- |%AllUsers%| to select the path of all authorized users in the system

If not enter a command |%Locked%| the user can not change this value during installation.
The default, if none has been specified, is: |%CurrentUser% |.

In the case of installation on systems configured as a single-user setting will be bypassed, using always only the current user's Start menu.

Section: LinksToCreate - Links to create:
<destination> / name> collegamento> / <Fully file puntato> / [<(command line confirming creation }>]/[<>]

(Corresponds to step CyberInstaller Studio: 11)

• destination can be any existing location on the disk. Usually you create shortcuts on the desktop or Start menu. Use the special commands to determine the destination:
  |$ CU_ ...$| for the current user (it bypasses the user's choice)
  |$ All_ ...$| for all users (it bypasses the user's choice)
  |$...$| To use the path selected in the user ChooseUserSpecialPath or according to the choices at installation
  
• If not using the command |$UserMenuFolder$| the destination is fixed and the user can not change it.
• If you want the link on a particular folder (not the system, which probably does not exist in the target system) you must create it by using the section FoldersToCreate. Note that using special folders, however, the links must be created in this folder no possibility of intervention by the user.
• enter the full path to the file pointed
• is not necessary to include a link to the removal, the command |%CreateRemovalLink%| will create it automatically.
• You can use the command |%% AskConfirm | by prompting the user before creating the connection, we recommend that you seek confirmation for all lines except those to be created in the Start Menu, where they can be created automatically
  

Eg:

$DesktopPath$|/CyberInstaller Studio/|$AppPath$|\Studio\CyberInstallerStudio.exe//|%AskConfirm%|
|$UserMenuFolder$|/Aggiornamenti on-line/|$AppPath$|\Updater\CISUpdater.exe
|$UserMenuFolder$|/CyberInstaller Studio/|$AppPath$|\Studio\CyberInstallerStudio.exe
|$UserMenuFolder$|\Documentazione/Edizioni - Licenze/|$AppPath$|\Documentazione\Edizioni - Licenze.txt
|$UserMenuFolder$|\Documentazione/Licenza/|$AppPath$|\Documentazione\CyberInstaller Suite - Licenza.txt
|$UserMenuFolder$|\Documentazione/Manuale in linea/|$AppPath$|\Help\0001.htm
|$UserMenuFolder$|\Documentazione/Manuale sintetico (aggiornato)/|$AppPath$|\Documentazione\CyberInstaller Suite - Manuale sintetico.txt
|$UserMenuFolder$|\Documentazione/Note di rilascio/|$AppPath$|\Documentazione\CyberInstaller Suite - Note di rilascio.txt
|$UserMenuFolder$|\Documentazione/Leggimi/|$AppPath$|\Documentazione\CyberInstaller Suite - Leggimi.txt
|$UserMenuFolder$|\Risorse Web/CyberBlog/|$AppPath$|\Documentazione\Risorse Web\CyberBlog.url
|$UserMenuFolder$|\Risorse Web/CyberInstaller su VB-T&T/|$AppPath$|\Documentazione\Risorse Web\CyberInstaller su VisualBasicT&T.it.url
|$UserMenuFolder$|\Risorse Web/Forum ufficiale/|$AppPath$|\Documentazione\Risorse Web\Forum ufficiale.url
|$UserMenuFolder$|\Risorse Web/SilverCyberTech (sito ufficiale)/|$AppPath$|\Documentazione\Risorse Web\SilverCyberTech (sito ufficiale).url
|%CreateRemovalLink%|

Section: ReadmeFileAfter - File containing the release notes to be displayed after the installation

(Corresponds to step CyberInstaller Studio: 3)

Must be contained in the data folder (you can refer to any)

Eg

Readme.txt

Section: AppsToRunAfter - Applications to be executed after the installation itself:
<description estesa> / <blank of comando: executable |{parametri}|>/<sincrona TRUE|FALSE> / <conferma execution TRUE|FALSE> /|<condition>|

(Corresponds to step CyberInstaller Studio 8)

• You can use the pattern |$AppsToRunPath$| to run existing applications in the apps of the distribution media.
• The command line includes the full path + executable any parameters to pass. These parameters must be enclosed in braces and can contain pattern system.
  
• By setting the 3rd parameter to TRUE, applications will be executed synchronously, ie before launching an application CyberInstaller wait until the end of the previous one and also you can not continue installation if the first does not close the application with the flags to TRUE. In contrast with the 3rd parameter to FALSE applications will not run in sequence, but without waiting for the end of the execution before and you can also continue to install them while running in the background.
• By setting the 4th parameter to TRUE will ask the user before starting
  application and it will be shown a window indicating the executable and any parameters.
  
• The last parameter can be a folder, a file, a key or registry value, the existence of which, if verified, will not run the application on.
  If instead that the item does not exist, the application will run normally. If this parameter is omitted the application will run
  however.
• The last parameter can also be an identification of the operating system. In this way the specified application is executed only if the operating system is indicated (see notes at the beginning of this file for valid IDs).

Eg:

asyBudget 1.7/|$AppsToRunPath$|\EasyBudget\EasyBudget.exe/FALSE/TRUE
Microsoft MDAC 3.5/|$AppsToRunPath$|\MDAC.exe/TRUE/FALSE/HKEY_LOCAL_MACHINE\SOFTWARE\Classes\MDACVer.Version\CurVer
Notepad/|$WinPath$|\Notepad.exe/TRUE/TRUE
Setup DirectX/|$AppsToRunPath$|\DX\Setup.exe/TRUE/FALSE/|SystemPath$|\DirectX
Driver XP/|$AppsToRunPath$|\Drivers\WinXP\Setup.exe/TRUE/TRUE/|%OS_WinXP%|
Setup DirectX/|$AppsToRunPath$|\DX\Setup.exe {/silent /c -copy |$AppPath$|}/TRUE/FALSE/|SystemPath$|\DirectX
Notepad/|$WinPath$|\Notepad.exe/TRUE/FALSE/|%OS_WinXP%|
Notepad/|$WinPath$|\Notepad.exe {|$WinPath$|\dasetup.log}/TRUE/FALSE
Notepad/|$WinPath$|\Notepad.exe {|$WinPath$|\dasetup.log}/TRUE/FALSE/|%OS_WinXP%|

Section: RebootWindows - Restart the computer after installing? <TRUE|FALSE>

(Corresponds to step CyberInstaller Studio: 1)

The default, if no command is specified (TRUE | FALSE) is FALSE.

   See also ...

 CyberInstaller Studio 

 Integrated editor
 CyberInstaller - core files and folder structure 

 Steps of package creation

 Step 1: General Parameters
 Step 2: Interface CyberInstaller

 Step 3: Documentation

 Step 4: Application Data

 Step 5: Folders

 Step 6: File Details

 Step 7: Fonts

 Step 8: External Applications

 Step 9 Packet MSI/MSM

 Step 10: Keys and values of log

 Step 11: Association extensions

 Step 12: File and Folder Attributes

 Step 13: Links

 Step 14: Minimum

 Step 15: Serial numbers

 Step 16: Languages

 Step 17: Output Media

 Step 18: Executable

 Step 19: Creating package

 Extra Step: Notes Package