plustek@linuxhacker.org

Hi there,

first of all sorry for the late response, I was out for buisness and
arrived yesterday.

Let me try to explain the major differences between 0.36 and 0.37:
The main difference is the function OpenScanPath which is necessary
each time you talk to the scanner. This functions didn't look very good
in 0.36 (but it seems to work OKAY ;-)) so I used the new one which
will be used by the PT12 code. All that stuff worked great here on
my rather old machines. The next thing is the #0 and #1 stuff:
#0 selects the parport functions of the kernel, #1 the io assembler
functions in and out. In 0.36 we used the delayed ones in 0.37 the
"normal" ones. So I think, that the ASIC 98001 inside the 9636 and
12000T
has some timing problems...
As soon as I have some time, I will reimplement the OpenScanPath from
version 0.36 into 0.37 and also will use again the delayed io
functions.
I would be great if you (Kevin and Mark) could test this driver!


Kevin: The version problem can be solved by recompiling
the backend code (that was delivered with the driver)!

Thanks guys for the good discussion.


On Thu, 25 Jan 2001 13:33:49 -0500, kevin wrote:

>Hi list,
>
>I went back to the plustek-sane-0_36_34.tar.gz file. With the "#if
>1" setting, the driver loads and I could do scans and prescans
>with no problems. Did several prescans in a row, then a scan (both
>color and B/W, one at 300 and one at 400 dpi), then another
>prescan. Quit xscanimage, restarted it, did several more prescans.
>I did this with Redhat 6.1 (kernel 2.2.12) on Cricket and Mandrake
>7.2 (kernel 2.2.17) on Paws, using the tarball version of
>sane-1.0.3. When I tried the "#if 0" setting, I could not get the
>driver to load (Gerhard, I got AsicID=88 and device or resource
>busy). When I reset to "#if 1", everything worked as before. I
>also tried using this driver on Mandrake 7.2 with the rpms for
>sane-1.0.4. The driver loads, but unfortunately I get a version
>mismatch when I do "scanimage -L", so I am not able to do a scan.
>Gerhard, is there a way of fixing this, or do I have to use the
>tarball version of 1.0.4 and compile it myself?
>
>For the moment, if you are having problems scanning, try the
>0_36_34 driver version (#if 1 is the default, so you shouldn't
>have to change that).
>
>	Kevin
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: plustek-unsubscribe@linuxhacker.org
>For additional commands, e-mail: plustek-help@linuxhacker.org
>


----------------------------------------
g.jaeger@earthling.net
----------------------------------------