DEVICENAMES

This backend expects device names of the form:
special
Where special is a path-name for the special device that corresponds to
a USB scanner. With GNU/Linux systems, such a device name could be
/dev/usb/scanner0 or /dev/usbscanner1, for example.

CONFIGURATION

The hp_rts88xx.conf file contains the device name that correspond to
the hp44x0c scanner. Empty lines and lines starting with a hash mark
(#) are ignored.
A sample configuration file is shown below:
# Comment
/dev/usbscanner # option_CCD # CCD0 or CCD1 allowed # if you
receive a black image, change it to CCD1 option CCD0
The first line is ignored. The second line is the device filename to
use in order to access the hp44x0c Scanner. If no device is given, the
backend will use libUSB.

FILES

/etc/sane.d/hp_rts88xx.conf
The backend configuration file (see also description of
SANE_CONFIG_DIR below).
/usr/lib/sane/libsane-hp_rts88xx.a
The static library implementing this backend.
/usr/lib/sane/libsane-hp_rts88xx.so
The shared library implementing this backend (present on systems
that support dynamic loading).

ENVIRONMENT

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
/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).
SEEALSOsane(7), sane-usb(5)
http://hp44x0backend.sourceforge.net