Specifications

SOFTWARE CONFIGURATION AE/LZB 119 1897 R1A
27
6.2.1.2 FIXSTR.INI
FIXSTR.INI stores most general operation and error text strings such as messages displayed in the console’s message
panel and the text icons displayed in standard communication modules. Changes via a text editor are not recommended.
However, some specialized applications may require minor text changes to this file. If so, the following information must be
observed:
Some keyword text strings in FIXSTR.INI have one or more “%d”, “%s”, “%X”, or other “%” format variable
identifiers. During operation, the console application fills these identifiers with appropriate text before the string is displayed
in the message panel. Identifiers should not be changed. Console application failure will result if improper changes are made.
In addition, since the area in which each string is displayed is a fixed length within the console’s message panel and standard
communication modules, adding to the length of a string may cause undesirable string truncation.
6.2.1.3 SCRCFG.INI And SCRCFG_0.INI Thru SCRCFG_9.INI
SCRCFG.INI is read by the console’s GUI program (GUI.EXE) when it starts. This screen initialization file stores all
screen-related configurations for the GUI such as the exact positioning of each display item on the screen, the number and
type of modules on each module page and nearly all display items’ color settings. It is the “active” screen initialization file.
Changes to SCRCFG.INI should only be accomplished via the UDS Configurator, a separately sold and distributed software
program.
SCRCFG_0.INI thru SCRCFG_9.INI store the same configuration information as SCRCFG.INI but these files are only
used during screen configuration edits within the UDS Configurator. Per user selection, one of ten (10) files is made (copied
to/as) the active screen initialization file (SCRCFG.INI) via the UDS Configurator.
See sections 5.2.1.2, 6.1.7, 0, and other sections within this manual for additional details. Also see the UDS Configurator
User’s Manual (AE/LZB 119 1896).
6.2.1.4 STATUS.INI
STATUS.INI stores definitions for all 128 possible RSM/RTT status codes. On a per code basis, it stores if the specific
code is set for RSM or RTT use, and the code’s descriptive text string. If RSM and/or RTT modules exist in the console
application’s current screen configuration, the console application reads STATUS.INI at start-up to determine each
RSM/RTT module’s respective text string. Each text string appears in the respective RSM/RTT module’s title bar during
console operation.
User-friendly edits to STATUS.INI can be performed using the Configuration Editor off-line program. Specifically, this
program’s Radio Status dialog box allows the user to set each status code to either RSM or RTT use and to define/change its
text string. For details on using the Configuration Editor for user-friendly INI file edits, see section 6.2.2 in this manual (page
28). For a detailed step-by-step procedure on setting-up RSM and/or RTT refer to section 6.2.7.3.3 in this manual (page 60).
RSM/RTT modules are added to and deleted from the console’s current screen configuration using the UDS Configurator
off-line program. See manual AE/LZB 119 1896 for complete details. To the UDS Configurator, STATUS.INI is a read-only
file. The UDS Configurator reads status code definitions stored in STATUS.INI and it uses these definitions during
RSM/RTT module additions. For example, each status code defined in STATUS.INI for RSM use appears in the UDS
Configurator’s Add RSM dialog box listing if the code has not previously been used for another RSM module (in the screen
initialization file being edited). The UDS Configurator user may then select one of the unused RSM status codes to complete
the RSM module addition.
6.2.1.5 PAGING.INI
PAGING.INI stores all paging related configurations such as specific paging codes, button text labels and button colors.
The console application reads this initialization file at start-up for use with the manual and preprogrammed integrated paging
features which it provides.
User-friendly edits to PAGING.INI can be performed using the Configuration Editor off-line program. This program’s
paging dialog boxes allow the user to define paging button properties. For example, one preprogrammed paging button may
be configured to page on conventional channel 129 with a GE Type 99 code plan and code number 101 and still another
preprogrammed paging button may be configured to page on conventional channel 130 with a Motorola™ Quik-Call II™
code plan and code number 345.