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

144 wiersze
5.8 KiB
HTML
Czysty Wina Historia

<HTML>
<HEAD>
<TITLE>sane-genesys.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="/images/sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-genesys.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-genesys.5.html">sane-genesys(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-genesys.5.html">sane-genesys(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-genesys - SANE backend for GL646 and GL841 based USB flatbed scan-
ners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-genesys</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to USB flatbed scanners based on the
Genesys GL646 and GL841 chips. At present, the following scanners are
known to work with this backend:
Medion MD6228
Medion MD6274
Hewlett-Packard HP2300C
Canon LiDE 35/40/50/60
This is BETA software. Especially if you test new or untested scanners,
keep your hand at the scanner's plug and unplug it, if the head bumps
at the end of the scan area.
If you own a scanner other than the ones listed above that works with
this backend, please let me know this by sending the scanner's exact
model name and the USB vendor and device ids (e.g. from
<I>/proc/bus/usb/devices</I> <I>,</I> <I>sane-find-scanner</I> or syslog) to the sane-devel
mailing list. Even if the scanner's name is only slightly different
from the models mentioned above, please let me know.
If you own a scanner that isn't detected by the genesys backend but has
a GL646 or GL841 chipset, you can try to add it to the backend.
</PRE>
<H2>SYSTEM ISSUES</H2><PRE>
This backend needs libusb-0.1.6 or later installed, and hasn't tested
in other configuration than a linux kernel 2.6.9 or higher. However, it
should work any system with libusb where the SANE package can be com-
piled. For setting permissions and general USB information look at
<B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>genesys.conf</I> file is a list of usb lines containing
vendor and product ids that correspond to USB scanners. The file can
also contain option lines. Empty lines and lines starting with a hash
mark (#) are ignored. The scanners are autodetected by <B>usb</B> <B>vendor_id</B>
<B>product_id</B> statements which are already included into <I>genesys.conf</I>.
"vendor_id" and "product_id" are hexadecimal numbers that identify the
scanner.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/genesys.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-genesys.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-genesys.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_GENESYS</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. If the
debug level is set to 1 or higher, some debug options become
available that are normally hidden. Handle them with care. This
will print messages related to core genesys functions.
<B>SANE_DEBUG_GENESYS_GL646</B>
This environment variable controls the debug level for the spe-
cific GL646 code part.
<B>SANE_DEBUG_GENESYS_GL841</B>
This environment variable controls the debug level for the spe-
cific GL841 code part.
Example (full and highly verbose output for gl646):
export SANE_DEBUG_GENESYS=255
export SANE_DEBUG_GENESYS_GL646=255
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>
</PRE>
<H2>AUTHOR</H2><PRE>
Oliver Rauch
Henning Meier-Geinitz &lt;henning@meier-geinitz.de&gt;
Gerhard Jaeger &lt;gerhard@gjaeger.de&gt;
St<53>phane Voltz &lt;svoltz@numericable.fr&gt;
Philipp Schmid &lt;philipp8288@web.de&gt;
</PRE>
<H2>BUGS</H2><PRE>
Support for buttons is missing.
sane-backends 1.0.18 20 Nov 2005 <B><A HREF="sane-genesys.5.html">sane-genesys(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>