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

633 wiersze
35 KiB
HTML
Czysty Wina Historia

<HTML>
<HEAD>
<TITLE>sane.7</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="/images/sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane.7</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane.7.html">sane(7)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane.7.html">sane(7)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane - Scanner Access Now Easy: API for accessing scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
<B>SANE</B> is an application programming interface (API) that provides stan-
dardized 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.
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.
This manual page provides a summary of the information available about
<B>SANE</B>.
If you have trouble getting your scanner detected, read the PROBLEMS
section.
</PRE>
<H2>TERMINOLOGY</H2><PRE>
An application that uses the <B>SANE</B> interface is called a <B>SANE</B> <B>frontend.</B>
A driver that implements the <B>SANE</B> interface is called a <B>SANE</B> <B>backend.</B>
A <B>meta</B> <B>backend</B> provides some means to manage one or more other back-
ends.
</PRE>
<H2>SOFTWARE PACKAGES</H2><PRE>
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>http://www.sane-</I>
<I>project.org/</I>). Information about other frontends and backends can also
be found on the <B>SANE</B> homepage.
</PRE>
<H2>GENERAL INFORMATION</H2><PRE>
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><A HREF="sane-dll.5.html">sane-dll(5)</A></B>') points to a manual page. In this case
`<B>man</B> <B>5</B> <B>sane-dll</B>' will display the page. Entries like
`<I>/usr/local/doc/sane-1.0.18/sane.tex</I>' are references to text files that
were copied to the <B>SANE</B> documentation directory
(<I>/usr/local/doc/sane-1.0.18/</I>) during installation. Everything else is a
URL to a resource on the web.
<B>SANE</B> <B>homepage</B>
Information on all aspects of SANE including a tutorial and a link to
the SANE FAQ can be found on the SANE homepage: <I>http://www.sane-</I>
<I>project.org/</I>.
<B>SANE</B> <B>device</B> <B>lists</B>
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>http://www.sane-project.org/sane-supported-devices.html</I>. The lists
are also installed on your system at /usr/local/doc/sane-1.0.18/.
<B>SANE</B> <B>mailing</B> <B>list</B>
There is a mailing list for the purpose of discussing the SANE stan-
dard and its implementations: sane-devel. Despite its name, the list
is not only intended for developers, but also for users. There are
also some more lists for special topics, however, for users, sane-
devel is the right list. How to subscribe and unsubscribe:
<I>http://www.sane-project.org/mailing-lists.html</I>.
<B>SANE</B> <B>IRC</B> <B>channel</B>
The IRC (Internet Relay Chat) channel #sane can be found on the
Freenode network (irc.freenode.net). It's for discussing <B>SANE</B> prob-
lems, talking about development and general <B>SANE</B> related chatting.
Before asking for help, please read the other documentation mentioned
in this manual page. The channel's topic is also used for announce-
ments of problems with SANE infrastructure (mailing lists, web
server, etc.).
<B>Compiling</B> <B>and</B> <B>installing</B> <B>SANE</B>
Look at <I>/usr/local/doc/sane-1.0.18/README</I> and the os-dependent README
files for information about compiling and installing <B>SANE.</B>
<B>SCSI</B> <B>configuration</B>
For information about various systems and SCSI controllers see <B>sane-</B>
<B><A HREF="scsi.5.html">scsi(5)</A></B>.
<B>USB</B> <B>configuration</B>
For information about USB configuration see <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>.
</PRE>
<H2>FRONTENDS AND MISCELLANEOUS PROGRAMS</H2><PRE>
<B>scanimage</B>
Command-line frontend. See <B><A HREF="scanimage.1.html">scanimage(1)</A></B>.
<B>saned</B>
<B>SANE</B> network daemon that allows remote clients to access image acqui-
sition devices available on the local host. See <B><A HREF="saned.8.html">saned(8)</A></B>.
<B>sane-find-scanner</B>
Command-line tool to find SCSI and USB scanners and determine their
Unix device files. See <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>.
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>http://www.sane-project.org/sane-frontends.html</I>.
</PRE>
<H2>BACKENDS FOR SCANNERS</H2><PRE>
<B>abaton</B>
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><A HREF="sane-abaton.5.html">sane-abaton(5)</A></B> for details.
<B>agfafocus</B>
This backend supports AGFA Focus scanners and the Siemens S9036
(untested). See <B><A HREF="sane-agfafocus.5.html">sane-agfafocus(5)</A></B> for details.
<B>apple</B>
The SANE backend for Apple flatbed scanners supports the following
scanners: AppleScanner, OneScanner and ColorOneScanner. See <B>sane-</B>
<B><A HREF="apple.5.html">apple(5)</A></B> for details.
<B>artec</B>
The SANE Artec backend supports several Artec/Ultima SCSI flatbed
scanners as well as the BlackWidow BW4800SP and the Plustek 19200S.
See <B><A HREF="sane-artec.5.html">sane-artec(5)</A></B> for details.
<B>artec_eplus48u</B>
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><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B> for details.
<B>as6e</B>
This is a SANE backend for using the Artec AS6E parallel port inter-
face scanner. See <B><A HREF="sane-as6e.5.html">sane-as6e(5)</A></B> for details.
<B>avision</B>
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 Mit-
subishi and Minolta film-scanners. See <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B> for details.
<B>bh</B>
The bh backend provides access to Bell+Howell Copiscan II series doc-
ument scanners. See <B><A HREF="sane-bh.5.html">sane-bh(5)</A></B> for details.
<B>canon</B>
The canon backend supports the CanoScan 300, CanoScan 600, and
CanoScan 2700F SCSI flatbed scanners. See <B><A HREF="sane-canon.5.html">sane-canon(5)</A></B> for details.
<B>canon630u</B>
The canon630u backend supports the CanoScan 630u and 636u USB scan-
ners. See <B><A HREF="sane-canon630u.5.html">sane-canon630u(5)</A></B> for details.
<B>canon_pp</B>
The canon_pp backend supports the CanoScan FB330P, FB630P, N340P and
N640P parallel port scanners. See <B><A HREF="sane-canon_pp.5.html">sane-canon_pp(5)</A></B> for details.
<B>coolscan</B>
This is a SANE backend for Nikon Coolscan film-scanners. See <B>sane-</B>
<B><A HREF="coolscan.5.html">coolscan(5)</A></B> for details.
<B>coolscan2</B>
This is a SANE backend for Nikon Coolscan film-scanners. See <B>sane-</B>
<B><A HREF="coolscan2.5.html">coolscan2(5)</A></B> or <I>http://coolscan2.sourceforge.net</I> for details.
<B>epson</B>
The SANE epson backend provides support for Epson SCSI, parallel port
and USB flatbed scanners. See <B><A HREF="sane-epson.5.html">sane-epson(5)</A></B> for details.
<B>fujitsu</B>
The fujitsu backend provides support for most Fujitsu SCSI and USB,
flatbed and adf scanners. See <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B> for details.
<B>genesys</B>
The genesys backend provides support for scanners based on the
Genesys Logic GL646 and GL841 chips like the Medion 6471 and Hewlett-
Packard 2300c. Support for GL841 based scanners is far from being
complete. See <B><A HREF="sane-genesys.5.html">sane-genesys(5)</A></B> for details.
<B>gt68xx</B>
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><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B> for details.
<B>hp</B>
The SANE hp backend provides access to Hewlett-Packard ScanJet scan-
ners which support SCL (Scanner Control Language by HP). See <B>sane-</B>
<B><A HREF="hp.5.html">hp(5)</A></B> for details.
<B>hpsj5s</B>
The SANE backend for the Hewlett-Packard ScanJet 5S scanner. See
<B><A HREF="sane-hpsj5s.5.html">sane-hpsj5s(5)</A></B> for details.
<B>hp3500</B>
The SANE backend for the Hewlett-Packard ScanJet 3500 series. See
<B><A HREF="sane-hp3500.5.html">sane-hp3500(5)</A></B> for details.
<B>hp4200</B>
The SANE backend for the Hewlett-Packard ScanJet 4200 series. See
<B><A HREF="sane-hp4200.5.html">sane-hp4200(5)</A></B> for details.
<B>hp5400</B>
The SANE backend for the Hewlett-Packard ScanJet 54XXC series. See
<B><A HREF="sane-hp5400.5.html">sane-hp5400(5)</A></B> for details.
<B>ibm</B>
The SANE backend for some IBM and Ricoh SCSI scanners. See <B>sane-</B>
<B><A HREF="ibm.5.html">ibm(5)</A></B> for details.
<B>leo</B>
This backend supports the Leo S3 and the Across FS-1130, which is a
re-badged LEO FS-1130 scanner. See <B><A HREF="sane-leo.5.html">sane-leo(5)</A></B> for details.
<B>lexmark</B>
This backend supports the Lexmark X1100 series of USB scanners. See
<B><A HREF="sane-lexmark.5.html">sane-lexmark(5)</A></B> for details.
<B>ma1509</B>
The ma1509 backend supports the Mustek BearPaw 1200F USB flatbed
scanner. See <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B> for details.
<B>matsushita</B>
This backend supports some Panasonic KVSS high speed scanners. See
<B><A HREF="sane-matsushita.5.html">sane-matsushita(5)</A></B> for details.
<B>microtek</B>
The microtek backend provides access to the "second generation"
Microtek scanners with SCSI-1 command set. See <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B> for
details.
<B>microtek2</B>
The microtek2 backend provides access to some Microtek scanners with
a SCSI-2 command set. See <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B> for details.
<B>mustek</B>
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-</B>
<B><A HREF="mustek.5.html">mustek(5)</A></B> for details.
<B>mustek_pp</B>
The mustek_pp backend provides access to Mustek parallel port flatbed
scanners. See <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B> for details.
<B>mustek_usb</B>
The mustek_usb backend provides access to some Mustek ScanExpress USB
flatbed scanners. See <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B> for details.
<B>mustek_usb2</B>
The mustek_usb2 backend provides access to scanners using the SQ113
chipset like the Mustek BearPaw 2448 TA Pro USB flatbed scanner. See
<B><A HREF="sane-mustek_usb2.5.html">sane-mustek_usb2(5)</A></B> for details.
<B>nec</B>
The SANE nec backend supports the NEC PC-IN500/4C SCSI scanner. See
<B><A HREF="sane-nec.5.html">sane-nec(5)</A></B> for details.
<B>niash</B>
The niash backend supports the Agfa Snapscan Touch and the HP ScanJet
3300c, 3400c, and 4300c USB flatbed scanners. See <B><A HREF="sane-niash.5.html">sane-niash(5)</A></B> for
details.
<B>pie</B>
The pie backend provides access to Pacific Image Electronics (PIE)
and Devcom SCSI flatbed scanners. See <B><A HREF="sane-pie.5.html">sane-pie(5)</A></B> for details.
<B>pixma</B>
The pixma backend supports Canon PIXMA MP series (multi-function
devices). See <B><A HREF="sane-pixma.5.html">sane-pixma(5)</A></B> or <I>http://home.arcor.de/wittawat/pixma/</I>
for details.
<B>plustek</B>
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><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
for details.
<B>plustek_pp</B>
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><A HREF="sane-plustek_pp.5.html">sane-plustek_pp(5)</A></B> for details.
<B>ricoh</B>
The ricoh backend provides access to the following Ricoh flatbed
scanners: IS50 and IS60. See <B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B> for details.
<B>s9036</B>
The s9036 backend provides access to Siemens 9036 flatbed scanners.
See <B><A HREF="sane-s9036.5.html">sane-s9036(5)</A></B> for details.
<B>sceptre</B>
The sceptre backend provides access to the Sceptre S1200 flatbed
scanner. See <B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B> for details.
<B>sharp</B>
The SANE sharp backend supports Sharp SCSI scanners. See <B>sane-</B>
<B><A HREF="sharp.5.html">sharp(5)</A></B> for details.
<B>sm3600</B>
The SANE sm3600 backend supports the Microtek ScanMaker 3600 USB
scanner. See <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B> for details.
<B>sm3840</B>
The SANE sm3840 backend supports the Microtek ScanMaker 3840 USB
scanner. See <B><A HREF="sane-sm3840.5.html">sane-sm3840(5)</A></B> for details.
<B>snapscan</B>
The snapscan backend supports AGFA SnapScan flatbed scanners. See
<B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B> for details.
<B>sp15c</B>
This backend supports the Fujitsu FCPA ScanPartner 15C flatbed scan-
ner. See <B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B> for details.
<B>st400</B>
The sane-st400 backend provides access to Siemens ST400 and ST800.
See <B><A HREF="sane-st400.5.html">sane-st400(5)</A></B> for details.
<B>tamarack</B>
The SANE tamarack backend supports Tamarack Artiscan flatbed scan-
ners. See <B><A HREF="sane-tamarack.5.html">sane-tamarack(5)</A></B> for details.
<B>teco1</B> <B>teco2</B> <B>teco3</B>
The SANE teco1, teco2 and teco3 backends support some TECO scanners,
usually sold under the Relisys, Trust, Primax, Piotech, Dextra names.
See <B><A HREF="sane-teco1.5.html">sane-teco1(5)</A></B>, <B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B> and <B><A HREF="sane-teco3.5.html">sane-teco3(5)</A></B> for details.
<B>u12</B>
The sane-u12 backend provides USB flatbed scanners based on Plustek's
ASIC 98003 (parallel-port ASIC) and a GeneSys Logics' USB-parport
bridge chip like the Plustek OpticPro U(T)12. See <B><A HREF="sane-u12.5.html">sane-u12(5)</A></B> for
details.
<B>umax</B>
The sane-umax backend provides access to several UMAX-SCSI-scanners
and some Linotype Hell SCSI-scanners. See <B><A HREF="sane-umax.5.html">sane-umax(5)</A></B> for details.
<B>umax_pp</B>
The sane-umax_pp backend provides access to Umax parallel port
flatbed scanners and the HP 3200C. See <B><A HREF="sane-umax_pp.5.html">sane-umax_pp(5)</A></B> for details.
<B>umax1200u</B>
The sane-umax1220u backend supports the UMAX Astra 1220U (USB)
flatbed scanner (and also the UMAX Astra 2000U, sort of). See <B>sane-</B>
<B><A HREF="umax1220u.5.html">umax1220u(5)</A></B> for details.
Also, have a look at the backend information page at <I>http://www.sane-</I>
<I>project.org/sane-supported-devices.html</I> and the list of projects in
<I>/usr/local/doc/sane-1.0.18/PROJECTS</I>.
</PRE>
<H2>BACKENDS FOR DIGITAL CAMERAS</H2><PRE>
<B>dc210</B>
Backend for Kodak DC210 Digital Camera. See <B><A HREF="sane-dc210.5.html">sane-dc210(5)</A></B>.
<B>dc240</B>
Backend for Kodak DC240 Digital Camera. See <B><A HREF="sane-dc240.5.html">sane-dc240(5)</A></B>.
<B>dc25</B>
Backend for Kodak DC20/DC25 Digital Cameras. See <B><A HREF="sane-dc25.5.html">sane-dc25(5)</A></B>.
<B>dmc</B>
Backend for the Polaroid Digital Microscope Camera. See <B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B>.
<B>gphoto2</B>
Backend for digital cameras supported by the gphoto2 library package.
(See <I>http://www.gphoto.org</I> for more information and a list of sup-
ported 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><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>.
<B>qcam</B>
Backend for Connectix QuickCam cameras. See <B><A HREF="sane-qcam.5.html">sane-qcam(5)</A></B>.
<B>stv680</B>
The sane-st680 backend provides access to webcams with a stv680 chip.
See <B><A HREF="sane-st680.5.html">sane-st680(5)</A></B> for details.
Also, have a look at the backend information page at <I>http://www.sane-</I>
<I>project.org/sane-supported-devices.html</I> and the list of projects in
<I>/usr/local/doc/sane-1.0.18/PROJECTS</I>.
</PRE>
<H2>MISCELLANEOUS BACKENDS</H2><PRE>
<B>dll</B>
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><A HREF="sane-dll.5.html">sane-dll(5)</A></B>.
<B>net</B>
The <B>SANE</B> network daemon saned provides access to scanners located on
different computers in connection with the net backend. See <B>sane-</B>
<B><A HREF="net.5.html">net(5)</A></B> and <B><A HREF="saned.8.html">saned(8)</A></B>.
<B>pnm</B>
PNM image reader pseudo-backend. The purpose of this backend is pri-
marily to aid in debugging of <B>SANE</B> frontends. See <B><A HREF="sane-pnm.5.html">sane-pnm(5)</A></B>.
<B>pint</B>
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 sys-
tems. See <B><A HREF="sane-pint.5.html">sane-pint(5)</A></B>.
<B>test</B>
The <B>SANE</B> test backend is for testing frontends and the <B>SANE</B> installa-
tion. It provides test pictures and various test options. See <B>sane-</B>
<B><A HREF="test.5.html">test(5)</A></B>.
<B>v4l</B>
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><A HREF="sane-v4l.5.html">sane-v4l(5)</A></B><B>.</B>
Also, have a look at the backend information page at <I>http://www.sane-</I>
<I>project.org/sane-supported-devices.html</I> and the list of projects in
<I>/usr/local/doc/sane-1.0.18/PROJECTS</I>.
</PRE>
<H2>CHANGING THE TOP-LEVEL BACKEND</H2><PRE>
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><A HREF="sane-dll.5.html">sane-dll(5)</A></B>. <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/local/lib/sane</I>.
</PRE>
<H2>DEVELOPER'S DOCUMENTATION</H2><PRE>
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.
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/local/doc/sane-1.0.18/sane.ps</I> (if latex is installed on
your system) and on the <B>SANE</B> website: <I>http://www.sane-project.org/html/</I>
(HTML), or <I>http://www.sane-project.org/sane.ps</I> (Postscript).
There is some more information for programmers in
<I>/usr/local/doc/sane-1.0.18/backend-writing.txt</I>. Most of the internal
<B>SANE</B> routines (<B>sanei</B>) are documented using doxygen: <I>http://www.sane-</I>
<I>project.org/sanei/</I>. Before a new backend or frontend project is
started, have a look at <I>/usr/local/doc/sane-1.0.18/PROJECTS</I> for
projects that are planned or not yet included into the <B>SANE</B> distribu-
tion and at our bug-tracking system: <I>http://www.http://www.sane-</I>
<I>project.org/bugs.html</I>.
There are some links on how to find out about the protocol of a scan-
ner: <I>http://www.meier-geinitz.de/sane/misc/develop.html</I>.
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.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/*.conf</I>
The backend configuration files.
<I>/usr/local/lib/sane/libsane-*.a</I>
The static libraries implementing the backends.
<I>/usr/local/lib/sane/libsane-*.so</I>
The shared libraries implementing the backends (present on sys-
tems that support dynamic loading).
<I>/usr/local/doc/sane-1.0.18/*</I>
<B>SANE</B> documentation: The standard, READMEs, text files for back-
ends etc.
</PRE>
<H2>PROBLEMS</H2><PRE>
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 scan-
ners, use the <B>sane-find-scanner</B> tool (see <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B> 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><A HREF="sane-usb.5.html">sane-usb(5)</A></B> or <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>. If your scanner (or
other device) is not connected over the SCSI bus or USB, read the back-
end's manual page for details on how to set it up.
Now your scanner is detected by the operating system but not by <B>SANE</B>?
Try <B>scanimage</B> <B>-L</B>. If the scanner is not found, check that the back-
end's name is mentioned in <I>/usr/local/etc/sane.d/dll.conf</I>. Some back-
ends 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.
Another reason for not being detected by <B>scanimage</B> <B>-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 cor-
rectly without the intervention of the administrator. Also on some
operating systems auto-detection may not work. Check the backend's man-
ual page for details.
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> <B>.</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, con-
tact the sane-devel mailing list for help (see REPORTING BUGS below).
Now that your scanner is found by <B>scanimage</B> <B>-L</B>, try to do a scan: <B>scan-</B>
<B>image</B> <B>&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</B> <B>--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.
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:
<B>scanimage</B> <B>-d</B> <I>test</I> <B>-T</B>
You should get a list of PASSed tests. You can do the same with your
backend by changing "test" to your backend's name.
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.
</PRE>
<H2>HOW CAN YOU HELP SANE</H2><PRE>
We appreciate any help we can get. Please have a look at our web page
about contributing to <B>SANE</B>: <I>http://www.sane-project.org/contrib.html</I>
</PRE>
<H2>CONTACT</H2><PRE>
For reporting bugs or requesting new features, please use our bug-
tracking system: <I>http://www.sane-project.org/bugs.html</I>. You can also
contact the author of your backend directly. Usually the email address
can be found in the <I>/usr/local/doc/sane-1.0.18/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>http://www.sane-project.org/mailing-</I>
<I>lists.html</I> for details).
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="saned.8.html">saned(8)</A></B>, <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="sane-abaton.5.html">sane-abaton(5)</A></B>, <B>sane-</B>
<B><A HREF="agfafocus.5.html">agfafocus(5)</A></B>, <B><A HREF="sane-apple.5.html">sane-apple(5)</A></B>, <B><A HREF="sane-artec.5.html">sane-artec(5)</A></B>, <B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B>,
<B><A HREF="sane-as6e.5.html">sane-as6e(5)</A></B>, <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B>, <B><A HREF="sane-bh.5.html">sane-bh(5)</A></B>, <B><A HREF="sane-canon.5.html">sane-canon(5)</A></B>, <B>sane-</B>
<B><A HREF="canon630u.5.html">canon630u(5)</A></B>, <B><A HREF="sane-canon_pp.5.html">sane-canon_pp(5)</A></B>, <B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B>, <B><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B>,
<B><A HREF="sane-dc210.5.html">sane-dc210(5)</A></B>, <B><A HREF="sane-dc240.5.html">sane-dc240(5)</A></B>, <B><A HREF="sane-dc25.5.html">sane-dc25(5)</A></B>, <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>, <B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B>,
<B><A HREF="sane-epson.5.html">sane-epson(5)</A></B>, <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>, <B><A HREF="sane-genesys.5.html">sane-genesys(5)</A></B>, <B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>, <B>sane-</B>
<B><A HREF="gt68xx.5.html">gt68xx(5)</A></B>, <B><A HREF="sane-hp.5.html">sane-hp(5)</A></B>, <B><A HREF="sane-hpsj5s.5.html">sane-hpsj5s(5)</A></B>, <B><A HREF="sane-hp3500.5.html">sane-hp3500(5)</A></B>, <B><A HREF="sane-hp4200.5.html">sane-hp4200(5)</A></B>,
<B><A HREF="sane-hp5400.5.html">sane-hp5400(5)</A></B>, <B><A HREF="sane-ibm.5.html">sane-ibm(5)</A></B>, <B><A HREF="sane-leo.5.html">sane-leo(5)</A></B>, <B><A HREF="sane-lexmark.5.html">sane-lexmark(5)</A></B>, <B>sane-</B>
<B><A HREF="ma1509.5.html">ma1509(5)</A></B>, <B><A HREF="sane-matsushita.5.html">sane-matsushita(5)</A></B>, <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B>, <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B>,
<B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>, <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B>sane-</B>
<B><A HREF="mustek_usb2.5.html">mustek_usb2(5)</A></B>, <B><A HREF="sane-nec.5.html">sane-nec(5)</A></B>, <B><A HREF="sane-net.5.html">sane-net(5)</A></B>, <B><A HREF="sane-niash.5.html">sane-niash(5)</A></B>, <B><A HREF="sane-pie.5.html">sane-pie(5)</A></B>,
<B><A HREF="sane-pint.5.html">sane-pint(5)</A></B>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>, <B><A HREF="sane-plustek_pp.5.html">sane-plustek_pp(5)</A></B>, <B><A HREF="sane-pnm.5.html">sane-pnm(5)</A></B>, <B>sane-</B>
<B><A HREF="qcam.5.html">qcam(5)</A></B>, <B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B>, <B><A HREF="sane-s9036.5.html">sane-s9036(5)</A></B>, <B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>,
<B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B>, <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B>, <B><A HREF="sane-sm3840.5.html">sane-sm3840(5)</A></B>, <B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B>, <B>sane-</B>
<B><A HREF="sp15c.5.html">sp15c(5)</A></B>, <B><A HREF="sane-st400.5.html">sane-st400(5)</A></B>, <B><A HREF="sane-stv680.5.html">sane-stv680(5)</A></B>, <B><A HREF="sane-tamarack.5.html">sane-tamarack(5)</A></B>, <B>sane-</B>
<B><A HREF="teco1.5.html">teco1(5)</A></B>, <B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B>, <B><A HREF="sane-teco3.5.html">sane-teco3(5)</A></B>, <B><A HREF="sane-test.5.html">sane-test(5)</A></B>, <B><A HREF="sane-u12.5.html">sane-u12(5)</A></B>,
<B><A HREF="sane-umax1220u.5.html">sane-umax1220u(5)</A></B>, <B><A HREF="sane-umax.5.html">sane-umax(5)</A></B>, <B><A HREF="sane-umax_pp.5.html">sane-umax_pp(5)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B>sane-</B>
<B><A HREF="v4l.5.html">v4l(5)</A></B>
</PRE>
<H2>AUTHOR</H2><PRE>
David Mosberger-Tang and many many more (see
<I>/usr/local/doc/sane-1.0.18/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.
sane-backends 1.0.18 16 October 2005 <B><A HREF="sane.7.html">sane(7)</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>
Reference in New Issue View Git Blame Kopiuj bezpośredni odnośnik