Trouble Shooting
If something goes wrong consider these golden rules:
· The whole system does not boot.
-> Disable the SCSI parameter "Reselection" on your SCSI host adapter for
your scanner.
· My scanner model is not recognized but it works!
-> Send a bug report of a session with a preview and a color scan to
me . I will examine this and modify the detection algorithm.
· During startup of ScanTek there opens a ScanTek SCSI Error requester.
-> Switch on your scanner and wait for the end of the scanner selftest.
-> Set the "SCSI Device Name" to the name of your SCSI device.
The device name is case sensitive. So do not fiddle around with
lower and upper case.
SCSI host adapter | SCSI device name
----------------------------------------------------
A3000 internal SCSI | scsi.device
A2008 Oktagon SCSI | oktagon.device
A1200 SCSI Blizzard | 1230scsi.device
GVP with Gururom | omniscsi.device
GVP | gvpscsi.device
Squirrel | squirrelscsi.device
Surf Squirrel | squirrelscsi.device
This list is only a hint for you. You should take a look into the
documentation of your SCSI host adapter for the real name.
Caution: The Amiga 4000 and Amiga 1200 have also a scsi.device
but this is a trick, because it is an emulation for the
internal IDE port. It is not a SCSI host adapter.
So you cannot use it for your scanner.
· The scanned image is scrambled.
-> Check the SCSI settings in ScanTek and click the <Test Device>-Button
for further information ;-)
Experiment with the settings of the memory types and buffer sizes.
Some SCSI host adapter are not compatible with "ANY" memory type.
They even crash the whole system.
The required settings for the Memory Type can be found in the manual of
the SCSI host adapter.
· The scanner is not ready (the READY lamp is blinking).
-> Wait until the READY lamp is on or you have to reset the scanner by
switching it off and on.
· The scanner may not be mounted, if you switch it on after the AMIGA
has booted.
-> Reboot the AMIGA or remount the scanner with an appropriate tool.
· During scanner operation there is a SCSI error.
-> An SCSI error will be generated by the SCSI device handler. It denotes
an error on the lower protocol layer. In most cases, there is an
invalid SCSI bus termination, which will lead to this failure.
The SCSI bus must be terminated on both ends, either akive or passive.
See the SCSI host adapter manual for further information about SCSI
bus termination.
-> Old version of Oktapussy may lead to SCSI errors and abort scanning
attempts. Use at least OktaPussy 1.9.
-> The FastlaneZ3 SCSI host adapter (z3scsi.device version 8.5) does
not work with scanners. It trashes SCSI data bytes.
· The SCSI bus locks up during the initialization phase of a preview or
scan attempt.
-> You are using the Surf Squirrel SCSI host adapter. Activate the
gadget "Prevent SCSI Init HangUp" in the Scanning Misc Window.
-> If you get a "Scanner Busy" requester, then you must increase the
SCSIHANGUPTIMER value in the ToolType section of the ScanTek.info icon.
· The SCSI bus locks up during the scanner access.
-> You may check your termination on the SCSI bus, since the scanner
is not terminated internally. You may have to connect an external
SCSI termination plug as well as terminate the SCSI bus correctly.
The SCSI bus must be terminated on both ends. These is necessary,
if you have problems with SCSI errors.
-> You may have to change the order of the discrete SCSI components.
· The scanned image is full of black lines.
-> You are using the unregistered test version of ScanTek.
Get registered and this black lines are gone.
· There is a kind of pattern over the scanned image and the scanned image
does not look good.
-> This may be caused by a moire effect.
You have possibly scanned a raster print. Each printed paper has its
own dpi rate. This dpi rate overlaps with the scanners dpi rate and
leads to the mentioned moire effect.
The only solution is to increase the scanner resolution to a value,
that is more than twice as high as the dpi rate of the print.
As a rule of thumb the dpi rate of rastered prints goes from 100 to 150
dpi. If you get this moire effect you should choose a resolution of 200
to 300 dpi.
· There is a SCSI error requester saying "Illegal scanning frame coordinate"
-> Decrease the Width or Height value of the maximum frame size.
· The scanned images have some kind of ghost pictures.
-> Any virtual memory manager software like VMM or GigaMem could scramble
the scanned data and kills performance.
DO NOT USE VMM OR GIGAMEM with ScanTek.
There is no need to use these tools with ScanTek.
ScanTek uses his own virtual memory facilities to scan large images.
· The color of the scanned images are not identical to the original.
-> You may activate or modify the current Look-Up Table.
· The external programme does not find the saved image.
-> You may change the directory path PROGDIR: in the save requester
to something else.
· The preview image is cutted on the right and/or bottom.
-> Set the width and height parameters in the Max Frame Setting Window
to the largest possible value.
-> You are using a Mustek scanner with more than 300(600) dpi.
You may tag the "Mustek Preview Correction" in the
Scanning Misc Window .
This should enable you to see the whole preview area.
· Large images have corrupt image data, even if the beginning of the
image file is correct for a couple of lines.
-> Maybe you are using a Mustek ScanExpress 12000SP or the identical
Mustek Paragon 1200IIISP.
This scanner models do not support segment scanning in the original
way.
-> A correct scanned image is only possible if the scanned image
data fits into the scanning buffer (SCSI parameter window).
To reduce the risk of corrupt data extend the size of the
<Scan Buffer> as large as possible.
-> Color Scanning for this model is only successful for 150, 300,
600 and 1200 dpi.
· FastlaneZ3 SCSI host adapter (z3scsi.device v8.5) does not work with
scanners. FastlaneZ3 trashes data bytes. No solution at the moment.
· Old version of Oktapussy may lead to SCSI errors and abort scanning
attempts. Use at least OktaPussy 1.9.
· Check if there is an interference with other programs. Especially
programs like MultiCX, MCX or other system hacks. Switch them off and
try again.
If nothing of the above mentioned first aid methods lead to a conclusion,
then you may give me a bug report .
 |
Do you have any suggestions or questions about ScanTek then email to
scantek@gmx.de |
    |
Copyright 1996/97/98/2002 by Waldemar Zöhner V1.1