Xref: utzoo comp.sys.att:8835 unix-pc.general:4858
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!think!snorkelwacker!mit-eddie!uw-beaver!sumax!polari!rwing!pat
From: pat@rwing.UUCP (Pat Myrto {rwing})
Newsgroups: comp.sys.att,unix-pc.general
Subject: Re: line printer problems with 3.51m
Summary: Parallel Printer Fine with 3.51m
Message-ID: <1063@rwing.UUCP>
Date: 18 Feb 90 18:54:33 GMT
References: <4772@rtech.rtech.com>
Distribution: usa
Organization: Very Little Organization, Seattle WA
Lines: 40

In article <4772@rtech.rtech.com>, bruces@daneel.rtech.com (Bruce Stewart) writes:
> Well, 3.51m was looking good until I tried to use my parallel printer.  Instead
> of a nice, steady stream of output, what I get is one line ... pause for 10
> minutes ... next line ... pause for 10 minutes ... etc.  Needless to say, I
> wasn't pleased (8-)).
> [ ... config and test with old kernel, etc deleted ... ]

Well, I don't know what to tell you - I have this Citoh 310 printer
configured to look like an Epson FX series hooked in, and it works
fine with 3.51m.  Note that I did not use the User Agent (office) to
set it up, I did it from the command line with lpadmin, etc., and gave
it the name 'citoh', class parallel.  My interface file is rather
heavily hacked up to restore stuff that was claimed to not be
supported, making it conform to the manual pages in the binders
supplied with the Utilities pkg.  None of the hacks were done to make
it function, just to make it work the way *I* wanted it to.

Just a guess is that there may have been something wrong with the
setup all along, and changes in 3.51m are being affected by it, whereas
3.51 ignored it.

If all else fails, perhaps you should go in, and re-configure the
thing FROM SCRATCH, and from shell level, and forget the 'convenient'
method provided by the User Agent and the install login.  Just be sure
to run /usr/lib/lpshut and su to lp and do all the install as user
'lp' to ensure all files have the correct ownership, etc.  If
everything is right, enabling and running accept, finally re-starting
lpsched, lpsched should stay running and the printer will work.  If
there is a problem, lpsched will not stay up and running.  Read the
manuals first, though, its been awhile since I have done this, so I am
probably missing something.

If you think it will help, send me an e-mail message and I will send
you my interface script.

-- 
pat@rwing                                       (Pat Myrto),  Seattle, WA
                            ...!uunet!pilchuck!rwing!pat
      ...!uw-beaver!uw-entropy!dataio!/
WISDOM:    "Travelling unarmed is like boating without a life jacket"