[sane-devel] Sane and microtek2 hangs on large scans

Karsten Festag karsten.festag@gmx.de
Wed, 25 Sep 2002 21:22:01 +0200


Hi Gerald,

Abel forwarded your logfiles to me, thanks. I think you should try the=20
no-backtracking option: Please remove the "#" from the line=20
 # option no-backtrack-option on
in your microtek2.conf file. This file usually resides in=20
/usr/local/etc/sane.d or /etc/sane.d depending on your distribution. You =
have=20
to be root to edit this file.

now please try scanimage with the option --no-backtracking=3Dyes, for exa=
mple:=20
scanimage --no-backtracking=3Dyes --resolution 300 -l 10 -t 10 -x 200 -y =
210=20
>scan.pnm

If you like to use xscanimage or xsane then you find the appropriate opti=
on in=20
the special options menu.

Have luck!=20

Karsten


On Wednesday 25 September 2002 10:38, Edenyard wrote:
> On Mon, 23 Sep 2002 19:47:53 +0200, abel deuring wrote:
> > Can you run another test with SANE_DEBUG_SANEI_SCSI=3D255 and
> > SANE_DEBUG_MICROTEK2=3D255 ? The debug output perhaps gives us a bett=
er
> > clue about the problem.
> >
> > As Henning already wrote, you don't need to set these variables in
> > /etc/profile, but you can set them on the command line.
>
>    Very many thanks for both the prompt response and also the useful
> clues here! I carried out your instructions, both for a 75 DPI scan
> (which worked) and a 150 DPI scan (which failed). The 75 DPI scan
> produced a log file 348346 bytes long, whereas the 150 DPI scan only
> produced one of 74816 bytes.
>
>    I've looked through both of these files, but to be honest, I have no
> real idea what I'm looking for. I'm sure I'd be very unpopular if I
> tried to send these files to the list, so what do you suggest that I do
> with them?
>
>    Thanks in advance!
>
>       Gerald.
>
>
>
>
> _______________________________________________
> Sane-devel mailing list
> Sane-devel@www.mostang.com
> http://www.mostang.com/mailman/listinfo/sane-devel