# Re: mustek owners: check your scsi cabling!

Christoph Doerbeck (doerbeck@dma.isg.mot.com)
Mon, 27 Oct 1997 08:28:03 -0500

- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
- Next message: Klaus Weglehner: "Scsi-Cabling"
- Previous message: Eric Ludlam: "Re[2]: Dark scans with HP ScanJet 3c"
- Maybe in reply to: David Mosberger-Tang: "mustek owners: check your scsi cabling!"
- Next in thread: becka@rz.uni-duesseldorf.de: "Re: mustek owners: check your scsi cabling!"
- Reply: becka@rz.uni-duesseldorf.de: "Re: mustek owners: check your scsi cabling!"

> OK, I think I found one reason I had all kinds of weird problems with
> my Mustek scanner since my move: the problem was due to incorrect SCSI
> termination. After terminating the 25-pin connector on the Mustek
> scanner (Paragon 600 II SP, in my case), I no longer see any
> horizontal shifts.
>
> If you see a similar problem, you might want to look into your scsi
> cabling. I'm by no means a scsi termination expert, but I think the
> scsi-howto has a pretty good section on termination issues.
>
> If scsi termination turns out to fix your problem, please let me know.
>

I have never seen the "horizontal shift" bug. Although, I never unpacked
the included SCSI card. The scanner is attached to a AHA1540 and was
properly terminated the day I set it up (providing my own terminator).

I did find it awful funny that the Scanner was sold without a terminator.

Here are the bugs I've seen:

1) First scan yeilds a out.pnm that xv complains about
being "truncated". Rescanning the image will work then.

2) No way of closing the xscanimage preview window

3) My new Mustek 600 II CD went past length of bed (made that funky
noise as described in the man pages) when I made a color scan with
a resolution of 300 dpi.

4) Color scan resolution set to 75, first scan comes out at
incorrect reolution. Re-scanning usually resets (?) scanner and
produces a correct out.pnm at 75 dpi. Often, the incorrect
output will have multiple small copies of the intended image.

#1 and #4 may be (probably are) related... I'm still a bit confused on
how to provide meaningful "DEBUG_MUSTEK" output. Perhaps someone could
whip-out a perl script to run the requested tests??

- Christoph

    --
    Source code, list archive, and docs: http://www.mostang.com/sane/
    To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com

- Next message: Klaus Weglehner: "Scsi-Cabling"
- Previous message: Eric Ludlam: "Re[2]: Dark scans with HP ScanJet 3c"
- Maybe in reply to: David Mosberger-Tang: "mustek owners: check your scsi cabling!"
- Next in thread: becka@rz.uni-duesseldorf.de: "Re: mustek owners: check your scsi cabling!"
- Reply: becka@rz.uni-duesseldorf.de: "Re: mustek owners: check your scsi cabling!"