Re: b0rked setup

[Michael Loßin <phallobst@xxxxxx>]

On 12-Mar-02 Steve wrote:
> Lo all,
> 
>   I had apsfilter working for months then it turded. I
> suspect that my dist upgraded a few files but not all
> the dependancies. I'm running debian and have since
                                ^^^^^^
So I guess you're using the .deb package, right?
Which version is it?

> I ran setup and it appeared to run correctly, however
> I don't believe it can find the printer driver (or
> script that it uses).

Usually the setup asks for your driver and checks if
your ghostscript executable has support for it.

> Heres the relevant entries from my printcap:
> 
># APS1_BEGIN:printer1
># - don't delete start label for apsfilter printer1
># - no other printer defines between BEGIN and END
> LABEL
> bubble|bjc50;r=300x300;q=draft;c=mono;p=letter;m=auto:\
         ^^^^^
You are using the bjc50 "pseudo" driver -- actually,
this printer is supported by the bjc600 driver, but
it knows only a subset of all possible options, so we
had to create a special bjc50 script (available at
apsfilter/driver/bjc50) to take care of that. This
properly resets the PRINTER setting back to bjc600.

> Now when I print I get this message in the printout
> Unknown device: bjc50

This shouldn't have happened -- obviously :^)

I checked with apsfilter-7.2.2 and got a working test
page creation command (with bjc600 as the gs device).
Probably the debian package has something messed up,
you should contact the maintainer(s) with this error.

If you get the original tarball from www.apsfilter.org
everything is supposed to work (TM).


HTH
Michael