Thanks.. that makes me feel better :) Abel Deuring also replied to me from
the list saying he didn't think it was my fault either... that most likely
it was broke before i got it. Time to send it back to the factory and see
what they say! If the scanner never got through all of its self test modes
because the lamp tracking mechanism was screwed maybe that would explain why
it was sending back some i/o errors when trying the set_window function.
-Andy
> -----Original Message-----
> From: owner-sane-devel@mostang.com
> [mailto:owner-sane-devel@mostang.com]On Behalf Of Karsten Festag
> Sent: Monday, May 21, 2001 1:46 PM
> To: sane-devel@mostang.com
> Subject: Re: something very bad??
>
>
> It might well be that the scanner gets the command to scan beyond it's
> physical borders. My scanner also does this and makes the strange noises
> when the motor gets blocked. But it never got damaged though I had this
> case several times when I was experimenting with my backend code. But if
> I remember correctly I had one time a system crash while scanning with
> windows (in the bad old times ;-) ) and the scanner also ran into the
> stop. If the cable gets disconnected in this case I think this is not
> your fault and caused by a bad design of the scanner (or the cable was
> really not assembled in the factory).
>
> Karsten Festag
>
>
>
> --
> Source code, list archive, and docs: http://www.mostang.com/sane/
> To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
>
-- 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 : Mon May 21 2001 - 14:10:01 PDT