Kelly Price <redwolf@pandora.orbl.org> wrote in message news:<slrnceoiko.34f.redwolf@tygris.strw.org>...
> On 7 Jul 2004 03:35:15 -0700, Kevin
> <kevin360@yahoo.com> probably wrote (unless it was a Kook):
> > Kelly Price <redwolf@pandora.orbl.org> wrote in message news:<slrnceluf4.8lq.redwolf@tygris.strw.org>...
> >> If you try to scan in high-rez (400+ dpi) black and white documents with
> >> Slack 10, you need to manually update your copy of XSane. It'll screw up
> >> your scan if you don't, forcing you to ether go greyscale and massaging
> >> it in Gimp, switching to XScanImage, or upgrading to 0.94, which scans OK.
> >>
> > Odd, I've scanned many documents at 600 dpi in b/w and it comes out
> > fine using the xsane-0.93-i486-1 and sane-1.0.14-i486-2 that's shipped
> > with Slack 10.
>
> That's what I said.

I don't think you fully read what I wrote above. I'm disagreeing with
you, I'm having no problems at all.

> And I checked with two different makes of scanners (an
> Acer/Benq 620U and now a new Canon LiDE 30), and it was Xsane's Gimp
> interface. However, when I manually upped to 0.94, it went away.
>
> Maybe the patch Patrick used didn't work right.

Right now I'm use the xsane-0.93-i486-1 and sane-1.0.14-i486-2
package. I compiled Gimp from source (v 2.0.2) I just did a test
scan with both xsane and using the Gimp with a Canon LiDE 30. The
sheet was scanned at 600dpi in binary mode (b/w). I have no problems
with the older 0.93 xsane package, I didn't need to upgrade to 0.94.

Do you also get these problems when you scan with just xsane? Are you
using libusb or did you compile in the support in the kernel. I'm
using the libusb package.