Bad Checksum
Some gages include a checksum when transmitting results. If this is an isolated occurrence, just measure the feature again. If the problem occurs often try a new cable (shorter or better shielded) or taking measurements more slowly.
Bad file mode
Usually happens after some other error, reboot the computer
Bad file name or number
Usually happens after some other error, reboot the computer. If the error still occurs, try checking QC-Gage settings for bad Spec Plan names, output files, etc. You may need to reinstall QC-Gage is a critical system file is missing or damaged
Bad record length
Contact Prolink with the exact circumstances this error occurred under
Bad record number
Usually from a corrupt file, if the error persists you may need to reload QC-Gage
Can't create AutoRedraw image
Your machine is out of graphical resources - close some windows. You may also need to reboot.
Can't rename with different drive
May occur if you run QC-Gage from a network drive, especially if the drive is not mounted (a UNC name instead of a drive letter)
Character was not read from the hardware before the next character arrived.
You may need to reduce the baud rate, buy a Windows approved serial port (16550 series UART), replace slow drivers (especially video), or unload other programs (especially virus checkers).
Communications port cannot allocate queues that are so many bytes long. Sizes:
Pick a smaller Queue size, put more memory in the computer, end some programs or reboot. Different operating systems have different Queue limits, regardless of memory size so adding more memory only helps some computers. The QC-Gage defaults should work with all systems as long as no other programs interfere with memory.
Communications port cannot support the number of bits per byte that it has encountered. The port name and the number of bits per byte are
Pick a different number of bits per byte
Communications port default parameters are in error. The port name is
Usually indicates hard disk problems, Windows does not usually let you set bad default settings. You can verify the windows default settings and set them to 2400 baud, No parity, 8 databits, 1 stop bit, no flow control. All computers should be able to handle these settings (See your Windows owner's manual)
Communications port is already open. The port name is
Your mouse, modem, terminal program, another RUN screen in QC-Gage, etc. is using that COM port or the interrupt the COM port uses. Sometimes computers with COM3 and COM4 use the same interrupts for COM1 and COM2, you may have to disable COM3 and COM4
Communications port is not available (is locked by another device). The port name you are trying to use is
Your mouse, modem, terminal program, another RUN screen in QC-Gage, etc. is using that COM port or the interrupt the COM port uses. Sometimes computers with COM3 and COM4 use the same interrupts for COM1 and COM2, you may have to disable COM3 and COM4
Communications port is not open. The port name is
The port was never opened or was closed prematurely. This problem is sometimes caused by errors in the operating system, simply rebooting the computer may solve this problem.
Communications port name is an invalid or unsupported device identifier. The port name is
You specified a COM port your computer does not have, pick a different COM port
CTS (clear-to-send) time-out.
Make sure hardware flow control is enabled on both machines or disabled on both machines. Check for loose or damaged cables. Make sure the cables are of the correct type
Default baud rate is unsupported on
Pick a different Baud rate in the Windows default COM port settings area (See your Windows owner's manual)
Default byte size is invalid on
Pick a different number of bits per byte in the Windows default COM port settings area (See your Windows owner's manual)
Device I/O error
Problem reading the disk drive, make sure it is connected and not damaged
Device unavailable
Usually from a portable or removable drive that is currently disconnected
Disk full
Clear some disk space
Disk not ready
Usually from a portable or removable drive that is currently disconnected
Division by zero
Contact Prolink with the exact circumstances this error occurred under
DSR (data-set-ready) time-out.
Make sure hardware flow control is enabled on both machines or disabled on both machines. Check for loose or damaged cables. Make sure the cables are of the correct type
Error in loading DLL
The DLL may have been damaged, you may need to reload QC-Gage. There may be another program that uses a different version of the same DLL - uninstall that program and reinstall QC-Gage. Note that some install programs, especially under Windows 95 and NT, cannot be completely uninstalled, you may need to reinstall windows!