> All problems are encountered using xscanimage using the latest
> available release (compiled by me) of SANE (0.64) and GIMP (0.99.11).
> 1) Unable to get xscanimage to function as a plug-in. I have not
> applied the patches as described in the xscanimage FAQ, but I read
> it as if that patch is only for older versions of gimp.
Probably the configure script doesn't detect GIMP properly and thus doesn't
build the "gimpified" version. Check the configure values, if all gimp-
related items are found. If not, fake them.
> 2) Color scan resolution set to 100, out.pnm is reported to "appear
> truncated" by xv on occasion. Rescanning will usually produce a
> 3) Color scan resolution set to 100, first scan comes out at incorrect
I suppose these are related. Could you cross-check that with scanimage ?
> 5) My new Mustek 600 II CD went past length of bed (made that funky
> noise as described in the man pages) when I made a color scan with
> a resolution of 300 dpi.
Urks. I heard of problem at res>=300 dpi.
> 6) Twice this weekend, the scanner became hung. I was unable to
> unload/reload the aha1542 module to reset the SCSI interface, thus
> I had to reboot.
Aha. Seems to be my problem ... Please turn on DEBUG_MUSTEK=255.
In my case this happens often, if the total number of scanned lines is exactly
1 more than the "natural" size we will get from the scanner. For my configuration
(MFS-12000SP, unpatched SCSI MAXLEN) a sure lockup is acquired by the
parameters --mode Color --resolution 111 -y 131. Could you test those ?
TNX and CU,ANdy
-- Andreas Beck | Email : <becka@sunserver1.rz.uni-duesseldorf.de> ======== GGI - The Right Thing To Do : http://synergy.foo.net/~ggi/ ========
-- Source code, list archive, and docs: http://www.azstarnet.com/~axplinux/sane/ To unsubscribe: mail -s unsubscribe sane-devel-request@listserv.azstarnet.com