On Mon, 22 Jan 2001 22:23:35 +0100
Oliver Schwartz <Oliver.Schwartz@gmx.de> wrote:
> Hi,
>
> have you modified your snapscan.conf? It should look like
> scsi AGFA
> scsi COLOR
> scsi Color
> /dev/usbscanner
>
> If this doesn't change the behaviour, set SANE_SNAPSCAN_DEBUG=255, run
> scanimage -L again and mail me the output.
>
> Oliver
>
>
I recompiled sane using the cvs files from the sourceforge page.
I changed my snapscan.conf, and my dll.conf so that it only tries to load the snapscan backend. Now when I run scanimage -L it does not freeze for so long, then it puts up the no scanner found message. (I am guessing the freeze time,is time that sane is trying different drivers.)
I am not sure how to set SANE_SNAPSCAN_DEBUG=255? Should I enter this line in the make file, pass the line as an arguement to ./configure? I ran the following command 'grep -l SANE_SNAPSCAN_DEBUG=255 *' in the sane-backend dir, the backend dir, and the frontend dir but came up with nothing.
I tried just setting SANE_SNAPSCAN_DEBUG=255 in my shell window, and then running scanimage -L, but the output was the same as it always is.
Let me know how to set SANE_SNAPSCAN_DEBUG=255 and I will try again, and email you the output.
<output>
storm:/usr/local/etc/sane.d# scanimage -L
No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
find-scanner tool (if appropriate). Please read the documentation which came
with this software (README, FAQ, manpages).
</output>
Thanks for your help
-- ...elbows out, stick on the ice!-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
This archive was generated by hypermail 2b29 : Mon Jan 22 2001 - 18:47:52 PST