I know one business that has used a timeclock connected to a computer to help with payroll for several years. Like other things, the serial port is the most basic connection to a PC so their timeclock connected this way.
As technology has advanced, the newer timeclocks now offer a network connection, just as your PC, perhaps your printer, and more and more devices do.
We seem to have run into a legacy (serial port) bug however. The timeclock software was originally written to use the serial port. It seems to want to talk with the clock device and when it can’t do it, it’s crashing Windows XP.
Serial ports have been around since before the first PC. I suspect they existed in the 1960′s when printers were first connected to computers (perhaps the 1950′s?). They are prone to error as much older technology was and are no longer the best choice available.
We’ll dig into this further but my guess is that there is a setting in the timeclock software that causing it to poll the clock periodically. Once we turn this off, Windows won’t crash anymore.
Never a dull moment