Hello, On Jan 3 14:55 Dave Howorth wrote (shortened):
is it worth trying Gutenprint?
Gutenprint is the successor of Gimp-Print but Gutenprint is not yet released (still in beta state). Now I did read what you posted in your earlier mail: http://www.linuxforum.com/forums/index.php?s=90bded507a9d366a0bf15abe733140ca&showtopic=155538&st=0entry675463 Therefore is seems the RX620 is compatible regarding printing (and perhaps even regarding scanning - see my other mail) with the RX600. If it is really compatible, you should be able to print with Gimp-Print in Suse Linux 9.3 out of the box with one of the following PPDs: /usr/share/cups/model/Epson/Stylus_Photo_RX600-gimp-print.ppd.gz "Epson Stylus Photo RX600 Foomatic/gimp-print (recommended)" /usr/share/cups/model/stp/escp2-rx600.ppd.gz "EPSON Stylus Photo RX600 - CUPS+Gimp-Print v4.2.7" Select the model RX600 in YaST and then you may have to use the [Edit] button to change the preselected PPD. The Gimp-Print driver may not produce the best possible photo quality but for normal printing it should be o.k. Additionally see http://www.linuxprinting.org/show_printer.cgi?recnum=Epson-Stylus_Photo_RX60...
64-bit application -> 64-bit library -> 64-bit kernel interface 32-bit application -> 32-bit library -> 32-bit kernel interface ... It seems obvious that with the current mix of 32-bit and 64-bit systems, it makes sense to design a process boundary in between components with different origins. Isn't CUPS designed that way? Running multiple incompatible versions of libraries on systems is by no means a new problem.
In fact there is no such problem. The linker knows whether to look for the libraries in ...lib... (for 32-bit applications) or in ...lib64... (for 64-bit applications). The only problem on 64-bit architecture is to have all necessary 32-bit libraries available in ...lib... so that the linker can link a 32-bit application with its required 32-bit libraries.
And I thought the whole point of having /usr/lib and /usr/lib64 was that dumb 32-bit software would automatically link to the right libraries.
Normally this works automatically. For example the proprietary binary-only 32-bit application "acroread" (the Adobe PDF Reader) runs well on the 64-bit AMD platform. It looks wrong when the Epson Avasys rastertopips filter is a 32-bit application but is stored in a ...lib64... directory on your system.
You can get rid of all 32-bit/64-bit problems when you simply install the 32-bit version of Suse Linux on your 64-bit system.
That's a depressing thought.
It was only meant as a possible test to prove that it is really a 32-bit versus 64-bit problem and/or as a last resource to get it working with the 32-bit Epson Avasys driver. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/