; QVS Configuration and Device Information file
;
; This file contains configuration information for Terminal Services
; (TS) and for Terminal Concentrator (TC) and may contain configuration
; information for other programs including non-QVS information. Future
; comments will refer to Terminal Services (TS), but will also apply
; to Terminal Concentrator (TC) except where noted.
;
; CDI File Configuration Options:
;
;
; An alternative to the use of QCDIFILE.MST
;
; Some users prefer to use a common configuration file located on the
; store controller. This file is named QCDIFILE.000 and is located
; on the Store controller in the ADX_UDT1: directory. The file enables
; the user to define both common and unique configurations for all
; TS terminal in a single file. Due to some initial startup limitations
; associated with the actual hardware configuration used on a specific
; terminal, TS must know a few basic configuration facts before it can
; properly boot and prior to reading the remote configuration file from
; the store controller. This local configuration file must exist in the
; installation directory on the local machine as file name QCDIFILE.IPL.
;
; Contained in QCDIFILE.IPL must be statements associated with the
; proper definition of Hard Totals, Keyboard, and 2x20 System Display
; of the terminal on which TS is installed. These definitions must
; match the actual peripheral hardware installed on the target machine
; to enable the terminal to boot up and read the remote configuration
; file, ADX_UDT1:QCDIFILE.000.
;
; The following statements should be included in QCDIFILE.IPL:
;
; physKeyboard="xxx"
; physNvRam="xxx"
; physNvRamSize="xx"
; systemDisplay_i="andisplay"
; physAndisplay="xxx"
;
; The parms within quotes must be valid for the machine configuration
; you are using since they cannot be changed.
;
; Important: Any statements used in QCDIFILE.IPL override similar
; statements used in QCDIFILE.000. This can be a source of confusion.
;
; The exception is the use of the statement:
; systemDisplay_i
;
; This statement allows you to use a different 2x20 display during
; startup than would be used during normal operation. It would be
; expected that a "systemDisplay" statement would be seen in the
; QCDIFILE.000 which would, in this case, override the "systemDisplay_i"
; statement in QCDIFILE.IPL. This might be useful with a common disk
; image for a variety of terminals that are then custom-configured with
; QCDIFILE.000.
;
;
; So, on startup, the following sequence is done:
;
; 2. If QCDIFILE.MST is not present, QCDIFILE.IPL located on the
; local terminal is read initially.
; 3. When the terminal is able to communicate with the controller,
; QCDIFILE.000 is read and any statements not already defined
; in QCDIFILE.IPL are added to the configuration.
;
;
; More detailed discussion of the startup sequence:
;
; Support files:
;
; LastIPL.dat
; This file contains the store number and terminal number used
; during the last ipl of TS. This file is used by TS when
; parsing CDI conditional statements (see below) that use
; store number or terminal number. Normally, TS gets the store
; number and terminal number from the hard totals device.
; LastIPL.dat allows keywords needed before devices come online
; to be within conditionals. Once the totals device does come
; online and if LastIPL.dat's storenum/termnum does not match
; what is found in totals, LastIPL.dat is updated and TS (but not
; TC) is restarted. For TC, LastIPL.dat is generated from the
; first terminal to come online.
;
; Support files when r::adx_udt1:qcdifile.000 is used:
;
; qcdifile.ipl (formerly qcdifile.sam)
;
; This file contains only those entries that are necessary to allow TS
; to come online to its controller. This file, if needed, is created
; during TS installation.
;
; To come online to a controller, TS needs a terminal number. To be able
; to enter a terminal number, the following devices are required: nvram,
; system display, keyboard. Qcdifile.ipl is used to configure the system
; so that these physical devices can be accessed.
;
; Additionally, you may optionally use:
;
; TermNum= to select the terminal number
; StoreNum= to select a specific store number
;
; TermNum and StoreNum should only be defined and used in a lab
; environment in which there may be multiple controllers having
; different store numbers. It allows for a sure connection to a
; specific controller.
;
; When there is no qcdifile.ipl, TS defaults to a device
; configuration where an rpam client is assumed to control
; the devices required for terminal number entry. The default
; physNvRamSize assumed is 1 KB.
;
; If a qcdifile.loc (see below) exists, qcdifile.loc is used
; in addition to qcdifile.ipl. When the same keyword value
; is found in both locations, the qcdifile.ipl version is taken.
;
; qcdifile.loc (formerly shrunk.dat)
; This file is an automatically generated, local copy of
; controller file, qcdifile.000. There needs to be a local
; copy in order for TS to access device and other configuration
; information early in its startup processing (prior to coming
; online to the controller).
;
; The configuration information in this file comes from two sources:
; QCDIFILE.IPL and QCDIFILE.000. QCDIFILE.000 resides on the controller.
; Information from QCDIFILE.IPL is first copied into this file, then
; data from QCDIFILE.000 is copied. However, if there are duplicate
; statements in both files, the statement in QCDIFILE.IPL takes
; precedence. To prevent confusion and to prevent startup problems,
; users should not specify any configuration statement in both the
; .IPL file and the .000 file.
;
; TS builds a new qcdifile.loc whenever it finds a qcdifile.000 on the
; controller that doesn't match the existing qcdifile.loc or if no
; qcdifile.loc exists. After building a new qcdifile.loc, TS
; automatically restarts so it can start with the proper settings
; (the restart is not necessarily visible to the user). Note that
; qcdifile.loc is deleted whenever a new terminal number is entered.
; It is also deleted if QCDIFILE.000 is ever deleted.
;
;
; The following are documentation-only versions of the cdi file:
;
; qcdifile.all (also formerly qcdifile.sam).
; This file documents all of the keywords supported by the
; current release of TS or TC.
;
; qcdifile.virtual_PC
; Example CDI file using pc and virtual devices. (pc keyboard,
; 2x20 mapped to pc display, pc file hard totals, virtual (emulated)
; cash drawer, virtual mod 4 printer).
;
;
;
; Format information:
;
; Comment lines are indicated with a ';'
; Option strings set to "" indicate default
;
;
; The CDI file can contain conditional expressions. Conditional expressions can
; be used to define a variable or to set any QCDIFILE option
;
; #if (conditional expression) then
; #define attribute
; or
; #if (conditional expression) then
; option="value"
;
; The expressions take the form:
; #if (conditional expression) then
; xxxxxx
; #elseif (conditional expression) then
; xxxxxx
; #else
; xxxxxx
; #endif
;
; A conditional expression in a CDI file is any logical expression that can be
; expressed in terms of:
;
; Store Number (STORE_NUM)
; Terminal Number (TERM_NUM)
; Controller ID (CTLR_ID) (used with TC when it runs on a 4690 or CSF controller)
; A previously defined attribute
;
; The logical operators &&, ||, and ! are supported as well as the relational
; operators >, >=, <, <=, ==, and !=.
; NOTE: Be sure to use ==, not = in this expression. Also note that none of the
; values are quoted. Example: #if (TERM_NUM == 16) then
:
; Example:
;
; #if ( (TERM_NUM >= 50) && (TERM_NUM < 60) ) then
; #define PHARMACY
; #endif
; #if PHARMACY then
; physPrinter= "4610"
; #else
; physPrinter = "7156"
; #endif
;
;
; ----------------------------------------------------------------------------[
; -------------------------------------------------------------------------
; SECTION: CDI FILE OPTIONS - ALLOWS USE OF CDI FILES IN ADDITION TO OR
; INSTEAD OF QCDIFILE.000.
;
; -------------------------------------------------------------------------
[CDI]
; -------------------------------------------------------------------------
; -------------------------------------------------------------------------
;
; The next keyword is only valid in QCDIFILE.000.
;
; cdiBasedOnTermNum
; Y or N, default = Y, If Y, QCDIFILE.nnn will be used if found.
; If N is specified, QCDIFILE.000 will be used instead.
;
; The next keywords are valid in any CDI FILE except QCDIFILE.IPL
;
; cdiAppendNnn
; Y or N, default = N. QCDIFILE.nnn options are appended to the
; QCDIFILE.000 options. Note that the "Nnn" in this parm does NOT
; represent a number. If "N" is specified, QCDIFILE.nnn replaces
; QCDIFILE.000. If this keyword is set to "N" in an appended file,
; the appended file replaces any parameters read in to that point.
;
; The next keyword is valid in any CDI FILE except QCDIFILE.IPL
;
; cdiAppendCDIFileList
; Specifies list of additional CDI files to process. These files are
; processed in sequence and can be nested (an appended file can call
; a list of appended files, all of which are processed before returning
; to the next file in the initial list). The sequence of files can have
; the same parm listed more than once. If this happens, the most
; recently-read version of the parm is made active. Recall also that
; any parms in the QCDIFILE.IPL file cannot be overridden. In effect,
; parms in the QCDIFILE.IPL file are read last. It is a good policy to
; use a unique naming convention for files contained in this list:
; example: pharmacy.cdi, video.cdi, etc
;
;
cdiBasedOnTermNum=""
cdiAppendNnn=""
cdiAppendCDIFileList=""
;
; END SECTION: CDI FILE OPTIONS ]
; --------------------------------------------------------------------------[
; --------------------------------------------------------------------------
; SECTION: TERMINAL SERVICES/TERMINAL CONCENTRATOR
[TS]
; --------------------------------------------------------------------------
; --------------------------------------------------------------------------
; --------------------------------------------------------
; Terminal Load Definition and Java Environment Information
;
; These options allow configuration of items such as
; the default terminal application and keyboard definition name.
;
; The special keyword GET_FROM_CONTROLLER is used to tell TS/TC to
; read this information from the 4690 controller terminal load definition
; file(s). If GET_FROM_CONTROLLER is not specified, the terminal
; application and keyboard definition name can be specified here and it
; is not necessary to have a terminal load definition on the controller.
; (It is necessary, however, to have terminals defined on the 4690
; conftroller "lan terminal definitions" under system configuration).
; Note also, that a "load configuration" or equivalent must be done to
; make TS/TC update this information. Simply changing the QCDIFILE and
; re-starting TS/TC is not enough.
;
; defaultApp1 is the name for the default starting application
; program. This replaces the default application name in defining
; the terminal load definition in the controller. Maximum of 24 characters.
; Make sure to include the "r::adx_ipgm:" if the file is to be loaded
; from the controller.
; keybDefName is the name of the keyboard definition file to be used for
; translating scan codes into function codes. Keyboard definition files
; are created under 4690 Terminal Configuration on the 4690 controller.
; termJava - indicates if 4960 java applications will be run. Set to '1'
; to enable java.
; defaultJapp1 is the Java class name for the default Java starting
; program. This replaces the default Java name in defining the terminal
; load definition in the controller. Maximum of 64 characters.
defaultApp1="GET_FROM_CONTROLLER"
keybDefName="GET_FROM_CONTROLLER"
; Java Redirection Information
;
; These options control the information that is returned to the terminal
; application at offset 59 of the terminal application status information
; structure when the ADXSERV function 4 (Get Application Status
; Inforamation) is executed. This byte shows which devices have been
; redirected to the Java application and what handlers and monitors have
; been installed by the Java application.
;
; NOTE: When a value for defaultJapp1 has been defined in the CDI file
; then ALL settings for Java Redirection Information must also
; be specified.
;
; iopRedirected
; "1" - I/O processor has been redirected to Java app
; "0" - I/O processor has not been redirected to Java app
;
; andisp1Redirected
; "1" - ANDISPLAY1 device has been redirected to Java app
; "0" - ANDISPLAY1 device has not been redirected to Java app
;
; crMonitorInstalled
; "1" - Java app has installed a cash receipt station monitor
; "0" - Java app has not installed a cash receipt station monitor
;
iopRedirected="0"
andisp1Redirected="0"
crMonitorInstalled="0"
; --------------------------------------------------------
; Java Classpath and JVM for Terminal Application
;
; prependJavaClasspath specifies an arbitrary string value that will be
; prepended to the classpath that is sent to the JVM when the
; Java program is started
; javaJVM specifies the .EXE name of the java runtime environment that is
; is to be used to run java programs. There are at least three
; different runtime names popularly in use: JRE.EXE, JVIEW.EXE,
; JAVA.EXE. JRE.EXE is the default. A fully qualified path is
; optional.
; javaJVMArgs specifies an arbitrary string value that will be
; passed to the JVM when a java program is started. This string will be
; inserted in between the name of the JVM program and the '-cp' classpath
; specification.
; debugClassName & debugClassPath
; these settings are meant to be used by QVS developers to help debug
; 4690 java applications. They allow you to specify an application
; specific classpath that will be used to start the JVM. For example. if
; you were to run the java class 'MainPgm [args] ...' you could override
; the classpath being used to run the JVM (either from the 4690
; configuration files or from the CDI javaClasspath setting) by setting
; the variable debugClassName="MainPgm" and then defining the varible
; debugClassPath="xxx". "xxx" would then be used as the class path when
; the JVM to run MainPgm is started.
;
prependJavaClasspath=""
javaJVM=""
javaJVMArgs=""
debugClassName=""
debugClassPath=""
; ----------------------------------------------------------------------------
; File Caching Support
;
; TS supports copying and keeping up-to-date certain controller-based files
; to the local hard drive. Keeping local copies makes terminal loading
; significantly faster. By default, the following files are copied:
;
; -Terminal sales application files
; -Terminal sales shared runtime libraries
; -Java class archive files specified in the java class path
; -X and Y ramdisk preload archives
;
; You can disable all file caching logic by specifying "NONE" as the
; value for the FileCacheFiles setting. The default value for this
; setting is 'AUTO'
;
; Also, you can specify additional files to be cached by using the
; FileCacheAdditionalFiles setting. List the additional files to be
; cached enclosed in quotes and seperated by commas. For example:
;
; FileCacheAdditionalFiles="R::JAVALIB:XYZ.GIF,R::JAVALIB:ABC.JAR"
;
FileCacheFiles="AUTO"
FileCacheAdditionalFiles=""
; ---------------------------------------------------------------------------
; TCC/IP Information
;
; tccipEnable - Set this to 1 to use TCC over IP instead of over DLC. The
; default is 0 to use DLC.
;
; tccipTTL - This is the "time to live" value. This parameter controls how
; many routers TCCIP packets will be sent across. The default value for
; this is 1.
;
; tccipAckPort - This defines the TCCIP Ack port value. The default is 4692.
;
; tccipMultiCastPort - This defines the TCCIP Multicast port value. The
; default is 4691.
;
; tccipMultiCast_Addr - This defines the TCCIP Multicast address value for
; the 4690 controller. The default is "224.46.90.1".
tccipEnable=""
tccipTTL=""
tccipAckPort=""
tccipMultiCastPort=""
tccipMultiCast_Addr=""
;----------------------------------------------------------------------------
; ForceTsfUpdate - by default, TSF will detect maintenance on the store
; controller. IF the maintenance level on the contoller is
; more recent than the current TSF level, then maintenance
; file (TSNT_MNT.UPD) from the controller is downloaded to
; the terminal and the new maintenance level is applied.
;
; ForceTsfUpdate="y" directs TSF to apply any maintenance
; level from the controller as long as it a) does not match
; the current terminal level, and b) the controller
; maintenance level is newer than TSF 2.00.00.20. Coding "y"
; will allow an older level of TSF maintenance to be applied
; over the current terminal level.
;
; ForceTsfUpdate="n" directs TSF to never apply maintenance
; found on the controller. This option should only be used
; in a lab environment where the terminal is being switched
; from one controller to another.
;
; ForceTsfUpdate="" directs TSF to apply controller
; maintenance if the controller maintenance version is
; newer than the terminal maintenance version.
; Default:
ForceTsfUpdate=""
;----------------------------------------------------------------------------
; AgeOutTsfDumps - by default, TSF will maintain up to 5 diagnostic dump
; files on the store controller. These files are named
; TSFL_nnn.Dmm, where nnn is the terminal number and mm is
; the dump occurrence. Once the maximum number of dumps
; have been transferred to the store controller, additional
; dumps will be discarded until the controller based dumps
; have been retrieved. By setting AgeOutTsfDumps keyword to
; "y", existing dumps on the store controller will be aged
; out as new news are created at the terminal. Thus with
; AgeOutTsfDumps="y" active, once the MaxDumps count is
; reached, the oldest dump file, TSFLnnn.D01, will be deleted
; and TSFL_nnn.D02 renamed to TSFL_nnn.D01; TSFL_nnn.D03
; renamed to TSFL_nnn.D02 and so on.
; Default:
AgeOutTsfDumps=""
;
; tcStartingTermNum parm not included in configuration utility - ltb 8/7/03
; ----------------------------------------------------------------------------
; Other Options
;
; storeNum - identifies the store number of the controller that TS/TC will
; connect to. This allows for multiple controllers to exist on
; the same lan such as in a lab environment. It only makes sense
; to use this option with a local QCDIFILE.MST. It should not be
; used when QCDIFILE is used from the 4690 controller. For this
; case, the store number is provided to the terminal through normal
; 4690 controller-to-terminal communications.
; termNum - again, this is probably just for the lab. It specifies the
; terminal number to be used, thus avoiding the "Z001" process.
; ctlrId4690 - used rarely for stand-alone TSF and TC to set the 2 character
; controller ID which would normally be obtained from the
; controller. TS/TC defaults to 'CC' if this value is not set.
; display - controls whether or not TS/TC display console is shown or hidden
; at startup. Default is to show. Set to 'Hide' to hide display.
;
; vdisplay - controls whether or not TS/TC VDISPLAY console is shown or hidden
; at startup. Default is to show. Set to 'Hide' to hide the
; VDISPLAY console. This keyword has meaning only when the
; physVdisplay keyword is used to define a VDISPLAY device as
; active.
; disableBeep - Former TERM_CMD_LINE1=-B option. The default is "" (beep is on)
; To turn off the system beep, set the value to "y".
;
; loadDelay - Former TERM_CMD_LINE1=Ldelay,nnn option
;
; monKeybWrites - Former TERM_CMD_LINE1=W option. The default is OFF ("").
; "Y" turns it on.
; dateTimeChanges - By default, TS/TC updates the system date/time on
; command from the 4690 controller. Set this option to 'N' to disable.
; javaConsoleAlwaysShow - Controls how and when the java console video session
; is made visible. Normally, the java console is visible for text mode
; java programs and completely hidden for graphics mode java programs.
; Setting this option to "Y" causes TS to not completely hide the java
; console session. Setting to "N" forces the normal behavior. This setting
; defaults to "N" when TS/TC tracing is off and defaults to "Y" when
; TS/TC tracing is on. This setting is only meaningful in terminals
; configured to use 4690 java applications.
; javaConsoleTitle - string used as title of the java text-mode console.
;
storeNum=""
termNum=""
ctlrId4690=""
display=""
vdisplay=""
disableBeep=""
loadDelay=""
monKeybWrites=""
dateTimeChanges=""
javaConsoleAlwaysShow=""
javaConsoleTitle=""
;----------------------------------------------------------------------------
; IbmAppTermType
; used to specify the terminal type returned to the application on an
; ADXSERVE, Function 4 call. The possible values supported are:
;
; IbmAppTermType="1" - 4693 terminal type returned
; IbmAppTermType="2" - 4694 terminal type returned
; IbmAppTermType="3" - 4683 terminal type returned
; IbmAppTermType="5" - SurePos terminal type returned
;
; The Default value is IbmAppTermType="3"
IbmAppTermType=""
;----------------------------------------------------------------------------
;IbmKybDef keyword
;
; - set to "Y" to force TS to use the remote IBM keyboard definition
; files, even though the keyboard is defines as a virtual device.
; This allows a client appl to originate keyboard switch key
; values which will be translated by TS using the controller
; keyboard definition files.
; This keyword is not included in the config utility due to its
; rare and very specific useage. ltb 8/7/03
IbmKybDef=""
;
; LanAdaptID keyword
;
; - this keyword is used when more than 1 LAN adapter definition
; is active on the machine where TS is installed. Without this
; keyword, TS always defaults the DLC binding to adapter 0 in
; machine. This keyword can be used to specify the LAN adapter
; number to be used for TCC communications.
; Example
; LanAdaptID = "01"
;
LanAdaptID = ""
;----------------------------------------------------------------------------
;4820KeyLock keyword
;
; - set to "Y" to force TS to recognize an IBM 4820 Touch Device
; with no keyboard, but with a Manager Keylock Feature as the
; actual keylock. A virtual keyboard is configured to TS, but the
; TS client owns the 4820 as a touch input device.
4820KeyLock=""
;----------------------------------------------------------------------------
;TotlDvr keyword
;
; - set to "N" to prevent the TOTAL1/TOTALS driver from being loaded
; by TSF. Default is to always load the TOTAL1/TOTALS internal
; drivers.
TotlDvr=""
;----------------------------------------------------------------------------
;ReqDevTimeOut keyword
;
; - Force a TSF timeout while waiting on required POS devices. By
; setting ReqDevTimeOut="nn", the user is directing TSF to wait
; no more than "nn" seconds for all required POS devices
; (display, keyboard, hard totals, printer, and cash drawer) to
; report online. Once this timeout occurs, if all required
; devices are NOT online, TSF will proceed with the terminal
; load. This will enable TSF to locate an updated QCDIFILE on the
; store controller which accurately defines the current POS device
; configuration. This parameter should ONLY be used in a lab
; environment where POS devices are routinely being changed, and
; where the QCDIFILE file is being accessed from the store
; controller. The default for this keyword is NEVER, meaning that
; TSF will wait until all required POS devices report online.
; Valid values for this keyword are: "20" (20 seconds) up to
; "99" (99 seconds).
;
; Note: This parm replaces the former "loadDelay" parm which was ;
; a replacement for the TERM_CMD_LINE1 parm: Ldelay,nnn ;
;
ReqDevTimeOut="" ; Preferred = 20 (no 485 devices)
; Preferred = 45 (w/485 devices)
;
;----------------------------------------------------------------------------
;IPL Status Messages
;
; iplStatus - set to "Y" to have TS/TC display information about what it is
; doing during IPL. Setting specifically to "N" disables IPL
; status. The default is for IPL status to display whenever
; tracing is on at TS/TC startup. Typical IPL status messages
; are:
;
; "Store Num sss"
; "Term Num ttt"
; "Reading QCDIFILE.SAM"
; "Reading QCDIFILE.MST"
; "Reading QCDIFILE.000"
; "LANTCC"
; "Finding CTLR"
; "CTLR sss found mmmmmmmmmm"
; "CTLR sss found mmmmmmmmmm" - will display multiples if more
; than one controller is found.
; sss is store number.
; "Session with CC Established"
; "Reading KEYMAP.000"
; "Reading ADXCSCTF" - terminal config
; "Reading ADXCSCKF" - store config
;
;
; iplStatusDelay - TS/TC will wait this many milliseconds after displaying
; each IPL status message to give the user a chance to read
; them. The default is 2000 (2 seconds).
; iplPosDevice - TS If set to "Y", then status msgs relative to POS device
; searches will be displayed prior to the 2X20 display
; driver being installed.
;
iplStatus="" ; Preferred = Y
iplStatusDelay="" ; Preferred = 0
iplPosDevice="" ; Preferred = Y
; --------------------------------------------------------
; TS/TC Tracing Options
;
; traceCmdLine - controls TSF tracing if no tracing was specified on the
; TPROCESS command line.
;
; Possible values:
; "" - default
; "-t" - same as '-t' TPROCESS option
; "-tx" - same as '-t' but delayed until application has loaded
; "-v" - samve as '-v' TPROCESS option
; "-vx" - same as '-v' but delayed until application has loaded
; "-m[nnnnn]" - big memory trace buffers option. nnnnn is size in
; kb of per-process trace buffer for most processes.
; The default for nnnnn is 640. Some processes can get
; extra large trace buffers. These processes get 10Mb
; trace buffers by default.
;
; Note that the options specified here can take any form that the
; trace options take on the TPROCESS command line. This includes
; specifying tracing for specific tasks such as "-t4".
; Note that use of -v or -vx is not recommended except for use in
; the QVS LAB because -t provides more information and/or smaller
; trace files. Some initialization tracing my be missed when compared
; to using the options from the command line.
;
; traceXtraBigTrcBuff - list of processes that get extra large trace
; buffers. Without -m, size is 500KB. Processes are listed by their
; EPTDA 'procname'. Multiple processes, separated by spaces or commas
; can be specified. An example:
; traceXtraBigTrcBuff="RIOAM_CTL IOP_TRIG0".
;
traceCmdLine=""
traceXtraBigTrcBuff=""
; --------------------------------------------------------
; Display Case Options
; These options apply to ANDISPLAY/ANDISPLAY2/ANDISPLAY3
;
; "0" all uppercase (default)
; "2" display mixed
;
; Note 1: To replace the environment setting TERM_CMD_LINE1=-dDISPLAY1,case
; use casefmt="2"
casefmt=""
; Control physical line I/F for the ASYNC connection where
; a pinpad type device does not have physical HW lines to raise
; either DTR or CTS signals.
;
; use
; raiseSerDtr = "N"
; to force TS to simulate report the true DTR/DSR line values. Default is
; to always report these values as high to the serial GETLONG request.
;
; Default: report DTR/DSR lines as high.
; ------------------------------------------------------------------
; Mag Stripe Reader Options
;
; appMsrTracks - This option is used to specify the MSR track capabilities
; expected by the application. Its format is "nttt" where
; n is number of tracks that the MSR device can read and 'ttt'
; corresponds to tracks 1, 2, and 3 respectively. Each 't'
; position can be either 0 or non-zero indicating if that
; track can be read. Here are some examples:
; "3123" - three track MSR; read tracks 1, 2 and 3
; "2120" - two track MSR; read tracks 1 and 2
; "1020" - single track MSR; read only track 2
; "2023" - two track MSR; read tracks 2 and 3
; "3120" - three track MSR; read tracks 1 and 2
; "0000" - no MSR
;
; the default for appMsrTracks is "2120"
;
; physMsr - The following options are possible:
; "virtual" - TS should install virtual support for this
; device.
; "POSS" - TS should install IBM POSS support for this
; device
; "rpamClient"
;
appMsrTracks=""
physMsr=""
; ----------------------------------------------------------------------
; Printer Options
;
; These options are used to specify the IBM printer type and features
; expected by the 4690 application and to specify information related
; to the physical printer.
;
; appPrinter - mod2, mod4, mod4r, 4610, 4610_TI4,
; Note: 4610_TI4 is only recognized when physPrinter is set to
; "virtual". It tells the virtual 4610 driver to report model
; TI4 as the 4610 model type instead of model TI2. Other
;
; physPrinter - mod2, mod4, 4610, 7193, 7194, 7156, 7158, K580, 7167,
; 7197, E5000, E6000, virtual, A758, POSS,
; rpamClient
; Notes:
; "POSS" - TS should install IBM POSS support for this device.
; POSS will detect and report the actual printer model.
; "rpamClient" can be used by itself or it can precede another
; printer type (for example rpamClient7158)
; physPrinterPort - used to specify COM port number of attached printer.
; Set to 'USB' for usb attach. Note 'USB' is supported only for
; the following physPrinter types: 4610, E6000.
; Examples: "1" or "USB"
; physPrinterBaud - used to specify baud rate of attached printer
; valid values are 9600, 19200, 38400, 57600, 115200
; physPrinterECLevel - used to override 4610 EC Level when emulating
; a 4610 on NCR printers. Valid values are like "24", "36". This is
; currently only supported in CE environment.
; physPrinterCodePage - indicates which code page to select when using
; a 7193, 7194, 7156, 7158, K580, 7167, 7197, E5000 or E6000 to
; emulate an IBM Model 4 printer. Only valid when appPrinter is
; set to "mod4". Valid values and code pages they correspond to are:
; 437 - US English
; 850 - Multilingual
; 852 - Slavic
; 860 - Portuguese
; 863 - French Canadian
; 865 - Nordic
; 858 - Multilingual with Euro Symbol
; 866 - Cyrillic
; (Ex: physPrinterCodePage="865" selects Nordic code page).
;
; rpamPrinterFilter - set to Y if RPAM client is used and wishes to
; monitor output to a printer controlled by directly by TS.
; This keyword is ignored if physPrinter setting starts with
; 'rpamClient'. The default for this keyword is "N".
;
;
; NOTE1: if physPrinter is specified as 4610, then physPrinterBaud is
; ignored and the 4610 MUST be set at 19,200 BAUD Rate.
;
; NOTE2: if appPrinter is specified as 4610, then physPrinter must be
; specified as either 7158, 7194, or 4610. All other choices
; for physPrinter are invalid and TS will panic at startup.
;
; These options are not necessarily required. For example, TS will
; auto-detect the attached printer type if the printer is attached via
; RS-485. These parameters are only used when auto-detection of the
; device is not possible such as when the device is being emulated in
; software or with a totally different device.
;
;
appPrinter=""
physPrinter=""
physPrinterPort=""
physPrinterBaud=""
physPrinterECLevel=""
rpamPrinterFilter=""
; ---------------------------------------------------------------------------
; Display device options
;
; The following options are possible:
;
; systemDisplay - defines a display device as the one used by the
; cashier. This is the display used by the I/O Processor
; and Application for prompts and messages. There is no
; default for this keyword (it should be specified).
; A non-null value in this keyword causes the deprecated
; 'andisp' and 'vdisp' keywords to be ignored and all
; display configuration to come from these keywords.
;
; Note that under TS and TC, system display data may also
; be mirrored to the workstation video display. These
; 'mirror' displays are activated if a) the workstation
; video display is not already configured as the 4690
; pos system display and b) the TS/TC console screen is
; configured as "show" and not "hide" during installation.
;
; "andisplay"
; "andisplay2"
; "vdisplay"
;
; systemDisplay_i - same description as systemDisplay but this one is
; meant for use in .ipl files. systemDisplay_i will
; be used only when systemDisplay is not found. Use of
; an _i keyword allows the controller CDI keyword to
; override the .ipl version.
;
; physAndisplayX
; "none" - not used (default)
; "POSS"
; Recommend POSS with no parms be unused since, with
; only one display, it will work with lowest or highest
; parms. That way, configurator only asks where you plug it
; If you are wrong and one is used, no big deal - ltb 8/7/03
; "POSS highest" - The highest designation corresponds to the address
; of the device on the RS485 device channel. The
; address of a device is based on two things: the
; device itself and whether it is plugged into an 'A'
; port or a 'B' port. 'A' port addresses are even
; (and therefore lower) while 'B' port addresses are
; odd.
; "POSS lowest" - See "highest" description above.
; "virtual1" - map 2x20 display to first (or only) workstation
; (vga) display
; "virtual2" - map 2x20 display to second workstation display
; "virtual" - virtual display device (doesn't map to any physical)
; "rpamClient"
;
;
; physVdisplayX
; "none" - not used (default)
; "virtual1" - map VDISPLAY display to first (or only) workstation
; (vga) display
; "virtual" - virtual display device (doesn't map to any physical)
; "rpamClient"
;
; vdisplayXDefaultMode (required if physVdisplayX is used)
; "12x40"
; "16x60"
; "25x80"
; "16x80"
;
; vdisplayXWindowMode
; "FullScreen" (default)
; "Windowed"
;
; vdisplayXWindowTitle
; "" (default)
; "Any Window Title Text"
;
; vdisplayXShowCursor
; "N" (default)
; "Y" Mouse cursor is visible on the VdisplayX console
;
;
; coverWindowsTaskbar
; "Y" (default) - cover the Windows taskbar with the VDISPLAY full
; screen window (take up the entire visible screen
; area).
; "N" (default) - do not cover the Windows taskbar with the VDISPLAY
; full screen window.
;
systemDisplay=""
systemDisplay_i=""
physAndisplay=""
physAndisplay2=""
physVdisplay=""
vdisplayDefaultMode=""
vdisplayWindowMode=""
vdisplayWindowTitle=""
vdisplay1ShowCursor=""
physAndisplayProfile=""
physAndisplay2Profile=""
; ------------------------------------------------------------------------
; Cash Drawer Option
;
; Specifies information on how the cash drawer is attached.
;
; The following options are possible:
;
; physCashDrawer
; "virtual" - TS should install virtual support for this device.
; "printer" - Indicate that cash drawer is connected to the printer.
; Note that in some environments, this is the default
; and specifying "printer" is not required.
; "POSS" - TS should install IBM POSS support for this device.
; "rpamClient"
;
physCashDrawer=""
; ------------------------------------------------------------------------
; Scale Options
;
; Specifies information about the scale device.
;
; The following options are possible:
;
; physScale
; "virtual" - TS should install virtual support for this device.
; "POSS" - TS should install IBM POSS support for this device.
; "rpamClient"
;
physScale=""
; ------------------------------------------------------------------------
; Keyboard Options
;
; Specifies information about the keyboard device.
;
; The following options are possible:
;
; physKeyboard
; "virtual" - TS should install virtual support for this device.
; "POSS" - TS should install IBM POSS support for this device.
; "rpamClient"
;
;
physKeyboard=""
; ------------------------------------------------------------------------
; Scanner Options
;
; Specifies information about the scanner device.
;
; The following options are possible:
; "virtual" - TS should install virtual support for this device.
; "POSS" - TS should install IBM POSS support for this device.
; "rpamClient"
physScanner=""
; ------------------------------------------------------------------------
; NVRAM Options
;
; Specifies information about the NVRAM (hard totals) device.
;
; physNvRam - The following options are possible:
; "virtual" - TS should install virtual support for this device
; (TS uses BATPRMEM.DAT file as NVRAM).
; "POSS" - TS should install IBM POSS support for this device.
; "rpamClient"
;
; physNvRamSize - by default, TS/TC reports NvRam size as 1K and terminal
; type as 4683. By setting this option to "16", you are
; enabling NvRam size of 16KB (4693/4694). By setting this
; option to "99", you are enabling CMOS size of 99KB,
; corresponding to a SurePos 700 series terminal
;
physNvRam=""
physNvRamSize=""
; ------------------------------------------------------------------------
; Serial Port (incluing 485 tailgate) Options
;
; Specifies information about the serial port devicies (pinpads, mag stripe,
; etc).
;
; physSerialX - A non-null value in any of these keyword causes
; all deprecated "cXtohdwr" and "cXOverride" keywords to be
; ignored.
;
; The following options are possible:
; "virtual" - install virtual support for this device
; "POSS 0xNN" - install IBM POSS support for this device. The 0xNN
; value is as follows and must be present.
; PosDEVICE_RS232_25A 0x64
; PosDEVICE_RS232_25B 0x65
; PosDEVICE_RS232_23A 0x68
; PosDEVICE_RS232_23B 0x69
;
; "COMx" - TS will support by mapping PC COM port X where X can
; be 1 - 15.
; "rpamClient" - This value is currently on valid for physSerial1 and
; physSerial2.
;
; physSerialXOverride - Optionally override .286 application OPEN SERIAL
; RS-232 parameters
;
; Example: To force settings for application port 3 to 9600 baud
; even parity, 7 data bits, 1 stop bit specify:
;
; physSerialXOverride="9600,E,7,1"
;
; AppSerialXReportXmitPending - Optionally allow reporting of actual device
; transmit pending status.
;
; AppSerialXReportXmitPending="Y"
;
AppSerial1ReportXmitPending=""
AppSerial2ReportXmitPending=""
AppSerial3ReportXmitPending=""
AppSerial4ReportXmitPending=""
;
; Notes: 1) These overrides are likely never used for RS-485 attached
; devices
; 2) By default, TS will override any application baud rates less
; than 4800 to 4800.
;
physSerial1=""
physSerial2=""
physSerial3=""
physSerial4=""
physSerial1Override=""
physSerial2Override=""
physSerial3Override=""
physSerial4Override=""
; --------------------------------------------------------
; TS/TC Detailed Trace Control
;
; See TRCHEUR.BAT for additional definitions. These definitions are meant
; to be used under direction of a QVS person. Not all options are
; supported even if documented here. The options that are most likely to
; be used are csftsfTraceCtrl options/offsets 2 and 4 which control max
; trace buffer and file sizes.
;
; Offset meanings for csftsfTraceCtrl:
;
; 0 turn on Base Kernel Tracing (default is 1)
; 1 turn on Extended Kernel Tracing (default is 0)
; 2 Log file size
; 0 = .5MB 4 = 10 MB (default if #3=1)
; 1 = 1MB 5 = 20 MB
; 2 = 2MB F = 250 MB
; 3 = 5MB (default)
; 3 Log file instances
; 0 = Log per process (default)
; 1 = Single Combined Log File (CSF1.LOG)
; 4 Memory trace buffer size (most processes)
; 0 = 0 KB (no tracing)
; 1 = 8 KB 5 = 128 KB
; 2 = 16 KB
; 3 = 32 KB (default)
; 4 = 64 KB
; 5 Global trace buffer size
; 0 = 0 KB (no tracing) (default)
; 1 = 128 KB
; 6 File read/write max amount of data traced
; 0 = 0x20 bytes (default for in-memory tracing)
; 1 = 0x30 bytes
; 2 = 0x40 bytes
; 3 = 0x80 bytes (default for -t tracing)
; F = 0x7FFFFFFF bytes
; 7-10 Future Use (default to ?)
; 11 turn on NOABORT/OKABORT Tracing (default is 0)
; 12 turn on NODISP/OKDISP Tracing (default is 0)
; 13 turn on KENTER Tracing (default is 0)
; 14 turn on MX Tracing (default is 0)
; 15 turn on ENABLE/DISABLE Tracing (default is 0)
; 16 turn on base DISK Tracing (default is 1)
; 17 turn on extended DISK Tracing (default is 0)
; 18 turn on base PIPE Tracing (default is 1)
; 19 turn on extended PIPE Tracing (default is 0)
; 20 turn on base RPAM Tracing (default is 1)
; 21 turn on extended RPAM Tracing (default is 0)
;
; 1 2
;; 0123456789012345678901
;csftsfTraceCtrl="??????????????????????"
; 1
;; 01234567890123456789
;tsfTraceCtrl="????????????????????"
; ---------------------------------------------------------------------------[ ;#DEP
; --------------------------------------------------------------------------- ;#DEP
; !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ;#DEP
; !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ;#DEP
; OBSOLETE options (options that should no longer be used but which are ;#DEP
; supported for backward compatibility) ;#DEP
; ;#DEP
; ;#DEP
; CFG_LVL_00: Pre-3.0.0.0 config information. ;#DEP
; This can include .ini files as well as keywords that are made obsolete ;#DEP
; by CFG_LVL_01. ;#DEP
; ;#DEP
; CFG_LVL_01: 3.0.0.0 config information. (see qcdifile.ts for full info) ;#DEP
; New keywords: physAndisplay, physAndisplay2, physCashDrawer, ;#DEP
; physKeyboard, physMsr, physNvRam, physScale, ;#DEP
; physScanner, physSerial1, physSerial2, physSerial3, ;#DEP
; physSerial4, physVdisplay, systemDisplay, ;#DEP
; systemDisplay_i, appMsrTracks ;#DEP
; Obsoleted files: .INI files, qcdifile.sam, shrunk.dat ;#DEP
; Obsoleted keywords: NoRS485, andisp, vdisp, c?tohdwr, c?override, ;#DEP
; cmos16Kb, VDisplayWindow, VDisplayTitle, ;#DEP
; physvdisplay1, physPrinterCashDrawer, msrTracks, ;#DEP
; com1pir, com2pir ;#DEP
; ;#DEP
; !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ;#DEP
; !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ;#DEP
; --------------------------------------------------------------------------- ;#DEP
;#DEP
;---------------------------------------------------------------------------- ;#DEP
;NoRS485 keyword ;#DEP
; ;#DEP
; - set to "Y" to force TS to bypass checks for a POSWIN prereq. ;#DEP
; before starting. This keyword would be coded when all normal ;#DEP
; RS485 type devices are to be managed by the RPA sub-system, ;#DEP
; instead of the POSWIN sub-system. ;#DEP
;NoRS485="" ;#DEP
;#DEP
;#DEP
; cmos16Kb - by default, TS/TC reports CMOS size as 1K and terminal type as ;#DEP
; 4683. By setting this option to "Y", you are enabling ;#DEP
; CMOS size of 16KB and terminal type as 4693 ;#DEP
;cmos16Kb="" ;#DEP
;#DEP
; --------------------------------------------------------------------------- ;#DEP
; 2x20 Display Options ;#DEP
; ;#DEP
; If you are using an application which requires support ;#DEP
; for 2x20 displays (drivers ANDISPLAY: or ANDISPLAY2: or ANDISPLAY3), ;#DEP
; you can tailor their configuration using the "wxyz" parameters as ;#DEP
; follows: ;#DEP
; ;#DEP
; ;#DEP
; w = 0 Default behavior: ;#DEP
; If there is one or more physical displays, ;#DEP
; The lowest address or only display is ANDISPLAY ;#DEP
; Else ;#DEP
; No ANDISPLAY will be installed. ;#DEP
; = 1 (ANDISPLAY is mapped to workstation VGA display) ;#DEP
; = 2 (ANDISPLAY is lowest address or only 2x20 display) ;#DEP
; = 3 (ANDISPLAY is highest address or only 2x20 display) ;#DEP
; x = 0 Default behavior: ;#DEP
; If w = 1 AND if there is a physical 2x20 display, ;#DEP
; the physical display is ANDISPLAY2 ;#DEP
; Else, if w = 2 AND there are 2 physical displays, ;#DEP
; the highest address display is ANDISPLAY2 ;#DEP
; Else, if w = 3 AND there are 2 physical displays, ;#DEP
; the lowest address display is ANDISPLAY2. ;#DEP
; Else, ;#DEP
; No ANDISPLAY2 will be installed. ;#DEP
; = 1 (ANDISPLAY2 is mapped to workstation VGA display) ;#DEP
; = 5 (ANDISPLAY2 is virtual and not mapped to any physical display ;#DEP
; that is controlled by TS) ;#DEP
; y = 0 Default behavior: ;#DEP
; No ANDISPLAY3 will be installed. ;#DEP
; z = 0 Default behavior: ;#DEP
; If any VDISPLAY is configured as the System Display, ;#DEP
; no ANDISPLAY's are the System Display. ;#DEP
; Else ;#DEP
; ANDISPLAY is System Display. ;#DEP
; = 1 (ANDISPLAY is System Display) ;#DEP
; ;#DEP
; Note 1: "System Display" means cashier display. This is the ;#DEP
; display used by the I/O Processor and Application for ;#DEP
; prompts and messages. ;#DEP
; ;#DEP
; Note 2: To replace the environment setting TERM_CMD_LINE1=-dDISPLAY1,none ;#DEP
; use andisp="1001" ;#DEP
; ;#DEP
; The default enables ANDISPLAY as the system display ;#DEP
; (w=2, x=0, y=0, z=1) ;#DEP
; ;#DEP
;andisp="2001" ;#DEP
;#DEP
; -------------------------------------------------------- ;#DEP
; Full Screen Video Options ;#DEP
; ;#DEP
; If you are using an application which requires support ;#DEP
; for FULL SCREEN VIDEO (drivers VDISPLAY: or VDISPLAY2:), ;#DEP
; you must activate the "xy" parameters as follows: ;#DEP
; ;#DEP
; x = 0 (VDISPLAY not used) ;#DEP
; = 1 (VDISPLAY as System Display in 12x40 mode) ;#DEP
; = 2 (VDISPLAY as System Display in 16x60 mode) ;#DEP
; = 3 (VDISPLAY as System Display in 25x80 mode) ;#DEP
; = 4 (VDISPLAY as System Display in 16x80 mode) ;#DEP
; = 5 (VDISPLAY as Customer Display in 12x40 mode) ;#DEP
; = 6 (VDISPLAY as Customer Display in 16x60 mode) ;#DEP
; = 7 (VDISPLAY as Customer Display in 25x80 mode) ;#DEP
; = 8 (VDISPLAY as Customer Display in 16x80 mode) ;#DEP
; y = 0 (VDISPLAY2 not used) ;#DEP
; ;#DEP
; Note: "System Display" means cashier display. This is the ;#DEP
; display used by the I/O Processor and Application for ;#DEP
; prompts and messages. ;#DEP
; ;#DEP
; ;#DEP
; ;#DEP
; The default turns off both VDISPLAY and VDISPLAY2 ;#DEP
; definitions (x=0 and y=0): ;#DEP
; ;#DEP
; When running TS VDISPLAY support the default is to cover the entire display ;#DEP
; with the VDISPLAY window (not title bar or border). You can optionall ;#DEP
; run the VDISPLAY window in an overlapped window. The VDisplayWindow ;#DEP
; setting controls whether full screen or windowed VDISPLAY is used. ;#DEP
; You can control the title of this window with the VDisplayTitle setting. ;#DEP
; The default title is 'TS VDisplay'. ;#DEP
;vdisp="00" ;#DEP
;VDisplayWindow="Y" ;#DEP
;VDisplayTitle="This came from the CDI file" ;#DEP
;#DEP
;#DEP
; ------------------------------------------------------------------------ ;#DEP
; VDISPLAY1 device option ;#DEP
; ;#DEP
; Specifies information on how the vdisplay1 device is attached ;#DEP
; ;#DEP
; The following options are possible: ;#DEP
; "virtual" - TS should install virtual support for this device. ;#DEP
; If the vdisp variable is sent for active a vdisplay device, then that ;#DEP
; vdisplay device is assumed to be real unless the physVdisplay1 = ;#DEP
; "virtual" is specified. ;#DEP
; ;#DEP
;physVdisplay1= "" ;#DEP
;#DEP
;-------------------------------------------------------- ;#DEP
; Match Application SERIAL port to physical COM port or 485 ;#DEP
; tailgate device. ;#DEP
; ;#DEP
; ;#DEP
; IBM applications specify SERIAL ports 1-4. ;#DEP
; These ports can be mapped to any of 15 possible physical ;#DEP
; COM ports or 2 485 tailgate devices. ;#DEP
; ;#DEP
; Example: ;#DEP
; To map the IBM application's use of port 4 to a ;#DEP
; physical COM3, add the following statement: ;#DEP
; c4tohdwr="3" ;#DEP
; ;#DEP
; To map application port 4 to 485 device 0x64, specify ;#DEP
; c4tohdwr="0x64" ;#DEP
; ;#DEP
; Note that 485 tailgate ports map as follows: ;#DEP
; ;#DEP
; PosDEVICE_RS232_25A 0x64 ;#DEP
; PosDEVICE_RS232_25B 0x65 ;#DEP
; PosDEVICE_RS232_A 0x66 ;#DEP
; PosDEVICE_RS232_B 0x67 ;#DEP
; PosDEVICE_RS232_23A 0x68 ;#DEP
; PosDEVICE_RS232_23B 0x69 ;#DEP
; ;#DEP
; ;#DEP
; Default: ;#DEP
; The default for serial devices depends on the ;#DEP
; environment. For 485 environments, the default is ;#DEP
; to map the first device that is found to ;#DEP
; application SERIAL port 1. All other environments require ;#DEP
; something to be specified here. ;#DEP
; ;#DEP
; Support for virtual SERIAL ports. TS supports a single virtual serial ;#DEP
; port by using a setting of "virtual". ;#DEP
; ;#DEP
;c1tohdwr="" ;#DEP
;c2tohdwr="" ;#DEP
;c3tohdwr="" ;#DEP
;c4tohdwr="" ;#DEP
;#DEP
; ;#DEP
; Optionally override .286 application OPEN SERIAL RS-232 parameters ;#DEP
; ;#DEP
; Example: To force settings for application port 3 to 9600 baud ;#DEP
; even parity, 7 data bits, 1 stop bit specify: ;#DEP
; ;#DEP
; c3Override=9600,E,7,1 ;#DEP
; ;#DEP
; Notes: 1) These overrides are likely never used for RS-485 attached devices ;#DEP
; 2) By default, TS will override any application baud rates less ;#DEP
; than 4800 to 4800. ;#DEP
; ;#DEP
;c1Override="" ;#DEP
;c2Override="" ;#DEP
;c3Override="" ;#DEP
;c4Override="" ;#DEP
;#DEP
; physPrinterCashDrawer - indicates whether or not cash drawer is ;#DEP
; controlled through the printer. The default varies depending on ;#DEP
; the system and printer type. The default for CE is 'Y'. The ;#DEP
; default for serial or usb attached 4610 is 'Y'. ;#DEP
;physPrinterCashDrawer="" ;#DEP
;#DEP
; ------------------------------------------------------------------ ;#DEP
; Mag Stripe Reader Options ;#DEP
; ;#DEP
; msrTracks ;#DEP
; This option is used to specify the msr track capabilities ;#DEP
; expected by the application. Its format is "nttt" where ;#DEP
; n is number of tracks that MSR device can read and 'ttt' ;#DEP
; corresponds to tracks 1, 2, and 3 respectively. Each 't' ;#DEP
; position can be either 0 or non-zero indicating if that ;#DEP
; track can be read. Here are some examples: ;#DEP
; "3123" - three track MSR; read tracks 1, 2 and 3 ;#DEP
; "2120" - two track MSR; read tracks 1 and 2 ;#DEP
; "1020" - single track MSR; read only track 2 ;#DEP
; "2023" - two track MSR; read tracks 2 and 3 ;#DEP
; "3120" - three track MSR; read tracks 1 and 2 ;#DEP
; "0000" - no MSR ;#DEP
; ;#DEP
; the default for msrTracks is "2120" ;#DEP
;msrTracks="" ;#DEP
;#DEP
; --------------------------------------------------------------------------- ;#DEP
; RPA Serial Options
; ;#DEP
; com1pir ;#DEP
; com2pir ;#DEP
; Valid values are "1" - "4". ;#DEP
; ;#DEP
; These keywords can be used to map sioaddrs 0x66 and 0x67 to ADXPIRx. ;#DEP
; ;#DEP
;com1pir="" ;#DEP
;com2pir="" ;#DEP
;#DEP
; --------------------------------------------------------------------------- ;#DEP
; --------------------------------------------------------------------------- ;#DEP
; !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ;#DEP
; !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ;#DEP
; END of OBSOLETE options ;#DEP
; !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ;#DEP
; !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ;#DEP
; --------------------------------------------------------------------------- ;#DEP
; ---------------------------------------------------------------------------] ;#DEP
; END SECTION: TERMINAL SERVICES/TERMINAL CONCENTRATOR ]
