We should probably place a "big fat warning" somewhere to tell people
to try with small scan areas first.
> How did the scanner go "crazy"? Did it start scaning normally and
> then when it hit the end of the scan surface it got very noisy? If
> so, that would explain a lot.
I will try to check, as I probably know the "victim".
(Sven: It was Rio, right ?)
> In any case, I'm sorry to hear that the mustek backend fried your
> scanner. I hope it's still under warranty and that you'll get a
> replacement quickly. Before wasting another scanner, could you send
> me the following info:
>
> - SCSI id string you get at boot up (something like MFC-08000CZ)
Only "Scanner", if my guess above is right. This seems to be the new
firmware >2.0 . I suppose they have done this to make OEMing easier ...
I have had another complaint about these scanner types not working
correctly, but this seemed to be rather a problem of the adaptor.
I will report about that, when I hear more from it.
CU,ANdy
P.S.: Could you tell your Mustek contact, that it would be a good idea to
spend an extra $2 for a hardware switch which prevents the carrier
from hitting into the bottom ?
-- Andreas Beck | Email : <becka@sunserver1.rz.uni-duesseldorf.de>
-- Source code, list archive, and docs: http://www.azstarnet.com/~axplinux/sane/ To unsubscribe: mail -s unsubscribe sane-devel-request@listserv.azstarnet.com