<br><br><div class="gmail_quote">On Thu, May 28, 2009 at 2:46 PM, Dominik Wnek <span dir="ltr"><<a href="mailto:dominalien@netscape.net">dominalien@netscape.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Alessandro Zummo pisze:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Thu, 28 May 2009 08:43:21 +0900<div class="im"><br>
Alesh Slovak <<a href="mailto:alesh.slovak@avasys.jp" target="_blank">alesh.slovak@avasys.jp</a>> wrote:<br>
<br>
<br>
</div><div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
iscan limits itself to the epkowa backend, but Xsane was probably using the epson2 backend, which supports the necessary network protocol, but it seems like it doesn't have support for your particular model. Maybe Alessandro (epson2 backend developer) can help you here.<br>
<br>
</blockquote>
<br></div>
If it has been detected by epson2 there are chances that we can<br>
make it work. I'd need a debug log.<br>
<br>
<br>
</blockquote>
Hello,<br>
<br>
Thank you very much for your answer. I'll be more than happy to assist with this. Please tell me what to do.<br>
<br>
Best regards,<br><font color="#888888">
<br>
Dominik</font><div><div></div><div class="h5"></div></div></blockquote><div><br>Before running your application (xsane, scanimage, etc), run the following from a bash shell:<br><br>export SANE_DEBUG_EPSON2=128<br>export SANE_DEBUG_EPSON2_NET=128<br>
<br>Then run something like following to capture debug logs:<br><br>scanimage 2> scanning.log<br><br>Chris<br></div></div>