Re: COOLSCAN II backend

Michael K. Johnson (johnsonm@redhat.com)
Wed, 06 Aug 1997 09:01:03 -0400

Didier Carlier writes:
>The umax backend seems ok, with little modifications, I got it to do
>simple things like the INQUIRE and POSITION commands on the COOLSCAN,
>and these seem to work. It even reads data but unfortunately the
>picture I get is a 28.8 Meg file all black ;-).

Ooh, that means you really are most of the way there. I'm fairly
certain that the problem is that the scanner is confused by the
set window command -- that often causes scanners to return all
zeros for data. Of course, getting the rest of the way there
can be a long journey. I don't know what you have done so far,
but I'd try reducing the size of the window descriptor block,
probably to just the minimum defined by section 14 of the scsi
2 standard. That gives less potential for conflict between
elements in the wdb, and a better chance of a good scan. If
that works, you can fill the wdb back in once you hear from Nikon
what their vendor-specific extensions to the wdb look like.

>I'm now waiting for some detailed interface specs from Nikon to go
>further and I have good hope, as at least they replied to my faxes and
>phone calls.

Sounds good! Best of luck,

michaelkjohnson

"Ever wonder why the SAME PEOPLE make up ALL the conspiracy theories?"

--
Source code, list archive, and docs: http://www.azstarnet.com/~axplinux/sane/
To unsubscribe: mail -s unsubscribe sane-devel-request@listserv.azstarnet.com