Re: Microtek E3+ and SANE 0.74 (OS/2)

Bernd Schroeder (bernd@aquila.muc.de)
Thu, 21 Jan 1999 00:45:05 +0100

On Wed, Jan 20, 1999 at 06:18:24AM -0500, Lee Riemenschneider wrote:
> Has anyone gotten this configuration working?
>
> I have a Tekram DC-390F controller. find-scanner finds the device
> information OK, but as "found scanner " Scanner 300A4 5.10" at device
> b0t6l0".

"Scanner 300A4" as the model string is ok for this model.

> When I run scanimage with -d microtek2:b0t6l0 --resolution 36 -x215.815
> -y292.926 > t.pnm, the screen shows "0:
> 00000000000000 ......." the scan mechanism moves to
> the start point(?), and then it locks up.

The zeroes look like the debugging output of the sense handler, which is
called, when a SCSI command fails. However, if this happens, the output
should contain more information than just these zeroes, to provide more
detailed information about the error.

Does the same thing happen, if you don't specify the x- and y-values ?

If so, can you send me a trace with 'option dump 2' set in the
microtek2.conf file ? This would allow to determine, which command failed
(and perhaps why).

> Is this something I have set-up wrong? Do I need to compile 1.0?

No. Compared to 0.74 the microtek2 backend in 1.0 has no changes regarding
a scan from the flatbed.

Bernd

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

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