I'm wondering if anyone in the linux community has made any efforts in the Lexmark X75 driver.
I've found out that Lexmark does provide a developers kit but I've been told it uses binary libraries which Sane cannot include. http://www.lexmark.com/US/products/info/linux/download.html I am new to this driver programming gig so bare with me. -- ---------------- z0manifest -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20050928/f3da6f56/attachment.html From oliver.schwa...@gmx.de Wed Sep 28 18:21:14 2005 From: oliver.schwa...@gmx.de (Oliver Schwartz) Date: Wed Sep 28 18:21:45 2005 Subject: [sane-devel] Epson 3590 In-Reply-To: <Pine.HPX.4.61.0509280852220.8885@xenon> References: <Pine.HPX.4.61.0509280852220.8885@xenon> Message-ID: <200509282021.15053.oliver.schwa...@gmx.de> Hi, > But as the scanner is slower in preview mode than in normal > scan mode at low resolution, it might be a good idea to > map the preview option to some low-res option in the backend. I don't quite understand that. Are you saying that preview is slower than a normal scan at 200 DPI? (200 DPI should be the lowest resolution for the 3590.) I was under the impression that any frontend would use the lowest available resolution as the default resolution for previewing. Some background: The author of the patch for 3490 support encountered a problem with previews, i.e. the area selected in the preview window of xsane didn't match the area that finally got scanned. Apparently that problem only occurred when using certain resolutions. After setting the lowest possible resolution to 200 DPI that problem was solved, afaik. > Another (although theoretical) problem with the Epson/Snapscan > backend: The backend reads the path of the firmware file from > the snapscan.conf file. What happens if there is more than > one scanner? They'll all use the same firmware :-) I know this is a potential problem, but up to now I didn't get any complaints. If anyone needs this feature I'll think of a solution... /Oliver
