Specifications

AE/LZB 119 1897 R1A SOFTWARE CONFIGURATION
54
2. From Windows NT Program Manager, copy the Dispatch Manager icon to the Startup program group. This Startup
program group is created when Windows NT is installed. Perform the copy by opening both the Startup and the
C3 Maestro program groups and then, while holding the PC keyboard’s <Ctrl> key depressed, click-and-drag the
Dispatch Manager icon to the Startup program group. The Dispatch Manager’s icon is shown in Table 3-1.
3. From the Configuration Editor’s Dispatch Manager dialog box, enable Start UI (start user interface) by checking
this check box. Save the change, if required, and exit the Configuration Editor. Typically, no change is required since
this is the normal factory setting. 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 auto-start configuration by logging off of and then logging back onto Windows NT via the same user
account name. The console’s serial control data link to/from the CIM in the CEC/IMC and the CIM itself must be
operational. Verify the console application automatically 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.
With the above configuration, Windows NT automatically starts the Dispatch Manager program (CONSOLE.EXE) when
the new user sessions begins (at user log-on). The Dispatch Manager program then automatically starts the Communications
Interface program (MCOMM.EXE) and the Graphical User Interface 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 the Windows NT Program Manager assuming no window
application switching has occurred since the console application started.
NOTE
Since all console initialization files are shared (common) between all user accounts on a given console/computer,
changing any INI file will affect the console application configuration of all other user accounts.
6.2.3.2 Manual Dispatch Manager Start-Up with Automatic GUI Start-Up
This start-up configuration is typically preferred if the console application is not the computer’s sole intended usage. It is
the factory default configuration for the both the CONSOLE and the Administrator user accounts. Configure as follows:
1. Log-on to Windows NT via the user account name which desires this start-up configuration.
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, enable Start UI (start user interface) by checking
this check box. Save the change, if required, and exit the Configuration Editor. Typically, no change is required since
this is the normal factory setting. 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 simply double-clicking on the Dispatch Manager’s icon in the C3 Maestro’s program
group. The console’s serial control data link to/from the CIM in the CEC/IMC and the CIM itself must be
operational. Verify the console application automatically 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.
With the above configuration, starting the Dispatch Manager program (CONSOLE.EXE) from Program Manager causes
it to automatically start both the Communications Interface program (MCOMM.EXE) and the Graphical User Interface
NOTE