Hi Adam and Marcel,
I looked through some config files which come with the windows driver, both
model codes 90 and 92 are listed for the Scanmaker E3+. Looks like they are
identical or at least very similar.
The patch overwrites the modelcode that the backend reads out of the scanner
(90) with 92. There is another function that uses the model code to list the
type of scanner, so it thinks 90=92. Normally I would add the 90 to this
function too. I will do that in my backend version which I will release to
CVS in the next future.
Greetings
Karsten
Adam Benjamin wrote:
>
> > If I remember correctly, some time ago someone used also a scanner with
> > modelcode 90, but after patching the backend, it still didn't work.
> > Maybe that's the reason it was left out of the backend. Because there
> > were other issues with this backend.
>
> Not sure. My assumption was that they had already coded the
> instructions for the E3+ and I knew mine was an E3+ - hence it seemed
> safe to kludge mine to being recognized as model code 92. I would
> also guess that this is not necessarily safe in the general case as
> perhaps there are other model code 90 Microtek2 scanners that are not
> E3+.
>
> > > + case 0x90:
> > > + mi->model_code = 0x92;
> > > + *model_string = "E3+ / Vobis HighScan";
> > > + break;
> >
> > I'm no programmer, so maybe this is a stupid question, but the line:
> > > + mi->model_code = 0x92;
> > What does it do?
>
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
This archive was generated by hypermail 2b29 : Thu Apr 05 2001 - 13:03:35 PDT