ML-1710 & Tiger

Posted on by

Has anybody gotten their Samsung ML-1710 printer to work with Tiger?

I’ve installed the drivers from Samsung’s website (for Mac OS X 10.3), but they do not seem to show up when I add the printer.

10 thoughts on “ML-1710 & Tiger”

  1. I was just trying to figure this out myself and there doesn’t seem to be any mention of it on Samsung’s website. So I guess I wait before I install… :-(

  3. I too got my 1710 working with my Airport on Tiger using the Samsung GDI drivers that Brad linked to.

  4. The 1710 isn’t listed as one of the printers; which one did you select to make it work?

  7. Man, I am so glad I found this post, since I’m having the identical ML-1710/Tiger issue. I only wanted to add that I think the following page explains how to get the Samsung-GDI thing from linuxprinting.org to use the ML-1710 PPD, which is not listed as one of the “supported” printers:

    http://www.macosx.com/content/faq.php/q4597/Printer-Not-Werking-In-Tiger.html

    (Page starts with question about 1740, but explanation towards the end specifies how to get/use the 1710 PPD.)

    I’ll also add that the following page from the same site suggests setting up your printer as a 4500 or 4550 rather than the 1210; I have know idea whether it makes much difference, but I’m going to try to get the 1710 PPD to work tonight.

    http://www.macosx.com/forums/archive/index.php/t-67085.html

    Thanks!!!

  8. Update: When it says it’s not supported, it ain’t supported. The first link I listed above points to where you can get a 1710 PPD, but that page looks like it’s oriented for Windows users; perhaps the options on the Windows driver are different–who knows? Anyway with the 1710 PPD the setup went great, but nothing comes out of the printer–no blinking light, nothing. Stick with the supported 1210 or 4500. I tried both with a .rtfd file with a few simple embedded graphics and I found the b/w shading on the 4500 configuration to be ever so slightly better, but the output could have been identical.

    That first link did, however, point point to where you could get a slightly newer version of the ESP GhostScript thingy.