sane-project-website/man/sane-avision.5.html

177 wiersze
6.9 KiB
HTML
Czysty Wina Historia

<HTML>
<HEAD>
<TITLE>sane-avision.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="/images/sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-avision.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-avision.5.html">sane-avision(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-avision - SANE backend for original Avision and Avision OEM scan-
ners (HP, Minolta, Mitsubishi, UMAX and possibly more) flatbed scanners
</PRE>
<H2>ABOUT THIS FILE</H2><PRE>
This file only is a short descripton of the avision-backend for sane!
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-avision</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to various Avision scanners and the Avi-
sion OEM scanners labelled by HP, Minolta, Mitsubishi or Fujitsu.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The configuration file for this backend resides in
/usr/local/etc/sane.d/avision.conf.
Its contents is a list of device names that correspond to Avision and
Avision compatible scanners and backend-options. Empty lines and lines
starting with a hash mark (#) are ignored. A sample configuration file
is shown below:
<B>I</B> <B>suggest</B> <B>you</B> <B>hold</B> <B>one</B> <B>hand</B> <B>on</B> <B>the</B> <B>power-button</B> <B>of</B> <B>the</B> <B>scanner</B> <B>while</B>
<B>you</B> <B>try</B> the first scans!
# this is a comment
option force-a4
option disable-gamma-table
option disable-calibration
option one-calib-only
option old-calibration
#scsi Vendor Model Type Bus Channel ID LUN
scsi AVISION
scsi HP
scsi /dev/scanner
usb 0x03f0 0x0701
- force-a4:
Forces the backend to overwrite the scanable area
returned by the scanner. This might be needed for
the AV 630 which returns no area - or newer scanners
which retun the area in a unkown format our backend
doesn't recongize yet.
- disable-gamma-table:
Disables the usage of the scanner's gamma-table. You
might try this if your scans hang or only produces
random garbage.
- disable-calibration:
Disables the scanner's color calibration. You
might try this if your scans hang or only produces
random garbage.
- one-calib-only:
When this option is enabled, the backend will only
perform a calibration when the backend is initialized
and not before each scan. This might extend the life
of the CCD, but does not work reliable with the newer
USB scanners (they hang sometimes or return garbage
image data). So this option should be used with care.
- old-calibration:
This enables the use of the old calibration code for
testing purposes.
Note: 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.
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form:
<I>scsi</I> <I>special</I> <I>usb</I> <I>special</I>
Where <I>special</I> is the path-name for the device that corresponds to a
SCSI scanner or the USB vendor/product ID pair corresponding to the USB
scanner. The special device name must be a generic SCSI device or a
symlink to such a device. The program <I>sane-find-scanner</I> helps to find
out the correct device. Under Linux, such a device name could be
<I>/dev/sg0</I> or <I>/dev/sga</I>, for example. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details.
Note: Since the backend now includes native USB access,
it is no longer needed - even considered obsolete -
to access the scanner via the SCSI emulation (named
hpusbscsi on Linux) for Avision USB devices such as
the HP 53xx, HP 74xx or Minolta film-scanners.
A list with supported devices is built into the avision backend so
normally specifying an ID should not be necessary.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/avision.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-avision.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-avision.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
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 config-
uration 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 directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_AVISION</B>
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 author's prefered value to debug backend
problems.
Example: export SANE_DEBUG_AVISION=7
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>
http://drocklinux.dyndns.org/rene/avision/index.html
</PRE>
<H2>AUTHOR</H2><PRE>
Ren<65> Rebe and Meino Christian Cramer
sane-backends 1.0.12-cvs 04 Mar 2003 <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B>
</PRE>
<HR>
<ADDRESS>
Man(1) output converted with
<a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a>
</ADDRESS>
</BODY>
</HTML>