Hi,
On Tue, Feb 01, 2000 at 09:36:04PM +0100, Karsten Festag wrote:
> Hello,
> I spend some time to play with my Phantom 330 CX (FW 1.26) and the
> pre0.9-version
> of the microtek2 backend (thanks to Bernd, who is fighting the strange
> behavior of the various types!). Here's the story:
> I'm using ppscsi 0.91, sane 1.00 with the upgrade patch to 1.01 and the
> microtek2-pre0.9.020100 backend.
> I am able to scan, but there are three points:
> -the option --backend-calibration=yes doesn't seem to work, (I can't
Yes, this option is not effective for that model. The calibration for
the 330cx is different from the calibration process on other models.
> hear the typical noise that the scanner makes under windows) and the
> fine vertical stripes that were mentioned before in this mailing list
> are there.
> -the image is horizontally mirrored (the preview also is)
Yes, that is a known problem. I will see whether I can fix it in the near
future. Grayscale and B/W scans, however, should not have this problem.
> -when the scan is performed, the head turns back into starting positon,
> but it doesn't stop. The motor drives the head approx. 20 seconds
> against the stop, then the head returns to its normal starting position.
> If I did a scan under windows before and didn't switch off the scanner
> in the meantime then the behaviour is normal, the head stops right at
This is interesting, because it is the first time, that I read, that
a scan with this model does not show this strange behaviour (hitting
the top or bottom of the scan area). The backend does not execute one
SCSI command for this model, that is executed, when other models are
connected. This command fails on the 330cx for whatever reason, and
I suspected that this missing command might cause these problems.
When the scanhead stops at the right position after a scan under windows
this shows, that the missing command is probably not the cause.
> the stop and goes into starting position. Starting only the Twain driver
> has no effect, only if a scan was performed the problem is fixed.
>
> I was able to get the scanner to work with wine (with scantest and with
> PaintShopPro) and to log some ASPI traces. So, Bernd, if you are
> interested in logfiles, let me know what information you need. For now,
> I did an "wine /dos/Programme/psp/psp.exe -debugmsg +aspi 2>wine.log".
These debug options are just fine. Can you make such a trace available,
from the first scan after the scanner is switched on ? Can you also
trace a scan (also immediately after the device is powered on) with
sane ? The 'option dump 2' should be set in the microtek2.conf file.
This will trace the SCSI commands, that the backend issues, so that we can
compare them.
However, there is one drawback of the wine traces. wine traces only the
SCSI commands, but not the parameters of the commands, and not the
replies from the device, so I cannot say, whether it will be sufficient.
Otherwise wine must be patched (I have a patched version of the 990704
release).
Bernd
-- Bernd Schroeder Email: mailto:bernd@aquila.muc.de PGP public key available: mailto:pgp@aquila.muc.de | Subject: send key-- 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 : Sat Feb 05 2000 - 08:46:14 PST