All of these scanners are pre-SCSI-2. They do not report properly to SCSI Inquiry. For example, in SCSI bus scans, the scanner will come up with incorrect vendor and models strings.
sane-agfafocus expects device names of the form:
special
where special is the path-name for the special device that corresponds to a SCSI scanner. For SCSI scanners, the special device name must be a generic SCSI device or a symbolic link to such a device.
agfafocus.conf contains a list of device names that correspond to Microtek scanners. Empty lines and lines starting with a hash (``#'') are ignored. A sample configuration file is shown below:
/dev/scanner # this is a comment /dev/sgeThe SANE_CONFIG_DIR environment variable specifies the list of directories that may contain the configuration file. The directories are separated by a colon (``:''). If this variable is not set, the configuration file is searched in two default directories: firstly, the current working directory (``.'') and then in /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 /etc/sane.d being searched (in this order).
The SANE_DEBUG_AGFAFOCUS environment variable controls the debug level for the sane-agfafocus backend if the library was compiled with debug support enabled. For example, a value of 128 requests all debug output to be printed. Smaller levels reduce verbosity.
in sh(1) and look for the ``disconnect:'' line.
If SANE does not detect your scanner, make sure the sane-artec backend is disabled.
If you encounter a problem (for example, a SCSI bus error or trimmed or displaced images) set the environment variable SANE_DEBUG_AGFAFOCUS to 128 and try to regenerate the problem.
Authors are Ingo Schneider and Karl Anders Oygard.