The [BlueZone] section of the default.ini file controls the following advanced configuration options:
[BlueZone]
RegistrationKey=
;0-Application Settings in HKEY_LOCAL_MACHINE, Session Settings in HKEY_CURRENT_USER
;1-All Settings in HKEY_LOCAL_MACHINE
;2-All Settings in HKEY_CURRENT_USER (default mode)
BaseRegistry=2
UsePersonalFolderAsWorkingDir=Yes
UseAllUsersCommonFolderAsWorkingDir=No
ProfileMode=Yes
ProfileSharing=Yes
;DesktopMode=desktop.ini ;Do not modify this line
EnablePowerKeys=No
FIPSMode=No
InstallForAllUsers=No
ExeMode=No
MajorVersion=6.2
Refer to Changing the base registry setting for more information on the different values.
Default value: BaseRegistry=0
If you want your users to be able to save their own BlueZone configurations, leave this value to Yes.
Default value: UsePersonalFolderAsWorkingDir=Yes
This means that the BlueZone working files are stored in the user's My Documents folder.
Default value: UseAllUsersCommonFolderAsWorkingDir=No
Possible values are Yes to enable profile mode and No to enable registry mode.
Default value: ProfileMode=Yes
If for any reason you do not want your 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 Preventing multiple session launch for more information.
Possible values are Yes to enable profile sharing and No to disable profile sharing.
Default value: ProfileSharing=Yes
Refer to Enabling power keys for more information.
Default value: EnablePowerKeys=No
Default value: FIPSMode=No
This setting is used to control how the Web-to-Host Control Module caches the emulators extensions.
When set to ExeMode=Yes, the Web-to-Host Control Module caches the emulators with .exe extensions instead of the default .pro extensions. It also sets the file association for each of the BlueZone configuration files so the user can double-click on a file to start the session, bypassing the need to go to the web server. When bypassing the web server using ExeMode, no checks are made to update BlueZone.
Default value: ExeMode=No