If you put "use client driver = yes" back into the [Samsung] section and uncomment the lines I mentioned in the previous email then Samba will take the output of the win2k client driver and pass it to CUPS, which will in-turn send it to the printer unmodified, which is what the printer wants. If you have "use client driver = yes" in the [Samsung] section and are also using a CUPS driver instead of RAW, what you are doing in effect is trying to pass the document through 2 drivers, which is why Samba complained that it was in an unknown format. The problem is though like you had mentioned, ie this will fix the problem for the win2k machines but cause a problem if you are printing from the local Linux box as it is no longer using the correct printer driver. It's just sending the data out in RAW (Unchanged) format to the printer, which it won't understand. Now if you are printing from a Linux client to a Linux server then I don't think there would be a problem as long as the output from the Linux client to the server was in a format the printer could understand. I don't know for sure as I have never tested this scenario. Another option might be to create 2 CUPS printers exactly the same but one using RAW and the other using the correct driver. Then you could use the one you need with the correct workstation setup. Hope this helps :)
-- Trevor Lauder Web: http://www.thelauders.net E-Mail: [EMAIL PROTECTED] > Came across this. If I can setup Samba/CUPS to use raw printing, would > it effect the Linux clients printing to the same machine? Now would I > just use the KDE/Control Panel applet to change the settings to be "raw" > for the Samsung printer?...not in front of a Linux machine at the moment > > > Using CUPS as a mere spooling print server -- "raw" printing with vendor > drivers download > > You can setup Samba and your Windows clients to use the CUPS print > subsystem just as you would with any of the more traditional print > subsystems: that means the use of vendor provided, native Windows > printer drivers for each target printer. If you setup the [print$] share > to download these drivers to the clients, their GDI system (Graphical > Device Interface) will output the Wndows EMF (Enhanced MetaFile) and > convert it -- with the help of the printer driver -- locally into the > format the printer is expecting. Samba and the CUPS print subsystem will > have to treat these files as raw print files -- they are already in the > shape to be digestable for the printer. This is the same traditional > setup for Unix print servers handling Windows client jobs. It does not > take much CPU power to handle this kind of task efficiently. > > ________________________________ > Open Enterprise Solutions > Open Solutions for an Open World > > Johnny Stork, BA > Calgary, AB > Canada > > http://www.openenterprise.ca > http://www.open-solutions.ca
