It saddens me to say it...but should I be abandoning the laser printer that I purchased only a year and a half ago. It's been sooooo long does either Apple or Epson ever plan to support my $400 paperweight?
There is still some hope, but it is looking pretty grim.
1. GIMP does not support the 5700i because it does not use Postscript. They also stated they would not write a driver cause it would take too much time.
2. Last Saturday the French site for Epson posted a LaserWriter driver for the 5800 which is a postscript printer. The good thing is that this driver has the Epson utilities in it, so theoritically all that is left to do is the actual driver for the 5700i.
3. I read on another board, that Epson Support had told one person that they would be coming out with a driver in September, needless to say it is now September.
The Omni printer system for Linux does support this printer and maybe even the full blown CUPS also probably comes with a driver, so if Epson can just take some time and port the driver over, it should be a lot closer than if they were to start with nothing.
I did some more research on this and it appears that we will have to wait probably for the Linux programmers to port Foomatic to OSX. That is if Epson does not release a driver eventually.
I tried to follow the directions on this site, but this assumes that you are running Linux and that Foomatic is already installed, along with Ghostscript and CUPS. I was able to apply the PPD file for the EPL-5700 to my printer and see it in Print Center but the in between framework is missing: the cupsomatic script and Foomatic system. I can print but the printer does not respond, so CUPS is not sending the data to the printer.
I couldn't figure out where to put the cupsomatic script since OSX does not have the directory substructure of redhat.
I have the same problem, my printer isnt supported for USB printer sharing and I have 2 computers. THe printer (Samsung ML 1210) is a great printer, but it just isnt supported by 10.2 USB printer sharing, and it has some bugs in 10.2, but Im sure Samsung will work them out - eventually.