[Fwd: Re: Microtek ScanMaker X6 / Phantom 636]

Bernd Schroeder (bernd@aquila.muc.de)
Sat, 3 Apr 1999 01:55:40 +0200

--YiEDa0DAkWCtVeE4
Content-Type: text/plain; charset=us-ascii

Hi,

I replied to this this mail, but forgot to cc it to the mailinglist.

Bernd

-- 
Bernd Schroeder 
Email: mailto:bernd@aquila.muc.de
PGP public key available: mailto:pgp@aquila.muc.de | Subject: send key 

--YiEDa0DAkWCtVeE4 Content-Type: message/rfc822 Content-Description: Forwarded message from Bernd Schroeder <bernd>

Date: Sat, 3 Apr 1999 01:45:34 +0200 From: Bernd Schroeder <bernd> To: Christian Schnell <cschnell@wpax13.physik.uni-wuerzburg.de> Subject: Re: Microtek ScanMaker X6 / Phantom 636 References: <Pine.GHP.4.10.9903151045410.9628-100000@wpax17.physik.uni-wuerzburg.de> Mime-Version: 1.0 X-Mailer: Mutt 0.88 In-Reply-To: <Pine.GHP.4.10.9903151045410.9628-100000@wpax17.physik.uni-wuerzburg.de>; from Christian Schnell on Mon, Mar 15, 1999 at 11:36:26AM +0100 Organization: private site in Munich Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment

Hi,

On Mon, Mar 15, 1999 at 11:36:26AM +0100, Christian Schnell wrote: > Hi ScanMaker users! > > Over the last days I've been very busy trying to get my Microtek ScanMaker > X6 to work with Linux / SANE. I think I've seen about every problem that > can possibly occur (according to this mailing list...) -- and now it _is_ > actually working. Since I've read nearly every `article' on the list, I > think it is only fair if I describe the solution which appears to get > around the problems (at least with my configuration...). > > Just for reference, I'm now using > o the new kernel version 2.2.1, > o an SCSI adapter AVA-1505 (which came with the scanner), > o a Microtek Phantom 636 scanner (Microtek says it's actually a ScanMaker X6), > o the kernel driver aha152x and > o the SANE package sane-pre1.01-3 > > First of all, the adapter card should have been PnP (it _was_ detected by isapnp), but this > approach didn't work; in fact, the situation was exactly the same as Mr Rogers described in > his article -- see for example > > http://chandra.ph1.uni-koeln.de/linux/lg/issue31/rogers2.html > > After the kernel had recognized the card, I tried to use an older version of SANE (which > came with S.u.S.E. Linux 5.3). Since it had no support for the new Microtek scanners, this > was doomed to failure... > Consequently, I upgraded to SANE 1.00; the scanner was now (should now have been?) > supported, but I just got to the point where it _should_ have started scanning (preview > scan with xscanimage). Then the whole X server got slowed down and still the scanner > wouldn't budge... > Another upgrade to SANE pre1.01-3 produced (after I manually edited part of the makefiles > to have it find _all_ of my SCSI and JPEG header files) xscanimage started producing > images, but they all had that greenish tint which is also described in some of the > `articles' on this list. The strange thing is: the preview scans were OK, just the `real' > scan was all green (and red -- in fact, only the blue parts appeared to be missing...). > > Since I had read about these problems, I then installed on of the `patches' for the > microtek2 backend, namely the file > > microtek2-pre0.6.120399.tar.gz > > which produced a more consistent result, i.e. _all_ scans (preview included) got green. > Installation of the old microtek2 backend from version 1.00 (just the microtek.? files) > slightly improved the results, but caused one further problem (also described on the > list): the first scan is OK, all further ones remain green. > Now comes the good ending: I replaced the microtek2.? files with those from another patch > > microtek2-pre0.6.291298.tar.gz > > and this combination, strangely enough, is working _and_ produces good color scans (24 > bit), not just one, but as many as I like...

Sorry for the late response, but the mail mail was delayed until today.

Since you have read the archive: The problem with the wrong colors is related to the "bytes_per_line should be 3 * pixels_per_line, but it isn't" problem.

Other users have reported exactly the same misbehaviour (wrong colors) for the version that works for you. I am currently trying to collect a list of models and FW versions to elaborate the circumstances, under which this behaviour is shown.

Thus it would be interesting, which FW version and model code your device has.

Also, there exists an update of the backend on

ftp://ftp.muc.de/people/bernds/mtek2/microtek2-pre0.6.280399.tar.gz .

If you like, you can try it and tell me the results. I would be interested, if it works for you or if the colors are wrong again.

In any case: I know now where the problem is and can provide a patch, if necessary.

Bernd

-- 
Bernd Schroeder 
Email: mailto:bernd@aquila.muc.de
PGP public key available: mailto:pgp@aquila.muc.de | Subject: send key 

--YiEDa0DAkWCtVeE4--

--
Source code, list archive, and docs: http://www.mostang.com/sane/
To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com