NOTE If
multiple sessions are open using the same Session Profile, the last session
to Save overwrites any settings saved from previously saved sessions Configuration Management
Starting with version 3.3, BlueZone has two modes of operation, Registry Mode and Profile Mode. Previously, BlueZone only operated in Registry Mode. These "modes" refer to the way BlueZone saves and recalls configuration settings. The selection of Profile Mode or Registry Mode is performed by your BlueZone Administrator.
Profile Mode - Profile Mode is now the default and recommended operation for BlueZone 3.3. BlueZone saves all of its settings in files, called Session Profiles. All parameters for each session are saved in a single file. BlueZone registers the file extensions with Windows during setup so simply clicking on a Session Profile file, launches BlueZone and loads the saved settings. Clicking the Session Profile multiple times results in multiple, identical BlueZone sessions.
Registry Mode - Registry Mode was in previous versions, the default mode of operation, and is now an optional mode. In Registry Mode, BlueZone saves all of its global and user settings in the Windows Registry. Each BlueZone Session (S1, S2, etc.) has a unique set of parameters that are loaded by clicking the BlueZone icon. The sessions launch in order, starting with the first unused session number. This was the default operation for BlueZone prior to version 3.3.
Session Manager has been completely redesigned for BlueZone 3.3, in order to support Profile Mode. When using Session Manager, the End User can view all of their saved Profiles and launch one or more sessions by clicking on the Profile entry. Session Manager uses the Configs folder in the user's working directory. Session Manager still works with Registry Mode and displays the session information in the same format it did in previous versions.
Converting from Registry Mode to Profile Mode is a function that is built into the Session Manager. The first time the Session Manager runs in Profile Mode, it checks the Registry for BlueZone configurations and converts them to Session Profile files. Once converted, the Session Profiles appear in the Session Manager. BlueZone uses the Registry Key name as the Session Profile file name. For example, Mainframe Display S1.ZMD.
Session Manager provides an interface to access, launch, and monitor BlueZone sessions. It is a Windows Tray application and is accessed by clicking the Session Manager tray icon. When the Session Manager is closed, it can be easily recalled with a single click on the tray icon.
To launch a BlueZone session using a Session Profile, select the Profile and double-click or click the Launch Session button.
To launch another identical session, perform the same action.
To launch a different session, select a different profile and double-click or click the Launch Session Button.
Starting New BlueZone Sessions - When starting new BlueZone sessions without specifying a Session Profile (using Session Manager or /F switch) the user is prompted to select an existing Session profile or create a new one.
Saving in Profile Mode - The configuration file, used to launch the session, displays on the session TitleBar. File:Save saves any changes made to the session to the Session Profile. File:Save As prompts the user to create a new file which will save all the current settings in the emulator.
BlueZone automatically creates a backup of the Session Profile each time a Save is performed. The files have the words Backup of pre-pended to the Session Profile filename.
Example: Test.zmd is backed up by Backup of Test.zmd
NOTE If
multiple sessions are open using the same Session Profile, the last session
to Save overwrites any settings saved from previously saved sessions
Opening Session Profiles in Profile Mode - File:Open in a BlueZone session loads the settings from the selected Session Profile into the session. The Session Profile name will display on the TitleBar.
Cloning Sessions in Profile Mode - To clone the current session, select File:Open Session:"Same Session Type" and BlueZone will launch a new session window using the Session Profile from the current session. Using the File>Open Session toolbar button is a convenient way to clone sessions.
Opening Different Session Types - File:Open Session:"Different Session Type" prompts the user to select a Session Profile for the new session.
Auto Launching Sessions using File:Properties:AutoLaunch - You can automatically launch up to four additional sessions by checking the checkbox and selecting the session type to launch. The Session Profile to use when launching each session must be specified in the "Switches" edit box using the /F command line switch.
Example: /fsessionfile.zmd
CAUTION! Failure
to specify a Session Profile results in an un-configured session launching.
Launching FTP from a BlueZone Session - BlueZone FTP sessions can be launched from a BlueZone emulator session by selecting Transfer:FTP from the BlueZone MenuBar. The first time an FTP session is launched, the user is prompted to select an FTP Session Profile. On subsequent FTP launches, the previously selected Session Profile will be used.
NOTE If
your BlueZone Administrator has supplied you with a BlueZone FTP profile
with the same name as the BlueZone Display profile that you are launching
the FTP session from, the FTP session will automatically start using that
profile without prompting you for a profile name.
As stated above, Registry Mode was in previous versions, the default mode of operation, and is now an optional mode. In Registry Mode, BlueZone saves all of its global and user settings in the Windows Registry. Each BlueZone Session (S1, S2, etc.), has a unique set of parameters that are loaded by clicking a BlueZone icon. The sessions launch in order, starting with the first unused session number.
BlueZone Configuration and the Windows Registry
In Registry Mode, BlueZone uses the Windows Registry to store and retrieve the configuration data associated with each session. It automatically creates a Registry Key with default values for each session once initiated. These default values are overwritten when any changes are made and the configuration is saved. The BlueZone configuration keys may be viewed with REGEDIT.EXE at the following location:
HKEY_CURRENT_USER\Software\SEAGULL\BlueZone