Once apon a time Kris Roebuck said, 'CPS Rates' to Simon Byrnand...

 SB> Sounds like your COMMS program is miscalculating your throughput then
 SB> I'm afraid! Where do you get 38400 bps = 4266 cps from? Since a
 SB> serial port is asyncronous, it actually sends *10* bits per byte, not
 SB> 8, as there is the start and stop bit as well as data....

 KR> My calculations.  I work on the same principle as the modem itself.

The principle of imaginary figures? ;-) With your comm port speed set
to 38400bps 8n1, there is *NO WAY* you can get more than 3840 cps, it
simply is not possible. Period.

My whole point is that if you are getting figures much higher than that,
your comms program is lying to you.

 KR> Maybe I have the priority of NComm set too high?  +19 to make sure I
 KR> get a reliable transfer.

Why on earth do you have it set that high? I run NComm at 0 priority at
38400 bps, and I hardly ever get any errors, even when multitasking
heavily. (This is on an A1200) Setting the priority that high wont help
anyway, because, its the serial.device driver that must respond quickly
to prevent errors, and that is an interrupt handler, not a process....

All you'll succeed in doing is to bog down other programs while receiving
data...and cause a system lockout if Ncomm should happen to get stuck in
a loop. Its also a bad idea to have a user program at a higher priority
than Filesystems and device drivers....

Regards,
Simon

... I have seen the evidence. I want DIFFERENT evidence...
--- FMail/386 0.98a