stewart
02-02-2002, 12:21 PM
Hi
I'm having a problem printing graphics on my samba networked printer - it just prints out a load of crap - although prints text fine.
I'm using cups on the client and lprng on the server.
Using client side printer drivers to
process the
printer job.
Sending text (ie, a plain text file) to the printer
works fine. If I
try
sending any sort of graphics - anything than is not
plain text
(including
printing from KWord etc, as well as bmp, png gifs etc
etc), the printer
prints a load of crap - it printers the graphics as
though as its text
-
much like if you try viewing the contents of a binary
file on the
console.
The printer is fine if I print non text files on the
server machine,
but
not if I try printing remotely.
I can't see what the problem is: the client PC
(windows and linux)
uses its
printer drivers to process the print job, and then all
that needs to to
happen is the data is sent to the server ready for
printing - without
any
need for server side print drivers. (ie, raw printing)
The printer command in smb.conf is:
print command = lpr -P %p -l %s
above: -l = -o raw
for raw printing
I've tried
print command = lpr -P %p -o raw %s -r
but the -o raw stops the printer from printing - the
job doesn't even
show
on the print queue.
/etc/printcap:
lp||Epson Stylus Color 640:\
:sd=/var/spool/lpd/lp:\
:lf=/var/log/lp-errs:\
:filter_options= --lprng $Z
/etc/foomatic/lpd/lp.lom:\
:if=/usr/sbin/lpdomatic:\
:lp=/dev/lp0:\
:force_localhost:\
:sh:\
:mx#0:
Thanks for any help
I'm having a problem printing graphics on my samba networked printer - it just prints out a load of crap - although prints text fine.
I'm using cups on the client and lprng on the server.
Using client side printer drivers to
process the
printer job.
Sending text (ie, a plain text file) to the printer
works fine. If I
try
sending any sort of graphics - anything than is not
plain text
(including
printing from KWord etc, as well as bmp, png gifs etc
etc), the printer
prints a load of crap - it printers the graphics as
though as its text
-
much like if you try viewing the contents of a binary
file on the
console.
The printer is fine if I print non text files on the
server machine,
but
not if I try printing remotely.
I can't see what the problem is: the client PC
(windows and linux)
uses its
printer drivers to process the print job, and then all
that needs to to
happen is the data is sent to the server ready for
printing - without
any
need for server side print drivers. (ie, raw printing)
The printer command in smb.conf is:
print command = lpr -P %p -l %s
above: -l = -o raw
for raw printing
I've tried
print command = lpr -P %p -o raw %s -r
but the -o raw stops the printer from printing - the
job doesn't even
show
on the print queue.
/etc/printcap:
lp||Epson Stylus Color 640:\
:sd=/var/spool/lpd/lp:\
:lf=/var/log/lp-errs:\
:filter_options= --lprng $Z
/etc/foomatic/lpd/lp.lom:\
:if=/usr/sbin/lpdomatic:\
:lp=/dev/lp0:\
:force_localhost:\
:sh:\
:mx#0:
Thanks for any help