Chris> Hi ! I ' ve recently bought bought a Mustek ScanEpxress
Chris> 12000SP, because I thought it would be compatble to the
Chris> 1200SP. (1200x600, 30bit, SCSI) Bad mistake. The kernel and
Chris> ./find-scanner report it as "SCANNER Rev.1.01", but the
Chris> backend does not recognize it. So tried to 'strcpy' a couple
Chris> of scanners (MFS-12000SP, CX, ...). With
Chris> SANE_DEBUG_MUSTEK=128, I can see that the connection to the
Chris> scanner is established, but it quits scanning
Chris> immediately. (Not even one line, Out of memory, 0 bytes
Chris> read). SCSI-Buffers is increased from 32k to 128k.
The out of memory most likely occurs due to get_image_status ()
getting bad values for the # of bytes per line etc.
Chris> Kernel &
Chris> Sane recompiled. It seems that the scanner tries to read
Chris> several lines to the SCSI buffer and quits, when this buffer
Chris> is full. Is there a chance make the scanner work?
Your best bet right now would be to try to guess or reverse-engineer
the changes in the ScanExpress. My recent inquiries to Mustek Taiwan
regarding more docs have not been successful. But if more people keep
asking for docs, someone might just get lucky.
--david
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com