Re: Microtek E3+ and SANE 0.74 (OS/2)
Bernd Schroeder (bernd@aquila.muc.de)
Sat, 23 Jan 1999 18:51:29 +0100
On Thu, Jan 21, 1999 at 02:32:22PM +0100, Stefan Gombar wrote:
> On Wed, 20 Jan 1999 06:18:24 -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".
> >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.
> >
> >Is this something I have set-up wrong? Do I need to compile 1.0?
>
> Hi!
>
> I have an Asus PC-200 PCI-SCSI-Controller (Symbios8xx), the screen shows also your
> output, but it scans normally. The scan is fine.
>
> [F:\INSTALL\SANE\sane074]scanimage.exe -d microtek2:b0t6l0 --resolution 36 -x215
> .815 -y292.926 1>t.pnm
> 0: 00000000000000 .......
>
> Using Warp 4, sane 0.74, Microtek E3+ (Vobis Highscan) 'Scanner 300A4 5.10'.
This output comes from the sense handler, which is normally called if
an error occurs. I am not familiar with OS/2, and don't know why it is
called, but all bytes 0 means 'no error'. It is probably a good idea
not to print the contents of the sense buffer, if it doesn't indicate
an error.
So I think, that Lee's problem is more likely a problem with the SCSI setup.
It looks as if it occurs when a command is executed that actually does
a disconnect from the SCSI bus.
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