kopia lustrzana https://gitlab.com/sane-project/website
103 wiersze
4.6 KiB
HTML
103 wiersze
4.6 KiB
HTML
|
<!-- received="Sun Sep 27 06:39:16 1998 PDT" -->
|
|||
|
|
<!-- sent="Sun, 27 Sep 1998 12:23:45 +0200" -->
|
|||
|
|
<!-- name="Bernd Schroeder" -->
|
|||
|
|
<!-- email="bernd@aquila.muc.de" -->
|
|||
|
|
<!-- subject="Re: FW: Re: Microtek ScanMaker V300?" -->
|
|||
|
|
<!-- id="" -->
|
|||
|
|
<!-- inreplyto="XFMail.980926092639.dbr@oto.dyn.ml.org" -->
|
|||
|
|
<title>sane-devel: Re: FW: Re: Microtek ScanMaker V300?</title>
|
|||
|
|
<h1>Re: FW: Re: Microtek ScanMaker V300?</h1>
|
|||
|
|
<b>Bernd Schroeder</b> (<a href="mailto:bernd@aquila.muc.de"><i>bernd@aquila.muc.de</i></a>)<br>
|
|||
|
|
<i>Sun, 27 Sep 1998 12:23:45 +0200</i>
|
|||
|
|
<p>
|
|||
|
|
<ul>
|
|||
|
|
<li> <b>Messages sorted by:</b> <a href="date.html#185">[ date ]</a><a href="index.html#185">[ thread ]</a><a href="subject.html#185">[ subject ]</a><a href="author.html#185">[ author ]</a>
|
|||
|
|
<!-- next="start" -->
|
|||
|
|
<li> <b>Next message:</b> <a href="0186.html">Bernd Schroeder: "Re: FW: Re: Microtek ScanMaker V300?"</a>
|
|||
|
|
<li> <b>Previous message:</b> <a href="0184.html">Shimony: "Epson GT-2000"</a>
|
|||
|
|
<!-- nextthread="start" -->
|
|||
|
|
<!-- reply="end" -->
|
|||
|
|
</ul>
|
|||
|
|
<!-- body="start" -->
|
|||
|
|
Hi,<br>
|
|||
|
|
<p>
|
|||
|
|
On Sat, Sep 26, 1998 at 09:26:39AM -0700, David B. Rees wrote:<br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> On 26-Sep-98 Bernd Schroeder wrote:</i><br>
|
|||
|
|
<i>> > Yes, the bpl is bytes per line and it is too big, and the above value</i><br>
|
|||
|
|
<i>> > differs from the one in "read_image_info" in the trace. At first glance </i><br>
|
|||
|
|
<i>> > it looks as if some memory area is overwritten with wrong data, but</i><br>
|
|||
|
|
<i>> > I don't know how this can happen in the function scsi_read_image_info()</i><br>
|
|||
|
|
<i>> > before the debug information is printed.</i><br>
|
|||
|
|
<i>> > </i><br>
|
|||
|
|
<i>> > Can you please send me another trace with 'option dump 2' set in </i><br>
|
|||
|
|
<i>> > microtek2.conf in addition to the environment variable ? There are</i><br>
|
|||
|
|
<i>> > then som additional debug infos, for example the result area of</i><br>
|
|||
|
|
<i>> > scsi_read_image_info() is printed to stderr as is.</i><br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> OK, I've attached the debugging output for you.</i><br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> > Which compiler did you use to build sane ?</i><br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> I used gcc 2.7.2.3. Should I try another?</i><br>
|
|||
|
|
<p>
|
|||
|
|
No, not necessary.<br>
|
|||
|
|
<p>
|
|||
|
|
<i>> [microtek2] scsi_set_window: ms=0x80554a8, wnd=1</i><br>
|
|||
|
|
<i>> [microtek2] dump_area2: setwindowcmd</i><br>
|
|||
|
|
<i>> [setwindowcmd]</i><br>
|
|||
|
|
<i>> 24000000000000004500</i><br>
|
|||
|
|
<i>> [microtek2] dump_area2: setwindowheader</i><br>
|
|||
|
|
<i>> [setwindowheader]</i><br>
|
|||
|
|
<i>> 000000000000003d</i><br>
|
|||
|
|
<i>> [microtek2] dump_area2: setwindowbody</i><br>
|
|||
|
|
<i>> [setwindowbody]</i><br>
|
|||
|
|
<i>> 0000004800480000000000000000000009f600000db6800080050800008000100000000000000000</i><br>
|
|||
|
|
<i>> 0080ff8080000080ff8080000080ff8080000080ff</i><br>
|
|||
|
|
<i>> [microtek2] scsi_read_image_info: ms=0x80554a8</i><br>
|
|||
|
|
<i>> [microtek2] dump_area2: readimageinfo</i><br>
|
|||
|
|
<i>> [readimageinfo]</i><br>
|
|||
|
|
<i>> 28008000000000001000</i><br>
|
|||
|
|
<i>> [microtek2] dump_area2: readimageinforesult</i><br>
|
|||
|
|
<i>> [readimageinforesult]</i><br>
|
|||
|
|
<i>> 02640732034a0017aa74d2012c0f09f6</i><br>
|
|||
|
|
<p>
|
|||
|
|
This is the information, that the scanner returns (as is) and it definitely<br>
|
|||
|
|
junk. According to the documentation the four values for "bpl", "ppl", "lines"<br>
|
|||
|
|
and "remaining bytes" are each returned in 4 bytes in little endian order.<br>
|
|||
|
|
The above output looks as if the first 6 bytes contain the correct values<br>
|
|||
|
|
for "bpl", "ppl" and "lines" in 2 bytes each and "remaining bytes" in 4 bytes,<br>
|
|||
|
|
with the last 6 bytes being something arbitrary.<br>
|
|||
|
|
<p>
|
|||
|
|
Looks as if I have to create a workaround for the V300.<br>
|
|||
|
|
<p>
|
|||
|
|
It would be interesting to know, if this is the case for all modes (color,<br>
|
|||
|
|
gray ...).<br>
|
|||
|
|
<p>
|
|||
|
|
<i>> [microtek2] scsi_read_image_info: ppl=40109874, bpl=55181335, lines=-1435184639,</i><br>
|
|||
|
|
<i>> remain=739183094</i><br>
|
|||
|
|
<i>> [microtek2] sane_start: Scan buffer too small</i><br>
|
|||
|
|
<p>
|
|||
|
|
Bernd<br>
|
|||
|
|
<p>
|
|||
|
|
<pre>
|
|||
|
|
--
|
|||
|
|
Bernd Schroeder
|
|||
|
|
Email: <a href="mailto:bernd@aquila.muc.de">mailto:bernd@aquila.muc.de</a>
|
|||
|
|
PGP public key available: <a href="mailto:pgp@aquila.muc.de">mailto:pgp@aquila.muc.de</a> | Subject: send key
|
|||
|
|
<p>
|
|||
|
|
<pre>
|
|||
|
|
--
|
|||
|
|
Source code, list archive, and docs: <a href="http://www.mostang.com/sane/">http://www.mostang.com/sane/</a>
|
|||
|
|
To unsubscribe: echo unsubscribe sane-devel | mail <a href="mailto:majordomo@mostang.com">majordomo@mostang.com</a>
|
|||
|
|
</pre>
|
|||
|
|
<!-- body="end" -->
|
|||
|
|
<p>
|
|||
|
|
<ul>
|
|||
|
|
<!-- next="start" -->
|
|||
|
|
<li> <b>Next message:</b> <a href="0186.html">Bernd Schroeder: "Re: FW: Re: Microtek ScanMaker V300?"</a>
|
|||
|
|
<li> <b>Previous message:</b> <a href="0184.html">Shimony: "Epson GT-2000"</a>
|
|||
|
|
<!-- nextthread="start" -->
|
|||
|
|
<!-- reply="end" -->
|
|||
|
|
</ul>
|