Simon Byrnand.  Kris Roebuck.  CPS Rates.  You know the drill.

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

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

That, combined with v34serial.device means that I never have errors.

NComm only crashes if I play with too many features.

 * AmyBW v2.11 *
... Liberal : Widening the gap between the rich and the poor.

--- AmyBW v2.11