Hello, I did incorporate it into the backend.
Here are the source files for that backend. Feel free to correct anything wrong. Thank you. Patrick Lessard. -------------- next part -------------- A non-text attachment was scrubbed... Name: umax1220u_backend.zip Type: application/x-zip Size: 18809 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060331/4b099cdb/umax1220u_backend.bin From llg...@earthlink.net Fri Mar 31 19:33:01 2006 From: llg...@earthlink.net (Lonny L. Granstrom) Date: Fri Mar 31 19:33:44 2006 Subject: [sane-devel] ADF jam creating empty output files Message-ID: <89f353d2-2403-404c-8677-86e6b0354...@earthlink.net> Hello, 1st post. Developer question. Using scanimage, scanadf, and fujitsu back-end, specifically model fi-4220C2. When an ADF "Document feeder jammed" error occurs I am catching the return code and STDERR message. Then, allowing Users 15 seconds to clear jam before beginning scanning loop again. Program written as BASH Shell script. Problems: 1. scanimage & scanadf both create an output file for the document that was not completely scanned due to ADF jam. 2. Output file is "blank". ImageMagick identify command finds image file construction correct, just empty. 3. These "blank" files occur in both PNM & TIFF formatted output. Should I code to remove the last output file produced every time the "Document feeder jammed" occurs? Is there another method or parameter to use to eliminate these "blanks"? Regards, Lonny L. Granstrom
