Subject: Re: [netatalk-admins] pap and epson stylus color 800 localtalk interface
From: Steve Hsieh (steveh@eecs.umich.edu)
Date: Wed Sep 24 1997 - 01:54:37 EDT
Thanks for the reply, Mike. But it sounds as if you are talking about
using papd to advertise the epson printer, which you sent data to over
the parallel port? (I can send Ps->ghostscript->epson parallel port just
fine).
I'm trying to go the opposite direction, namely
unix/netatalk/pap -> ethertalk -> localtalk bridge -> epson w/localtalk
interface
If you were able to do the latter, I'd definitely be interested in your
setup. For me, 'pap -pEpsonprinter:EPSONLQ2@ZONE datafile' results in
really messed up output and a printer which gets stuck in status: busy
indefinitely.
-- Stephen Hsieh Dept. of Electrical Engineering and Computer Science steveh@eecs.umich.edu Univ. of Michigan at Ann Arbor -------------------------------------------------------------------------------On Tue, 23 Sep 1997, Mike Holling wrote:
> > Anyone out there using pap to connect to an epson stylus color 800 inket > > with the localtalk interface? It would seem that this particular printer > > doesn't work too well with pap. When you send a job, data flows very > > slowly, and pap isn't able to disconnect when done (there is no way to get > > out of a pap -pprinter:EPSONLQ2@ZONE once you start reading from stdin). > > Even if you use the -E option, it says "Bad response". If you terminate > > pap with ctrl-c, the epson will remain busy forever until you pull its > > power plug and plug it back in (the power switch doesn't reset the > > interface). > > > > While the printer may not conform to all the standards, it does seem to > > work fine with the Macintosh epson appletalk driver, so it seems possible > > that netatalk could work with it if someone knew what was going on... > > I've had this printer working fine together with Ghostscript. I can > probably dig up the configuration files if you'd like. The supplied Epson > drivers still ran faster and produced better output, so the > netatalk/ghostscript solution was never put into production. The printer > was connected to the parallel port of a 486/66 running FreeBSD and > netatalk. > > - Mike > >
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:26:44 EST