kopia lustrzana https://gitlab.com/sane-project/website
81 wiersze
3.7 KiB
HTML
81 wiersze
3.7 KiB
HTML
<!-- received="Tue Mar 10 02:14:32 1998 PST" -->
|
|
<!-- sent="Tue, 10 Mar 1998 11:04:24 +0100 (MET)" -->
|
|
<!-- name="Rogier Wolff" -->
|
|
<!-- email="R.E.Wolff@BitWizard.nl" -->
|
|
<!-- subject="Re: Microtek ScanMaker 330" -->
|
|
<!-- id="199803101004.LAA01169@cave.BitWizard.nl" -->
|
|
<!-- inreplyto="199803100608.BAA18481@yoo-hoo.ai.mit.edu" -->
|
|
<title>sane-devel: Re: Microtek ScanMaker 330</title>
|
|
<h1>Re: Microtek ScanMaker 330</h1>
|
|
<b>Rogier Wolff</b> (<a href="mailto:R.E.Wolff@BitWizard.nl"><i>R.E.Wolff@BitWizard.nl</i></a>)<br>
|
|
<i>Tue, 10 Mar 1998 11:04:24 +0100 (MET)</i>
|
|
<p>
|
|
<ul>
|
|
<li> <b>Messages sorted by:</b> <a href="date.html#66">[ date ]</a><a href="index.html#66">[ thread ]</a><a href="subject.html#66">[ subject ]</a><a href="author.html#66">[ author ]</a>
|
|
<!-- next="start" -->
|
|
<li> <b>Next message:</b> <a href="0067.html">Rogier Wolff: "Re: Microtek woes"</a>
|
|
<li> <b>Previous message:</b> <a href="0065.html">Helmut Koeberle: "Re: Sane 0.71 and CanoScan 300"</a>
|
|
<li> <b>In reply to:</b> <a href="0063.html">Matto Marjanovic: "Re: Microtek ScanMaker 330"</a>
|
|
<!-- nextthread="start" -->
|
|
<!-- reply="end" -->
|
|
</ul>
|
|
<!-- body="start" -->
|
|
Matto Marjanovic wrote:<br>
|
|
<p>
|
|
<i>> It seems to follow some kind of SCSI-II standard. I don't know how</i><br>
|
|
<i>> similar it is to the command sets of other brands of new scanners,</i><br>
|
|
<i>> but perhaps one generic SCSI-II scanner backend will be possible.</i><br>
|
|
<i>> We can dream, no?</i><br>
|
|
<p>
|
|
The SCSI-II standard about scanners is sufficiently vague that you<br>
|
|
cannot build a scanner solely on the specs. <br>
|
|
<p>
|
|
I mean that a disk drive implements a well-defined "read" and "write",<br>
|
|
and that's sufficient for a functional disk drive. The amount of<br>
|
|
commands that a scanner needs to support to be able to function is<br>
|
|
much larger, but the specs leave enough "vague" that a manufacturer<br>
|
|
almost always needs to do essential stuff in "vendor extentions".<br>
|
|
<p>
|
|
Tamarack sent me their interpretation of the SCSI-II specs. I was able<br>
|
|
to build the Tamarack backend on that. Getting access to the SCSI-II<br>
|
|
specs and noting the similarity, I wasn't able to get the coolscan to<br>
|
|
work with the tamarack driver. (I didn't put in very much time though).<br>
|
|
<p>
|
|
A general SCSI-II standard driver would need:<br>
|
|
<p>
|
|
- A "standard" way to approach a scanner, adhering to SCSI-II/scanner<br>
|
|
as close as possible.<br>
|
|
<p>
|
|
- A config file that specifies at what points this scanner is<br>
|
|
"different"from the standard: Specifying extra required commands at<br>
|
|
certain points, and ways to extract information like "bytes per<br>
|
|
line" from the replies.<br>
|
|
<p>
|
|
It is not a trivial task to create such a backend. <br>
|
|
<p>
|
|
Roger. <br>
|
|
<p>
|
|
<p>
|
|
<pre>
|
|
--
|
|
If it's there and you can see it, it's REAL <a href="mailto:|___R.E.Wolff@BitWizard.nl">|___R.E.Wolff@BitWizard.nl</a> |
|
|
If it's there and you can't see it, it's TRANSPARENT | Tel: +31-15-2137555 |
|
|
If it's not there and you can see it, it's VIRTUAL |__FAX:_+31-15-2138217 |
|
|
If it's not there and you can't see it, it's GONE! -- Roy Wilks, 1983 |_____|
|
|
<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="0067.html">Rogier Wolff: "Re: Microtek woes"</a>
|
|
<li> <b>Previous message:</b> <a href="0065.html">Helmut Koeberle: "Re: Sane 0.71 and CanoScan 300"</a>
|
|
<li> <b>In reply to:</b> <a href="0063.html">Matto Marjanovic: "Re: Microtek ScanMaker 330"</a>
|
|
<!-- nextthread="start" -->
|
|
<!-- reply="end" -->
|
|
</ul>
|