"Stens, Ralph" <RStens@atg-test-systems.de> writes:
> Please explain me what I should do and maybe within the next few
> days I can make a log of the SCSI commands. I talk also to the
All right, here is how I got my scanner working with wine:
you need to launch your windows scanning driver with wine (there are
other solutions for windows directly but I didn't tried them). Windows
uses a library called ASPI to access the SCSI bus, you have to get
wine ASPI to work (read stuff concerning ASPI in wine doc).
Your scanner driver probably uses ASPI and since ASPI is emulated by
wine, it can log everything : wine -debugmsg +aspi yourscannerprog
this gives you a log of all scsi commands used by the driver. You can
look in snapscan sources to find what each command means (in
snapscan-scsi.c, example: #define SEND 0x2A).
Unfortunately, to get the buffer associated with some commands you
have to modify the wine ASPI dll code. This is quite easy, I did it a
few weeks ago but I have removed it since. It may not be necessary
since the command to tell the ADF to get a page may be quite simple
(or it may not?) and so may not need an associated buffer.
Note : there is a basic twain client on www.twain.org that can make
any twain request to your scanner driver. If there is a twain command
corresponding to get_new_page_by_adf or something, then the scsi log
will give you exactly what you need.
I don't know how the ADF works. There must be something at the
beginning of the scan to detect it (probably difficult to find - you
have to compare all commands with what snapscan already do; I did it
and it's really boring, but quite usefull) and then after each page,
there must be something to tell the ADF to get a new page (this one
may be easy to find: a new scsi command that does not appear at all in
snapscan).
If you want more details don't hesitate to ask, I did it recently so I
know what it looks like (main aspect: it's extremely boring).
> guys from Agfa and try to get the programming manual for the
> 1236s and the ADF. I expect that it will become easier if I
> get this manual.
Quite a lot of people (me included) asked for such manuals to AGFA or
others and we haven't even received an answer. Good luck!
> It is very nice that the work with the SnapScan backend starts
> again.
I will start a new job in 2 weeks, so I try to make a version working
more or less for everybody that can be submited to sane CVS before
that. I will probably not do much after that for quite some time
(except for testing new versions and easy corrections). Fortunately,
there are other people working on it as well.
-- Sébastien Sablé sebastien.sable@gmx.net-- 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 Nov 02 2000 - 18:33:47 PST