Xref: utzoo comp.sys.encore:58 comp.unix.wizards:9518 Path: utzoo!attcan!uunet!husc6!think!ames!nrl-cmf!mailrus!tut.cis.ohio-state.edu!mandrill!gatech!hubcap!ncrcae!ncr-sd!ncrlnk!ncrpcd!wright!jsloan From: jsloan@wright.EDU (John Sloan) Newsgroups: comp.sys.encore,comp.unix.wizards Subject: Re: Spooling to an Encore annex via lpd Message-ID: <888@wright.EDU> Date: 19 Jun 88 14:34:01 GMT References: <5114@super.upenn.edu> Distribution: na Organization: Wright State University, Dayton OH, 45435 Lines: 28 in article <5114@super.upenn.edu>, david@linc.cis.upenn.edu (David Feldman) says: > I am currently trying to get lpd to spool through an annex UX port. Or, > I am at least thinking about it. The target device is a laserwriter > (SUN) running postscript. : If you ever figure out how to do this reliably you should do the net a favor and announce it. In our version of Transcript (admittedly not the latest one), the filter pscomm talks directly to the device /dev/lw (or whatever you have it configured for), which makes it difficult (I'm not enough of a Unix expert to claim impossible) to fork and exec pscomm from another lpd filter that speaks TCP/IP to the Annex. The network filter to talk to the Annex is not difficult to write, given the C code that comes with the Annex as an example. Is there an undocumented switch for pscomm that makes it behave differently? Everytime you see someone on the net who says something to the effect "We have our Laserwriter hooked up to a serial port on a XYZ ethernet terminal server, but sometimes something doesn't print and we don't know why" you know that they've got a unidirectional connection and they're throwing away all the error messages generated by the printer that would normally have been logged by pscomm. -- John Sloan, The SPOTS Group Wright State University Research Building CSNET: jsloan@SPOTS.Wright.Edu 3171 Research Blvd., Kettering, OH 45420 UUCP: ...!wright!jsloan +1-513-259-1384 +1-513-873-2491 Logical Disclaimer: belong(opinions,jsloan). belong(opinions,_):-!,fail.