apsfilter and new hpijs release (1.2.2)

["James B. Hiller" <jhiller@xxxxxxxx>]

Hi.

I'm using apsfilter-7.2.2 along with GNU ghostscript-7.05 on my
HP OfficeJet Pro 1170C with lpd 0.48 (lpr?) and I'm trying to get it
all lashed up with hpoj-0.90.  I think I'm almost there, but am finding
a few possible issues that I don't know how to fix.  For ref, I have
the ijs device compiled into ghostscript, and that's what is getting
folded in by apsfilter (as it should).

The observable behavior when I send a print request is that the request
hangs in the queue, several instances of apsfilter are running, and a
very large error log (infinite) gets created in my lpd directory.  I've
traced the source of the errors by using set -x in the installed apsfilter
script, and what I've come up with is as follows:

a.  The apsfilter installation sets the driver to use as the Deskjet 810
as equivalent for the OfficeJet 1170C.  That sets the DeviceModel string
to DESKJET 810, which in itself doesn't seem to be a problem for hpoj or
ghostscript.  However, somewhere there are IjsParams for Quality, ColorMode,
MediaType, and Penset that are getting set, and I don't believe these are
suitable for the OfficeJet 1170C.  Reason I say that is that the log ends
up with many instances of:

unable to set key=Quality, value=0
unable to set key=ColorMode, value=2
unable to set key=MediaType, value=0
unable to set key=PenSet, value=2

in it.

So, first question is, is there any easy way (i.e. without hand-editing
the installed apsfilter script, which I suppose I could do) to prevent
these from being attempted to be set?

b.  Either ghostscript or the ijs driver seem to require:

-dIjsUseOutputFD

to be in the ghostscript command, but that isn't happening.  Again, any
easy way to make this so, either at configuration time, or possibly a
newer version of apsfilter that takes the newer hpijs into account?

Without a fix, the result is:

unable to write to output, fd=0, count=1000: Bad file descriptor

forever.

c.  The only other badness that I can seem to find right now is that, when
I manually use the gs command that apsfilter generates, along with inserting
the changes I described above (that is, insert the IjsUseOutputFD, and
get rid of the errant key-setting attempt), once the submitted .ps file
completes printing, the gs command given to the command line hangs, and
the printer seems to remain in its print mode (one of the lights on the
panel that indicates data processing keeps flashing) and this continues
until I CTRL-C the command.

I don't know whether this is a badness somewhere else other than something
that apsfilter is doing, or whether it's an artifact of entering the
command at the command line vice via the script piping, or what, but figured
I'd ask now in hopes of avoiding a later stumbling block.

Any help that one can provide would be greatly appreciated.

thx,
jbh