On Sun, Sep 07, 2003 at 08:23:18PM -0300, Frank Hrebabetzky wrote: > > On Sun, 7 Sep 2003, Jason Chambers wrote: > > > To avoid rebooting you should do a 'checkpc -f' which will check the > > /etc/printcap - making sure that filters exists and are executable and > > that spool directories exists (-f makes it create any spool directories > > with right permissions rather than just complaining about problems). > > My linux doesn't know that command. What package is it from? >
lprng. Sorry I thought that was standard lpd command, I should have check
that. Very useful though, especially when you forget the executable
permission on your filter (read I never done that before :-) ).
> > Then a 'lpc reread' (or calling the init.d script with reload) will get
> > lpd to use the new printcap.
>
> 'reread' seems to be from lprng command, my lpc (lpr-ppd) doesn't accept
> it. I tried 'lpc stop all' and 'lpc start all' instead and it worked.
>
> > Odd. Copied and pasted your printcap entry from the email and it worked
> > on my machine (I use lprng). Have you tried lpq -v (use multiple v's
> > for even more output) it should show when it started the filter, what
> > its outcome was.
>
> the -v option isn't accepted by my lpq either. It seems the arguments in
> favor of lprng are accumulating.
Yeah lpr-ppd does seem to missing some useful options. lprng has worked
for me without a hitch, and there's a nice HTML manual in lprng-doc
explaining in detail how it all works.
>
> > As you said in a previous mail that /dev/lp0 is working as you can copy
> > a text file to it and it prints then try a simple printcap entry with no
> > filter.
> >
> > lp:
> > :sd=/var/spool/lpd/lp
> > :lp=/dev/lp0
>
> Did that and it works. 'lpr <textfile>' produced output on the printer.
>
> What now? Any hint how to test the filter?
>
Now that the lpd daemon can send to /dev/lp0 does the normal filter
work? Does the test filter containing 'cat' work? Is there any output
from lpd to syslog or other log files?
> Another option would be lprng instead of lpr-ppd. As I wrote earlier, I
> tried it, but lprngtool crashed when I configured my printer. I depend on
> it as long as I don't know how to create a printcap file for my printer
> (Epson Stylus Color 740) by hand. The problem is printer-specific because
> lprngtool didn't crash when I selected another printer. I don't remember
> the exact error message, but it looked as if Tcl/Tk didn't like an empty
> or missing string or option.
>
Its been a long time since I tried the filters that come with the lprngtool, I
can't remember why I stopped using them. I see what you mean about the
Tcl/Tk error though. What about the driver above it (the Epson Stylus 800)? It
may not give the higher resolutions of later models but the ghostscript
drivers are usually pretty compatible so it should work at lower
resolutions.
Using lprngtool you can also add any other filters not listed by typing
the full path in the input filter box instead of clicking select.
I use magicfilter, and it works fine. It should work simply by adding a filter line
to the simple printcap entry you've got working above.
Try adding:
:if=/etc/magicfilter/StylusColor-generic-filter
and see what happens. That filter might not give the highest resolution
that you printer is capable of. There are other Stylus filters in
/etc/magcfilter but not one for your model. However they are all
compatible the just use different resolutions so a quick browse of the
comments in these files should find you a better one of you need it.
Magicfilter relies on other programs to convert different file types so
make sure you look at the Recommended and Suggested packages for other
programs you might need.
--
.''`. Jason Chambers <[EMAIL PROTECTED]>
: :' : Registered linux user #271693
`. `'`
`- http://www.debian.org/ - The Universal Operating System
pgp00000.pgp
Description: PGP signature
