Am Montag, 30. Juni 2008 06:53:34 schrieb stef:
> the only difference I could spot is slightly different motor
> acceleration tables. The ones generated by the backend are very
> close to the ones in windows logs, but in case your scanner's
> motor is less tolerant (or failing ?), it might not like them.
> But I'd like to be sure at what point the trouble arise. Could
> you try to trigger the problem with scanning scanning script at
> 100 dpi and do a CTRL-C when there is a motor trouble ? The log
> will show us at what exact the problem is happening.
Done!
I hit CTRL-C in the first second after bad motor noise, but the
noise ended after 1/2 min and the prompt is back also after 1/2
min.
Therefore, in the next test, I made a copy in the bad moment:
cp scan.log scan.copy
then, I hit CTRL-C.
I send both files direct to you.
--
Viele Gr??e
Werner Holtfreter
