sane-project-website/old-archive/1999-04/0020.html

<!-- received="Fri Apr  2 14:02:34 1999 PST" -->
<!-- sent="Mon, 15 Mar 1999 11:36:26 +0100 (MET)" -->
<!-- name="Christian Schnell" -->
<!-- email="cschnell@wpax13.physik.uni-wuerzburg.de" -->
<!-- subject="Microtek ScanMaker X6 / Phantom 636" -->
<!-- id="¨Õÿ
" -->
<!-- inreplyto="" -->
<title>sane-devel: Microtek ScanMaker X6 / Phantom 636</title>
<h1>Microtek ScanMaker X6 / Phantom 636</h1>
<b>Christian Schnell</b> (<a href="mailto:cschnell@wpax13.physik.uni-wuerzburg.de"><i>cschnell@wpax13.physik.uni-wuerzburg.de</i></a>)<br>
<i>Mon, 15 Mar 1999 11:36:26 +0100 (MET)</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#20">[ date ]</a><a href="index.html#20">[ thread ]</a><a href="subject.html#20">[ subject ]</a><a href="author.html#20">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0021.html">Bert Bakker: "Sane drivers"</a>
<li> <b>Previous message:</b> <a href="0019.html">Jamie Zawinski: "Re: xscanimage won't detect my scanner"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>
<!-- body="start" -->
Hi ScanMaker users!<br>
<p>
Over the last days I've been very busy trying to get my Microtek ScanMaker<br>
X6 to work with Linux / SANE. I think I've seen about every problem that<br>
can possibly occur (according to this mailing list...) -- and now it _is_<br>
actually working. Since I've read nearly every `article' on the list, I<br>
think it is only fair if I describe the solution which appears to get<br>
around the problems (at least with my configuration...).  <br>
<p>
Just for reference, I'm now using<br>
 o the new kernel version 2.2.1,<br>
 o an SCSI adapter AVA-1505 (which came with the scanner),<br>
 o a Microtek Phantom 636 scanner (Microtek says it's actually a ScanMaker X6), <br>
 o the kernel driver aha152x and <br>
 o the SANE package sane-pre1.01-3<br>
<p>
First of all, the adapter card should have been PnP (it _was_ detected by isapnp), but this <br>
approach didn't work; in fact, the situation was exactly the same as Mr Rogers described in <br>
his article -- see for example<br>
<p>
  <a href="http://chandra.ph1.uni-koeln.de/linux/lg/issue31/rogers2.html">http://chandra.ph1.uni-koeln.de/linux/lg/issue31/rogers2.html</a><br>
<p>
After the kernel had recognized the card, I tried to use an older version of SANE (which<br>
came with S.u.S.E. Linux 5.3). Since it had no support for the new Microtek scanners, this<br>
was doomed to failure...<br>
Consequently, I upgraded to SANE 1.00; the scanner was now (should now have been?)<br>
supported, but I just got to the point where it _should_ have started scanning (preview<br>
scan with xscanimage). Then the whole X server got slowed down and still the scanner<br>
wouldn't budge...<br>
Another upgrade to SANE pre1.01-3 produced (after I manually edited part of the makefiles<br>
to have it find _all_ of my SCSI and JPEG header files) xscanimage started producing<br>
images, but they all had that greenish tint which is also described in some of the<br>
`articles' on this list. The strange thing is: the preview scans were OK, just the `real'<br>
scan was all green (and red -- in fact, only the blue parts appeared to be missing...).<br>
<p>
Since I had read about these problems, I then installed on of the `patches' for the<br>
microtek2 backend, namely the file<br>
<p>
  microtek2-pre0.6.120399.tar.gz <br>
<p>
which produced a more consistent result, i.e. _all_ scans (preview included) got green.<br>
Installation of the old microtek2 backend from version 1.00 (just the microtek.? files)<br>
slightly improved the results, but caused one further problem (also described on the<br>
list): the first scan is OK, all further ones remain green.<br>
Now comes the good ending: I replaced the microtek2.? files with those from another patch<br>
<p>
 microtek2-pre0.6.291298.tar.gz<br>
<p>
and this combination, strangely enough, is working _and_ produces good color scans (24<br>
bit), not just one, but as many as I like...<br>
<p>
Of course I don't really know _why_ (or how) this combination solves the problems -- being<br>
somewhat of a Linux novice myself -- but maybe my report could help others who experience <br>
related problems. And then, since I've been studying this mailing list rather extensively, <br>
it is only fair to report the success.  <br>
<p>
Bye, Christian<br>
<p>
<p>
P.S. If someone can find out why the backend behaves the way it does (especially where the<br>
greenish colors come from), please mail me...<br>
<p>
<p>
<p>
<p>
<p>
<p>
<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="0021.html">Bert Bakker: "Sane drivers"</a>
<li> <b>Previous message:</b> <a href="0019.html">Jamie Zawinski: "Re: xscanimage won't detect my scanner"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>