> Off the very top of my head, look through the backend man page and
> try the "no precal" option --- there is some kind of calibration
> that some scanners do on color images, which ends up making them
> miss the first 1/2 cm of the scanning tray; the backend by default
> trys to calibrate once, and then shut it off for successive scans.
> This is tricky, because the scanner hangs if it is not calibrated
> at all. Maybe something is sending some kind of reset to the scanner,
> so it loses the calibration info? It's been a while.
> Like I said, it will take me a few days to get rev'ved up....
>
> -matt marjanovic
I (a would-be user of SANE-OS2) believe I've tried inserting "#option
no precal" into the "microtek.conf" file, but to no avail. Even though
the list of capabilities reported by the E3 does include
precal-suppression, every "scanimage" run seems to start with a precal.
Of course, many aspects of configuration seem to be different when one
compares Linux-SANE and OS/2-SANE, (probably because the filesystems
themselves are so different), so maybe Yuri can reassure us whether/how
"#option ..." lines actually get processed?
Irv Thomae
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com