[sane-devel] Oops . . here's the logs (xsane-win32/saned + epson 1650 prob)

Henning Meier-Geinitz henning@meier-geinitz.de
Thu, 10 Jun 2004 16:10:41 +0200


On Thu, Jun 10, 2004 at 07:09:36AM -0700, Keith Clayton wrote:
> What sort of steps are availble for me to take debugging-wise on the
> windows end?
> If xsane is started from the command prompt, are there any swithces
> available to generate debugging output at the command prompt?

I don't know how setting environment variables works on windows but
with bash you'd do

export XSANE=DEBUG=255
export SANE_DEBUG_NET=255

XSANE_DEBUG will produce a huge amount of debug messages.