Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!think.com!paperboy!hsdndev!cmcl2!phri!marob!daveh
From: daveh@marob.uucp (Dave Hammond)
Newsgroups: comp.unix.xenix.sco
Subject: Re: Serious flaws in
Keywords: SCO 286 386 SIO ASYNC performance FAS dumb serial
Message-ID: <276E285B.1413@marob.uucp>
Date: 18 Dec 90 14:31:55 GMT
References: <1634@boink.UUCP> <271@n4hgf.Mt-Park.GA.US>
Organization: ESCC, New York City
Lines: 21

wht@n4hgf.Mt-Park.GA.US (Warren Tucker) writes:
harald@boink.UUCP (Harald Milne) writes:
>>Conclusion: SIO is broken, and broken bad enough to crash your system. 
>>Don't use SIO with dumb serial cards.
>
>Hmmmm....  I do asynchronous communications like most people
>breathe...  pretty often. [...]

Likewise.  I have been putting SCO on 286 machines (from ATs to
no-names) since 2.1.3 (circa 1985) and have never had a panic caused by
SIO.  I've used generic single-port "COM2:" cards and dumb 4-port cards
from Arnet, DigiBoard and AST.  These have been running in production
machines without incident for several years.  My shop still installs at
least one 286 Xenix machine per month (running 2.3.2).  We would not be
in business if the SIO caused machines to crash and burn.

I suggest that harold@boink investigate possible hardware problems.

--
Dave Hammond
daveh@marob.masa.com