Specifications
SOFTWARE CONFIGURATION AE/LZB 119 1897 R1A
17
This software installation procedure will create a new common program group within Program Manager (if not already)
for the console’s program icons. These icons are shown in Table 3-1. As shown in the table, most files are copied to the
C:\MAESTRO directory on hard disk drive. The installation software automatically creates this directory if it does not exist.
If a re-installation or upgrade is performed, existing (old) console application files which are present in the
C:\MEASTRO directory are moved to a \SAVE.xxx sub-directory (C:\MAESTRO\SAVE.xxx), where xxx is the first unused
sequential number from 001 to 999. The installation software automatically creates this sub-directory if old console files exist
in C:\MAESTRO. For example, if no \SAVE.xxx sub-directory exists, a \SAVE.001 sub-directory will be created and the
existing console application files in C:\MAESTRO will be moved to it before the new files on the floppy disks are copied to
C:\MAESTRO. For another example, if \SAVE.001 and \SAVE.003 sub-directories exist but \SAVE.002 does not,
\SAVE.002 will be created and the existing console application files will be moved to it. After the re-installation procedure is
completed, if necessary, any important customer-related files such as SCRCFG.INI, PAGING.INI, STATUS.INI and in some
cases ENTITY.DAT, must be manually copied or moved from the appropriate \SAVE.xxx sub-directory to the C:\MAESTRO
directory before the console application is started. Moving/copying ENTITY.DAT is only required if the EDACS trunked
radio system is not equipped with a System Manager.
Since the UDS Configurator program is sold and distributed separately from the console application software, the console
application installation procedure does not install the UDS Configurator software or its ten (10) screen initialization files
(SCRCFG_0.INI thru SCRCFG_9.INI). It does install the active screen initialization file SCRCFG.INI. Therefore, the
console may be executed without installing the UDS Configurator using this factory-supplied default screen initialization file.
As supplied from the factory, this default file is set-up for a screen resolution of 640 x 480 pixels.
5.2.1.2 UDS Configurator Software
As previously stated, the UDS Configurator software is sold and distributed separately from the console application
software. Normally, it is not installed at the factory. It is distributed on one (1) 3 ½-inch floppy disk. The installation/re-
installation procedure follows. This procedure must be executed after the console application software installation
procedure. Also, do not use this procedure for upgrades:
1. If necessary, log-on to Windows NT via the Administrator user account.
2. If re-installing, use File Manager to back-up any important customer-specific screen initialization files
(SCRCFG_0.INI thru SCRCFG_9.INI and PAGE0.INI thru PAGE9.INI) which exist in directory C:\MAESTRO.
Ignore this step if this is a new installation.
3. Insert the UDS Configurator disk into the computer’s floppy disk drive (normally the A drive).
4. From Program Manager’s menu, select File…, Run… and then type in command line “A:\SETUP” in the respective
text box. Execute this command by clicking the <OK> command button or by pressing <Enter> key.
5. Follow any additional instructions which appear on the screen.
6. When the installation is complete, remove the floppy disk from the disk drive.
This UDS Configurator software installation procedure over-writes existing UDS Configurator-related files, if any, in the
C:\MAESTRO directory. See Table 3-1 for program icons and program file names.
6. SOFTWARE CONFIGURATION
6.1 WINDOWS NT
6.1.1 Dual-Boot Capabilities
Factory-delivered PCs used with the C3 Maestro console for Windows NT normally also have the MS-DOS operating
system installed on the computer’s hard disk drive. In this case, the computer is configured with dual-boot capabilities so it
can be booted-up with either MS-DOS or Windows NT. MS-DOS is not required to run the C3 Maestro console for
Windows NT. Note the following primary requirements for dual-boot capabilities of this type: