-------------------- TELCHART ERROR CODES -------------------- Sentinel: 97: Read error 98: Error in periodic Hash lookup 99: Not TELchart V3 (Ver!=4 or Sub!=4) eToken: 188: Status: Error in periodic ID check 189: Read: File read failed (-5) 190: Read: Read of file length failed (-4) 191: Read: File number out of bounds (-3) 192: Read: CMap init error (-2) 193: Read: Init has not been called (-1) 194: Status: Error parsing system ID (-6) 195: Status: CMap registry error (-5) 196: Status: Dongle is not Telko dongle (-4) 197: Status: No eToken dongle present (-3) 198: Status: CMap init error (-2) 199: Status: Init has not been called (-1) 200: Status: Unknown error ( 0) --------------------------- SENTINEL ERROR CODE SUMMARY --------------------------- The following is a summary of all recoverable error code. Since this error code table supports multiple products, please note the product column to verify the error codes that apply to your product. Status Codes are obtained differently for each product. For a Sentinel Pro, issue either a Get Status command ("03") or a Get Extended Status command ("04") in the Sentinel Pro. For the Sentinel Superpro, the result is the error code. Please consult your manual for more details. The following list contains all available status codes that can be returned by the Rainbow driver. Some of these codes are specific to a particular environment, such as Windows NT. Note that the names given here may be different than those found in the include files. In those files the names often have a unique prefix. Please refer to the section ERROR CODE DESCRIPTION for more details. The following is a summary of: KEY - SP (Sentinel Pro) SX (Sentinel Superpro) SP SX -- -- SUCCESS 0 X X INVALID_FUNCTION_CODE 1 X INVALID_PACKET 2 X X UNIT_NOT_FOUND 3 X X ACCESS_DENIED 4 X INVALID_MEMORY_ADDRESS 5 X INVALID_ACCESS_CODE 6 X PORT_IS_BUSY 7 X X WRITE_NOT_READY 8 X NO_PORT_INSTALLED 9 X X ALREADY_ZERO 10 X DRIVER_NOT_INSTALLED 12 X X COMMUNICATIONS_ERROR 13 X X VERSION_NOT_SUPPORTED 18 X X OS_ENV_NOT_SUPPORTED 19 X X QUERY_TOO_LONG 20 X X DRIVER_IS_BUSY 30 X PORT_ALLOCATION_FAILURE 31 X X PORT_RELEASE_FAILURE 32 X X AQUIRE_PORT_TIMEOUT 39 X X SIGNAL_NOT_SUPPORTED 42 X X INIT_NOT_CALLED 57 X X DRIVER_TYPE_NOT_SUPPORTED 58 X X FAIL_ON_DRIVER_COMM 59 X X The documented errors are all recoverable errors. If you receive any unknown error numbers, please report the error number( extended error number if possible) to Rainbow Technologies Technical Support. ---------------------- ERROR CODE DESCRIPTION ---------------------- 0 - SUCCESS 1 - INVALID FUNCTION CODE was specified - See your language's include file for valid API function codes. Generally, this error should not occur if you are using a Rainbow-provided interface to communicate with the driver. 2 - INVALID PACKET - A checksum error was detected in the command packet, indicating an internal inconsistency. The packet record structure may have been tampered with. Generally, this error should not occur if you are using a Rainbow-provided interface to communicate the driver. 3 - UNIT NOT FOUND - The specific unit could not be found. Make sure you are sending the correct information to find the unit. This error is returned by other functions if the unit has disappeared( that is, unplugged). 4 - ACCESS DENIED - You attempted to perform an illegal action on a word. For example, you may have tried to read an algorithm/hidden word, write to a locked word, or decrement a word that is not a data nor counter word. 5 - INVALID MEMORY ADDRESS - You specified an invalid SentinelSuperPro memory address. Valid addresses are 0-63 decimal(0-3F hex). Cells 0-7 are invalid for many operations. Algorithm descriptors must be referenced by the first (even) address. 6 - INVALID ACCESS CODE - You specified an invalid access code. The access code must be 0(read/write date), 1(read only data), 2 (counter), or 3(algorithm/hidden). 7 - PORT IS BUSY - The requested operation could not be completed because the port is busy. This can happen if there is considerable printer activity, or if a unit on the port is performing a write operation and is blocking the port. Try the function again. 8 - WRITE NOT READY - The write or decrement could not be performed due to a momentary lack of sufficient power. Try the operation again. 9 - NO PORT FOUND - No parallel ports could be found on the workstation. 10 - ALREADY ZERO - You tried to decrement a counter or data word that already contains the value 0. If you are using the counter to control demo prgram executions, this condition may occur after the corresponding algorithm descriptor has been reactivated with its activation password. 12 - DRIVER NOT INSTALLED - The system device driver was not installed or or detected. Communication was the unit was not possible. Please verify that the device driver is properly loaded. 13 - COMMUNICATIONS ERROR - The system device driver is having problems communicating with the unit. Please verify that the device driver is properly installed. 18 - VERSION NOT SUPPORTED - The current system device driver is outdated. Please update the system device driver. 19 - OS Environment not supported - The Operating System or Environment is currently not supported by the client library. Please contact Tech Support. 20 - QUERY TOO LONG - The maximum query string supported in 56 characters. Send a shorter string. 30 - DRIVER IS BUSY - The system device driver is busy. Try the operation again. 31 - PORT ALLOCATION FAILURE - Failed to allocate a parallel port through the Operating System's parallel port contention handler. 32 - PORT RELEASE FAILURE - Failed to release a previously allocated parallel port through the Operating System's parallel port contention handler. 39 - ACQUIRE PORT TIMEOUT - Failed to acquire access to a parallel port within the defined time-out. 42 - SIGNAL NOT SUPPORTED - The particular machine does not support a signal line. For example, an attempt was made to use the ACK line on a NEC 9800 computer. The NEC 9800 does not have an ACK line. Therefore, this error is reported. 57 - INITIALIZE NOT CALLED - Failed to call the client library's initialize API. This API must be called prior to the API that generated this error. 58 - DRIVER TYPE NOT SUPPORTED - The type of driver access, either direct I/O or system driver, is not supported for the defined Operating System and client library. 59 - FAILURE ON DRIVER COMMUNICATION - The client library failed on communicating with a Rainbow system driver.