Hi everyone,
After obtaining the log, and having it looked at by Gerald and
St?phane, the Canon Lide 70 appears that it could be related to the
Canon 600F (not confirmed yet). Anyway, we have filtered the USB
logs, and I wanted to know if anyone would like to look at them.
I have no idea what th
On 5/21/07, Tom Garvin wrote:
>
> Correct. That was my first attempt to address the issue, but I backed
> out these changes (I rebuilt/installed from a fresh backend archive)
> when you're solution (adding "option force-a3" to avision.conf) worked
> so well. That was all on my development workst
in an older mail in this thread (quoted below) you said:
I changed the value of A3_Y_RANGE (line 1419 of avision.c) from 16.5
to 17, recompiled and reinstalled...
allan
On 5/21/07, Tom Garvin wrote:
>
> This solution worked on my development system, but now I'm having a
> similar issue with the
Correct. That was my first attempt to address the issue, but I backed
out these changes (I rebuilt/installed from a fresh backend archive)
when you're solution (adding "option force-a3" to avision.conf) worked
so well. That was all on my development workstation.
Now I'm on a new system, and I'm
This solution worked on my development system, but now I'm having a
similar issue with the production system. While they're both running
the same version of SANE (backend=*.18, frontend=*.14), the option no
longer seems to work. If I run 'scanadf -h' without the force-a3 entry,
I see that my hei
On 20/05/07, Julien BLACHE wrote:
> "Hugh McMaster" wrote:
>
> > This is the best explanation, since libusb can communicate with the
> > mouse, so it would get displayed wouldn't it? Although I thought
> > sane-find-scanner was programmed to display scanners only?
>
> There's no way to reliably id
