Dear Printer-Strugglers,

I have a problem with some extra lines of "reprobation" that ifhp seems
to add to a print job.  The basic problem: printing a .ps file.

I shall state my scenarios, and then state my system.

Scenario 1:  I add the line ":/tmp/out" to my /etc/printcap.  This causes
lpr to send the processed .ps file to /tmp/out.  I do this, and then
run "file /tmp/out"; I am told that /tmp/out is a PCL file, which is good,
since my printer is a lovely old HP LaserJet series II, state of the art
in 1989<g>.  But when I "tail" /tmp/out, I get:

                                                      Unrecoverable error: 
invalidfileaccess in w
Operand stack:
    %stdout

And when I cat /tmp/out to /dev/lp0, my printer, I get a lovely printout of
my .ps file, and then an extra single sheet of paper, with the word
"%stdout" printed on the upper RH side.

Scenario 2:  I use an old script that I have had for many years.  Its
operative line is:

    gs -q -sDEVICE=laserjet -sPAPERSIZE=letter -dNOPAUSE -dSAFER 
-sOutputFile='/tmp/$1.READY.TO.PRINT' $1

"$1" is, of course, the .ps file that I want to print.

After running this script, I get, in /tmp/, a file "...READY.TO.PRINT".  It
is, like /tmp/out, a PCL file.  But I have no ugly error message appended
when I "tail" it.  And when I cat /tmp/"$1".READY.TO.PRINT to /dev/lp0
I get the lovely printout of my .ps file, but no extra sheet of paper.

In contrasting the two scenarios, it seems to me that there is, perhaps,
a bug in the ifhp SW.  But I cannot of course make this judgment without
having a much greater knowledge of the the ifhp/lprng process than I
at present do.  I hope very much that people on this E-list more knowledgeable
than I can make suggestions that will help me resolve this difficulty.

Finally, the details about my system:  I'm running Debian Woody, LPRNG-3.7.4,
ifhp-3.4.7, and gs 7.0.  As stated above, my printer is a (rebuilt)
HP LaserJet series II, which has worked fine in the past; and the appropriate
gs device really does seem to be "laserjet".

I append my /etc/printcap below.

I would be most grateful for any suggestions.

Best wishes,

Alan McConnell

(start of printcap)--------------------------------------
## The Super Quick Guide to LPRng Printcaps
##  Patrick Powell <[EMAIL PROTECTED]>
##          23 Dec 2000
# VERSION=3.7.4
#
#  Alan copied this from the LPRng printcap.in file, and followed
#     the directions given in this file.  I've deleted all but
#     the operative commands.  The documentation is in printcap.DOCUM
#
#  Alan got rid of the .common in this file(see printcap.DOCUM)
lp:sd=/var/spool/lpd/%P
    :force_localhost
    :lp=/dev/lp0
    :sh:sf:mx=0:mc=0
# lp:lp=/dev/lp0:tc=.common:server
    :filter=/root/bin/ifhp
    :ifhp=model=gs_laserjet
#    :lp=/tmp/out
#  Last line of printcap

            -------------------------------------(end of printcap)

-- 
Alan McConnell         An interesting article by Bill Moyers, from "The
Pixel Analysis         Nation", is to be found, with other good stuff, on
patriot.net/~alan      my web site -- Click on "Public Policy"

-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------

Reply via email to