Xref: utzoo unix-pc.general:2337 comp.sys.att:5654
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!nic.MR.NET!shamash!nis!sialis!rjg
From: rjg@sialis.mn.org (Robert J. Granvin)
Newsgroups: unix-pc.general,comp.sys.att
Subject: Re: NMI Parity Errors while Parallel Printing
Message-ID: <1218@sialis.mn.org>
Date: 25 Feb 89 17:45:28 GMT
References: <788@rush.cts.com> <1106@banzai.UUCP> <14989@cup.portal.com>
Reply-To: rjg@sialis.mn.org (Robert J. Granvin)
Followup-To: unix-pc.general
Distribution: usa
Organization: Dr. Ho Laboratory and Day Care Center
Lines: 26

>One thing to check on 3B1/7300's is that in my experience with my own and
>numerous others is that they seem to eat parallel cables. I know this sounds
>really stupid but i have seen all kind of printer problems develop on Unix PC's
>rapidly and then mysteriously disappear when the cable is replaced... ????

A very common problem with the 3b1/7300 and parallel cables isn't the
cable itself, but rather how the cable connects to the 3b1.

For some reason, the parts normally available on the cable and 3b1 end
don't deal all that well with each other.  When you plug it in, it may
look and feel like it has a solid connection, but it often doesn't.

Many people have had parallel printer problems, ranging from odd
printing to complete failures.

Solution?  Forcibly press in the cable into the 3b1 while testing the
printer.  If this improves printer performance (or brings it back to
life), then get some screws and bolt the cable in place.

You'd be surprised, but it does wonders.

-- 
       Robert J. Granvin
 National Information Services              Gorn base 2 just appeared.
       rjg@sialis.mn.org
{amdahl,hpda}!bungia!sialis!rjg