plustek@linuxhacker.org

Tomas Nykung wrote:
<snip>
> Looks like the only way to make the situation a little bit better is to
> close all processes / programs that are running before scanning.

Continuing my monologue...

As a _last_ resort, I downloaded the Windows driver and rebooted to Win 95 
(no, I'm not going to upgrade, that was the last Windows version that I 
bought :)) and tried the scanner there. What I noticed when scanning under 
Windows was that it took _much_ longer to scan. An image the size of a CD 
cover took at least 5-6 times longer to scan in Windows (300 dpi) than the 
same image in Linux (also 300 dpi). The sensor moved forward much slower, 
and even then, the scanner paused about 5 times, and moved the sensor a bit 
back before it started scanning again.
The scan took about 10 seconds in Linux and maybe around one minute in 
Windows (I didn't check with a clock, but something like that).

This got me thinking:
Would it somehow be possible to slow down the scanner in Linux, so that the 
reading from the parallel port would be more reliable?
I wouldn't mind if it took _much_ longer to scan a picture, if only the 
resulting picture would be useable.
What source file(s) do I need to change to test this (motor.c and scale.c?) 
and what to change?
Or is this (slowdown thingy) even possible, and if it's possible, would it 
help anything at all?


Tomas