Klaus> First of all I was a
Klaus> little bit confused because the Adaptec driver shows still no
Klaus> Modell-ID at SCSI-Startup. But since sane can determine the
Klaus> ID well I suppose this is ok, isn't it?
This appears to be a feature of newer firmware revisions. If SANE
recognizes your scanner, you should be OK, though.
Klaus> I tried to scan a
Klaus> LineArt picture and everything seems to work well. But when I
Klaus> tried to scan Color or even Grayscale pictures the scanner
Klaus> mechanic moves to its physical end and makes the well known
Klaus> sound which is described in the PROBLEMS file. I can limit
Klaus> the scaning area to a non-dangerous value, but the image
Klaus> seems to be compressed in y-direction and the scaning range
Klaus> was always more than I have specified on the
Klaus> comandline.
That's strange. It appears as if the line-distance command does not
get issued. If you run sane-0.66, make sure that "option
linedistance-fix" is turned on (if you use the default mustek.conf,
you should be fine, but verify to be sure: it's in
/usr/local/etc/sane.d/mustek.conf).
If you have the linedistance-fix on and it still doesn't work, can you
invoke scanimage with environment variable SANE_DEBUG_MUSTEK set to
255 and send me the output you get?
Klaus> A tip how to get the Adaptec 1505 with the supplied
Klaus> Windows-Twain-Driver working would be very useful too.
Hmmh, sane-scsi(5) lists the Adaptec AHA-1505 to be working fine. I'm
not familiar with that adapter, but if it has some sort of BIOS
configuration, you may have to disable synchronous transfers, tagged
queueing, and target disconnects (as documented in sane-mustek(5)).
If you get it working, please let me know what you had to do so I can
add it to the man page.
--david
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com