mirror
/
sane-project-website
kopia lustrzana https://gitlab.com/sane-project/website
1
0
Forkuj 0
Kod Zgłoszenia Projekty Wydania Wiki Aktywność
sane-project-website/man/sane.7.html

1232 wiersze
27 KiB
HTML
Czysty Zwykły widok Historia

Added missing file.
2005-01-19 09:41:18 +00:00
Content-type: text/html
<HTML><HEAD><TITLE>Manpage of sane</TITLE>
</HEAD><BODY>
<H1>sane</H1>
Section: SANE Scanner Access Now Easy (7)<BR>Updated: 03 Aug 2004<BR><A HREF="#index">Index</A>
<HR>
<A NAME="ixAAB"></A>
<P>
<A NAME="lbAB">&nbsp;</A>
<H2>NAME</H2>
sane - Scanner Access Now Easy: API for accessing scanners
<P>
<A NAME="lbAC">&nbsp;</A>
<H2>DESCRIPTION</H2>
<B>SANE</B>
is an application programming interface (API) that provides standardized
access to any raster image scanner hardware. The standardized interface makes
it possible to write just one driver for each scanner device instead of one
driver for each scanner and application.
<P>
While
<B>SANE</B>
is primarily targeted at a UNIX environment, the standard has been carefully
designed to make it possible to implement the API on virtually any hardware or
operating system.
<P>
This manual page provides a summary of the information available about
<B>SANE</B>.
<P>
If you have trouble getting your scanner detected, read the PROBLEMS section.
<P>
<A NAME="lbAD">&nbsp;</A>
<H2>TERMINOLOGY</H2>
<P>
An application that uses the
<B>SANE</B>
interface is called a
<B>SANE frontend.</B>
A driver that implements the
<B>SANE</B>
interface is called a
<B>SANE backend.</B>
A
<B>meta backend</B>
provides some means to manage one or more other backends.
<P>
<P>
<A NAME="lbAE">&nbsp;</A>
<H2>SOFTWARE PACKAGES</H2>
The package
`<B>sane-backends</B>'
contains a lot of backends, documentation (including the
<B>SANE</B>
standard), networking support, and the command line frontend
`<B>scanimage</B>'.
The frontends
`<B>xscanimage</B>', `<B>xcam</B>', and `<B>scanadf</B>'
are included in the package
`<B>sane-frontends</B>'.
Both packages can be downloaded from the
<B>SANE</B>
homepage
(<I><A HREF="http://www.sane-project.org/">http://www.sane-project.org/</A></I>).
Information about other frontends and backends can be found on the frontend
page
(<I><A HREF="http://www.sane-project.org/sane-frontends.html">http://www.sane-project.org/sane-frontends.html</A></I>).
<P>
<A NAME="lbAF">&nbsp;</A>
<H2>GENERAL INFORMATION</H2>
The following sections provide short descriptions and links to more
information about several aspects of
<B>SANE.</B>
A name with a number in parenthesis (e.g.
`<B>sane-dll</B>(5)')
points to a manual page. In this case
`<B>man 5 sane-dll</B>'
will display the page. Entries like
`<I>/usr/doc/sane-1.0.15/sane.tex</I>'
are references to text files that were copied to the
<B>SANE</B>
documentation directory
(<I>/usr/doc/sane-1.0.15/</I>)
during installation. Everything else is a URL to a resource on the web.
<P>
<DL COMPACT>
<DT><B>SANE homepage</B>
<DD>
Information on all aspects of SANE including a tutorial and a link to the SANE FAQ
can be found on the SANE homepage:
<I><A HREF="http://www.sane-project.org/">http://www.sane-project.org/</A></I>.
<DT><B>SANE device lists</B>
<DD>
The
<B>SANE</B>
device lists contain information about the status of
<B>SANE</B>
support for a specific device. If your scanner is not listed there (either
supported or unsupported), please contact us. See section HOW CAN YOU HELP
SANE for details. There are lists for specific releases of SANE, for the
current development version and a search engine:
<I><A HREF="http://www.sane-project.org/sane-supported-devices.html">http://www.sane-project.org/sane-supported-devices.html</A></I>.
The lists are also installed on your system at /usr/doc/sane-1.0.15/.
<DT><B>SANE mailing list</B>
<DD>
There is a mailing list for the purpose of discussing the SANE standard and
its implementations: sane-devel. Despite its name, the list is not only
intended for developers, but also for users. Since this is currently the only
mailing list devoted to SANE, it's perfectly OK to ask questions that are not
strictly related to SANE development. How to subscribe and unsubscribe:
<I><A HREF="http://www.sane-project.org/mailing-lists.html">http://www.sane-project.org/mailing-lists.html</A></I>.
<DT><B>SANE IRC channel</B>
<DD>
The IRC (Internet Relay Chat) channel #sane can be found on the Freenode
network (irc.freenode.net). It's for discussing
<B>SANE</B>
problems, talking about development and general
<B>SANE</B>
related chatting. Before asking for help, please read the other documentation
mentioned in this manual page.
<DT><B>Compiling and installing SANE</B>
<DD>
Look at
<I>/usr/doc/sane-1.0.15/README</I>
and the os-dependent README files for information about compiling and
installing
<B>SANE.</B>
<DT><B>SCSI configuration</B>
<DD>
For information about various systems and SCSI controllers see
<B>sane-scsi</B>(5).
<DT><B>USB configuration</B>
<DD>
For information about USB configuration see
<B>sane-usb</B>(5).
<P>
</DL>
<A NAME="lbAG">&nbsp;</A>
<H2>FRONTENDS AND MISCELLANEOUS PROGRAMS</H2>
<DL COMPACT>
<DT><B>scanimage</B>
<DD>
Command-line frontend. See
<B>scanimage</B>(1).
<DT><B>saned</B>
<DD>
<B>SANE</B>
network daemon that allows remote clients to access image acquisition devices
available on the local host. See
<B>saned</B>(8).
<DT><B>sane-find-scanner</B>
<DD>
Command-line tool to find SCSI and USB scanners and determine their Unix
device files. See
<B>sane-find-scanner</B>(1).
</DL>
<P>
Also, have a look at the
<B>sane-frontends</B>
package (including
<B>xscanimage</B>, <B>xcam</B>, and <B>scanadf</B>)
and the frontend information page at
<I><A HREF="http://www.sane-project.org/sane-frontends.html">http://www.sane-project.org/sane-frontends.html</A></I>.
<P>
<A NAME="lbAH">&nbsp;</A>
<H2>BACKENDS FOR SCANNERS</H2>
<DL COMPACT>
<DT><B>abaton</B>
<DD>
The SANE backend for Abaton flatbed scanners supports the Scan 300/GS (8bit,
256 levels of gray) and the Scan 300/S (black and white, untested). See
<B>sane-abaton</B>(5)
for details.
<DT><B>agfafocus</B>
<DD>
This backend supports AGFA Focus scanners and the Siemens S9036 (untested).
See
<B>sane-agfafocus</B>(5)
for details.
<DT><B>apple</B>
<DD>
The SANE backend for Apple flatbed scanners supports the following scanners:
AppleScanner, OneScanner and ColorOneScanner. See
<B>sane-apple</B>(5)
for details.
<DT><B>artec</B>
<DD>
The SANE Artec backend supports several Artec/Ultima SCSI flatbed scanners as
well as the BlackWidow BW4800SP and the Plustek 19200S. See
<B>sane-artec</B>(5)
for details.
<DT><B>artec_eplus48u</B>
<DD>
The SANE artec_eplus48u backend supports the scanner Artec E+ 48U and re-badged
models like Tevion MD 9693, Medion MD 9693, Medion MD 9705 and Trust Easy
Webscan 19200. See
<B>sane-artec_eplus48u</B>(5)
for details.
<DT><B>as6e</B>
<DD>
This is a SANE backend for using the Artec AS6E parallel port interface
scanner. See
<B>sane-as6e</B>(5)
for details.
<DT><B>avision</B>
<DD>
This backend supports several Avision based scanners. This includes the
original Avision scanners (like AV 630, AV 620, ...) as well as the HP
ScanJet 53xx and 74xx series, Fujitsu ScanPartner, some Mitsubishi and
Minolta film-scanners.
See
<B>sane-avision</B>(5)
for details.
<DT><B>bh</B>
<DD>
The bh backend provides access to Bell+Howell Copiscan II series document
scanners. See
<B>sane-bh</B>(5)
for details.
<DT><B>canon</B>
<DD>
The canon backend supports the CanoScan 300, CanoScan 600, and CanoScan
2700F SCSI flatbed scanners. See
<B>sane-canon</B>(5)
for details.
<DT><B>canon630u</B>
<DD>
The canon630u backend supports the CanoScan 630u and 636u USB scanners. See
<B>sane-canon630u</B>(5)
for details.
<DT><B>canon_pp</B>
<DD>
The canon_pp backend supports the CanoScan FB330P, FB630P, N340P and N640P
parallel port scanners. See
<B>sane-canon_pp</B>(5)
for details.
<DT><B>coolscan</B>
<DD>
This is a SANE backend for Nikon Coolscan film-scanners. See
<B>sane-coolscan</B>(5)
for details.
<DT><B>coolscan2</B>
<DD>
This is a SANE backend for Nikon Coolscan film-scanners.
See
<B>sane-coolscan2</B>(5)
or
<I><A HREF="http://coolscan2.sourceforge.net">http://coolscan2.sourceforge.net</A></I>
for details.
<DT><B>epson</B>
<DD>
The SANE epson backend provides support for Epson SCSI, parallel port and USB
flatbed scanners. See
<B>sane-epson</B>(5)
for details.
<DT><B>fujitsu</B>
<DD>
The fujitsu backend provides support for Fujitsu 3091, 3093, 3096 and
fi-4340 SCSI scanners. See
<B>sane-fujitsu</B>(5)
for details.
<DT><B>gt68xx</B>
<DD>
The gt68xx backend provides support for scanners based on the Grandtech
GT-6801 and GT-6816 chips like the Artec Ultima 2000 and several Mustek
BearPaw CU and TA models. Some Genius, Lexmark, Medion, Packard Bell, Plustek,
and Trust scanners are also supported. See
<B>sane-gt68xx</B>(5)
for details.
<DT><B>hp</B>
<DD>
The SANE hp backend provides access to Hewlett-Packard ScanJet scanners which
support SCL (Scanner Control Language by HP). See
<B>sane-hp</B>(5)
for details.
<DT><B>hpsj5s</B>
<DD>
The SANE backend for the Hewlett-Packard ScanJet 5S scanner. See
<B>sane-hpsj5s</B>(5)
for details.
<DT><B>hp5400</B>
<DD>
The SANE backend for the Hewlett-Packard ScanJet 54XXC series. See
<B>sane-hp5400</B>(5)
for details.
<DT><B>ibm</B>
<DD>
The SANE backend for some IBM and Ricoh SCSI scanners. See
<B>sane-ibm</B>(5)
for details.
<DT><B>leo</B>
<DD>
This backend supports the Leo S3 and the Across FS-1130, which is a re-badged
LEO FS-1130 scanner. See
<B>sane-leo</B>(5)
for details.
<DT><B>ma1509</B>
<DD>
The ma1509 backend supports the Mustek BearPaw 1200F USB flatbed scanner. See
<B>sane-ma1509</B>(5)
for details.
<DT><B>matsushita</B>
<DD>
This backend supports some Panasonic KVSS high speed scanners. See
<B>sane-matsushita</B>(5)
for details.
<DT><B>microtek</B>
<DD>
The microtek backend provides access to the &quot;second generation&quot; Microtek
scanners with SCSI-1 command set. See
<B>sane-microtek</B>(5)
for details.
<DT><B>microtek2</B>
<DD>
The microtek2 backend provides access to some Microtek scanners with a
SCSI-2 command set. See
<B>sane-microtek2</B>(5)
for details.
<DT><B>mustek</B>
<DD>
The SANE mustek backend supports most Mustek SCSI flatbed scanners including the
Paragon and ScanExpress series and the 600 II N and 600 II EP (non-SCSI). Some
Trust scanners are also supported. See
<B>sane-mustek</B>(5)
for details.
<DT><B>mustek_pp</B>
<DD>
The mustek_pp backend provides access to Mustek parallel port flatbed
scannersr. See
<B>sane-mustek_pp</B>(5)
for details.
<DT><B>mustek_usb</B>
<DD>
The mustek_usb backend provides access to some Mustek ScanExpress USB flatbed
scanners. See
<B>sane-mustek_usb</B>(5)
for details.
<DT><B>nec</B>
<DD>
The SANE nec backend supports the NEC PC-IN500/4C SCSI scanner. See
<B>sane-nec</B>(5)
for details.
<DT><B>niash</B>
<DD>
The niash backend supports the Agfa Snapscan Touch and the HP ScanJet 3300c,
3400c, and 4300c USB flatbed scanners. See
<B>sane-niash</B>(5)
for details.
<DT><B>pie</B>
<DD>
The pie backend provides access to Pacific Image Electronics (PIE) and Devcom
SCSI flatbed scanners. See
<B>sane-pie</B>(5)
for details.
<DT><B>plustek</B>
<DD>
The SANE plustek backend supports USB flatbed scanners that use the National
Semiconductor LM983[1/2/3]-chipset aka Merlin. Scanners using this LM983x chips
include some models from Plustek, KYE/Genius, Hewlett-Packard, Mustek, Umax,
Epson, and Canon. See
<B>sane-plustek</B>(5)
for details.
<DT><B>plustek_pp</B>
<DD>
The SANE plustek_pp backend supports Plustek parallel port flatbed scanners.
Scanners using the Plustek ASIC P96001, P96003, P98001 and P98003 include some
models from Plustek, KYE/Genius, Primax. See
<B>sane-plustek_pp</B>(5)
for details.
<DT><B>ricoh</B>
<DD>
The ricoh backend provides access to the following Ricoh flatbed
scanners: IS50 and IS60. See
<B>sane-ricoh</B>(5)
for details.
<DT><B>s9036</B>
<DD>
The s9036 backend provides access to Siemens 9036 flatbed scanners. See
<B>sane-s9036</B>(5)
for details.
<DT><B>sceptre</B>
<DD>
The sceptre backend provides access to the Sceptre S1200 flatbed scanner. See
<B>sane-sceptre</B>(5)
<BR>&nbsp;for&nbsp;details.
<DT><B>sharp</B>
<DD>
The SANE sharp backend supports Sharp SCSI scanners. See
<B>sane-sharp</B>(5)
for details.
<DT><B>sm3600</B>
<DD>
The SANE sm3600 backend supports the Microtek ScanMaker 3600 USB scanner. See
<B>sane-sm3600</B>(5)
for details.
<DT><B>snapscan</B>
<DD>
The snapscan backend supports AGFA SnapScan flatbed scanners. See
<B>sane-snapscan</B>(5)
for details.
<DT><B>sp15c</B>
<DD>
This backend supports the Fujitsu FCPA ScanPartner 15C flatbed scanner. See
<B>sane-sp15c</B>(5)
for details.
<DT><B>st400</B>
<DD>
The sane-st400 backend provides access to Siemens ST400 and ST800. See
<B>sane-st400</B>(5)
for details.
<DT><B>tamarack</B>
<DD>
The SANE tamarack backend supports Tamarack Artiscan flatbed scanners. See
<B>sane-tamarack</B>(5)
for details.
<DT><B>teco1 teco2 teco3</B>
<DD>
The SANE teco1, teco2 and teco3 backends support some TECO scanners,
usually sold under the Relisys, Trust, Primax, Piotech, Dextra
names. See
<B>sane-teco1</B>(5), <B>sane-teco2</B>(5) and <B>sane-teco3</B>(5)
for details.
<DT><B>umax</B>
<DD>
The sane-umax backend provides access to several UMAX-SCSI-scanners and some
Linotype Hell SCSI-scanners. See
<B>sane-umax</B>(5)
for details.
<DT><B>umax_pp</B>
<DD>
The sane-umax_pp backend provides access to Umax parallel port flatbed scanners
and the HP 3200C. See
<B>sane-umax_pp</B>(5)
for details.
<DT><B>umax1200u</B>
<DD>
The sane-umax1220u backend supports the UMAX Astra 1220U (USB) flatbed scanner
(and also the UMAX Astra 2000U, sort of). See
<B>sane-umax1220u</B>(5)
for details.
</DL>
<P>
Also, have a look at the backend information page at
<I><A HREF="http://www.sane-project.org/sane-supported-devices.html">http://www.sane-project.org/sane-supported-devices.html</A></I>
and the list of projects in
<I>/usr/doc/sane-1.0.15/PROJECTS</I>.
<P>
<A NAME="lbAI">&nbsp;</A>
<H2>BACKENDS FOR DIGITAL CAMERAS</H2>
<DL COMPACT>
<DT><B>dc210</B>
<DD>
Backend for Kodak DC210 Digital Camera. See
<B>sane-dc210</B>(5).
<DT><B>dc240</B>
<DD>
Backend for Kodak DC240 Digital Camera. See
<B>sane-dc240</B>(5).
<DT><B>dc25</B>
<DD>
Backend for Kodak DC20/DC25 Digital Cameras. See
<B>sane-dc25</B>(5).
<DT><B>dmc</B>
<DD>
Backend for the Polaroid Digital Microscope Camera. See
<B>sane-dmc</B>(5).
<DT><B>gphoto2</B>
<DD>
Backend for digital cameras supported by the gphoto2 library package. (See
<I><A HREF="http://www.gphoto.org">http://www.gphoto.org</A></I>
for more information and a list of supported cameras.) Gphoto2 supports over
140 different camera models. However, please note that more development and
testing is needed before all of these cameras will be supported by
<B>SANE</B>
backend. See
<B>sane-gphoto2</B>(5).
<DT><B>qcam</B>
<DD>
Backend for Connectix QuickCam cameras. See
<B>sane-qcam</B>(5).
</DL>
<P>
Also, have a look at the backend information page at
<I><A HREF="http://www.sane-project.org/sane-supported-devices.html">http://www.sane-project.org/sane-supported-devices.html</A></I>
and the list of projects in
<I>/usr/doc/sane-1.0.15/PROJECTS</I>.
<P>
<A NAME="lbAJ">&nbsp;</A>
<H2>MISCELLANEOUS BACKENDS</H2>
<DL COMPACT>
<DT><B>dll</B>
<DD>
The sane-dll library implements a
<B>SANE</B>
backend that provides access to an arbitrary number of other
<B>SANE</B>
backends by dynamic loading. See
<B>sane-dll</B>(5).
<DT><B>net</B>
<DD>
The
<B>SANE</B>
network daemon saned provides access to scanners located on different
computers in connection with the net backend. See
<B>sane-net</B>(5) and <B>saned</B>(8).
<DT><B>pnm</B>
<DD>
PNM image reader pseudo-backend. The purpose of this backend is primarily to
aid in debugging of
<B>SANE</B>
frontends. See
<B>sane-pnm</B>(5).
<DT><B>pint</B>
<DD>
Backend for scanners that use the
<B>PINT</B>
(Pint Is Not Twain) device driver. The
<B>PINT</B>
driver is being actively developed on the OpenBSD platform, and has been
ported to a few other *nix-like operating systems. See
<B>sane-pint</B>(5).
<DT><B>test</B>
<DD>
The
<B>SANE</B>
test backend is for testing frontends and the
<B>SANE</B>
installation. It provides test pictures and various test options. See
<B>sane-test</B>(5).
<DT><B>v4l</B>
<DD>
The sane-v4l library implements a
<B>SANE</B>
backend that provides generic access to video cameras and similar equipment
using the
<B>V4L</B>
(Video for Linux) API. See
<B>sane-v4l</B>(5)<B>.</B>
</DL>
<P>
Also, have a look at the backend information page at
<I><A HREF="http://www.sane-project.org/sane-supported-devices.html">http://www.sane-project.org/sane-supported-devices.html</A></I>
and the list of projects in
<I>/usr/doc/sane-1.0.15/PROJECTS</I>.
<P>
<A NAME="lbAK">&nbsp;</A>
<H2>CHANGING THE TOP-LEVEL BACKEND</H2>
By default, all
<B>SANE</B>
backends (drivers) are loaded dynamically by the
<B>sane-dll</B>
meta backend. If you have any questions about the dynamic loading,
read
<B>sane-dll</B>(5).
<B>SANE</B>
frontend can also be linked to other backends directly by copying or linking a
backend to
<B>libsane.so</B>
in
<I>/usr/lib/sane</I>.
<P>
<P>
<A NAME="lbAL">&nbsp;</A>
<H2>DEVELOPER'S DOCUMENTATION</H2>
It's not hard to write a
<B>SANE</B>
backend. It can take some time, however. You should have basic knowledge of C
and enough patience to work through the documentation and find out how your
scanner works. Appended is a list of some documents that help to write backends
and frontends.
<P>
The
<B>SANE</B>
standard defines the application programming interface (API) that is used to
communicate between frontends and backends. It can be found at
<I>/usr/doc/sane-1.0.15/sane.ps</I>
(if latex is installed on your system) and on the
<B>SANE</B>
website:
<I><A HREF="http://www.sane-project.org/html/">http://www.sane-project.org/html/</A></I>
(HTML), or
<I><A HREF="http://www.sane-project.org/sane.ps">http://www.sane-project.org/sane.ps</A></I>
(Postscript).
<P>
There is some more information for programmers in
<I>/usr/doc/sane-1.0.15/backend-writing.txt</I>.
Most of the internal
<B>SANE</B>
routines
(<B>sanei</B>)
are documented using doxygen:
<I><A HREF="http://www.sane-project.org/sanei/">http://www.sane-project.org/sanei/</A></I>.
Before a new backend or frontend project is started, have a look at
<I>/usr/doc/sane-1.0.15/PROJECTS</I>
for projects that are planned or not yet included into the
<B>SANE</B>
distribution and at our bug-tracking system:
<I><A HREF="http://www.http://www.sane-project.org/bugs.html">http://www.http://www.sane-project.org/bugs.html</A></I>.
<P>
There are some links on how to find out about the protocol of a scanner:
<I><A HREF="http://www.meier-geinitz.de/sane/misc/develop.html">http://www.meier-geinitz.de/sane/misc/develop.html</A></I>.
<P>
<P>
If you start writing a backend or frontend or any other part of
<B>SANE,</B>
please contact the sane-devel mailing list for coordination so the same work
isn't done twice.
<P>
<A NAME="lbAM">&nbsp;</A>
<H2>FILES</H2>
<DL COMPACT>
<DT><I>/etc/sane.d/*.conf</I>
<DD>
The backend configuration files.
<DT><I>/usr/lib/sane/libsane-*.a</I>
<DD>
The static libraries implementing the backends.
<DT><I>/usr/lib/sane/libsane-*.so</I>
<DD>
The shared libraries implementing the backends (present on systems that
support dynamic loading).
<DT><I>/usr/doc/sane-1.0.15/*</I>
<DD>
<B>SANE</B>
documentation: The standard, READMEs, text files for backends etc.
<P>
</DL>
<A NAME="lbAN">&nbsp;</A>
<H2>PROBLEMS</H2>
If your device isn't found but you know that it is supported, make
sure that it is detected by your operating system. For SCSI and USB scanners,
use the
<B>sane-find-scanner</B>
tool (see
<B>sane-find-scanner</B>(1)
for details). It prints one line for each scanner it has detected and some
comments (#). If
<B>sane-find-scanner</B>
finds your scanner only as root but not as normal user, the permissions for
the device files are not adjusted correctly. If the scanner isn't found at all,
the operating system hasn't detected it and may need some help. Depending on
the type of your scanner, read
<B>sane-usb</B>(5)
or
<B>sane-scsi</B>(5).
If your scanner (or other device) is not connected over the SCSI bus or USB,
read the backend's manual page for details on how to set it up.
<P>
<P>
Now your scanner is detected by the operating system but not by
<B>SANE</B>?
Try
<B>scanimage -L</B>.
If the scanner is not found, check that the backend's name is mentioned in
<I>/etc/sane.d/dll.conf</I>.
Some backends are commented out by default. Remove the comment sign for your
backend in this case. Also some backends aren't compiled at all if one of their
prerequisites are missing. Examples include dc210, dc240, canon_pp, hpsj5s,
gphoto2, pint, qcam, v4l, net, sm3600, snapscan, pnm. If you need one of these
backends and they aren't available, read the build instructions in the
<B>README</B>
file and the individual manual pages of the backends.
<P>
<P>
Another reason for not being detected by
<B>scanimage -L</B>
may be a missing or wrong configuration in the backend's configuration
file. While
<B>SANE</B>
tries to automatically find most scanners, some can't be setup correctly
without the intervention of the administrator. Also on some operating systems
auto-detection may not work. Check the backend's manual page for details.
<P>
If your scanner is still not found, try
setting the various environment variables that are available to assist in
debugging. The environment variables are documented in the
relevant manual pages. For example, to get the maximum amount of debug
information when testing a Mustek SCSI scanner, set environment variables
<B>SANE_DEBUG_DLL</B>, <B>SANE_DEBUG_MUSTEK</B>, and <B>SANE_DEBUG_SANEI_SCSI</B>
to 128 and then invoke
<B>scanimage</B>
<B>-L .</B>
The debug messages for the dll backend tell if the mustek backend was found
and loaded at all. The mustek messages explain what the mustek backend is
doing while the SCSI debugging shows the low level handling. If you can't find
out what's going on by checking the messages carefully, contact the sane-devel
mailing list for help (see REPORTING BUGS below).
<P>
Now that your scanner is found by
<B>scanimage -L</B>,
try to do a scan:
<B>scanimage &gt;image.pnm</B>.
This command starts a scan for the default scanner with default settings. All
the available options are listed by running
<B>scanimage --help</B>.
If scanning aborts with an error message, turn on debugging as mentioned
above. Maybe the configuration file needs some tuning, e.g. to setup the path
to a firmware that is needed by some scanners. See the backend's manual page
for details. If you can't find out what's wrong, contact sane-devel.
<P>
To check that the
<B>SANE</B>
libraries are installed correctly you can use the test backend, even if you
don't have a scanner or other
<B>SANE</B>
device:
<DL COMPACT>
<DT><DD>
<B>scanimage -d</B>
<I>test</I>
<B>-T</B>
</DL>
<P>
You should get a list of PASSed tests. You can do the same with your backend
by changing &quot;test&quot; to your backend's name.
<P>
So now scanning with
<B>scanimage</B>
works and you want to use one of the graphical frontends like
<B>xsane</B>,
<B>xscanimage</B>, or
<B>quiteinsane</B>
but those frontends don't detect your scanner? One reason may be that you
installed two versions of
<B>SANE</B>.
E.g. the version that was installed by your distribution in
<I>/usr</I>
and one you installed from source in
<I>/usr/local/</I>.
Make sure that only one version is installed. Another possible reason is, that
your system's dynamic loader can't find the
<B>SANE</B>
libraries. For Linux, make sure that
<I>/etc/ld.so.conf</I>
contains
<I>/usr/local/lib</I>
and does
<B>not</B>
contain
<I>/usr/local/lib/sane</I>.
See also the documentation of the frontends.
<P>
<P>
<A NAME="lbAO">&nbsp;</A>
<H2>HOW CAN YOU HELP SANE</H2>
We appreciate any help we can get. Please have alook at our web page about
contributing to
<B>SANE</B>:
<I><A HREF="http://www.sane-project.org/contrib.html">http://www.sane-project.org/contrib.html</A></I>
<P>
<P>
<A NAME="lbAP">&nbsp;</A>
<H2>CONTACT</H2>
For reporting bugs or requesting new features, please use our bug-tracking
system:
<I><A HREF="http://www.sane-project.org/bugs.html">http://www.sane-project.org/bugs.html</A></I>.
You can also contact the author of your backend directly. Usually the email
address can be found in the
<I>/usr/doc/sane-1.0.15/AUTHORS</I>
file or the backend's manpage. For general discussion about SANE, please use
the
<B>SANE</B>
mailing list sane-devel (see
<I><A HREF="http://www.sane-project.org/mailing-lists.html">http://www.sane-project.org/mailing-lists.html</A></I>
for details).
<P>
<P>
<A NAME="lbAQ">&nbsp;</A>
<H2>SEE ALSO</H2>
<B>saned</B>(8),
<B>sane-find-scanner</B>(1),
<B>scanimage</B>(1),
<B>sane-abaton</B>(5),
<B>sane-agfafocus</B>(5),
<B>sane-apple</B>(5),
<B>sane-artec</B>(5),
<B>sane-artec_eplus48u</B>(5),
<B>sane-as6e</B>(5),
<B>sane-avision</B>(5),
<B>sane-bh</B>(5),
<B>sane-canon</B>(5),
<B>sane-canon630u</B>(5),
<B>sane-canon_pp</B>(5),
<B>sane-coolscan2</B>(5),
<B>sane-coolscan</B>(5),
<B>sane-dc210</B>(5),
<B>sane-dc240</B>(5),
<B>sane-dc25</B>(5),
<B>sane-dll</B>(5),
<B>sane-dmc</B>(5),
<B>sane-epson</B>(5),
<B>sane-fujitsu</B>(5),
<B>sane-gphoto2</B>(5),
<B>sane-gt68xx</B>(5),
<B>sane-hp</B>(5),
<B>sane-hpsj5s</B>(5),
<B>sane-hp5400</B>(5)
<B>sane-ibm</B>(5),
<B>sane-leo</B>(5),
<B>sane-ma1509</B>(5),
<B>sane-matsushita</B>(5),
<B>sane-microtek2</B>(5),
<B>sane-microtek</B>(5),
<B>sane-mustek</B>(5),
<B>sane-mustek_pp</B>(5),
<B>sane-mustek_usb</B>(5),
<B>sane-nec</B>(5),
<B>sane-net</B>(5),
<B>sane-niash</B>(5),
<B>sane-pie</B>(5),
<B>sane-pint</B>(5),
<B>sane-plustek</B>(5),
<B>sane-plustek_pp</B>(5),
<B>sane-pnm</B>(5),
<B>sane-qcam</B>(5),
<B>sane-ricoh</B>(5),
<B>sane-s9036</B>(5),
<B>sane-sceptre</B>(5),
<B>sane-scsi</B>(5),
<B>sane-sharp</B>(5),
<B>sane-sm3600</B>(5),
<B>sane-snapscan</B>(5),
<B>sane-sp15c</B>(5),
<B>sane-st400</B>(5),
<B>sane-tamarack</B>(5),
<B>sane-teco1</B>(5),
<B>sane-teco2</B>(5),
<B>sane-teco3</B>(5),
<B>sane-test</B>(5),
<B>sane-u12</B>(5),
<B>sane-umax1220u</B>(5),
<B>sane-umax</B>(5),
<B>sane-umax_pp</B>(5),
<B>sane-usb</B>(5),
<B>sane-v4l</B>(5)
<P>
<A NAME="lbAR">&nbsp;</A>
<H2>AUTHOR</H2>
David Mosberger-Tang and many many more (see
<I>/usr/doc/sane-1.0.15/AUTHORS</I>
for details). This man page was written by Henning Meier-Geinitz. Quite a lot
of text was taken from the
<B>SANE</B>
standard, several man pages, and README files
<HR>
<A NAME="index">&nbsp;</A><H2>Index</H2>
<DL>
<DT><A HREF="#lbAB">NAME</A><DD>
<DT><A HREF="#lbAC">DESCRIPTION</A><DD>
<DT><A HREF="#lbAD">TERMINOLOGY</A><DD>
<DT><A HREF="#lbAE">SOFTWARE PACKAGES</A><DD>
<DT><A HREF="#lbAF">GENERAL INFORMATION</A><DD>
<DT><A HREF="#lbAG">FRONTENDS AND MISCELLANEOUS PROGRAMS</A><DD>
<DT><A HREF="#lbAH">BACKENDS FOR SCANNERS</A><DD>
<DT><A HREF="#lbAI">BACKENDS FOR DIGITAL CAMERAS</A><DD>
<DT><A HREF="#lbAJ">MISCELLANEOUS BACKENDS</A><DD>
<DT><A HREF="#lbAK">CHANGING THE TOP-LEVEL BACKEND</A><DD>
<DT><A HREF="#lbAL">DEVELOPER'S DOCUMENTATION</A><DD>
<DT><A HREF="#lbAM">FILES</A><DD>
<DT><A HREF="#lbAN">PROBLEMS</A><DD>
<DT><A HREF="#lbAO">HOW CAN YOU HELP SANE</A><DD>
<DT><A HREF="#lbAP">CONTACT</A><DD>
<DT><A HREF="#lbAQ">SEE ALSO</A><DD>
<DT><A HREF="#lbAR">AUTHOR</A><DD>
</DL>
<HR>
This document was created by
<A HREF="http://wsinwp01.win.tue.nl:1234/cgi-bin/man2html">man2html</A>,
using the manual pages.<BR>
Time: 09:36:01 GMT, January 19, 2005
</BODY>
</HTML>