![GSi TYMPSTAR 1 Service Manual Download Page 202](http://html1.mh-extra.com/html/gsi/tympstar-1/tympstar-1_service-manual_2275118202.webp)
Chapter 8
Ini file not found during write.
Subcodes: none
Likely Causes: The .INI file was not found for read access; it
should be part of the initial TympStar installation. In this
case one or more data files may have been corrupted due to a
previous system crash (possible if a file was open for write
and system crashes for any reason). It is also possible to be a
DOC failure on the PC104. It is less likely a software
problem with the file system, as all file I/O occurs through
the PharLap OS.
Ini file write/append error.
Subcodes: none
Likely Causes: The .INI file was found but could not be
written. It is possible the disc is full. In this case one or
more data files may have been corrupted due to a previous
system crash (possible if a file was open for write and system
crashes for any reason). It is also possible to be a DOC
failure on the PC104. It is less likely a software problem with
the file system, as all file I/O occurs through the PharLap OS.
GFX - string out of bounds array index or indices.
Subcodes: none
Likely Causes: Strings are always referenced in the system by
a unique index number. If this number is out of bounds
based on the current string list, this failure occurs. This
indicates an internal software failure.
Attempt to read a 16-bit port with 8-bit routine.
Subcodes: none
Likely Causes: Ports are defined in a look-up table and all
callers should know if their port is 8 bit or 16 bit. This failure
indicates an internal software failure.
Attempt to write a 16-bit port with 8-bit routine.
Subcodes: none
Likely Causes: Ports are defined in a look-up table and all
callers should know if their port is 8 bit or 16 bit. This failure
indicates an internal software failure.
Attempt to read an 8-bit port with 16-bit routine.
Subcodes: none
Likely Causes: Ports are defined in a look-up table and all
callers should know if their port is 8 bit or 16 bit. This failure
indicates an internal software failure.
Attempt to write an 8-bit port with 16-bit routine.
Subcodes: none
Likely Causes: Ports are defined in a look-up table and all
callers should know if their port is 8 bit or 16 bit. This failure
indicates an internal software failure.
Error attempting to update the RTC
Subcodes: getlasterror() - see Windows documentation
Likely Causes: The PharLap OS performs Real-Time-Clock
read/writes. These are modeled after the Windows API calls.
Any failures are associated with a faulty RTC on the PC104
or indicate an internal software failure.
Grason-Stadler
CP Error codes
2503
ABORT_INI_WRITE_FILE_NOT_FOUND
2504
ABORT_INI_WRITE_FILE_ERROR
2600
ABORT_GFX_STR_IDX_OUTOFBOUNDS
2700
ABORT_HW_PORT_WRITEBYTE
2701
ABORT_HW_PORT_READBYTE
2702
ABORT_HW_PORT16_WRITEBYTE
2703
ABORT_HW_PORT16_READBYTE
2800
ABORT_RTC_DATE_WRITE_ERR
8 - 12
Summary of Contents for TYMPSTAR 1
Page 1: ...Part Number 2000 0110RevB...
Page 20: ...Chapter 1 1 8 Grason Stadler...
Page 72: ...Chapter 3 Grason Stadler 3 32...
Page 168: ...Chapter 5 Grason Stadler 5 30...
Page 170: ...Chapter 6 Case chassis Grason Stadler 6 2...
Page 171: ...System Level Parts GSI TympStar Version 1 and Version 2 Service Manual 6 3...
Page 172: ...Chapter 6 Overallassembly Grason Stadler 6 4...
Page 173: ...System Level Parts LCD assembly GSI TympStar Version 1 and Version 2 Service Manual 6 5...
Page 174: ...Chapter 6 Top case assembly Grason Stadler 6 6...
Page 176: ...Instrumentassembly 6 8 Chapter 6 Grason Stadler...
Page 177: ...System Level Parts Labels GSI TympStar Version 1 and Version 2 Service Manual 6 9...
Page 178: ...Chapter 6 Grason Stadler 6 10...
Page 179: ...System Level Parts PrinterAssembly GSI TympStar Version 1 and Version 2 Service Manual 6 11...
Page 180: ...Chapter 6 Grason Stadler 6 12...