search for: lpdomatic

Displaying 4 results from an estimated 4 matches for "lpdomatic".

2003 Mar 19
0
Problem accessing Windows printer from Linux side
...Hat Printer Config, now I can see the status of the printer is "Idle (accepting jobs)" in the Print dialog, but whenever I print, nothing occurs. Checking /var/spool/lpd/LaserJet4500/status.pr I found the folowing lines: IF filter 'mf_wrapper' filter msg - '/usr/sbin/lpdomatic: postscript job line1=>%!PS-Adobe-3.0' at 2003-03-19-10:45:41.787 ## A=root@wuyw+671 number=671 process=1743 IF filter 'mf_wrapper' filter msg - '<' at 2003-03-19-10:45:41.787 ## A=root@wuyw+671 number=671 process=1743 IF filter 'mf_wrapper' filter msg...
2003 Jan 29
18
None
Hi friends We want communciate our windows 2000 computers with samba. We want use samba as domain controller. Before we had NT computers. Now we want install windows 2000 computers. For that reason we do all things again. At first step we have a problem. We want to add the computers to a domain. But when we try to do that it displays a message to enter the username and password. We do not
2004 Mar 11
1
Newbe samba confusion - windows to samba to lpd which driver does the translation?
...the windows queue. At this stage I assume we have printer codes in the spool queue? Next the data is past across the network to a samba spool queue /var/spool/samba. Next the samba server demon picks up this data and passes it to the linux printing system and yet another set of 'drivers' gs lpdomatic hpijs etc. process the data an it is spooled ready to be finally to be passed to an actual device driver /dev/lp0 or whatever. First question is this simplified picture correct? I think it is because I have a working Epson printer setup which works just fine. If so then how on earth is the data n...
2001 Oct 31
0
[RHSA-2001:138-10] Comprehensive Printing Update
...bug, which caused all users of the 'stp' driver, including virtually all Epson printers, to fail to print as a result of miscalculated driver data. A filtration problem, which caused many PCL and PJL printers to produce garbage. This was solved by switching to the foomatic distributed 'lpdomatic' program for filtration. A few printconf crashers in the new printconf-tui programme. And in addition, this update adds the Omni print drivers from IBM, which support an additional 300 printers. 4. Solution: Before applying this update, make sure all previously released errata relevant to y...