Henning Meier-Geinitz wrote:
> Which scanner do you have?
UMAX Astra 600s
> Local scanning works?
Yes, perfectly.
> * Use a current version of SANE (1.0.3)
Unfortunately, the machine is a 486 with very little hard drive space,
so having to compile SANE on it is something I'd like to avoid, and
there is no pre-compiled binary for 1.0.3.
> * To look for the source of errors, use saned directly on the command
> line (disable it in inetd.conf while testing):
> saned -d128
> You will get some information in the syslog.
How exactly do you access syslog information? I get nothing on the
console, and I can't find any log file or anything...
> You can set variables in this mode so to get information e.g. about
> Mustek scanners you would use SANE_DEBUG_MUSTEK=255 saned -d128
> The debug output from the backend is printed directly to the console.
When I type SANE_DEBUG_UMAX=255 saned -d128, I simply get
"SANE_DEBUG_UMAX=255: Command not found."
> * At the client, use
> SANE_DEBUG_DLL=255 SANE_DEBUG_NET=255 to find out where the segfault
> occurs.
Again, I'm not really sure where these options should be typed...
I have made some progress, however. I've found, when I run saned -d128
from the command line, XSane running on the client will see the scanner
on the server. I can begin a preview capture, and it seems to work okay
at first, but as it nears the completion of the preview scan, saned dies
on the server and XSane dies on the client.
Thanks for all your help!
Matthew
"If your mirror has a monster in it, do not shout.
This kind of situation does not call for freaking out.
And do nothing that you would not like to see him do
'cause, that monster in the mirror, he just might be you."
- Grover Monster
-- 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 : Sun Nov 12 2000 - 10:41:25 PST