BZSetup section

In the [BZSetup] section, you can customize the BlueZone installation process. The following code displays the default values in the [BZSetup] section:

[BZSetup]
;default SourceDir is drive and directory of SETUP.EXE
;SourceDir=A:\
;DestinationDir="C:\Program Files\BlueZone\6.1"
WorkingDirType=1
;0 - Custom, 1 - User's Personal Folder (My Documents), 2 - All Users Shared Document Folder
;3 - User's AppData Folder, 4 - All Users AppData Folder
;WorkingDir="C:\Program Files\BlueZone\6.1"
;CopyPrevWorkingDir=Yes
;fourteen digit registration key
RegistrationKey=
;SNA Server, Renex Async Protocol, TN3270E, Communications Server, IntranetWare for SAA
Connection=TN3270E
;see Administrator's Guide for Lock values
Lock=0
LockFTP=0
LockFTPSession=0
LockFTPConnection=0
LockFTPInitialCommands=0
LockFTPMiscellaneous=0
LockFTPSchedule=0
LockFTPFirewall=0
LockFTPSecurity=0
LockFTPCertificate=0
LockTelnet=0
LockDisplay=0
LockFont=No
ShowLockedDialogs=Yes
DisableAppendToClipboard=No
;0-HKEY_CURRENT_USER (Session Settings - Default), 1-HKEY_LOCAL_MACHINE (All Settings)
;2-HKEY_CURRENT_USER (All Settings)
BaseRegistry=0
ProfileMode=Yes
ProfileSharing=Yes
SetPath=No
EnablePowerKeys=No
FIPSMode=No
InstallScriptPlayerOnly=No
SessionManagerRunInTray=No
ScriptRecordHiddenText=No

