Jesse> I also think that I'm not gonna have much luck with the
Jesse> ImageReader scanner. But, I wanted to give it a try, since
Jesse> it may use a driver that's compatible with other drivers (the
Jesse> manufacturer mentioned Plustek -- is this promising?).
OK, it's certainly worth a shot. I don't know about Plustek either,
though.
Jesse> But, even supposing that the driver is not supported,
Jesse> shouldn't saned find the scanner? Or are my intuitions
Jesse> wrong?
No, saned finds only what the other programs find. But it won't
_tell_ you what it finds, so it's not the best choice for debugging
things.
Jesse> Here's what I get from scanimage:
Jesse> root:/home/jesse$ scanimage
Jesse> scanimage: sane_start: Invalid argument
Here is what's going on: if you do "scanimage -L" you'll see the list
of available devices. You'll probably see pnm:0 and pnm:1 only. By
default, scanimage opens the first available device. In your case,
pnm:0. By default, pnm:0 attempts to read /tmp/input.ppm and since
you probably don't have such a file, the scan fails with "Invalid
argument".
Jesse> Or else: root:/home/jesse$ scanimage -d /dev/sga
Jesse> scanimage: open of device /dev/sga failed
/dev/sga is not a valid device name in the default configuration. See
sane-dll(5) for some details, but briefly, you'd use:
mustek:/dev/sga
or
umax:/dev/sga
or
hp:/dev/sga
depending on the driver you want to use.
--david
-- Source code, list archive, and docs: http://www.azstarnet.com/~axplinux/sane/ To unsubscribe: mail -s unsubscribe sane-devel-request@listserv.azstarnet.com