Re: Mustek Paragon CD II

David Mosberger-Tang (
Tue, 6 May 1997 19:38:59 -0700

>>>>> On Tue, 6 May 1997 17:13:11 +0200 (MET DST), (Sven Neumann) said:

Sven> Hi, a friend of mine and myself, were both trying to get a
Sven> Mustek SP II but were both shipped a new model called Mustek
Sven> Paragon CD II. The vendor claimed that only the name was
Sven> changed and all technical details remained unchanged. This is
Sven> NOT the fact! I thought it might be of interest for the
Sven> developers of SANE that my friend has just crashed its new
Sven> scanner by using the mustek-backend of xscanimage with it!

That's bad news.

Sven> Don't misunderstand me: I don't want to bother anyone here for
Sven> this. My intention is to warn you not to use (better: not to
Sven> buy) this scanner unless there is a backend that knows how to
Sven> handle this scanner.

I just sent mail to my Mustek contact. I hope this might shed some
light (crossing fingers that I'll get an answer...).

Sven> As it is suggested to buy another card for the mustek scanner
Sven> like e.g. an NCR 810 we have tried to use the scanner with
Sven> this card. It is correctly initialized by the kernel, the
Sven> scanner is found, everythings should work just fine... When
Sven> my friend started preview from xscanimage on his scanner the
Sven> thing went crazy, brutally damaging the moving parts!! I don't
Sven> know why exactly this happened but we are afraid, that Mustek
Sven> changed the protocol of the scanner.

Sven> So far... Has anyone of you heard of similar experiences? Do
Sven> you know someone who uses this model with Linux? Any ideas how
Sven> to solve this?

There was one other report: that scanner got damaged because the scan
area length was wrong. What is the SCSI id string you get for your
scanner? If it is MFC-08000CZ, then this might explain the problem.

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.

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)
- the label on the front of the scanner
- the firmware version; the best way to get this is to do something
like this:

SANE_DEBUG_MUSTEK=2 scanimage -d mustek -h >/dev/null


Source code, list archive, and docs:
To unsubscribe: mail -s unsubscribe