On Tuesday 23 September 2008 07:59:58 am William Jojo wrote: > Anyone see this before?
While I haven't seen ths specific issue before, it may be part of a class of issues around drivers setting data associated with the printer instance on the share. Often called the data blob. When the blob isn't set properly on the share, drivers can malfunction in strange and unpleasant ways. My suggestions are: i. Install the driver locally and use the MS property page for the print share to load the driver again. Set some of the data properties (eg. font or duplexer). This may force the blob to get set. ii. Alternatively, you could change your print architecture to use the standard MS PostScript driver and Ghostscript to convert the print jobs to the printer's language (PCL). The PostScript driver appears to avoid blob related issues. A good description of this works can be found at: http://www.enterprisenetworkingplanet.com/netsysm/article.php Regards, Mark Gannon -- There are risks and costs to a program of action. But they are far less than the long-range risks and costs of comfortable inaction. -John F. Kennedy
signature.asc
Description: This is a digitally signed message part.
-- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
