|Forces the backend to overwrite the scanable area returned by the scanner to ISO A4. Scanner that are known to return bogus data are marked in the backend so if you need this option please report this to the backend maintainer. USE WITH CARE!|
|Forces the backend to overwrite the scanable area returned by the scanner to ISO A3. Scanner that are known to return bogus data are marked in the backend so if you need this option please report this to the backend maintainer. USE WITH CARE!|
|Disables the usage of the scanners gamma-table. You might try this if your scans hang or only produces random garbage.|
|Disables the scanners color calibration. You might try this if your scans hang or only produces random garbage.|
Any option above modifies the default code-flow
for your scanner. The options should only be used
when you encounter problems with the default be-
haviour of the backend. Please report the need of
options to the backend-author so the backend can
be fixed as soon as possible.
This backend expects device names of the form:
Where scsi-spec is the path-name to a special device or a device ID for the device that corresponds to a SCSI scanner. The special device name must be a generic SCSI device or a symlink to such a device, for example on Linux "/dev/sga" or "/dev/sg0". The device ID is the ID returned by the scanner, for example "HP" or "AVISION". See sane-scsi(5) for details.
usb-spec is the USB device name, the vendor/product ID pair or the name used by libusb corresponding to the USB scanner. For example "0x03f0 0x0701" or "libusb:002:003". See sane-usb(5) for details.
Note: Since the backend now includes native USB access, it is no longer needed - even considered obsolete - to access USB scanner via the SCSI emulation (named hpusbscsi on Linux) for Avision USB devices such as the HP 53xx, HP 74xx or Minolta film-scanners.
The program sane-find-scanner helps to find out the correct scsi or usb device name.
A list with supported devices is built into the avision backend so normally specifying an ID should not be necessary.
/usr/local/etc/sane.d/avision.conf The backend configuration file (see also description of SANE_CONFIG_DIR below). /usr/local/lib/sane/libsane-avision.a The static library implementing this backend. /usr/local/lib/sane/libsane-avision.so The shared library implementing this backend (present on systems that support dynamic loading).
SANE_CONFIG_DIR This environment variable specifies the list of directories that may contain the configuration file. Under UNIX, the directories are separated by a colon (:), under OS/2, they are separated by a semi-colon (;). If this variable is not set, the configuration file is searched in two default directories: first, the current working directory (".") and then in /usr/local/etc/sane.d. If the value of the environment variable ends with the directory separator character, then the default directories are searched after the explicitly specified directories. For example, setting SANE_CONFIG_DIR to "/tmp/config:" would result in directories "tmp/config", ".", and "/usr/local/etc/sane.d" being searched (in this order). SANE_DEBUG_AVISION If the library was compiled with debug support enabled, this environment variable controls the debug level for this backend. Higher debug levels increase the verbosity of the output. The debug level 7 is the authors preferred value to debug backend problems.
Example: export SANE_DEBUG_AVISION=7
sane(7), sane-scsi(5), sane-usb(5)
Ren[e] Rebe and Meino Christian Cramer
|SANE-AVISION (5)||11 Jul 2008|