kopia lustrzana https://gitlab.com/sane-project/website
68 wiersze
3.2 KiB
HTML
68 wiersze
3.2 KiB
HTML
<!-- received="Mon Mar 9 22:15:46 1998 PST" -->
|
|
<!-- sent="Tue, 10 Mar 1998 01:16:05 -0500" -->
|
|
<!-- name="Matto Marjanovic" -->
|
|
<!-- email="maddog@mir.com" -->
|
|
<!-- subject="Microtek woes" -->
|
|
<!-- id="199803100616.BAA18507@yoo-hoo.ai.mit.edu" -->
|
|
<!-- inreplyto="" -->
|
|
<title>sane-devel: Microtek woes</title>
|
|
<h1>Microtek woes</h1>
|
|
<b>Matto Marjanovic</b> (<a href="mailto:maddog@mir.com"><i>maddog@mir.com</i></a>)<br>
|
|
<i>Tue, 10 Mar 1998 01:16:05 -0500</i>
|
|
<p>
|
|
<ul>
|
|
<li> <b>Messages sorted by:</b> <a href="date.html#64">[ date ]</a><a href="index.html#64">[ thread ]</a><a href="subject.html#64">[ subject ]</a><a href="author.html#64">[ author ]</a>
|
|
<!-- next="start" -->
|
|
<li> <b>Next message:</b> <a href="0065.html">Helmut Koeberle: "Re: Sane 0.71 and CanoScan 300"</a>
|
|
<li> <b>Previous message:</b> <a href="0063.html">Matto Marjanovic: "Re: Microtek ScanMaker 330"</a>
|
|
<!-- nextthread="start" -->
|
|
<li> <b>Next in thread:</b> <a href="0067.html">Rogier Wolff: "Re: Microtek woes"</a>
|
|
<li> <b>Reply:</b> <a href="0067.html">Rogier Wolff: "Re: Microtek woes"</a>
|
|
<li> <b>Reply:</b> <a href="0073.html">Didier Carlier: "Re: Microtek woes"</a>
|
|
<li> <b>Reply:</b> <a href="0082.html">Stefano Buelow: "Re: Microtek woes"</a>
|
|
<!-- reply="end" -->
|
|
</ul>
|
|
<!-- body="start" -->
|
|
Hey, all,<br>
|
|
<p>
|
|
I've been looking into why the Microtek backend has suddenly started dying<br>
|
|
with sane-0.71....<br>
|
|
<p>
|
|
Ugh -- I'm not sure what all has caused this problem to rear its head now,<br>
|
|
but part of the problem is that, apparently, the Microtek scanners do *not*<br>
|
|
follow the SCSI-II standard for the REQUEST_SENSE command reply --- and the<br>
|
|
Linux mid-level scsi driver (scsi.c) is coded to parse standard sense data,<br>
|
|
not the weird stuff pumped out by these scanners.<br>
|
|
Thus, during error conditions, the scsi driver is certainly confused by what<br>
|
|
the scanner tells it. <br>
|
|
<p>
|
|
Perhaps one solution is to try to ignore the scsi driver's complaints, and<br>
|
|
have the backend send its own REQUEST_SENSE under suspicious circumstances.<br>
|
|
I'm playing with it.<br>
|
|
<p>
|
|
In any case, does any one have any insights into how other OS's handle scsi<br>
|
|
CHECK_CONDITION conditions and REQUEST_SENSE requests? No one else has<br>
|
|
complained yet (well, except for a similar unresolved problem in OS/2, and<br>
|
|
that thing with Solaris....).<br>
|
|
<p>
|
|
-matt m.<br>
|
|
<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="0065.html">Helmut Koeberle: "Re: Sane 0.71 and CanoScan 300"</a>
|
|
<li> <b>Previous message:</b> <a href="0063.html">Matto Marjanovic: "Re: Microtek ScanMaker 330"</a>
|
|
<!-- nextthread="start" -->
|
|
<li> <b>Next in thread:</b> <a href="0067.html">Rogier Wolff: "Re: Microtek woes"</a>
|
|
<li> <b>Reply:</b> <a href="0067.html">Rogier Wolff: "Re: Microtek woes"</a>
|
|
<li> <b>Reply:</b> <a href="0073.html">Didier Carlier: "Re: Microtek woes"</a>
|
|
<li> <b>Reply:</b> <a href="0082.html">Stefano Buelow: "Re: Microtek woes"</a>
|
|
<!-- reply="end" -->
|
|
</ul>
|