Does anyone have any hints about at least the first following problem ?
1. After a scan is complete and also most times when 'scanimage' is stopped
by ctrl-c, I get a scsi timeout (after 10 minutes) in return to the last
scsi stop command sent by the mustek backend (in stop_scan()).
Only at certain times (e.g. while image data is actually transferred
from the scanner to the computer) the scan terminates cleanly and the
scanner can be used immediately for a next try.
I tried increasing the timeout in the kernel's scsi.c, but it didn't
change anything. After the 10 minutes passed, the kernel reports the
timeout in the syslog and the scanner carriage moves a very little bit.
To me it looks like the scanner expects something else before the stop
command and doesn't recognize it as such ? The last debug output of the
program seems to be correct, (I'm not sure about the 1000):
"Read 4096 bytes... Read 1000 bytes... Read 0 bytes..." - halt.
BTW, the image file then seems to be complete and correct.
2. While
scanimage --mode color -y 100
does what I expected it to,
scanimage -y 100 --mode color
results in a full 36cm scan (-y 100 is ignored).
bibi,
Kolja
--- Kolja Waschk (kawk@Home.Yo.COM) http://WWW.TU-Harburg.DE/~sekw0206 Operator of "Yo.COM news & mail service for small budget" Tel +49-40-8891-3034, BBS/Fax -3035 (ISDN V.110/X.75 & ZyXEL/V.34)
-- Source code, list archive, and docs: http://www.azstarnet.com/~axplinux/sane/ To unsubscribe: mail -s unsubscribe sane-devel-request@listserv.azstarnet.com