|For a proper setup, at least one of the following entries are needed:|
net [IP ADDRESS] [DEVICE-ID]
usb [VENDOR-ID] [DEVICE-ID]
/usr/local/etc/sane.d/magicolor.conf The backend configuration file /usr/local/lib/sane/libsane-magicolor.a The static library implementing this backend. /usr/local/lib/sane/libsane-magicolor.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_MAGICOLOR 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.
Example: export SANE_DEBUG_MAGICOLOR=127
To obtain debug messages from the backend, set this environment variable before calling your favorite frontend (e.g. xscanimage).
Example: SANE_DEBUG_MAGICOLOR=65 xscanimage
Large color scans may sometimes timeout due to unknown reasons (the scanner simply stops returning data)
Cancelling large scans may lock up the scanner.
Reinhold Kainhofer <firstname.lastname@example.org>
|SANE-MAGICOLOR (5)||10 Jan 2011|