<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<a class="moz-txt-link-abbreviated" href="mailto:pierre@pirsoft.dnsalias.org">pierre@pirsoft.dnsalias.org</a> wrote:
<blockquote cite="mid453BCD9B.6090400@pirsoft.dnsalias.org" type="cite">
<pre wrap="">Aaron Lawrence schrieb:
</pre>
<blockquote type="cite">
<pre wrap=""><a class="moz-txt-link-abbreviated" href="mailto:pierre@pirsoft.dnsalias.org">pierre@pirsoft.dnsalias.org</a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Aaron Lawrence schrieb:
</pre>
<blockquote type="cite">
<pre wrap="">Hello all,
</pre>
</blockquote>
<pre wrap="">[...]
</pre>
<blockquote type="cite">
<pre wrap="">I used the awk and perl script on <a class="moz-txt-link-freetext" href="http://john.daltons.info/lide60/">http://john.daltons.info/lide60/</a> to
generate some output of plugging in the scanner, initializing and a
300dpi color scan. It was a while ago when I took the usb log but I
believe I canceled the scan partway through.
<a class="moz-txt-link-freetext" href="http://www.ford23.com/canon_lide_80/300dpi_color/00index.html">http://www.ford23.com/canon_lide_80/300dpi_color/00index.html</a>
</pre>
</blockquote>
<pre wrap="">Can you somehow give me access to the raw log? That way i should be able
to create a test program replicating the behavior in the log to figure
out which parts of the scanning process is missing. Private mail should
be possible, if your web server does not allow you to upload such large
amounts of data. Alternatively i can setup a ftp server.
</pre>
</blockquote>
<pre wrap="">Here's the raw log.
<a class="moz-txt-link-freetext" href="http://www.ford23.com/canon_lide_80/usbsnoop-300dpi_color.log.zip">http://www.ford23.com/canon_lide_80/usbsnoop-300dpi_color.log.zip</a> (38 MB zipped,
180MB unzipped)
</pre>
</blockquote>
<pre wrap=""><!---->
So, here is the small test program. It closely resembles the actions in
the log, but i still expect it to hang, because there seem to be at
least two gaps in the log. To compile simply use make in the directory.
In the meantime i will try to create a patch that makes sane work with
your scanner.
Regards,
Pierre
</pre>
</blockquote>
<br>
Thank you very much. The test program did hang like you expected.<br>
<br>
The first time I ran it it produced this output:<br>
<br>
Info: open_scanner: Success<br>
usbsnoop-300dpi_color.c:33207: failed assertion:
set_read_register(0x41) == 0xf8<br>
usbsnoop-300dpi_color.c:33208: failed assertion:
set_read_register(0x41) == 0xf8<br>
usbsnoop-300dpi_color.c:33209: failed assertion:
set_read_register(0x41) == 0xf8<br>
usbsnoop-300dpi_color.c:33210: failed assertion:
set_read_register(0x41) == 0xf8<br>
<br>
<br>
The second time I ran it, this was the output:<br>
<br>
Info: open_scanner: Success<br>
usbsnoop-300dpi_color.c:2: failed assertion: set_read_register(0x41) ==
0x50<br>
usbsnoop-300dpi_color.c:3: failed assertion: set_read_register(0x41) ==
0x50<br>
usbsnoop-300dpi_color.c:4: failed assertion: set_read_register(0x6b) ==
0x00<br>
usbsnoop-300dpi_color.c:19: failed assertion: set_read_register(0x6c)
== 0x00<br>
usbsnoop-300dpi_color.c:22: failed assertion: set_read_register(0x6d)
== 0x0f<br>
usbsnoop-300dpi_color.c:7803: failed assertion: unknown8e(24) == 0x00<br>
usbsnoop-300dpi_color.c:33207: failed assertion:
set_read_register(0x41) == 0xf8<br>
usbsnoop-300dpi_color.c:33208: failed assertion:
set_read_register(0x41) == 0xf8<br>
usbsnoop-300dpi_color.c:33209: failed assertion:
set_read_register(0x41) == 0xf8<br>
usbsnoop-300dpi_color.c:33210: failed assertion:
set_read_register(0x41) == 0xf8<br>
<br>
Every time I run it after that I get the same output as the second time
and once I disconnect and reconnect the scanner it reverts back to the
original output.<br>
<br>
<br>
Thank you,<br>
Aaron<br>
</body>
</html>