Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cornell!uw-beaver!sumax!thebes!polari!rwing!nanook
From: nanook@rwing.UUCP (Robert Dinse)
Newsgroups: comp.sys.tandy
Subject: Re: Thanks!
Message-ID: <139@rwing.UUCP>
Date: 2 Sep 90 05:03:47 GMT
References: <5730@plains.NoDak.edu> <137@rwing.UUCP> <945@bilver.UUCP>
Distribution: usa
Organization: Totally Unorganized
Lines: 28
Summary: Port Lockup

In article <945@bilver.UUCP>, bill@bilver.UUCP (Bill Vermillion) writes:
> I have seen this happen routinely on external ports since 1984.  What I
> have observed though is that it only occurs on tty06

     This is a different problem. This problem I am having (and the others
I know of) affects all of the ports on the multi-terminal interface boards,
ie, tty04, tty05, tty06, tty07, tty08, tty09. It doesn't require power off,
just a boot to clear, and it doesn't affect tty01 or tty02.

     At one point Tandy told me that the SIO's they used had a one-byte
pre-fetch queue and if an interrupt was missed they'd lock up but they
were working on fixing this and expected it to be fixed in a point issue
that would be released concurrently with the 3.02.00 development system.
Well, no point issue is release and now they deny there is any problem.

     This has more or less been the kind of response I've gotten from Tandy
in general (either deny the problem outright or say the hardware is broken
and to bring it in to the service center, even though it's a generic problem
on every machine I've seen in the same kind of service), so I've gotten to
the point where it doesn't seem worth it to bother to call Fort Worthless
with problems since I know I'm not going to get help there. Writing letters
doesn't help either, it does apparently get their attention, I have been
called several times by someone named Archenhold, but he does not appear to
have any technical background and I've yet to be successful at connecting to
anyone who does.

     Anyway, different problem. The problem with tty06 is like nothing I have
experienced and does sound like a hardware problem.