Elo TouchSystems DOS and Windows Driver Disk, Руководство пользователя

Страница: 124 / 134

TouchBack Error Conditions 121
T
OUCH
B
ACK
E
RROR
C
ONDITIONS
TouchBack may output an error message as it is loaded. Once loaded, run-time
error conditions are indicated with beep codes rather than error messages. Error
messages and beep codes are listed in the following sections.
Error Messages
TouchBack may display any of the following error messages as it is loaded.
TouchBack also returns an exit code, sometimes called an "error level" code, that
can allow DOS batch files to process fatal errors with the ERRORLEVEL
command. The exit code that corresponds to each error message appears in
parentheses following the message. Exit code 0 indicates no error. See a DOS
manual for information on writing batch files which check the ERRORLEVEL
code.
-b flag cannot be updated. (4)
Reminds you that TouchBack's buffers cannot be changed with the -b
command after TouchBack has been loaded. Extract TouchBack using the
-x flag, then reinstall it with the desired -b flag. See page 71.
Buffer too large. (9)
You have specified buffers that occupy more space than is available. The
product of the number of buffers times the buffer size of each may not be
greater than 52K.
Can't install TouchBack -- conflicting TSR. (11)
Another TSR program is using the same multiplex interrupt ID value. Try
installing TouchBack with each TSR separately to identify the conflicting
TSR.
ELODEV not calibrated. (3)
The -c flag was not specified when you loaded ELODEV, or you failed to
run ELOCALIB after ELODEV was loaded. See Chapter 4.
ELODEV not installed. (1)
ELODEV must be installed before loading TouchBack (see page 68).
Look for an error message while the system is booting. If you are using
ELODEV's -i flag, make sure the interrupt is between 60 and 66 (hex), or
use TCHBACK's -i flag.