Another problem: You can have passed the printing data through a driver
twice:
You can either use a printer driver on the server side. Then let Samba
as it is and configure you printer as generic PostScript printer on your
Windows clients. The PostScript is arriving at Samba and passed to CUPS.
C
I could not reproduce this bug. I could print without problems on an HP
Laserjet 4050 PostScript printer which is on a Mandrake 7.2 machine with
Samba 2.07-9mdk. The only bug was that I have to change the entry
"printcap name" from "lpstats" to "lpstat" and for testing without
having a Samba accou
I could not reproduce this bug. I could print without problems on an HP
Laserjet 4050 PostScript printer which is on a Mandrake 7.2 machine with
Samba 2.07-9mdk. The only bug was that I have to change the entry
"printcap name" from "lpstats" to "lpstat" and for testing without
having a Samba accou
I could not reproduce this bug. I could print without problems on an HP
Laserjet 4050 PostScript printer which is on a Mandrake 7.2 machine with
Samba 2.07-9mdk. The only bug was that I have to change the entry
"printcap name" from "lpstats" to "lpstat" and for testing without
having a Samba accou
I have decided to go with cups vs. lpr I set my printing = cups line in
my /etc/smb.conf and until I created a set of symbolic links to lpr-cups
as lpr, etc. nothing worked. I have my Windows boxes configured as a
HP III with postscript (I have an HP III) and when I did a print test
from my win