Table 1: BZSetup entries
Entry	Description
`SourceDir=`	Source directory is only used when installing BlueZone from a floppy diskette. Note that the value of `SourceDir` must be where SETUP.EXE is located. Default value: `;SourceDir=A:\` (commented out)
`DestinationDir=`	Controls the installation location of the BlueZone program files. This feature is typically used in conjunction with the quiet mode installation. If you want to install BlueZone in a specific location, uncomment this item and edit the value with the custom location. Default value: `;DestinationDir="C:\Program Files\BlueZone\6.1"` (commented out)
`WorkingDirType=`	Controls the location of the working directory folder. The working directory contains the BlueZone working files: certificate, configuration, macro, script, spool, trace, and transfer files. BlueZone working files are connected to a specific user. The available `WorkingDirType=` values are: 0 - Custom Folder 1 - User's Personal Folder (My Documents) 2 - All Users Shared Document Folder 3 - User's AppData Folder 4 - All Users AppData Folder If you set `WorkingDirType=0`, use the `WorkingDir=` entry to control the exact location of the working directory. Default value: `WorkingDirType=1`
`WorkingDir=`	Defines the custom location of the working directory. If you set `WorkingDirType=0`, uncomment this entry and define the custom working directory location. Default value: `;WorkingDir="C:\Program Files\BlueZone\6.1"` (commented out) Note: The `WorkingDir=` entry supports environment variables. For example, you can use the `%USERNAME%` environment variable to call the user name as shown here: `;WorkingDir="C:\%USERNAME%\BlueZone\6.1"` Also, the environment variable feature can be used in conjunction with installing BlueZone on a network drive as shown here: `;WorkingDir="Y:\%USERNAME%\BlueZone\6.1"`
`CopyPrevWorkingDir=`	Copies the previous version’s working directory to the newly installed version’s working directory. This allows the user to continue to use the same user configuration profiles from a previous version. Default value: `;CopyPrevWorkingDir=Yes` (commented out)
`Connection=`	Sets the BlueZone preferred connection type. This is the connection that BlueZone uses as a default when an end user selects Session → Configure from the BlueZone menu bar. Possible values: Microsoft SNA Server = `SNAServer` Renex Async Protocol = `RenexAsync` TN3270 / TN3270E = `TN3270E` IBM Communications Server = `CommServ` IntranetWare for SAA = `Intranetware` For example, if you are a Microsoft SNA Server shop and you want to install BlueZone using Microsoft SNA Server as the preferred connection type, set `Connection=SNAServer`. Note: Some BlueZone emulation clients only support one connection type. Therefore, the value of `Connection=` is ignored during installation of these clients. Default value: `Connection=TN3270E`
`Lock=`	Controls the locking of one or more BlueZone features. The possible values for the lock feature are provided in the BlueZone feature lock table. Refer to BlueZone feature locks for a table of lockable BlueZone features and their values, and BlueZone feature locking for more information. A zero value indicates that no BlueZone features are locked. Default value: `Lock=0`.
`LockFTP=`	Controls the locking of one or more BlueZone Secure FTP commands. The possible values for the `LockFTP` feature are provided in the BlueZone Secure FTP lock table. Refer to BlueZone Secure FTP command and feature locks for a table of lockable BlueZone functions and their values. Also refer to BlueZone feature locking for more information. A zero value indicates that no BlueZone FTP commands are locked. Default value: `LockFTP=0`
`LockFTPSession= LockFTPConnection= LockFTPInitialCommands= LockFTPMiscellaneous= LockFTPSchedule= LockFTPFirewall= LockFTPSecurity= LockFTPCertificate=`	Controls the locking of one or more BlueZone Secure FTP features. The possible values for the above items, are provided in the BlueZone Secure FTP feature lock table. Refer to BlueZone Secure FTP individual feature locks for the tables of lockable BlueZone features and their values. Also refer to BlueZone feature locking for more information. A zero value indicates that no BlueZone Secure FTP features are locked. Default values: `LockFTPSession=0` `LockFTPConnection=0` `LockFTPInitialCommands=0` `LockFTPMiscellaneous=0` `LockFTPSchedule=0` `LockFTPFirewall=0` `LockFTPSecurity=0` `LockFTPCertificate=0`
`LockTelnet=`	Controls the locking of one or more of the BlueZone Telnet features. The possible values for the lock feature are provided in the Telnet feature lock table. Refer to Telnet feature locks for a table of lockable BlueZone Telnet features and their values. Also refer to BlueZone feature locking for more information. A zero value indicates that no Telnet features are locked. Default value: `LockTelnet=0`
`LockDisplay=`	Controls the locking of one or more of the BlueZone Display features. The possible values for the lock feature are provided in the Display feature lock table. Refer to Display feature locks for a table of lockable BlueZone Display features and their values. Also refer to BlueZone feature locking for more information. A zero value indicates that no Display features are locked. Default value: `LockDisplay=0`
`LockFont=`	Controls the locking of the currently configured font. Possible values are `Yes` to lock the currently configured font and `No` to allow users to be able to change the configured font. When this value is set to `Yes`, the Change button on the Font dialog is disabled. Default value: `LockFont=No`
`ShowLockedDialogs=`	Controls whether the BlueZone dialog is displayed if that particular feature is locked using the BlueZone feature locking feature. Normally, if you lock a particular BlueZone feature, your end users are still able to access the associated BlueZone configuration dialog for that feature. They can view it and make changes to the settings. They cannot however apply or save those changes. The OK button will be grayed out. However, if would prefer for your end user's to not be able to see the dialogs at all, you can turn them off by setting this value of `ShowLockedDialogs=` to `No`. An message box displays instead. Refer to Configuring the show locked dialogs feature for more information. Default value: `ShowLockedDialogs=Yes`
`DisableAppendToClipboard=`	Disables the BlueZone append to clipboard feature. If you do not want your users to be able to append data to their Windows clipboard, you can turn this feature off by setting this value to `Yes`. Default value: `DisableAppendToClipboard=No`
`BaseRegistry=`	Controls how BlueZone uses the Windows registry. Possible values are 0, 1 or 2. Refer to Base registry setting for more information. Default value: `BaseRegistry=0`
`ProfileMode=`	Controls whether BlueZone operates in profile mode or registry mode. Possible values are `Yes` to enable profile mode and `No` to enable registry mode. Default value: `ProfileMode=Yes`
`ProfileSharing=`	Controls whether a BlueZone profile (configuration file), can be used to start more than one BlueZone session. The default value is for profile sharing to be enabled. This means that end users can use a single BlueZone profile to open up multiple BlueZone sessions. If for any reason you don't want your end users to be able to start more than one BlueZone session for a profile, disable this feature by setting the value to `No`. Refer to Profile sharing feature for more information. Possible values are `Yes` to enable profile sharing and `No` to disable profile sharing. Default value: `ProfileSharing=Yes`
`SetPath=`	Controls the placing of the BlueZone installation directory into the Windows "PATH" during the BlueZone installation. This feature is especially helpful if you are using a third-party HLLAPI application in conjunction with BlueZone. Default value: `SetPath=No`
`EnablePowerKeys=`	Turns on the old power keys feature. Changing this value to `Yes` enables the old power keys feature and disables the new power pads feature. Refer to Enabling the power keys feature and Power pads for more information. Default value: `EnablePowerKeys=No`
`FIPSMode=`	Enables FIPS mode. Changing this value to `Yes` enables FIPS mode. Refer to Enabling FIPS mode support for more information. Default value: `FIPSMode=No`
`InstallScriptPlayerOnly=`	This setting is used in conjunction with the BlueZone Scripting CAB file (BZSC.CAB). The default setting allows end users to record and play scripts. Changing this value to `Yes` deploys only the BlueZone Script Player only (BZSHP.EXE) program. The BlueZone Scripting CAB contains both the BZSH.EXE and the BZSHP.EXE files. If the BlueZone scripting CAB is deployed with `InstallScriptPlayerOnly=` set to `No`, both files are deployed. When both files are present in the installation, end users can run and edit BlueZone scripts. By setting the value to `Yes`, only the BZSHP.EXE file is deployed. When only this file is present in the installation, end users can only run BlueZone scripts and not edit or record them. Note: The BZSC.CAB file must be part of the BlueZone distribution image in order for this setting to have any effect. Default value: `InstallScriptPlayerOnly=No`
`SessionManagerRunInTray=`	Controls whether or not the BlueZone Session Manager automatically displays in a user's Windows system tray. By default this value is set to `No`. Setting this value to `Yes` causes the BlueZone Session Manager to automatically run out of the Windows system tray whenever BlueZone Session Manager is launched. Default value: `SessionManagerRunInTray=No`
`ScriptRecordHiddenText=`	Controls the automatic password prompting feature. This entry is not included in the default setup.ini file and must be added manually. Refer to Controlling script passwords for more information on the automatic password prompting feature.