On Monday 29 October 2001 17:32, Roger L.S. Griffiths BSc (Hons) wrote:
On Monday 29 Oct 2001 3:37 pm, jk05308 wrote:
It is a GDI printer. It won't work under lpdold, and with CUPS it won't work unless it is listed when you do "gs -h", which list the supported printers in the GhostScript gs_lib file,. I recently returned a Samsung ML4500 for that very reason.
I have a Samsung ML4600 and have it working under Linux fine. YaST CUPS Configuration utility provided with SuSE 7.2 has the Samsung ML4500 listed despite it being GDI.
YaST2 pulls the mfgr name and model number from the printer bios, but it fails to recognize the printer regardless. I, too, am running a fully installed SuSE 7.2 and when I do a 'gs -h' on GhostScript (where the driver actually is) the ML4500 is NOT listed.
ghostscript (ie gs) does not list my ML4600 either, but my printer is supported according to YaST CUPS Config via three different mechanisms:- Foomatic + lj5gray Foomatic + ljet4 Foomatic + pxlmono
The ML4500 is listed as being supported by ONE mechanism Foomatic + gdi
The ML6000/ML6100 printers are supported by ONE mechanism Foomatic + ljet4
I had tried all of these configs to no avail.
I got this information from YaST2 without any printer connected, just try adding a printer manually with the CUPS printer configuration utility.
That document has not been updated since August 2000 (over 1 year old)! I think it might be somewhat out of date.
I suspect that the drivers may be susecptible to printer changes within the model designation. The GDI is, after all, a WIndows propriatary protocol, and I have no doubts that MS can make tweeks GDI formats that render formerly good Linux drivers worthless on later version of the same model.
Anyway, maybe someone could shed some light on the Foomatic business?
TTFN
Roger