Author: Ratko V Tomic
Date: 19:39:12 10/04/99
Go up one level in this thread
>>By setting the baud rate to a very slow one (e.g. 300 baud, that's >>plenty for sporadic few byte packets in an autoplay) and comparing >>the Rebel's nps, you could test whether this was the problem. In any >>case, good or bad serial chip, a positive correlation of baud rate and >>decrease in nps would indicate excessive or otherwise faulty serial >>port activity. > > Can you give me a hint how to do this? Normally, serial applications let you set up the COM port and baud rate through either a command line parameter (e.g. /COM1:9600) or via some configuration menu or file. But Christophe just said in another reply that auto232 doesn't have a baud rate option, so this can't be tried. Unfortunately I don't have auto232 to track down the problem, but with some other programs which don't allow user configured baud rate I had to use Soft-ICE debugger to find in memory the location where they kept the control data they use to initialize serial port (Soft-ICE allows breakpoints on any i/o port writes). Then for uniqueness of the pattern, I wrote down the several bytes of data around the baud rate byte and located that pattern in the executable file, so it could be patched. Of course, in this case one wouldn't really need to use the baud rate diagnostic test if one can run the debugger and see directly what causes the slowdown.
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.