Not sure if this applicable in your case or not, but have you considered
abandoning Appletalk and simply using the Desktop Printer Utility to setup
a printer using LPR? In as much as Appletalk as a protocol is a pain in
the @$$ and probalby a dead duck, it might make more sense to investigate
this. This is what I did...
David Houston
CIT Client Services Coordinator
University of Vermont
On Apr 11, 2002, Rob Joyce wrote:
RJ. Thanks. The latest version I see on ftp.lprng.com is 3.5.8alpha2, dated
RJ. April 3.
RJ.
RJ. One thing I noticed is that ps_eoj@ and ps_eoj_at_end@ didn't have any
RJ. effect until I added the following to vars.c:
RJ.
RJ. { "Ps_eoj", "ps_eoj", (char **)&Ps_eoj, FLGV,0 },
RJ. { "Ps_eoj_at_end", "ps_eoj_at_end", (char **)&Ps_eoj_at_end, FLGV,0 },
RJ.
RJ. Even completely quashing the ^D's doesn't quite solve the problem, as the
RJ. printer will wait for data as long as the connection's open. From what I
RJ. gather, ^T and ^D are technically invalid over non-serial-line PostScript
RJ. channels. Looking at netatalk's pap.c source, it appears that status
RJ. requests (^T) and EOJ (^D) are sent out-of-band, so it would be
RJ. impossible(*) for ifhp to send these over a pipe to lp=|/path/to/pap.
RJ.
RJ. As pap gathers status information anyway, one can pretty easily modify
RJ. pap.c to put this on stdout or stderr. My question now is, how does one
RJ. format/route this information so it's visible in lpq? (It would be
RJ. helpful, e.g., to see "paper out" status messages in lpq.) I tried
RJ. forcing both ifhp's and lprng's poll_for_status on, but that didn't work.
RJ. I did -- once -- see a PostScript status message in the Status: (not
RJ. Filter_status:) line of lpq, but I've been unable to repeat it.
RJ.
RJ. Thanks,
RJ. _Rob
RJ.
RJ. (*) I guess the Adobe TBCP standard would help, but I'm a little hesitant
RJ. to try that.
RJ.
RJ.
RJ. On April 10th, Patrick Powell wrote:
RJ.
RJ. > > Date: Mon, 8 Apr 2002 20:57:47 -0400
RJ. > > From: Rob Joyce <[EMAIL PROTECTED]>
RJ. > > To: [EMAIL PROTECTED]
RJ. > > Subject: LPRng: Netatalk, LaserWriter, and ^D
RJ. > >
RJ. > > Hi all,
RJ. > >
RJ. > > We have LPRng 3.8.10 and ifhp 3.5.7 running on Solaris 7, and can print
RJ. > > just fine to HP/Jetdirect printers and others. But for some reason
RJ. > > printing via AppleTalk fails to both Apple and HP printers (that normally
RJ. > > can do AppleTalk); they seem to issue PostScript errors about ^D.
RJ. > > netatalk is 1.4b2+asun2.1.4 from May 2000, and
RJ. > > "cat test.ps | /usr/local/bin/pap -e -p 'printer name'" works fine.
RJ. > >
RJ. > > lpd_printcap contains:
RJ. > >
RJ. > > iss
RJ. > > :tc=.cf_server
RJ. > > :cm=B327, LaserWriter Pro 630, ISS Group
RJ. > > :lp=| -$ /usr/local/bin/pap -e -p "iss - B317, LaserWriter Pro 630"
RJ. > > :ifhp=model=apple,debug=1
RJ. > >
RJ. > > .cf_server
RJ. > > :server
RJ. > > :filter=/usr/local/libexec/filters/ifhp
RJ. > > :sd=/var/spool/lpd/%P
RJ. > > :mx=0
RJ. > > :mc=0
RJ. > >
RJ. > > Adding ",ps_eoj@,ps_eoj_at_start@,ps_eoj_at_end@" to the end of the ifhp=
RJ. > > string doesn't help.
RJ. > >
RJ. > > The "lpq -Piss -L" output is attached (where the first job has the default
RJ. > > ps_eoj* settings and the second has the ps_eoj*@ stuff).
RJ. > >
RJ. > > Why would the printer be so upset about the ^D ?
RJ. >
RJ. > I don't know... but I have found a possible cause... Please get
RJ. > ifhp-3.5.8 (next release) and try it.
RJ. >
RJ. > Patrick Powell Astart Technologies,
RJ. > [EMAIL PROTECTED] 9475 Chesapeake Drive, Suite D,
RJ. > Network and System San Diego, CA 92123
RJ. > Consulting 858-874-6543 FAX 858-279-8424
RJ. > LPRng - Print Spooler (http://www.lprng.com)
RJ.
RJ.
RJ.
RJ. -----------------------------------------------------------------------------
RJ. YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
RJ. The address you post from MUST be your subscription address
RJ.
RJ. If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
RJ. or lprng-digest-requests) with the word 'help' in the body. For the impatient,
RJ. to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
RJ. with: | example:
RJ. subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
RJ. unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
RJ.
RJ. If you have major problems, send email to [EMAIL PROTECTED] with the word
RJ. LPRNGLIST in the SUBJECT line.
RJ. -----------------------------------------------------------------------------
RJ.
-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address
If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body. For the impatient,
to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
with: | example:
subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
If you have major problems, send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------
