Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!lucy.swin.edu.au!news.rmit.EDU.AU!goanna.cs.rmit.edu.au!news.apana.org.au!cantor.edge.net.au!news.teragen.com.au!news.access.net.au!news.mel.connect.com.au!munnari.OZ.AU!uunet!in1.uu.net!207.22.81.9!europa.clark.net!cpk-news-hub1.bbnplanet.com!news.bbnplanet.com!rill.news.pipex.net!pipex!tank.news.pipex.net!pipex!news.utell.co.uk!usenet
From: brian@shift.lan.awfulhak.org (Brian Somers)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Printer Problem -- Oops! recovery
Date: 10 Mar 1997 11:33:31 GMT
Organization: Awfulhak Ltd.
Lines: 42
Message-ID: <5g0rib$lbs@ui-gate.utell.co.uk>
References: <5fsrjh$lb@quail.swcp.com>
Reply-To: brian@awfulhak.demon.co.uk, brian@utell.co.uk
NNTP-Posting-Host: shift.utell.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Newsreader: knews 0.9.8
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:36862
In article <5fsrjh$lb@quail.swcp.com>,
crs@quail.swcp.com (Charlie Sorsby) writes:
> First, I'm way behind in reading news so, it it isn't too much
> trouble, I'll appreciate if you will Cc: of any responses to
>
> crs@swcp.com
>
> just to be sure that I don't lose any among all the messages that
> I haven't read yet on the news group.
>
> I'm Cc:'ing this to questions@freebsd.org because and earlier query
> there didn't contain as much information as I've gathered into this
> post.
>
> I have a problem with an HP DeskJet 600C that was working until
> yesterday.
>
> Background:
>
> When I first began setting the printer up (on FreeBSD 2.1.0, later
> 2.1.5) I had a problem with it being *very* slow. A query to the
> net provided the information that it doesn't work properly with an
> interrupt-driven lpt port so I switched to polled mode and it's been
> working OK. I wrote a very simple input filter script using the
> information in the handbook and it has been able to handle ordinary
> text files and postscript using ghostscript (albeit, in the later
> case, the fonts leave something to be desired).
>
> Until now. :(
>
> Yesterday, I tried to print two files, both simple text files. The
> first printed; the second did not. The following error message was
> printed to the console window:
>
[.....]
This really sounds like a cable problem. If you can get a hold of
another cable, try it out.
Brian <brian@awfulhak.demon.co.uk> <brian@freebsd.org>
<http://www.awfulhak.demon.co.uk>
Don't _EVER_ lose your sense of humour !