scanimage -d mustek:0x36b --resolution 100
It's a bug that the SANE backend picks a default resolution of 18 dpi
when the smallest supported value is 51. A patch would be welcome.
--david
>>>>> On Fri, 19 Feb 1999 22:32:06 +0000, Rene Vellekoop <rmvlkoop@caiw.nl> said:
Rene> Hi there! I use a Mustek 600 II N scanner. 'scanimage -L'
Rene> returns:
Rene> device `pnm:0' is a Noname PNM file reader virtual device
Rene> device `pnm:1' is a Noname PNM file reader virtual device
Rene> device `mustek:0x36b' is a Mustek MFC-06000CZ flatbed scanner
Rene> Looks quite nice I think, the scanner moves about a centimeter
Rene> up and down, lamp goes on, no problem..
Rene> But when I acctually want to scan an image the scanner gives
Rene> me the same action as the 'initialisation' as mentioned above
Rene> but then locks up. CTRL-C sais: stopping scanner... but this
Rene> has no effect I have to kill the scanimage process and a 0
Rene> byte output file remains.
Rene> another strange thing:
Rene> --resolution 51..600dpi (in steps of 1) [18] Sets the
Rene> resolution of the scanned image. (look at the default value
Rene> and the range given)
Rene> and when I do:
Rene> # scanimage --resolution 100
Rene> I get: scanimage: unrecognized option `--resolution'
Rene> the --preview option also makes scanimage lock up.
Rene> Anybody got an answer?
Rene> Thanks in advance!
Rene> Greets!
Rene> Rene Vellekoop
Rene> -- Source code, list archive, and docs:
Rene> http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe
Rene> sane-devel | mail majordomo@mostang.com
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com