Specifications

SOFTWARE CONFIGURATION AE/LZB 119 1897 R1A
55
program (GUI.EXE). The Communications Interface program’s monitor window may or may not be visible per Configuration
Editor configuration; see section 6.2.2.2.3 or section 6.4 for additional details on the monitor.
Upon exiting the console application, operation will return to Windows NT Program Manager assuming no window
application switching has occurred since the console application started.
6.2.3.3 Manual Dispatch Manager Start-Up and Manual GUI Start-Up
Normally, this start-up configuration is only required during console troubleshooting/diagnostic periods. Configure as
follows:
1. Log-on to Windows NT via the user account name which desires this start-up configuration—typically the
Administrator user account.
2. If necessary, from Windows NT Program Manager remove (delete) the Dispatch Manager icon from the Startup
program group. The icon is shown in Table 3-1.
3. From the Configuration Editor’s Dispatch Manager dialog box, disable Start UI (start user interface) by clearing
(not checking) this check box. Save the change and exit the Configuration Editor. If necessary, refer to section
6.2.2.3 (page 34) for additional information on the Dispatch Manager dialog box.
4. Use any text editor such as the Windows NT Notepad to view/edit MAESTRO.INI. Verify the
Start CIM
Interface
setting in its
[DispatchManager]
section
=1.
Typically, no change is required since this is the
factory setting.
5. Test this start-up configuration as follows:
6. Double-click on the Dispatch Manager’s icon in the C3 Maestro’s program group. After the Dispatch Manger and
Communications Interface programs load, verify the GUI does not start—the “Initializing, please wait…” dialog
box does not appear. If desired, also use the Windows NT Task List to verify the GUI program is not running. The
Task List is accessible via a <Ctrl><Esc> keystroke sequence from the standard PC keyboard. The Dispatch
Manager and the Communications Interface programs will successfully start without an active serial control data link
to/from the CIM.
7. Now start the GUI program by double-clicking on its icon in the C3 Maestro program group. The icon is shown in
Table 3-1. Verify the GUI program starts-up by, at a minimum, observing the momentary appearance of the
“Initializing, please wait…” dialog box followed by the display of modules on module page A.
6.2.3.4 Automatic Dispatch Manager Start-Up and No (Local) GUI Start-Up after Windows NT User Log-On
This start-up configuration may be desired if the console’s Sever application (mainly the Dispatch Manager and the
Communications Interface programs) is run on a different computer than the Client application (the GUI program).
1. Repeat section 6.2.3.1 steps 1 and 2.
2. From the Configuration Editor’s Dispatch Manager dialog box, disable Start UI (start user interface) by clearing
(not checking) this check box. Save the change and exit the Configuration Editor.
3. Use any text editor such as the Windows NT Notepad to view/edit MAESTRO.INI. Verify the
Start CIM
Interface
setting in its
[DispatchManager]
section
=1.
Typically, no change is required since this is the
factory setting.
4. Test this start-up configuration by logging off of and then logging back onto Windows NT via the same user account
name. Verify the Dispatch Manager and the Communications Interface programs automatically start-up after user
log-on.
5. Start the GUI program either on the local computer or on the remote computer and verify successful console
operation. The console’s serial control data link to/from the CIM in the CEC/IMC, and the CIM itself must be
operational.