[net.micro.pc] CROSSTALK @ 9600baud. Beware!

ray@othervax.UUCP (Raymond D. Dunn) (09/18/85)

References:

Due to occasional loss of data using XTALK at 9600baud over
standard serial ports, in terminal mode, with Capture on or
off, an investigation has revealed:

 1. When updating the screen status line (done in XTALK's
    timer interrupt), XTALK keeps interrupts inhibited for
    periods exceeding 1Msec.

 2. XTALK does NOT check for overrun or other errors
    on the port, thus data loss/parity errors are IGNORED.

The fault can be demonstrated easily by having the online timer
running during data receipt.

Beware!

Ray Dunn.  ..philabs!micomvax!othervax

peter@graffiti.UUCP (Peter da Silva) (09/25/85)

> Due to occasional loss of data using XTALK at 9600baud over
> standard serial ports, in terminal mode, with Capture on or
> off, an investigation has revealed:

Also note that using anything at 9600 baud on a PC is pushing the
capabilities of the machine. I find that to make XTALK or anything
else reliable at that speed I have to get rid of all my desktop
utilities except for sidekick (which doesn't seem to bother it).