after fiddling with it for a few minutes this evening I found out that
the scan works fine when you place xscanimage in any mode other than
color. IE, if I switch scan-mode to grey, I can scan away to my hearts
content... but if I switch it to color, I get nothing.
Below are scsi-commands to the scanner from xscanimage (they start at the
window-id) The first comes from a color scan, the second from a greyscale
scan.
Now here's the interesting bit... between a color scan (that fails):
v-window id
home /kernel: 000: 00 00 00 00 00 00 00 f6 01 00 00 1b 00 1b 00 00
home /kernel: 016: 00 00 00 00 00 00 00 00 27 c1 00 00 36 b0 00 7f
home /kernel: 032: 00 05 08 00 03 03 00 00 00 00 00 00 00 00 00 00
Image Comp Mode ------^^
home /kernel: 048: 01 80 ff 00 00 00 0f 11 01 00 00 00 00 00 00 00
Color select ----^^
and a greyscale scan (that works): v-window id
home /kernel: 000: 00 00 00 00 00 00 00 52 00 00 00 1b 00 1b 00 00
home /kernel: 016: 00 00 00 00 00 00 00 00 27 c1 00 00 36 b0 00 7f
home /kernel: 032: 00 02 08 00 03 03 00 00 00 00 00 00 00 00 00 00
Image Comp Mode ------^^
home /kernel: 048: 01 00 ff 00 00 00 0f 11 01 00 00 00 00 00 00 00
Color select ----^^
There are only three differences:
1. The window-id, color = 01 (for red), grey = 00 (for all).
2. The 'Image Composition mode', rgb_full = 05, grey = 02.
3. The 'select color' flag, which appears to be 80 for color, and 00 for
grey.
The 00 for grey looks correct, but the 80 for color doesn't look right to
me. Isn't 80 the value for WD_speed_smear? Could there be some strange
mis-calculation going on here?
Thanks again, and any insight would be greatly appreciated!
Jay
--- Everyone can be taught to sculpt: Michelangelo would have had to be taught how not to. So it is with the great programmers.
-- Source code, list archive, and docs: http://www.azstarnet.com/~axplinux/sane/ To unsubscribe: mail -s unsubscribe sane-devel-request@listserv.azstarnet.com