kopia lustrzana https://gitlab.com/sane-project/website
Updated man pages.
Henning Geinitz
rodzic
d8bc494df7
commit
84c44d29d1
|
|
@ -71,7 +71,7 @@
|
|||
<H2>EMAIL-CONTACT</H2><PRE>
|
||||
Oliver.Rauch@Rauch-Domain.DE
|
||||
|
||||
sane-backends 1.0.14-cvs 11 Sep 2002 <B><A HREF="gamma4scanimage.1.html">gamma4scanimage(1)</A></B>
|
||||
sane-backends 1.0.15 11 Sep 2002 <B><A HREF="gamma4scanimage.1.html">gamma4scanimage(1)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -142,7 +142,7 @@
|
|||
The sane-abaton backend was partially written by David Huggins-Daines,
|
||||
based on the sane-apple backend by Milon Firikis.
|
||||
|
||||
sane-backends 1.0.14-cvs 19 Nov 1998 <B><A HREF="sane-abaton.5.html">sane-abaton(5)</A></B>
|
||||
sane-backends 1.0.15 19 Nov 1998 <B><A HREF="sane-abaton.5.html">sane-abaton(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -178,7 +178,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
Ingo Schneider and Karl Anders Øygard.
|
||||
|
||||
sane-backends 1.0.14-cvs 17 Oct 1998 <B><A HREF="sane-agfafocus.5.html">sane-agfafocus(5)</A></B>
|
||||
sane-backends 1.0.15 17 Oct 1998 <B><A HREF="sane-agfafocus.5.html">sane-agfafocus(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -283,7 +283,7 @@
|
|||
Firikis. It is mostly based on the mustek backend from David Mosberger
|
||||
and Andreas Czechanowski
|
||||
|
||||
sane-backends 1.0.14-cvs 13 May 1998 <B><A HREF="sane-apple.5.html">sane-apple(5)</A></B>
|
||||
sane-backends 1.0.15 13 May 1998 <B><A HREF="sane-apple.5.html">sane-apple(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -172,7 +172,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
Chris Pinkham (cpinkham@corp.infi.net)
|
||||
|
||||
sane-backends 1.0.14-cvs 24 Jan 2000 <B><A HREF="sane-artec.5.html">sane-artec(5)</A></B>
|
||||
sane-backends 1.0.15 24 Jan 2000 <B><A HREF="sane-artec.5.html">sane-artec(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -187,7 +187,7 @@
|
|||
<I>http://www.angelfire.com/linux/crapsite</I>. Please contact me if you find
|
||||
a bug or missing feature: <crapsite@gmx.net>
|
||||
|
||||
sane-backends 1.0.14-cvs 19 Nov 2002 <B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B>
|
||||
sane-backends 1.0.15 19 Nov 2002 <B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -38,7 +38,7 @@
|
|||
|
||||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="as6edriver.5.html">as6edriver(5)</A></B>, <B><A HREF="saned.1.html">saned(1)</A></B>, <B>http://as6edriver.sourceforge.net</B>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="as6edriver.5.html">as6edriver(5)</A></B>, <B><A HREF="saned.8.html">saned(8)</A></B>, <B>http://as6edriver.sourceforge.net</B>
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -50,7 +50,7 @@
|
|||
<H2>EMAIL-CONTACT</H2><PRE>
|
||||
yossarian@users.sourceforge.net
|
||||
|
||||
sane-backends 1.0.14-cvs Dec 14th, 2003 <B><A HREF="sane-as6e.5.html">sane-as6e(5)</A></B>
|
||||
sane-backends 1.0.15 Dec 14th, 2003 <B><A HREF="sane-as6e.5.html">sane-as6e(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -13,8 +13,8 @@
|
|||
</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 scan-
|
||||
ners.
|
||||
ners (HP, Minolta, Mitsubishi, UMAX and possibly more) flatbed and film
|
||||
scanners.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -29,8 +29,11 @@
|
|||
backend that provides access to various Avision scanners and the Avi-
|
||||
sion OEM scanners labelled by HP, Minolta, Mitsubishi or Fujitsu.
|
||||
|
||||
<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!
|
||||
It is fully big-endian aware and in every-day use on PowerPC and SPARC
|
||||
systems.
|
||||
|
||||
<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>
|
||||
you try the first scans - especially with film-scanners!
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -38,14 +41,15 @@
|
|||
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
|
||||
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:
|
||||
|
||||
# this is a comment
|
||||
|
||||
option force-a4
|
||||
option force-a3
|
||||
option disable-gamma-table
|
||||
option disable-calibration
|
||||
option one-calib-only
|
||||
|
|
@ -59,10 +63,17 @@
|
|||
|
||||
- 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.
|
||||
returned by the scanner to ISO A4. Scanner that are
|
||||
known to return bogus data are marked in the backend
|
||||
so if you need this option please report this to the
|
||||
backend maintainer. USE WITH CARE!
|
||||
|
||||
- force-a3:
|
||||
Forces the backend to overwrite the scanable area
|
||||
returned by the scanner to ISO A3. Scanner that are
|
||||
known to return bogus data are marked in the backend
|
||||
so if you need this option please report this to the
|
||||
backend maintainer. USE WITH CARE!
|
||||
|
||||
- disable-gamma-table:
|
||||
Disables the usage of the scanner's gamma-table. You
|
||||
|
|
@ -103,10 +114,10 @@
|
|||
<I>usb</I> <I>usb-sec</I>
|
||||
|
||||
Where <I>scsi-spec</I> is the path-name to a special device or a device ID for
|
||||
the device that corresponds to a SCSI scanner. The special device name
|
||||
must be a generic SCSI device or a symlink to such a device, for exam-
|
||||
the device that corresponds to a SCSI scanner. The special device name
|
||||
must be a generic SCSI device or a symlink to such a device, for exam-
|
||||
ple on Linux "/dev/sga" or "/dev/sg0". The device ID is the ID returned
|
||||
by the scanner, for example "HP" or "AVISION". See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for
|
||||
by the scanner, for example "HP" or "AVISION". See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for
|
||||
details.
|
||||
|
||||
Note: Since the backend now includes native USB access,
|
||||
|
|
@ -116,7 +127,7 @@
|
|||
the HP 53xx, HP 74xx or Minolta film-scanners.
|
||||
|
||||
<I>usb-spec</I> is the USB device name, the vendor/product ID pair or the name
|
||||
used by libusb corresponding to the USB scanner. For example "0x03f0
|
||||
used by libusb corresponding to the USB scanner. For example "0x03f0
|
||||
0x0701" or "libusb:002:003". See <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B> for details.
|
||||
|
||||
The program <I>sane-find-scanner</I> helps to find out the correct scsi or usb
|
||||
|
|
@ -129,7 +140,7 @@
|
|||
</PRE>
|
||||
<H2>FILES</H2><PRE>
|
||||
<I>/usr/local/etc/sane.d/avision.conf</I>
|
||||
The backend configuration file (see also description of
|
||||
The backend configuration file (see also description of
|
||||
<B>SANE_CONFIG_DIR</B> below).
|
||||
|
||||
<I>/usr/local/lib/sane/libsane-avision.a</I>
|
||||
|
|
@ -145,22 +156,22 @@
|
|||
<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
|
||||
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
|
||||
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
|
||||
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
|
||||
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
|
||||
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
|
||||
|
|
@ -169,14 +180,14 @@
|
|||
</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>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>
|
||||
http://www.rocklinux-consulting.de/oss/avision/
|
||||
http://www.exactcode.de/oss/avision/
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>AUTHOR</H2><PRE>
|
||||
René Rebe and Meino Christian Cramer
|
||||
|
||||
sane-backends 1.0.14-cvs 04 Mar 2003 <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B>
|
||||
sane-backends 1.0.15 04 Mar 2003 <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -502,7 +502,7 @@
|
|||
Reifschneider of tummy.com ltd. Some 8000 enhancements added by Mark
|
||||
Temple.
|
||||
|
||||
sane-backends 1.0.14-cvs 15 Sep 1999 <B><A HREF="sane-bh.5.html">sane-bh(5)</A></B>
|
||||
sane-backends 1.0.15 15 Sep 1999 <B><A HREF="sane-bh.5.html">sane-bh(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -108,7 +108,7 @@
|
|||
support by Mitsuru Okaniwa; FS2710S support by Ulrich Deiters
|
||||
Man page by Henning Meier-Geinitz (mostly based on canon.README)
|
||||
|
||||
sane-backends 1.0.14-cvs 03 May 2001 <B><A HREF="sane-canon.5.html">sane-canon(5)</A></B>
|
||||
sane-backends 1.0.15 03 May 2001 <B><A HREF="sane-canon.5.html">sane-canon(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -117,7 +117,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
Nathan Rutman
|
||||
|
||||
sane-backends 1.0.14-cvs 06 Apr 2002 <B><A HREF="sane-canon630u.5.html">sane-canon630u(5)</A></B>
|
||||
sane-backends 1.0.15 06 Apr 2002 <B><A HREF="sane-canon630u.5.html">sane-canon630u(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -222,7 +222,7 @@
|
|||
Many thanks to Kevin Easton for his comments and help, and Kent A. Sig-
|
||||
norini for his help with the N340P.
|
||||
|
||||
sane-backends 1.0.14-cvs 1 October 2002 <B><A HREF="sane-canon_pp.5.html">sane-canon_pp(5)</A></B>
|
||||
sane-backends 1.0.15 1 October 2002 <B><A HREF="sane-canon_pp.5.html">sane-canon_pp(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -69,7 +69,7 @@
|
|||
This manual page was written by Julien BLACHE <jblache@debian.org>, for
|
||||
the Debian GNU/Linux system (but may be used by others).
|
||||
|
||||
sane-backends 1.0.14-cvs 8 Jan 2004 <B><A HREF="sane-config.1.html">sane-config(1)</A></B>
|
||||
sane-backends 1.0.15 8 Jan 2004 <B><A HREF="sane-config.1.html">sane-config(1)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -122,7 +122,7 @@
|
|||
<H2>EMAIL-CONTACT</H2><PRE>
|
||||
andreas.rick@free.fr
|
||||
|
||||
sane-backends 1.0.14-cvs 4 July 2000 <B><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B>
|
||||
sane-backends 1.0.15 4 July 2000 <B><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -17,12 +17,13 @@
|
|||
|
||||
</PRE>
|
||||
<H2>DESCRIPTION</H2><PRE>
|
||||
The library implements a SANE (Scanner Access Now Easy) backend that
|
||||
provides access to Nikon Coolscan film scanners. Some functions of
|
||||
this backend should be considered <B>beta-quality</B> software. Most functions
|
||||
have been stable for a long time, but of course new development can not
|
||||
and will not function properly from the very first day. Please report
|
||||
any strange behaviour to the maintainer of the backend.
|
||||
The <B>sane-coolscan2</B> library implements a SANE (Scanner Access Now Easy)
|
||||
backend that provides access to Nikon Coolscan film scanners. Some
|
||||
functions of this backend should be considered <B>beta-quality</B> software.
|
||||
Most functions have been stable for a long time, but of course new
|
||||
development can not and will not function properly from the very first
|
||||
day. Please report any strange behaviour to the maintainer of the back-
|
||||
end.
|
||||
|
||||
At present, the following scanners are known to work with this backend:
|
||||
|
||||
|
|
@ -34,109 +35,109 @@
|
|||
LS-4000 ED IEEE 1394
|
||||
LS-8000 ED IEEE 1394
|
||||
|
||||
Please send mail to the backend author (andras@users.sourceforge.net)
|
||||
Please send mail to the backend author (andras@users.sourceforge.net)
|
||||
to report successes or failures.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>OPTIONS</H2><PRE>
|
||||
The options the backend supports can either be selected through command
|
||||
line options to programs like scanimage or through GUI elements in
|
||||
line options to programs like scanimage or through GUI elements in
|
||||
xscanimage or xsane.
|
||||
|
||||
Valid command line options and their syntax can be listed by using
|
||||
scanimage --help -d coolscan2:<interface>:<device>
|
||||
where <interface> and <device> specify the device in question, as in
|
||||
the configuration file (see next section). The "-d" parameter and its
|
||||
argument can be omitted to obtain information on the first scanner
|
||||
where <interface> and <device> specify the device in question, as in
|
||||
the configuration file (see next section). The "-d" parameter and its
|
||||
argument can be omitted to obtain information on the first scanner
|
||||
identified. Use the command
|
||||
scanimage -L
|
||||
to list all devices recognized by your SANE installation.
|
||||
|
||||
The options should be fully described by the description or tooltips
|
||||
given by frontend. Here is a description of some of the most important
|
||||
The options should be fully described by the description or tooltips
|
||||
given by frontend. Here is a description of some of the most important
|
||||
options, in the syntax with which they must be supplied to scanimage:
|
||||
|
||||
<I>--frame</I> <I><n></I>
|
||||
This option specifies which frame to operate on, if a motorized
|
||||
film strip feeder or APS adapter are used. The frame number <I><n></I>
|
||||
This option specifies which frame to operate on, if a motorized
|
||||
film strip feeder or APS adapter are used. The frame number <I><n></I>
|
||||
ranges from 1 to the number of frames available, which is sensed
|
||||
each time the backend is initialized (usually each time you
|
||||
each time the backend is initialized (usually each time you
|
||||
start the frontend).
|
||||
|
||||
<I>--subframe</I> <I><x></I>
|
||||
This option shifts the scan window by the specified amount
|
||||
This option shifts the scan window by the specified amount
|
||||
(default unit is mm).
|
||||
|
||||
<I>--infrared=yes/no</I>
|
||||
If set to "yes", the scanner will read the infrared channel,
|
||||
thus allowing defect removal in software. The infrared image is
|
||||
read during a second scan, with no options altered. The backend
|
||||
must not be restarted between the scans. If you use scanimage,
|
||||
perform a batch scan with batch-count=2 to obtain the IR infor-
|
||||
mation.
|
||||
If set to "yes", the scanner will read the infrared channel,
|
||||
thus allowing defect removal in software. The infrared image is
|
||||
read during a second scan, with no options altered. The backend
|
||||
must not be restarted between the scans. If you use scanimage,
|
||||
perform a batch scan with batch-count=2 to obtain the IR
|
||||
information.
|
||||
|
||||
<I>--depth</I> <I><n></I>
|
||||
Here <n> can either be 8 or the maximum number of bits supported
|
||||
by the scanner (10, 12, or 14). It specifies whether or not the
|
||||
scanner reduces the scanned data to 8 bits before sending it to
|
||||
by the scanner (10, 12, or 14). It specifies whether or not the
|
||||
scanner reduces the scanned data to 8 bits before sending it to
|
||||
the backend. If 8 bits are used, some information and thus image
|
||||
quality is lost, but the amount of data is smaller compared to
|
||||
higher depths. Also, many imaging programs and image formats
|
||||
quality is lost, but the amount of data is smaller compared to
|
||||
higher depths. Also, many imaging programs and image formats
|
||||
cannot handle depths greater than 8 bits.
|
||||
|
||||
<I>--autofocus</I>
|
||||
Perform autofocus operation. Unless otherwise specified by the
|
||||
Perform autofocus operation. Unless otherwise specified by the
|
||||
other options ( <I>--focus-on-centre</I> and friends), focusing is per-
|
||||
formed on the centre of the selected scan area.
|
||||
|
||||
<I>--ae-wb</I>
|
||||
|
||||
<I>--ae</I> Perform a pre-scan to calculate exposure values automatically.
|
||||
<I>--ae-wb</I> will maintain the white balance, while <I>--ae</I> will adjust
|
||||
<I>--ae</I> Perform a pre-scan to calculate exposure values automatically.
|
||||
<I>--ae-wb</I> will maintain the white balance, while <I>--ae</I> will adjust
|
||||
each channel separately.
|
||||
|
||||
<I>--exposure</I>
|
||||
Multiply all exposure times with this value. This allows expo-
|
||||
Multiply all exposure times with this value. This allows expo-
|
||||
sure correction without modifying white balance.
|
||||
|
||||
<I>--load</I> Load the next slide when using the slide loader.
|
||||
|
||||
<I>--eject</I>
|
||||
Eject the film strip or mounted slide when using the slide
|
||||
Eject the film strip or mounted slide when using the slide
|
||||
loader.
|
||||
|
||||
<I>--reset</I>
|
||||
Reset scanner. The scanner will perform the same action as when
|
||||
power is turned on: it will eject the film strip and calibrate
|
||||
itself. Use this whenever the scanner refuses to load a film
|
||||
Reset scanner. The scanner will perform the same action as when
|
||||
power is turned on: it will eject the film strip and calibrate
|
||||
itself. Use this whenever the scanner refuses to load a film
|
||||
strip properly, as a result of which <I>--eject</I> does not work.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONFIGURATION FILE</H2><PRE>
|
||||
The configuration file /usr/local/etc/sane.d/coolscan2.conf specifies
|
||||
the device(s) that the backend will use. Owing to the nature of the
|
||||
supported connection types SCSI, USB, and IEEE 1394, the default con-
|
||||
The configuration file /usr/local/etc/sane.d/coolscan2.conf specifies
|
||||
the device(s) that the backend will use. Owing to the nature of the
|
||||
supported connection types SCSI, USB, and IEEE 1394, the default con-
|
||||
figuration file supplied with the SANE distribution should work without
|
||||
being edited.
|
||||
|
||||
Each line in the configuration file is either of the following, where
|
||||
Each line in the configuration file is either of the following, where
|
||||
all entries are case-sensitive:
|
||||
|
||||
<I>blank</I> <I>or</I> <I>starting</I> <I>with</I> <I>a</I> <I>'#'</I> <I>character</I>
|
||||
These lines are ignored, thus '#' can be used to include com-
|
||||
These lines are ignored, thus '#' can be used to include com-
|
||||
ments.
|
||||
|
||||
<I>containing</I> <I>only</I> <I>the</I> <I>word</I> <I>"auto"</I>
|
||||
This instructs the backend to probe for a scanner by scanning
|
||||
the buses for devices with know identifiers. This is the action
|
||||
This instructs the backend to probe for a scanner by scanning
|
||||
the buses for devices with know identifiers. This is the action
|
||||
taken when no configuration file is present.
|
||||
|
||||
<I>a</I> <I>line</I> <I>of</I> <I>the</I> <I>form</I> <I><interface>:<device></I>
|
||||
Here <interface> can be one of "scsi" or "usb", and <device> is
|
||||
the device file of the scanner. Note that IEEE 1394 devices are
|
||||
handled by the SBP-2 module in the kernel and appear to SANE as
|
||||
Here <interface> can be one of "scsi" or "usb", and <device> is
|
||||
the device file of the scanner. Note that IEEE 1394 devices are
|
||||
handled by the SBP-2 module in the kernel and appear to SANE as
|
||||
SCSI devices.
|
||||
|
||||
|
||||
|
|
@ -150,16 +151,16 @@
|
|||
that support dynamic loading).
|
||||
|
||||
<I>/usr/local/etc/sane.d/coolscan2.conf</I>
|
||||
Configuration file for this backend, read each time the backend
|
||||
Configuration file for this backend, read each time the backend
|
||||
is initialized.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_DEBUG_COOLSCAN2</B>
|
||||
If the library was compiled with debug support enabled, this
|
||||
environment variable controls the debug level for this backend.
|
||||
E.g., a value of 128 requests all debug output to be printed.
|
||||
If the library was compiled with debug support enabled, this
|
||||
environment variable controls the debug level for this backend.
|
||||
E.g., a value of 128 requests all debug output to be printed.
|
||||
Smaller levels reduce verbosity.
|
||||
|
||||
|
||||
|
|
@ -170,29 +171,29 @@
|
|||
|
||||
</PRE>
|
||||
<H2>BUGS</H2><PRE>
|
||||
Currently, the SANE protocol does not allow automatically updating
|
||||
options whenever the hardware changes. Thus the number of choices for
|
||||
the <B>--frame</B> option will be fixed when the backend is initialized (usu-
|
||||
ally when the user runs the frontend). In particular, if there is no
|
||||
film strip in the automatic film strip feeder when the backend is ini-
|
||||
Currently, the SANE protocol does not allow automatically updating
|
||||
options whenever the hardware changes. Thus the number of choices for
|
||||
the <B>--frame</B> option will be fixed when the backend is initialized (usu-
|
||||
ally when the user runs the frontend). In particular, if there is no
|
||||
film strip in the automatic film strip feeder when the backend is ini-
|
||||
tialized, the frame option will not appear at all. Also, restarting the
|
||||
frontend after swapping film adapters is strongly recommended.
|
||||
|
||||
Linux kernels prior to 2.4.19 had a patch that truncated INQUIRY data
|
||||
Linux kernels prior to 2.4.19 had a patch that truncated INQUIRY data
|
||||
from IEEE 1394 scanners to 36 bytes, discarding vital information about
|
||||
the scanner. The IEEE 1394 models therefore only work with 2.4.19 or
|
||||
the scanner. The IEEE 1394 models therefore only work with 2.4.19 or
|
||||
later.
|
||||
|
||||
No real bugs currently known, please report any to the backend main-
|
||||
No real bugs currently known, please report any to the backend main-
|
||||
tainer or the SANE developers' email list.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>AUTHORS</H2><PRE>
|
||||
The backend is written and maintained by András Major
|
||||
The backend is written and maintained by András Major
|
||||
(andras@users.sourceforge.net).
|
||||
|
||||
sane-backends 1.0.14-cvs 22/08/2002 <B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B>
|
||||
sane-backends 1.0.15 22/08/2002 <B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -123,7 +123,7 @@
|
|||
be subscribed to the list, otherwise your mail won't be sent to the
|
||||
subscribers.
|
||||
|
||||
sane-backends 1.0.14-cvs 15 July 2000 <B><A HREF="sane-dc210.5.html">sane-dc210(5)</A></B>
|
||||
sane-backends 1.0.15 15 July 2000 <B><A HREF="sane-dc210.5.html">sane-dc210(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -126,7 +126,7 @@
|
|||
be subscribed to the list, otherwise your mail won't be sent to the
|
||||
subscribers.
|
||||
|
||||
sane-backends 1.0.14-cvs 23 March 2001 <B><A HREF="sane-dc240.5.html">sane-dc240(5)</A></B>
|
||||
sane-backends 1.0.15 23 March 2001 <B><A HREF="sane-dc240.5.html">sane-dc240(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -116,7 +116,7 @@
|
|||
be subscribed to the list, otherwise your mail won't be sent to the
|
||||
subscribers.
|
||||
|
||||
sane-backends 1.0.14-cvs 12 April 1999 <B><A HREF="sane-dc25.5.html">sane-dc25(5)</A></B>
|
||||
sane-backends 1.0.15 12 April 1999 <B><A HREF="sane-dc25.5.html">sane-dc25(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -148,7 +148,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
David Mosberger
|
||||
|
||||
sane-backends 1.0.14-cvs 4 Dec 2002 <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>
|
||||
sane-backends 1.0.15 4 Dec 2002 <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -159,7 +159,7 @@
|
|||
|
||||
The backend is derived from <B>sane-hp</B> by David Mosberger
|
||||
|
||||
sane-backends 1.0.14-cvs 13 May 1998 <B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B>
|
||||
sane-backends 1.0.15 13 May 1998 <B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -284,7 +284,7 @@
|
|||
The package is actively maintained by Karl Heinz Kremer (khk@khk.net).
|
||||
The software is based on work by Christian Bucher and Kazuhiro Sasayama
|
||||
|
||||
sane-backends 1.0.14-cvs 27-Dec-2000 <B><A HREF="sane-epson.5.html">sane-epson(5)</A></B>
|
||||
sane-backends 1.0.15 27-Dec-2000 <B><A HREF="sane-epson.5.html">sane-epson(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@
|
|||
|
||||
</PRE>
|
||||
<H2>SYNOPSIS</H2><PRE>
|
||||
<B>sane-find-scanner</B> [<B>-h</B>|<B>-?</B>] [<B>-v</B>] [<B>-q</B>] [<B>-p</B>] [<B>-f</B>] [<I>devname</I>]
|
||||
<B>sane-find-scanner</B> [<B>-h</B>|<B>-?</B>] [<B>-v</B>] [<B>-q</B>] [<B>-p</B>] [<B>-f</B>] [<B>-F</B> <I>filename</I>] [<I>devname</I>]
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -69,14 +69,22 @@
|
|||
devices. That's useful if <B>sane-find-scanner</B> is wrong in
|
||||
determing the device type.
|
||||
|
||||
<B>devname</B> Test device file "devname". No other devices are checked if
|
||||
<B>-F</B> <B>filename</B>
|
||||
filename is a file that contains USB descriptors in the format
|
||||
of /proc/bus/usb/devices as used by Linux. <B>sane-find-scanner</B>
|
||||
tries to identify the chipset(s) of all USB scanners found in
|
||||
such a file. This option is useful for developers when the out-
|
||||
put of "cat /proc/bus/usb/devices" is avaliable but the scanner
|
||||
itsself isn't.
|
||||
|
||||
<B>devname</B> Test device file "devname". No other devices are checked if
|
||||
devname is given.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>EXAMPLE</H2><PRE>
|
||||
<B>sane-find-scanner</B> <B>-v</B>
|
||||
Check all SCSI and USB devices for available scanners and print a line
|
||||
Check all SCSI and USB devices for available scanners and print a line
|
||||
for every device file.
|
||||
|
||||
<B>sane-find-scanner</B> <B>/dev/scanner</B>
|
||||
|
|
@ -88,7 +96,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>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>,
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>,
|
||||
<B><A HREF="xsane.1.html">xsane(1)</A></B>, <B>sane-"backendname"</B>(5)
|
||||
|
||||
|
||||
|
|
@ -99,21 +107,20 @@
|
|||
|
||||
</PRE>
|
||||
<H2>SUPPORTED PLATFORMS</H2><PRE>
|
||||
USB support is limited to Linux (kernel, libusb), FreeBSD (kernel,
|
||||
libusb), NetBSD (libusb), OpenBSD (kernel, libusb). Detecting the ven-
|
||||
USB support is limited to Linux (kernel, libusb), FreeBSD (kernel,
|
||||
libusb), NetBSD (libusb), OpenBSD (kernel, libusb). Detecting the ven-
|
||||
dor and device ids only works with Linux or libusb.
|
||||
|
||||
SCSI support is available on Irix, EMX, Linux, Next, AIX, Solaris,
|
||||
SCSI support is available on Irix, EMX, Linux, Next, AIX, Solaris,
|
||||
FreeBSD, NetBSD, OpenBSD, and HP-UX.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>BUGS</H2><PRE>
|
||||
No support for most parallel port scanners yet.
|
||||
Detection of USB chipsets is limited to GrandTech 6801 and 6816, Mustek
|
||||
chips and National Semiconductor lm983x chips.
|
||||
Detection of USB chipsets is limited to a few chipsets.
|
||||
|
||||
sane-backends 1.0.14-cvs 18 Jul 2003 <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>
|
||||
sane-backends 1.0.15 4 Oct 2004 <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -157,7 +157,7 @@
|
|||
them yet. I don't know if the ScanPartner 15C still works, because I'm
|
||||
not able to test it. 3091/3092 don't support halftone
|
||||
|
||||
sane-backends 1.0.14-cvs 17 Apr 2002 <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>
|
||||
sane-backends 1.0.15 17 Apr 2002 <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -131,7 +131,7 @@
|
|||
be subscribed to the list, otherwise your mail won't be sent to the
|
||||
subscribers.
|
||||
|
||||
sane-backends 1.0.14-cvs 04 September 2001 <B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>
|
||||
sane-backends 1.0.15 04 September 2001 <B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -32,6 +32,7 @@
|
|||
Genius Colorpage Vivid4
|
||||
Genius Colorpage Vivid4x
|
||||
Genius Colorpage Vivid4xe
|
||||
Genius Colorpage Vivid 1200 xe
|
||||
Googlegear 2000
|
||||
Lexmark X70
|
||||
Lexmark X73
|
||||
|
|
@ -47,8 +48,11 @@
|
|||
Mustek BearPaw 2400 TA (Plus)
|
||||
Mustek BearPaw 2448 CS Plus
|
||||
Mustek BearPaw 2448 TA Plus
|
||||
Mustek Plug-n-Scan 2400 M
|
||||
Plug-n-Scan 2400 MT
|
||||
Mustek ScanExpress A3 USB
|
||||
Mustek ScanExpress 1200 UB Plus
|
||||
Mustek ScanExpress 1248 UB
|
||||
Mustek ScanExpress 2400 USB
|
||||
Mustek ScanMagic 1200 UB Plus
|
||||
Packard Bell Diamond 1200 (Plus)
|
||||
|
|
@ -61,6 +65,7 @@
|
|||
RevScan 19200i
|
||||
Trust Compact Scan USB 19200
|
||||
Trust Flat Scan USB 19200
|
||||
Trust 240TH Easy Webscan Gold
|
||||
|
||||
More details can be found on the gt68xx backend homepage
|
||||
<I>http://www.meier-geinitz.de/sane/gt68xx/</I>.
|
||||
|
|
@ -79,82 +84,87 @@
|
|||
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 gt68xx backend but has
|
||||
a GT-6801 or GT-6816 chipset, you can try to add it to the backend.
|
||||
Have a look at the following web page: <I>http://www.meier-</I>
|
||||
<I>geinitz.de/sane/gt68xx-backend/adding.html</I>
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>KERNEL ISSUES</H2><PRE>
|
||||
If libusb-0.1.6 or later is installed, this section can be skipped. The
|
||||
scanner should be found by sane-find-scanner without further actions.
|
||||
For setting permissions and general USB information looks at
|
||||
scanner should be found by sane-find-scanner without further actions.
|
||||
For setting permissions and general USB information looks at
|
||||
<B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>.
|
||||
|
||||
The scanners based on the GT-6816 (Mustek BearPaw TA and BearPaw Plus
|
||||
models, the Packard Bell and the Lexmark scanner) need a Linux kernel
|
||||
2.4.12 or newer. Recent 2.2 kernels may also work, but I haven't
|
||||
tested them. Older kernels or other operating systems won't work. Use
|
||||
The scanners based on the GT-6816 (Mustek BearPaw TA and BearPaw Plus
|
||||
models, the Packard Bell and the Lexmark scanner) need a Linux kernel
|
||||
2.4.12 or newer. Recent 2.2 kernels may also work, but I haven't
|
||||
tested them. Older kernels or other operating systems won't work. Use
|
||||
libusb instead.
|
||||
|
||||
The scanners based on the GT-6801 (all other scanners) need Linux ker-
|
||||
The scanners based on the GT-6801 (all other scanners) need Linux ker-
|
||||
nel 2.4.21 or newer. Older kernels will not work.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>FIRMWARE FILE</H2><PRE>
|
||||
You need a firmware file for your scanner. That's a small file contain-
|
||||
ing software that will be uploaded to the scanner's memory. It's usu-
|
||||
ally named *.usb, e.g. <I>PS1fw.usb</I>. It comes on the installation CD
|
||||
that was provided by the manufacturer, but it may be packaged together
|
||||
ing software that will be uploaded to the scanner's memory. It's usu-
|
||||
ally named *.usb, e.g. <I>PS1fw.usb</I>. It comes on the installation CD
|
||||
that was provided by the manufacturer, but it may be packaged together
|
||||
with the installation program in an .exe file. For Mustek scanners, the
|
||||
file can be dowloaded from the gt68xx backend homepage. For other scan-
|
||||
ners, check the CD for .usb files. If everything else fails, you must
|
||||
install the Windows driver and get the firmware from there (usually in
|
||||
the <I>windows/system</I> or <I>system32</I> directories). Put that firmware file
|
||||
into <I>/usr/local/share/sane/gt68xx/</I>. Make sure that it's readable by
|
||||
ners, check the CD for .usb files. If everything else fails, you must
|
||||
install the Windows driver and get the firmware from there (usually in
|
||||
the <I>windows/system</I> or <I>system32</I> directories). Put that firmware file
|
||||
into <I>/usr/local/share/sane/gt68xx/</I>. Make sure that it's readable by
|
||||
everyone.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONFIGURATION</H2><PRE>
|
||||
The contents of the <I>gt68xx.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>gt68xx.conf</I>.
|
||||
"vendor_id" and "product_id" are hexadecimal numbers that identfy the
|
||||
The contents of the <I>gt68xx.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>gt68xx.conf</I>.
|
||||
"vendor_id" and "product_id" are hexadecimal numbers that identfy the
|
||||
scanner.
|
||||
|
||||
The <B>override</B>, <B>firmware</B>, <B>vendor</B>, <B>model</B>, and <B>afe</B> options must be placed
|
||||
The <B>override</B>, <B>firmware</B>, <B>vendor</B>, <B>model</B>, and <B>afe</B> options must be placed
|
||||
after the <B>usb</B> line they refer to.
|
||||
|
||||
Option <B>override</B> is used to override the default model parameters.
|
||||
Option <B>override</B> is used to override the default model parameters.
|
||||
That's necessary for some scanners that use the same vendor/product ids
|
||||
but are different. For these scanners there are already commented out
|
||||
override lines in the configuration file. <B>override</B> <B>mustek-scanex-</B>
|
||||
<B>press-1200-ub-plus</B> is necessary for the Mustek Scanexpress 1200 UB
|
||||
but are different. For these scanners there are already commented out
|
||||
override lines in the configuration file. <B>override</B> <B>mustek-scanex-</B>
|
||||
<B>press-1200-ub-plus</B> is necessary for the Mustek Scanexpress 1200 UB
|
||||
Plus, the Medion/Lifetec/Tevion LT 9452, and the Trust Compact Scan USB
|
||||
19200. <B>override</B> <B>artec-ultima-2000</B> is used for the Artec Ultima 2000,
|
||||
the Boeder SmartScan Slim Edition, the Medion/ Lifetec/ Tevion/ Cytron
|
||||
MD/LT 9385, the Medion/ Lifetec/ Tevion MD 9458, and the Trust Flat
|
||||
Scan USB 19200. <B>override</B> <B>mustek-bearpaw-2400-cu</B> is necessary for the
|
||||
Mustek BearPaw 2400 CU and the Fujitsu 1200CUS. The <B>override</B> option
|
||||
19200. <B>override</B> <B>artec-ultima-2000</B> is used for the Artec Ultima 2000,
|
||||
the Boeder SmartScan Slim Edition, the Medion/ Lifetec/ Tevion/ Cytron
|
||||
MD/LT 9385, the Medion/ Lifetec/ Tevion MD 9458, and the Trust Flat
|
||||
Scan USB 19200. <B>override</B> <B>mustek-bearpaw-2400-cu</B> is necessary for the
|
||||
Mustek BearPaw 2400 CU and the Fujitsu 1200CUS. The <B>override</B> option
|
||||
must be the first one after the <B>usb</B> line.
|
||||
|
||||
Option <B>firmware</B> selects the name and path of the firmware file. It's
|
||||
only necessary if the default (or override) doesn't work. The default
|
||||
firmware directory is <I>/usr/local/share/sane/gt68xx/</I>. You may need to
|
||||
create this directory. If you want to place the firmware files at a
|
||||
Option <B>firmware</B> selects the name and path of the firmware file. It's
|
||||
only necessary if the default (or override) doesn't work. The default
|
||||
firmware directory is <I>/usr/local/share/sane/gt68xx/</I>. You may need to
|
||||
create this directory. If you want to place the firmware files at a
|
||||
different path, use a <B>firmware</B> line.
|
||||
|
||||
The <B>vendor</B> and <B>model</B> options are not absolutely necessary but for con-
|
||||
venience. Quite a lot of scanners from different manufacturers share
|
||||
The <B>vendor</B> and <B>model</B> options are not absolutely necessary but for con-
|
||||
venience. Quite a lot of scanners from different manufacturers share
|
||||
the same vendor/product ids so you can set the "correct" name here.
|
||||
|
||||
The <B>afe</B> option allows to set custom offset and gain values for the Ana-
|
||||
log FrontEnd of the scanner. This option can be either used to select
|
||||
the AFE values if automatic coarse calibration is disabled, or to make
|
||||
log FrontEnd of the scanner. This option can be either used to select
|
||||
the AFE values if automatic coarse calibration is disabled, or to make
|
||||
automatic coarse calibration faster. For the latter usage, enable debug
|
||||
level 3 (see below), scan an image and look for debug line string with
|
||||
"afe". Copy this line to <I>gt68xx.conf</I>. The option has six parameters:
|
||||
red offset, red gain, green offset, green gain, blue offset, and blue
|
||||
level 3 (see below), scan an image and look for debug line string with
|
||||
"afe". Copy this line to <I>gt68xx.conf</I>. The option has six parameters:
|
||||
red offset, red gain, green offset, green gain, blue offset, and blue
|
||||
gain.
|
||||
|
||||
A sample configuration file is shown below:
|
||||
|
|
@ -170,7 +180,7 @@
|
|||
</PRE>
|
||||
<H2>FILES</H2><PRE>
|
||||
<I>/usr/local/etc/sane.d/gt68xx.conf</I>
|
||||
The backend configuration file (see also description of
|
||||
The backend configuration file (see also description of
|
||||
<B>SANE_CONFIG_DIR</B> below).
|
||||
|
||||
<I>/usr/local/lib/sane/libsane-gt68xx.a</I>
|
||||
|
|
@ -186,22 +196,22 @@
|
|||
<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
|
||||
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
|
||||
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
|
||||
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
|
||||
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_GT68XX</B>
|
||||
If the library was compiled with debug support enabled, this
|
||||
environment variable controls the debug level for this backend.
|
||||
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
|
||||
debug level is set to 1 or higher, some debug options become
|
||||
available that are normally hidden. Handle them with care.
|
||||
|
||||
Example: export SANE_DEBUG_GT68XX=4
|
||||
|
|
@ -209,41 +219,40 @@
|
|||
|
||||
</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>, <B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B> <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>,
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B> <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>,
|
||||
<B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>, <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(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>
|
||||
<I>/usr/local/doc/sane-1.0.14-cvs/gt68xx/gt68xx.CHANGES</I>
|
||||
<I>/usr/local/doc/sane-1.0.15/gt68xx/gt68xx.CHANGES</I>
|
||||
<I>http://www.meier-geinitz.de/sane/gt68xx</I>
|
||||
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>AUTHOR</H2><PRE>
|
||||
Henning Meier-Geinitz <henning@meier-geinitz.de>
|
||||
The original gt68xx driver was written by Sergey Vlasov, Andreas
|
||||
Nowack, and David Stevenson. Thanks for sending patches and answering
|
||||
The original gt68xx driver was written by Sergey Vlasov, Andreas
|
||||
Nowack, and David Stevenson. Thanks for sending patches and answering
|
||||
questions to them and all the other contributors.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>BUGS</H2><PRE>
|
||||
Currently scanning seems to only work reliably under Linux. With
|
||||
FreeBSD, NetBSD and OpenBSD scanning works only once. Then the scanner
|
||||
Currently scanning seems to only work reliably under Linux. With
|
||||
FreeBSD, NetBSD and OpenBSD scanning works only once. Then the scanner
|
||||
isn't detected anymore and has to be replugged.
|
||||
|
||||
The first few lines of the image are garbage for the 2400 TA Plus.
|
||||
|
||||
Interpolation should be used instead of just copying data, when the X-
|
||||
Interpolation should be used instead of just copying data, when the X-
|
||||
and Y-resolution differ.
|
||||
|
||||
Support for buttons is missing.
|
||||
|
||||
More detailed bug information is available at the gt68xx backend home-
|
||||
More detailed bug information is available at the gt68xx backend home-
|
||||
page <I>http://www.meier-geinitz.de/sane/gt68xx</I>. Please contact me if you
|
||||
find a bug or missing feature: <henning@meier-geinitz.de>. Please send
|
||||
a debug log if your scanner isn't detected correctly (see
|
||||
find a bug or missing feature: <henning@meier-geinitz.de>. Please send
|
||||
a debug log if your scanner isn't detected correctly (see
|
||||
SANE_DEBUG_GT68XX above).
|
||||
|
||||
sane-backends 1.0.14-cvs 4 Apr 2004 <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>
|
||||
sane-backends 1.0.15 2 Oct 2004 <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -255,7 +255,7 @@
|
|||
The sane-hp backend was written by Geoffrey T. Dairiki. HP PhotoSmart
|
||||
PhotoScanner support by Peter Kirchgessner.
|
||||
|
||||
sane-backends 1.0.14-cvs 27 Mar 2004 <B><A HREF="sane-hp.5.html">sane-hp(5)</A></B>
|
||||
sane-backends 1.0.15 27 Mar 2004 <B><A HREF="sane-hp.5.html">sane-hp(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -110,7 +110,7 @@
|
|||
other operating systems and especially on big-endian platforms. The
|
||||
scanner may get wrong data.
|
||||
|
||||
sane-backends 1.0.14-cvs 17 Apr 2003 <B><A HREF="sane-hp5400.5.html">sane-hp5400(5)</A></B>
|
||||
sane-backends 1.0.15 17 Apr 2003 <B><A HREF="sane-hp5400.5.html">sane-hp5400(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -111,7 +111,7 @@
|
|||
Max Vorobiev
|
||||
Man page mostly based on canon.man
|
||||
|
||||
sane-backends 1.0.14-cvs 24 Feb 2002 <B><A HREF="sane-hpsj5s.5.html">sane-hpsj5s(5)</A></B>
|
||||
sane-backends 1.0.15 24 Feb 2002 <B><A HREF="sane-hpsj5s.5.html">sane-hpsj5s(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -94,7 +94,7 @@
|
|||
mf <massifr@tiscalinet.it>
|
||||
Maintained by Henning Meier-Geinitz <henning@meier-geinitz.de>
|
||||
|
||||
sane-backends 1.0.14-cvs 15 Apr 2003 <B><A HREF="sane-ibm.5.html">sane-ibm(5)</A></B>
|
||||
sane-backends 1.0.15 15 Apr 2003 <B><A HREF="sane-ibm.5.html">sane-ibm(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -134,7 +134,7 @@
|
|||
The package is actively maintained by Frank Zago.
|
||||
http://www.zago.net/sane/#leo
|
||||
|
||||
sane-backends 1.0.14-cvs 16 April 2002 <B><A HREF="sane-leo.5.html">sane-leo(5)</A></B>
|
||||
sane-backends 1.0.15 16 April 2002 <B><A HREF="sane-leo.5.html">sane-leo(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -127,7 +127,7 @@
|
|||
More detailed bug information is available at the MA-1509 backend home-
|
||||
page <I>http://www.meier-geinitz.de/sane/ma1509-backend/</I>.
|
||||
|
||||
sane-backends 1.0.14-cvs 24 Feb 2003 <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>
|
||||
sane-backends 1.0.15 24 Feb 2003 <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -184,7 +184,7 @@
|
|||
The package is actively maintained by Frank Zago.
|
||||
http://www.zago.net/sane/#matsushita
|
||||
|
||||
sane-backends 1.0.14-cvs February 11th, 2004 <B><A HREF="sane-matsushita.5.html">sane-matsushita(5)</A></B>
|
||||
sane-backends 1.0.15 February 11th, 2004 <B><A HREF="sane-matsushita.5.html">sane-matsushita(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -166,7 +166,7 @@
|
|||
ers mailing list. Have a look at http://www.sane-project.org/mail-
|
||||
ing-lists.html concerning subscription to sane-devel.
|
||||
|
||||
sane-backends 1.0.14-cvs February 8, 2000 <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B>
|
||||
sane-backends 1.0.15 February 8, 2000 <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -283,7 +283,7 @@
|
|||
Karsten Festag karsten.festag@gmx.de
|
||||
|
||||
|
||||
sane-backends 1.0.14-cvs 28 Jan 2002 <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B>
|
||||
sane-backends 1.0.15 28 Jan 2002 <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -70,7 +70,7 @@
|
|||
noises and the scan mechanism may be damaged. Thus, if you hear such a
|
||||
noise, IMMEDIATELY turn off the scanner. This shouldn't happen if your
|
||||
scanner is in the list of known scanners. There is more information in
|
||||
the <I>/usr/local/doc/sane-1.0.14-cvs/PROBLEMS</I> file.
|
||||
the <I>/usr/local/doc/sane-1.0.15/PROBLEMS</I> file.
|
||||
|
||||
If you own a Mustek (or Trust) scanner other than the ones listed above
|
||||
that works with this backend, please let us know by sending the scan-
|
||||
|
|
@ -245,7 +245,7 @@
|
|||
access the I/O ports. Thus, either make frontends such as <B><A HREF="scanimage.1.html">scanimage(1)</A></B>
|
||||
and <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B> setuid root (generally not recommended for safety
|
||||
reasons) or, alternatively, access this backend through the network
|
||||
daemon <B><A HREF="saned.1.html">saned(1)</A></B>.
|
||||
daemon <B><A HREF="saned.8.html">saned(8)</A></B>.
|
||||
|
||||
If the Mustek backend blocks while sending the inqiury command to the
|
||||
scanner, add the option <B>force-wait</B> to <I>mustek.conf</I>.
|
||||
|
|
@ -311,7 +311,7 @@
|
|||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B>sane-</B>
|
||||
<B><A HREF="gt68xx.5.html">gt68xx(5)</A></B>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>
|
||||
<I>/usr/local/doc/sane-1.0.14-cvs/mustek/mustek.CHANGES</I>
|
||||
<I>/usr/local/doc/sane-1.0.15/mustek/mustek.CHANGES</I>
|
||||
<I>http://www.meier-geinitz.de/sane/mustek-backend/</I>
|
||||
|
||||
|
||||
|
|
@ -334,7 +334,7 @@
|
|||
More detailed bug information is available at the Mustek backend home-
|
||||
page: <I>http://www.meier-geinitz.de/sane/mustek-backend/</I>.
|
||||
|
||||
sane-backends 1.0.14-cvs 25 Dec 2002 <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>
|
||||
sane-backends 1.0.15 25 Dec 2002 <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -83,7 +83,7 @@
|
|||
Some scanners work faster when <B>EPP/ECP</B> is enabled in the BIOS.
|
||||
|
||||
Note that the backend needs to run as root. To allow user access to the
|
||||
scanner run the backend through the network interface (See <B><A HREF="saned.1.html">saned(1)</A></B> and
|
||||
scanner run the backend through the network interface (See <B><A HREF="saned.8.html">saned(8)</A></B> and
|
||||
<B><A HREF="sane-net.5.html">sane-net(5)</A></B>). Note also that the backend <I>does</I> <I>not</I> support <I>parport</I> <I>shar-</I>
|
||||
<I>ing</I> <I>,</I> i.e. if you try printing while scanning, your computer may crash.
|
||||
This backend also conflicts with the <I>sane-musteka4s2</I> backend. You can
|
||||
|
|
@ -338,7 +338,7 @@
|
|||
|
||||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-net.5.html">sane-net(5)</A></B>, <B><A HREF="saned.1.html">saned(1)</A></B>, <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-net.5.html">sane-net(5)</A></B>, <B><A HREF="saned.8.html">saned(8)</A></B>, <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>
|
||||
|
||||
For latest bug fixes and information see
|
||||
<I>http://www.penguin-breeder.org/sane/mustek</I><B>_</B><I>pp/</I>
|
||||
|
|
|
|||
|
|
@ -149,8 +149,8 @@
|
|||
<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>, <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>sane-plus-</B>
|
||||
<B><A HREF="tek.5.html">tek(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>, <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>
|
||||
<I>/usr/local/doc/sane-1.0.14-cvs/mustek</I><B>_</B><I>usb/mustek</I><B>_</B><I>usb.CHANGES</I>,
|
||||
<I>/usr/local/doc/sane-1.0.14-cvs/mustek</I><B>_</B><I>usb/mustek</I><B>_</B><I>usb.TODO</I>
|
||||
<I>/usr/local/doc/sane-1.0.15/mustek</I><B>_</B><I>usb/mustek</I><B>_</B><I>usb.CHANGES</I>,
|
||||
<I>/usr/local/doc/sane-1.0.15/mustek</I><B>_</B><I>usb/mustek</I><B>_</B><I>usb.TODO</I>
|
||||
<I>http://www.meier-geinitz.de/sane/mustek</I><B>_</B><I>usb-backend/</I>
|
||||
|
||||
|
||||
|
|
@ -176,7 +176,7 @@
|
|||
More detailed bug information is available at the Mustek backend home-
|
||||
page <I>http://www.meier-geinitz.de/sane/mustek</I><B>_</B><I>usb-backend/</I>.
|
||||
|
||||
sane-backends 1.0.14-cvs 3 Mar 2004 <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>
|
||||
sane-backends 1.0.15 3 Mar 2004 <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@
|
|||
<H2>AUTHORS</H2><PRE>
|
||||
Kazuya Fukuda
|
||||
|
||||
sane-backends 1.0.14-cvs 17 Feb 2000 <B><A HREF="sane-nec.5.html">sane-nec(5)</A></B>
|
||||
sane-backends 1.0.15 17 Feb 2000 <B><A HREF="sane-nec.5.html">sane-nec(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -67,10 +67,10 @@
|
|||
<I>ner.univ.edu</I> are contacted in addition to the hosts listed above.
|
||||
|
||||
For this backend to function properly, it is also necessary to define
|
||||
the <B>sane</B> service in <I>/etc/services</I>. The <B>sane</B> service should be defined
|
||||
using a line of the following form:
|
||||
the <B>sane-port</B> service in <I>/etc/services</I>. The <B>sane</B> service should be
|
||||
defined using a line of the following form:
|
||||
|
||||
sane 6566/tcp # SANE network scanner daemon
|
||||
sane-port 6566/tcp # SANE network scanner daemon
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -122,7 +122,7 @@
|
|||
|
||||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="saned.1.html">saned(1)</A></B>, <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="saned.8.html">saned(8)</A></B>, <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>
|
||||
|
||||
<I>http://www.penguin-breeder.org/?page=sane-net</I>
|
||||
|
||||
|
|
@ -131,7 +131,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
David Mosberger and Andreas Beck
|
||||
|
||||
sane-backends 1.0.14-cvs 8 Oct 2002 <B><A HREF="sane-net.5.html">sane-net(5)</A></B>
|
||||
sane-backends 1.0.15 8 Oct 2002 <B><A HREF="sane-net.5.html">sane-net(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -49,11 +49,20 @@
|
|||
that support dynamic loading).
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CAVEATS</H2><PRE>
|
||||
If you use a
|
||||
Hewlett-Packard Scanjet 3400c or
|
||||
Hewlett-Packard Scanjet 4300c
|
||||
together with Linux kernel <B>2.6</B> , kernel version <B>2.6.8</B> or newer is nec-
|
||||
essary.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_DEBUG_NIASH</B>
|
||||
If the library was compiled with debug support enabled, this
|
||||
environment variable controls the debug level for this backend.
|
||||
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.
|
||||
|
||||
Example: export SANE_DEBUG_NIASH=255
|
||||
|
|
@ -69,7 +78,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
Bertrik Sikken <bertrik@zonnet.nl>
|
||||
|
||||
sane-backends 1.0.14-cvs 29 July 2004 <B><A HREF="sane-niash.5.html">sane-niash(5)</A></B>
|
||||
sane-backends 1.0.15 29 July 2004 <B><A HREF="sane-niash.5.html">sane-niash(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -66,7 +66,7 @@
|
|||
Please send any information and bug-reports to:
|
||||
<B>Simon</B> <B>Munton</B> <B><simon@munton.demon.co.uk></B>
|
||||
|
||||
sane-backends 1.0.14-cvs 7 Sept 2000 <B><A HREF="sane-pie.5.html">sane-pie(5)</A></B>
|
||||
sane-backends 1.0.15 7 Sept 2000 <B><A HREF="sane-pie.5.html">sane-pie(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -135,7 +135,7 @@
|
|||
No testing has been done on three-pass or handheld scanners, or with
|
||||
Automatic Document Feeder support.
|
||||
|
||||
sane-backends 1.0.14-cvs 13 May 1998 <B><A HREF="sane-pint.5.html">sane-pint(5)</A></B>
|
||||
sane-backends 1.0.15 13 May 1998 <B><A HREF="sane-pint.5.html">sane-pint(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -75,6 +75,7 @@
|
|||
----------------------------------------------------------
|
||||
USB Model: ASIC: Properties: Prod-ID
|
||||
----------------------------------------------------------
|
||||
UMAX 3400 LM9832 600x1200dpi 42bit 512Kb 0x0050
|
||||
UMAX 3400/3450 LM9832 600x1200dpi 42bit 512Kb 0x0060
|
||||
UMAX 5400 LM9832 1200x2400dpi 42bit 512Kb 0x0160
|
||||
|
||||
|
|
@ -113,13 +114,15 @@
|
|||
are supported by this backend. Older versions of the U12, the UT12, the
|
||||
U1212 and U1248 (GrandTech chipset) are not supported.
|
||||
|
||||
Model Chipset backend
|
||||
---------------------------
|
||||
U1248 GrandTech gt68xx
|
||||
UT16B GrandTech gt68xx
|
||||
U12 P98003 u12
|
||||
UT12 P98003 u12
|
||||
1212U P98003 u21
|
||||
Model Chipset backend
|
||||
------------------------------------
|
||||
U1248 GrandTech gt68xx
|
||||
UT16B GrandTech gt68xx
|
||||
OpticSlim 1200 GrandTech gt68xx
|
||||
OpticSlim 2400 GrandTech gt68xx
|
||||
U12 P98003 u12
|
||||
UT12 P98003 u12
|
||||
1212U P98003 u12
|
||||
For a more complete and up to date list see: <B>http://www.sane-</B>
|
||||
<B>project.org/sane-supported-devices.html</B>
|
||||
|
||||
|
|
@ -134,19 +137,22 @@
|
|||
|
||||
<I>device</I> <I>/dev/usbscanner</I>
|
||||
|
||||
<I>[usb]</I> tells the backend, that the following devicename (here <I>/dev/usb-</I>
|
||||
<I>scanner</I> ) has to be interpreted as USB scanner device. If vendor- and
|
||||
product-id has not been specified, the backend tries to detect this by
|
||||
its own. If device ist set to <I>auto</I>
|
||||
then the next matching device is used.
|
||||
<I>[usb]</I> tells the backend, that the following devicename (here
|
||||
<I>/dev/usbscanner</I> ) has to be interpreted as USB scanner device. If ven-
|
||||
dor- and product-id has not been specified, the backend tries to detect
|
||||
this by its own. If device is set to <I>auto</I> then the next matching device
|
||||
is used.
|
||||
The following options can be used for a default setup of your device.
|
||||
Most of them are also availaby through the frontend.
|
||||
|
||||
<B>The</B> <B>Options:</B>
|
||||
|
||||
option warmup t
|
||||
<I>t</I> specifies the warmup period in seconds
|
||||
<I>t</I> specifies the warmup period in seconds, if set to -1, the
|
||||
automatic warmup function will be used
|
||||
|
||||
option lampOff t
|
||||
<I>t</I> is the time in seconds for switching off the lamps in standby
|
||||
<I>t</I> is the time in seconds for switching off the lamps in standby
|
||||
mode
|
||||
|
||||
option lOffonEnd b
|
||||
|
|
@ -154,7 +160,7 @@
|
|||
lamps off, 0 --> do not change lamp status
|
||||
|
||||
option mov m
|
||||
<I>m</I> is the model override switch. It works only with Mustek
|
||||
<I>m</I> is the model override switch. It works only with Mustek
|
||||
BearPaw devices.
|
||||
m/PID | 0x1000 | 0x1001
|
||||
------+--------------+--------------
|
||||
|
|
@ -162,33 +168,34 @@
|
|||
1 | no function | BearPaw 1200
|
||||
|
||||
option invertNegatives b
|
||||
<I>b</I> 0 --> do not invert the picture during negativ scans, 1 -->
|
||||
<I>b</I> 0 --> do not invert the picture during negativ scans, 1 -->
|
||||
invert picture
|
||||
|
||||
option cacheCalData b
|
||||
<I>b</I> 0 --> do not save coarse calibration results, 1 --> save
|
||||
<I>b</I> 0 --> do not save coarse calibration results, 1 --> save
|
||||
results of coarse calibration in ~/.sane/ directory
|
||||
|
||||
option altCalibration b
|
||||
<I>b</I> 0 --> use standard calibration routines, 1 --> use alternate
|
||||
<I>b</I> 0 --> use standard calibration routines, 1 --> use alternate
|
||||
calibration (only non Plustek
|
||||
devices, standard for CIS devices)
|
||||
|
||||
option skipFine b
|
||||
<I>b</I> 0 --> perform fine calibration, 1 --> skip fine calibration
|
||||
<I>b</I> 0 --> perform fine calibration, 1 --> skip fine calibration
|
||||
(only non Plustek devices)
|
||||
|
||||
option skipFineWhite b
|
||||
<I>b</I> 0 --> perform white fine calibration, 1 --> skip white fine
|
||||
<I>b</I> 0 --> perform white fine calibration, 1 --> skip white fine
|
||||
calibration (only non Plustek devices)
|
||||
|
||||
option skipCalibration b
|
||||
<I>b</I> 0 --> perform calibration, 1 --> skip calibration (only non
|
||||
<I>b</I> 0 --> perform calibration, 1 --> skip calibration (only non
|
||||
Plustek devices)
|
||||
|
||||
option enableTPA b
|
||||
<I>b</I> 0 --> default behaviour, specified by the internal tables, 1
|
||||
--> override internal tables and allow TPA mode (EPSON only)
|
||||
<I>b</I> 0 --> default behaviour, specified by the internal tables, 1
|
||||
--> override internal tables and allow TPA mode (EPSON/UMAX
|
||||
only)
|
||||
|
||||
option posOffX x
|
||||
option posOffY y
|
||||
|
|
@ -216,11 +223,14 @@
|
|||
can be adjusted.
|
||||
|
||||
option red_gain r
|
||||
option red_offset ro
|
||||
option green_gain g
|
||||
option green_offset go
|
||||
option blue_gain b
|
||||
<I>r</I> <I>g</I> <I>b</I> These values can be used to adjust the internally detected
|
||||
gain values of the AFE for each channel. The range is between 0
|
||||
and 63.
|
||||
option blue_offset bo
|
||||
<I>r</I> <I>g</I> <I>b</I> <I>ro</I> <I>go</I> <I>bo</I> These values can be used to set the gain and off-
|
||||
set values of the AFE for each channel. The range is between 0
|
||||
and 63. -1 means autocalibration.
|
||||
|
||||
See the plustek.conf file for examples.
|
||||
|
||||
|
|
@ -273,24 +283,22 @@
|
|||
|
||||
</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>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>,
|
||||
<I>/usr/local/doc/sane-1.0.14-cvs/plustek/Plustek-USB.changes</I>
|
||||
<I>http://www.gjaeger.de/scanner/plustek.html</I>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-u12.5.html">sane-u12(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>,
|
||||
<I>/usr/local/doc/sane-1.0.15/plustek/Plustek-USB.changes</I>
|
||||
<I>http://www.gjaeger.de/scanner/plustek/</I>
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONTACT AND BUG-REPORTS</H2><PRE>
|
||||
Please send any information and bug-reports to:
|
||||
<B>Plustek</B> <B>Driver</B> <B>Mailing</B> <B>List</B> <B><plustek@linuxhacker.org></B>
|
||||
or directly to:
|
||||
<B>Gerhard</B> <B>Jaeger</B> <B><gerhard@gjaeger.de></B>
|
||||
<B>SANE</B> <B>Mailing</B> <B>List</B>
|
||||
|
||||
Additional info and hints can be obtained from our
|
||||
Mailing-List archive at:
|
||||
<B>http://www.linuxhacker.org/cgi-bin/ezmlm-cgi/3</B>
|
||||
<B>http://www.sane-project.org/mailing-lists.html</B>
|
||||
|
||||
or directly from the projects' homepage at:
|
||||
<B>http://www.gjaeger.de/scanner/plustek.html</B>
|
||||
<B>http://www.gjaeger.de/scanner/plustek/</B>
|
||||
|
||||
To obtain debug messages from the backend, please set the environment-
|
||||
variable <I>SANE</I><B>_</B><I>DEBUG</I><B>_</B><I>PLUSTEK</I> before calling your favorite scan-frontend
|
||||
|
|
@ -298,7 +306,7 @@
|
|||
<B>i.e.:</B> <B>export</B> <B>SANE_DEBUG_PLUSTEK=20</B> <B>;</B> <B>xscanimage</B>
|
||||
|
||||
The value controls the verbosity of the backend. Please note, that val-
|
||||
ues greater than 19 force the backend to output raw data files, which
|
||||
ues greater than 24 force the backend to output raw data files, which
|
||||
could be rather large. The ending of these files is ".raw". For prob-
|
||||
lem reports it should be enough the set the verbosity to 13.
|
||||
|
||||
|
|
@ -311,7 +319,8 @@
|
|||
of the CDD-sensor and the stepper motor i.e. you have a
|
||||
600x1200 dpi scanner and you are scanning using 800dpi,
|
||||
so scaling is necesary, because the sensor only delivers
|
||||
600dpi but the motor is capable to perform 1200dpi steps.
|
||||
600dpi but the motor is capable to perform 1200dpi
|
||||
steps.
|
||||
* Plusteks' model policy is somewhat inconsistent. This
|
||||
means, they sell technical different devices under the
|
||||
same product name. Therefore it is possible that some
|
||||
|
|
@ -320,7 +329,7 @@
|
|||
the one your device has.
|
||||
* Negative/Slide scanning quality is poor.
|
||||
|
||||
sane-backends 1.0.14-cvs 22 Mar 2004 <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
|
||||
sane-backends 1.0.15 02 July 2004 <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -185,28 +185,25 @@
|
|||
source-files of this sane-backend installation. Unpack this tar-ball
|
||||
and go to the directory:
|
||||
<I>sane-backends/doc/plustek</I>
|
||||
Within this directory, you should find a file called:
|
||||
<I>Makefile.module</I>
|
||||
Within this directory, you should find a script called:
|
||||
<I>MakeModule.sh</I>
|
||||
Now if your Linux kernelsources are installed correctly, it should be
|
||||
possible to build, install and load the module <B>pt_drv.</B> Try
|
||||
<I>make</I> <I>-f</I> <I>Makefile.module</I>
|
||||
to obtain a help text, about the targets, the makefile supports.
|
||||
Use
|
||||
<I>make</I> <I>-f</I> <I>Makefile.module</I> <I>all</I>
|
||||
to build the module. Use
|
||||
<I>make</I> <I>-f</I> <I>Makefile.module</I> <I>install</I>
|
||||
to install the module. Use
|
||||
<I>make</I> <I>-f</I> <I>Makefile.module</I> <I>load</I>
|
||||
to load the module.
|
||||
<B>Note:</B> <B>Installing</B> <B>and</B> <B>loading</B> <B>the</B> <B>can</B> <B>only</B> <B>be</B> <B>done</B> <B>as</B> <B>superuser.</B>
|
||||
possible to build, install and load the module <B>pt_drv.</B> <B>Please</B> <B>note,</B>
|
||||
that the kernelsources need to be configured correctly. Refer to your
|
||||
distributions manual on how this is done. As root user, try
|
||||
<I>./MakeModule.sh</I>
|
||||
the script will try and get all necessary information about your run-
|
||||
ning kernel and will lead you through the whole installation process.
|
||||
<B>Note:</B> <B>Installing</B> <B>and</B> <B>loading</B> <B>the</B> <B>can</B> <B>only</B> <B>be</B> <B>done</B> <B>as</B> superuser.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>KERNEL MODULE SETUP</H2><PRE>
|
||||
The configuration of the kernel module is done by providing some or
|
||||
The configuration of the kernel module is done by providing some or
|
||||
more options found below to the kernel module at load time. This can be
|
||||
done by invoking insmod with the appropriate parameters or appending
|
||||
the options to the file <B>/etc/conf.modules</B>
|
||||
done by invoking insmod with the appropriate parameters or appending
|
||||
the options to the file <B>/etc/modules.conf</B> <B>(kernel</B> <B><</B> <B>2.6.x)</B> or <B>/etc/mod-</B>
|
||||
<B>probe.conf</B> <B>(kernel</B> <B>>=</B> <B>2.6.x)</B>
|
||||
|
||||
<B>The</B> <B>Options:</B>
|
||||
lampoff=lll
|
||||
|
|
@ -274,13 +271,14 @@
|
|||
has been set to EPP-mode. When detecting any other mode such as
|
||||
ECP or PS/2 the driver tries to set to a faster, supported mode.
|
||||
If this fails, it will use the SPP mode, as this mode should
|
||||
work with all Linux supported parallel ports.
|
||||
work with all Linux supported parallel ports. If in doubt, enter
|
||||
your BIOS and set it to any mode except ECP.
|
||||
|
||||
Former Plustek scanner models (4830, 9630) supplied a ISA parallel port
|
||||
adapter card. This card is <B>not</B> supported by the driver.
|
||||
|
||||
The ASIC 96001/3 based models have sometimes trouble with high resolu-
|
||||
tion modes. If you encounter sporadic corrupted images (parts dupli-
|
||||
The ASIC 96001/3 based models have sometimes trouble with high resolu-
|
||||
tion modes. If you encounter sporadic corrupted images (parts dupli-
|
||||
cated or shifted horizontally) kill all other applications before scan-
|
||||
ning and (if sufficient memory available) disable swapping.
|
||||
|
||||
|
|
@ -299,8 +297,11 @@
|
|||
The shared library implementing this backend (present on systems
|
||||
that support dynamic loading).
|
||||
|
||||
<I>/lib/modules/<Kernel-Version>/misc/pt</I><B>_</B><I>drv.o</I>
|
||||
The Linux Kernelmodule.
|
||||
<I>/lib/modules/<Kernel-Version>/kernel/drivers/parport/pt</I><B>_</B><I>drv.o</I>
|
||||
The Linux kernelmodule for kernels < 2.6.x.
|
||||
|
||||
<I>/lib/modules/<Kernel-Version>/kernel/drivers/parport/pt</I><B>_</B><I>drv.ko</I>
|
||||
The Linux kernelmodule for kernels >= 2.6.x.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -308,20 +309,20 @@
|
|||
<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
|
||||
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
|
||||
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
|
||||
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
|
||||
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_PLUSTEK_PP</B>
|
||||
If the library was compiled with debug support enabled, this
|
||||
environment variable controls the debug level for this backend.
|
||||
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.
|
||||
|
||||
Example: export SANE_DEBUG_PLUSTEK_PP=10
|
||||
|
|
@ -330,26 +331,24 @@
|
|||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>,
|
||||
<I>/usr/local/doc/sane-1.0.14-cvs/plustek/Plustek-PARPORT.changes</I>
|
||||
<I>http://www.gjaeger.de/scanner/plustek.html</I>
|
||||
<I>/usr/local/doc/sane-1.0.15/plustek/Plustek-PARPORT.changes</I>
|
||||
<I>http://www.gjaeger.de/scanner/plustek</I><B>_</B><I>pp/</I>
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONTACT AND BUG-REPORTS</H2><PRE>
|
||||
Please send any information and bug-reports to:
|
||||
<B>Plustek</B> <B>Driver</B> <B>Mailing</B> <B>List</B> <B><plustek@linuxhacker.org></B>
|
||||
or directly to:
|
||||
<B>Gerhard</B> <B>Jaeger</B> <B><gerhard@gjaeger.de></B>
|
||||
<B>SANE</B> <B>Mailing</B> <B>List</B>
|
||||
|
||||
Additional info and hints can be obtained from our
|
||||
Mailing-List archive at:
|
||||
<B>http://www.linuxhacker.org/cgi-bin/ezmlm-cgi/3</B>
|
||||
<B>http://www.sane-project.org/mailing-lists.html</B>
|
||||
|
||||
or directly from the projects' homepage at:
|
||||
<B>http://www.gjaeger.de/scanner/plustek.html</B>
|
||||
<B>http://www.gjaeger.de/scanner/plustek_pp/</B>
|
||||
|
||||
To obtain debug messages from the backend, please set the environment-
|
||||
variable <I>SANE</I><B>_</B><I>DEBUG</I><B>_</B><I>PLUSTEK</I><B>_</B><I>PP</I> before calling your favorite scan-fron-
|
||||
To obtain debug messages from the backend, please set the environment-
|
||||
variable <I>SANE</I><B>_</B><I>DEBUG</I><B>_</B><I>PLUSTEK</I><B>_</B><I>PP</I> before calling your favorite scan-fron-
|
||||
tend (i.e. xscanimage).
|
||||
<B>i.e.:</B> <B>export</B> <B>SANE_DEBUG_PLUSTEK_PP=20</B> <B>;</B> <B>xscanimage</B>
|
||||
|
||||
|
|
@ -387,7 +386,7 @@
|
|||
* The scanspeed on 600x1200 dpi models is slow.
|
||||
* The scanquality of the A3I is poor
|
||||
|
||||
sane-backends 1.0.14-cvs 13 Jan 2004 <B><A HREF="sane-plustek_pp.5.html">sane-plustek_pp(5)</A></B>
|
||||
sane-backends 1.0.15 18 June 2004 <B><A HREF="sane-plustek_pp.5.html">sane-plustek_pp(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -74,7 +74,7 @@
|
|||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>
|
||||
|
||||
sane-backends 1.0.14-cvs 22 April 2001 <B><A HREF="sane-pnm.5.html">sane-pnm(5)</A></B>
|
||||
sane-backends 1.0.15 22 April 2001 <B><A HREF="sane-pnm.5.html">sane-pnm(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -109,7 +109,7 @@
|
|||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>
|
||||
|
||||
sane-backends 1.0.14-cvs 25 October 1997 <B><A HREF="sane-qcam.5.html">sane-qcam(5)</A></B>
|
||||
sane-backends 1.0.15 25 October 1997 <B><A HREF="sane-qcam.5.html">sane-qcam(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -85,7 +85,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
Feico W. Dillema
|
||||
|
||||
sane-backends 1.0.14-cvs 24 Jun 2000 <B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B>
|
||||
sane-backends 1.0.15 24 Jun 2000 <B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -83,7 +83,7 @@
|
|||
Ingo Schneider
|
||||
|
||||
|
||||
sane-backends 1.0.14-cvs 24 Jun 2000 <B><A HREF="sane-s9036.5.html">sane-s9036(5)</A></B>
|
||||
sane-backends 1.0.15 24 Jun 2000 <B><A HREF="sane-s9036.5.html">sane-s9036(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -147,7 +147,7 @@
|
|||
The package is actively maintained by Frank Zago.
|
||||
http://www.zago.net/sane/#sceptre
|
||||
|
||||
sane-backends 1.0.14-cvs April 21st, 2002 <B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B>
|
||||
sane-backends 1.0.15 April 21st, 2002 <B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -303,7 +303,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
David Mosberger
|
||||
|
||||
sane-backends 1.0.14-cvs 28 Oct 2003 <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>
|
||||
sane-backends 1.0.15 28 Oct 2003 <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -366,7 +366,7 @@
|
|||
Parts of this man page are a plain copy of <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B> by David Mos-
|
||||
berger-Tang, Andreas Czechanowski and Andreas Bolsch
|
||||
|
||||
sane-backends 1.0.14-cvs 21 Nov 2000 <B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B>
|
||||
sane-backends 1.0.15 21 Nov 2000 <B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -110,7 +110,7 @@
|
|||
Marian Eichholz (eichholz@computer.org)
|
||||
Glenn Ramsey (glenn@componic.com)
|
||||
|
||||
sane-backends 1.0.14-cvs 10.02.2002 <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B>
|
||||
sane-backends 1.0.15 10.02.2002 <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -114,7 +114,7 @@
|
|||
Man page by Henning Meier-Geinitz (mostly based on the web pages and
|
||||
source code).
|
||||
|
||||
sane-backends 1.0.14-cvs 26 May 2001 <B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B>
|
||||
sane-backends 1.0.15 26 May 2001 <B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -78,7 +78,7 @@
|
|||
working first driver. Watch this space for changes.
|
||||
|
||||
|
||||
sane-backends 1.0.14-cvs 17 Apr 2002 <B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B>
|
||||
sane-backends 1.0.15 17 Apr 2002 <B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -153,7 +153,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
Ingo Wilken <Ingo.Wilken@informatik.uni-oldenburg.de>
|
||||
|
||||
sane-backends 1.0.14-cvs 08 Mar 1999 <B><A HREF="sane-st400.5.html">sane-st400(5)</A></B>
|
||||
sane-backends 1.0.15 08 Mar 1999 <B><A HREF="sane-st400.5.html">sane-st400(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -87,7 +87,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
Roger Wolff
|
||||
|
||||
sane-backends 1.0.14-cvs 24 Jun 2000 <B><A HREF="sane-tamarack.5.html">sane-tamarack(5)</A></B>
|
||||
sane-backends 1.0.15 24 Jun 2000 <B><A HREF="sane-tamarack.5.html">sane-tamarack(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -166,7 +166,7 @@
|
|||
Thanks to Gerard Delafond for the VM4542 support. Thanks to Jean-Yves
|
||||
Simon for the VM3510 support.
|
||||
|
||||
sane-backends 1.0.14-cvs August 30th, 2002 <B><A HREF="sane-teco1.5.html">sane-teco1(5)</A></B>
|
||||
sane-backends 1.0.15 August 30th, 2002 <B><A HREF="sane-teco1.5.html">sane-teco1(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -29,7 +29,7 @@
|
|||
---------------------- -------------- -----------
|
||||
|
||||
Mustek ScanMagic 4830S VM3575 untested
|
||||
Primax Jewel 4800 VM356A basic
|
||||
Primax Jewel 4800 VM356A good
|
||||
Primax Profi 9600 VM6575 basic
|
||||
Primax Profi 19200 VM6586 good
|
||||
Relisys APOLLO Express 3 VM356A basic
|
||||
|
|
@ -39,7 +39,7 @@
|
|||
Relisys AVEC Super 3 VM3575 basic
|
||||
Relisys SCORPIO Pro VM6575 good
|
||||
Relisys SCORPIO Pro-S VM6586 untested
|
||||
Relisys SCORPIO Super 3 VM3575 basic
|
||||
Relisys SCORPIO Super 3 VM3575 good
|
||||
|
||||
For all these scanners, black&white and grayscale mode work well. How-
|
||||
ever, most of them do not support more than a handful of resolutions in
|
||||
|
|
@ -78,54 +78,62 @@
|
|||
Color selects the resolution for a scan. The scanner can do only
|
||||
the resolutions listed.
|
||||
|
||||
All values with ydpi > 300 (300 x 600) or 600 (600 x 1200)
|
||||
result in a wrong proportion for the scan. The proportion can be
|
||||
adjusted with the following command: convert -geometry
|
||||
(dpi/max_xdpi * 100%)x100% max_xdpi is for the vm3575 constant
|
||||
with 300 dpi e.g. 600dpi adjust with: convert -geometry
|
||||
200%x100%
|
||||
|
||||
<B>Geometry</B> <B>options</B>
|
||||
|
||||
<B>-l</B> <B>-t</B> <B>-x</B> <B>-y</B>
|
||||
control the scan area: -l sets the top left x coordinate, -t the
|
||||
top left y coordinate, -x selects the width and -y the height of
|
||||
the scan area. All parameters are specified in millimeters by
|
||||
the scan area. All parameters are specified in millimeters by
|
||||
default.
|
||||
|
||||
<B>Enhancement</B> <B>options</B>
|
||||
|
||||
<B>--custom-gamma</B> <B>(no</B> <B>custom</B> <B>gamma</B> <B>option</B> <B>for</B> <B>the</B> <B>VM3564</B> <B>and</B> <B>VM356A)</B>
|
||||
(color mode only) allows the user to specify a gamma table (see
|
||||
(color mode only) allows the user to specify a gamma table (see
|
||||
the next 3 parameters).
|
||||
|
||||
<B>--red-gamma-table</B>
|
||||
(color mode only) can be used to download a user defined gamma
|
||||
(color mode only) can be used to download a user defined gamma
|
||||
table for the red channel. The table must be 256 bytes long.
|
||||
|
||||
<B>--green-gamma-table</B>
|
||||
(color mode only) can be used to download a user defined gamma
|
||||
(color mode only) can be used to download a user defined gamma
|
||||
table for the green channel. The table must be 256 bytes long.
|
||||
|
||||
<B>--blue-gamma-table</B>
|
||||
(color mode only) can be used to download a user defined gamma
|
||||
(color mode only) can be used to download a user defined gamma
|
||||
table for the blue channel. The table must be 256 bytes long.
|
||||
|
||||
<B>--white-level-r</B>
|
||||
(VM3564, VM356A, VM3575 only) Selects what red radiance level
|
||||
should be considered "white", when scanning some sheets by
|
||||
changing the calibration value loaded into the scanner. Scale
|
||||
0..64 in steps of 1.
|
||||
(VM3564, VM356A, VM3575 and VM6575 only) Selects what red radi-
|
||||
ance level should be considered "white", when scanning some
|
||||
sheets by changing the calibration value loaded into the scan-
|
||||
ner. Scale 0..64 in steps of 1.
|
||||
|
||||
<B>--white-level-g</B>
|
||||
(VM3564, VM356A, VM3575 only) Selects what green radiance level
|
||||
should be considered "white", when scanning some sheets by
|
||||
changing the calibration i value loaded into the scanner. Scale
|
||||
0..64 in steps of 1.
|
||||
(VM3564, VM356A, VM3575 and VM6575 only) Selects what green
|
||||
radiance level should be considered "white", when scanning some
|
||||
sheets by changing the calibration i value loaded into the scan-
|
||||
ner. Scale 0..64 in steps of 1.
|
||||
|
||||
<B>--white-level-g</B>
|
||||
(VM3564, VM356A, VM3575 only) Selects what blue radiance level
|
||||
should be considered "white", when scanning some sheets by
|
||||
changing the calibration value loaded into the scanner. Scale
|
||||
0..64 in steps of 1.
|
||||
<B>--white-level-b</B>
|
||||
(VM3564, VM356A, VM3575 and VM6575 only) Selects what blue radi-
|
||||
ance level should be considered "white", when scanning some
|
||||
sheets by changing the calibration value loaded into the scan-
|
||||
ner. Scale 0..64 in steps of 1.
|
||||
|
||||
<B>--preview</B>
|
||||
requests a preview scan. The resolution used for that scan is 22
|
||||
dpi and the scan area is the maximum allowed. The scan mode is
|
||||
user selected. The default is "no".
|
||||
requests a preview scan. The resolution used for that scan is 50
|
||||
dpi (for VM356A and VM6575 75 dpi) and the scan area is the max-
|
||||
imum allowed. The scan mode is user selected. The default is
|
||||
"no".
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -154,9 +162,9 @@
|
|||
|
||||
<B>SANE_TECO2_CAL_ALGO</B>
|
||||
Either 0 or 1. Selects the algorithm for the calibration. A
|
||||
value of 1 seems to give better scans on the VM3575. Feedback on
|
||||
it is welcome. For VM356A and VM3575 default 1. For other sup-
|
||||
ported types default 0.
|
||||
value of 1 seems to give better scans on the VM356A, VM3575.
|
||||
Feedback on it is welcome. For VM356A, VM3575, VM6575 default
|
||||
1. For other supported types default 0.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -203,7 +211,7 @@
|
|||
|
||||
Michael Hoeller for his testing the VM356A.
|
||||
|
||||
sane-backends 1.0.14-cvs 15 January 2004 <B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B>
|
||||
sane-backends 1.0.15 03 August 2004 <B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -139,7 +139,7 @@
|
|||
The package is actively maintained by Frank Zago.
|
||||
http://www.zago.net/sane/#teco3
|
||||
|
||||
sane-backends 1.0.14-cvs 25 July 2002 <B><A HREF="sane-teco3.5.html">sane-teco3(5)</A></B>
|
||||
sane-backends 1.0.15 25 July 2002 <B><A HREF="sane-teco3.5.html">sane-teco3(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -279,7 +279,7 @@
|
|||
<H2>BUGS</H2><PRE>
|
||||
- config file values aren't tested for correctness
|
||||
|
||||
sane-backends 1.0.14-cvs 24 Jul 2002 <B><A HREF="sane-test.5.html">sane-test(5)</A></B>
|
||||
sane-backends 1.0.15 24 Jul 2002 <B><A HREF="sane-test.5.html">sane-test(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -130,8 +130,8 @@
|
|||
</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>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>,
|
||||
<I>/usr/local/doc/sane-1.0.14-cvs/u12/U12.changes</I>
|
||||
<I>http://www.gjaeger.de/scanner/u12.html</I>
|
||||
<I>/usr/local/doc/sane-1.0.15/u12/U12.changes</I>
|
||||
<I>http://www.gjaeger.de/scanner/u12/</I>
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -144,7 +144,7 @@
|
|||
<B>http://www.sane-project.org/mailing-lists.html</B>
|
||||
|
||||
or directly from the projects' homepage at:
|
||||
<B>http://www.gjaeger.de/scanner/u12.html</B>
|
||||
<B>http://www.gjaeger.de/scanner/u12/</B>
|
||||
|
||||
To obtain debug messages from the backend, please set the environment-
|
||||
variable <I>SANE</I><B>_</B><I>DEBUG</I><B>_</B><I>U12</I> before calling your favorite scan-frontend
|
||||
|
|
@ -161,7 +161,7 @@
|
|||
* When using libusb, it might be, that the backend hangs.
|
||||
In that case, reconnect the scanner.
|
||||
|
||||
sane-backends 1.0.14-cvs 23 Apr 2004 <B><A HREF="sane-u12.5.html">sane-u12(5)</A></B>
|
||||
sane-backends 1.0.15 18 June 2004 <B><A HREF="sane-u12.5.html">sane-u12(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -268,7 +268,7 @@
|
|||
<H2>EMAIL-CONTACT</H2><PRE>
|
||||
Oliver.Rauch@Rauch-Domain.DE
|
||||
|
||||
sane-backends 1.0.14-cvs 29 november 2002 <B><A HREF="sane-umax.5.html">sane-umax(5)</A></B>
|
||||
sane-backends 1.0.15 29 november 2002 <B><A HREF="sane-umax.5.html">sane-umax(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -134,7 +134,7 @@
|
|||
When reporting bugs, please run the backend with SANE_DEBUG_UMAX1220U
|
||||
set to 10 and attach a copy of the log messages.
|
||||
|
||||
sane-backends 1.0.14-cvs 6 Jan 2002 <B><A HREF="sane-umax1220u.5.html">sane-umax1220u(5)</A></B>
|
||||
sane-backends 1.0.15 6 Jan 2002 <B><A HREF="sane-umax1220u.5.html">sane-umax1220u(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -30,36 +30,37 @@
|
|||
Astra 1600P
|
||||
Astra 2000P
|
||||
|
||||
This backend handles 75x75, 150x150, 300x300, 600x600 and 600x1200 dpi
|
||||
scan resolutions, in color and gray levels. There is a software lineart
|
||||
This backend handles 75x75, 150x150, 300x300, 600x600 and 600x1200 for
|
||||
1220P/1600P/2000P dpi scan reslutions,and 75x75, 150x150, 300x300 and
|
||||
300x600 for 610P. In color and gray levels, there is a software lineart
|
||||
mode.
|
||||
|
||||
These scanners share the same ASIC. Only parts such as CCD and ADC
|
||||
change from one to another. They even all reports being UMAX Astra
|
||||
1220P via IEEE1284. There isn't software way to recognize them prop-
|
||||
erly. Under windows, model is set by the driver installed, regardless
|
||||
of the hardware.
|
||||
The new generation models share a newer version of the 610P ASIC embed-
|
||||
ded in an EPAT chip. Only parts such as CCD and ADC change from one to
|
||||
another. They even all reports being UMAX Astra 1220P via IEEE1284.
|
||||
There isn't software way to recognize them properly. Under windows,
|
||||
model is set by the driver installed, regardless of the hardware.
|
||||
|
||||
<B>EPP/ECP</B> <B>MODES</B> <B>ONLY</B>
|
||||
The current version of the backend uses only EPP or ECP mode to
|
||||
communicate with the scanner. PS/2 and SPP mode aren't imple-
|
||||
mented. It is recommended that you set your parallel port to EPP
|
||||
in BIOS with the current version of this backend. You can leave
|
||||
it to ECP or ECP+EPP, but in this case you may not use ppdev but
|
||||
only direct hardware access if you have to use ECP. ECPEPP will
|
||||
only
|
||||
The current version of the backend uses only EPP or ECP mode to
|
||||
communicate with the scanner. PS/2 mode isn't implemented. The
|
||||
610P only use SPP. It is recommended that you set your parallel
|
||||
port to EPP in BIOS with the current version of this backend.
|
||||
You can leave it to ECP or ECP+EPP, but in this case you may not
|
||||
use ppdev but only direct hardware access if you have to use
|
||||
ECP. ECPEPP will only
|
||||
work if you use a 2.4 or 2.6 kernel with ppdev character device
|
||||
support.
|
||||
|
||||
This backend does support parport sharing only <I>if</I> <I>you</I> <I>have</I> <I>a</I> <I>kernel</I>
|
||||
This backend does support parport sharing only <I>if</I> <I>you</I> <I>have</I> <I>a</I> <I>kernel</I>
|
||||
<I>with</I> <I>ppdev</I> <I>support.</I>
|
||||
|
||||
Note that if you don't use the ppdev character device, the backend
|
||||
Note that if you don't use the ppdev character device, the backend
|
||||
needs to run as root. To allow user access to the scanner run the back-
|
||||
end through the network interface (See <B><A HREF="saned.1.html">saned(1)</A></B> and <B><A HREF="sane-net.5.html">sane-net(5)</A></B>). A
|
||||
more relaxed solution (security wise) is to add suid bit to the fron-
|
||||
tend (See <B><A HREF="chmod.1.html">chmod(1)</A></B>). The backend drop root priviledges as soon as it
|
||||
can, right after gaining direct access to IO ports, which lessen risks
|
||||
end through the network interface (See <B><A HREF="saned.8.html">saned(8)</A></B> and <B><A HREF="sane-net.5.html">sane-net(5)</A></B>). A
|
||||
more relaxed solution (security wise) is to add suid bit to the fron-
|
||||
tend (See <B><A HREF="chmod.1.html">chmod(1)</A></B>). The backend drop root priviledges as soon as it
|
||||
can, right after gaining direct access to IO ports, which lessen risks
|
||||
when being root.
|
||||
|
||||
|
||||
|
|
@ -93,7 +94,7 @@
|
|||
<B>NOTE:</B> in all cases, you must have sufficient priviledges
|
||||
to get access to the chosen device or address. Depending on the
|
||||
security settings, devices may not be available for all users.
|
||||
You have to change permissions on the dev/ppi* or /dev/parport*
|
||||
You have to change permissions on the dev/ppi* or /dev/parport*
|
||||
devices.
|
||||
|
||||
You can rename any device using the
|
||||
|
|
@ -109,43 +110,42 @@
|
|||
<H2>CONFIGURATION</H2><PRE>
|
||||
Please make sure to edit umax_pp.conf <B>before</B> you use the backend.
|
||||
|
||||
The contents of the <B>umax_pp.conf</B> file is a list of options and device
|
||||
The contents of the <B>umax_pp.conf</B> file is a list of options and device
|
||||
names that correspond to Umax scanners. Empty lines and lines starting
|
||||
with a hash mark (#) are ignored.
|
||||
|
||||
The height options supported are <B>red-brightness</B>, <B>green-brightness</B>,
|
||||
<B>blue-brightness</B>, <B>red-contrast</B>, <B>green-contrast</B>, <B>blue-contrast</B>, <B>astra</B>,
|
||||
and <B>buffer</B>.
|
||||
The height options supported are <B>red-gain</B>, <B>green-gain</B>, <B>blue-gain</B>,
|
||||
<B>red-offset</B>, <B>green-offset</B>, <B>blue-offset</B>, <B>astra</B>, and <B>buffer</B>.
|
||||
|
||||
Options <B>red-brightness</B> , <B>green-brightness</B> and <B>blue-brightness</B> allow you
|
||||
to adjust the sensitivy of your scanner for the given color. Values
|
||||
range from 0 (lowest brightness) to 15 (highest). If the advanced
|
||||
option "Brightness" isn't checked in the frontend, the backend does
|
||||
automatic brightness calibration, and do not use user provided values.
|
||||
Options <B>red-gain</B> , <B>green-gain</B> and <B>blue-gain</B> allow you to adjust the
|
||||
sensitivy of your scanner for the given color. Values range from 0
|
||||
(lowest gain) to 15 (highest). If the advanced option "Gain" isn't
|
||||
checked in the frontend, the backend does automatic gain calibration,
|
||||
and do not use user provided values.
|
||||
|
||||
Options <B>red-contrast</B> , <B>green-contrast</B> and <B>blue-contrast</B> allow you to
|
||||
adjust the contrast of your scanner for the given color. Values range
|
||||
from 0 (lowest contrast) to 15 (highest).
|
||||
Options <B>red-offset</B> , <B>green-offset</B> and <B>blue-offset</B> allow you to adjust
|
||||
the offset of your scanner for the given color. Values range from 0
|
||||
(lowest offset) to 15 (highest).
|
||||
|
||||
Option <B>astra</B> allows you to change the model of your scanner. Current
|
||||
auto detection is based on side effects on scanning when using 1220P
|
||||
Option <B>astra</B> allows you to change the model of your scanner. Current
|
||||
auto detection is based on side effects on scanning when using 1220P
|
||||
command set on other models, so it may fail on unkown hardware combina-
|
||||
tion. Valid values are 610, 1220, 1600 and 2000. It is usefull only
|
||||
tion. Valid values are 610, 1220, 1600 and 2000. It is usefull only
|
||||
when autodetection fails to detect properly your scanner model. If your
|
||||
scanner work properly but is reported wrongly, let it be that way. The
|
||||
only valid case to change the model is when your scanner produces
|
||||
only valid case to change the model is when your scanner produces
|
||||
'black' or prevent scanner model autodetection.
|
||||
|
||||
Option <B>buffer</B> allows you to change the size of the scan buffer. The
|
||||
size must be specified in bytes. The default value is 2 megabytes.
|
||||
Decreasing this value will improve the smoothness of progress bar in
|
||||
Option <B>buffer</B> allows you to change the size of the scan buffer. The
|
||||
size must be specified in bytes. The default value is 2 megabytes.
|
||||
Decreasing this value will improve the smoothness of progress bar in
|
||||
the frontend, but will stall the scan more often.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>FILES</H2><PRE>
|
||||
<I>/usr/local/etc/sane.d/umax</I><B>_</B><I>pp.conf</I>
|
||||
The backend configuration file (see also description of
|
||||
The backend configuration file (see also description of
|
||||
<B>SANE_CONFIG_DIR</B> below).
|
||||
|
||||
<I>/usr/local/lib/sane/libsane-umax</I><B>_</B><I>pp.a</I>
|
||||
|
|
@ -161,21 +161,21 @@
|
|||
<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
|
||||
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
|
||||
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
|
||||
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
|
||||
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_UMAX_PP</B>
|
||||
If the library was compiled with debug support enabled, this
|
||||
environment variable controls the debug level for this backend.
|
||||
E.g., a value of 128 requests all debug output to be printed.
|
||||
If the library was compiled with debug support enabled, this
|
||||
environment variable controls the debug level for this backend.
|
||||
E.g., a value of 128 requests all debug output to be printed.
|
||||
Smaller levels reduce verbosity.
|
||||
|
||||
level debug output
|
||||
|
|
@ -189,8 +189,8 @@
|
|||
6 special debug information
|
||||
|
||||
<B>SANE_DEBUG_UMAX_PP_LOW</B>
|
||||
This variable sets the debug level for the SANE interface for
|
||||
the Umax ASIC. Note that enabling this will spam your terminal
|
||||
This variable sets the debug level for the SANE interface for
|
||||
the Umax ASIC. Note that enabling this will spam your terminal
|
||||
with some million lines of debug output.
|
||||
|
||||
level debug output
|
||||
|
|
@ -205,7 +205,7 @@
|
|||
|
||||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-net.5.html">sane-net(5)</A></B>, <B><A HREF="saned.1.html">saned(1)</A></B>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-net.5.html">sane-net(5)</A></B>, <B><A HREF="saned.8.html">saned(8)</A></B>
|
||||
|
||||
For latest bug fixes and information see
|
||||
<I>http://umax1220p.sourceforge.net/</I>
|
||||
|
|
@ -216,6 +216,12 @@
|
|||
Stéphane VOLTZ <svoltz@wanadoo.fr>
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CREDITS</H2><PRE>
|
||||
Support for the 610P has been made possible thank to an hardware dona-
|
||||
tion by William Stuart.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>BUG REPORTS</H2><PRE>
|
||||
If something doesn't work, please contact me. But I need some informa-
|
||||
|
|
@ -241,7 +247,7 @@
|
|||
better), or you think I should know something, please include
|
||||
it.
|
||||
|
||||
sane-backends 1.0.14-cvs 16 September 2003 <B><A HREF="sane-umax_pp.5.html">sane-umax_pp(5)</A></B>
|
||||
sane-backends 1.0.15 23 August 2004 <B><A HREF="sane-umax_pp.5.html">sane-umax_pp(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -64,152 +64,152 @@
|
|||
nel, libsub), NetBSD (libusb), OpenBSD (kernel, libusb) and MacOS X
|
||||
(libusb). Testing on MacOS X is very limited and not all scanners seem
|
||||
to work reliably with the BSDs. For installation issues, also check the
|
||||
/usr/local/doc/sane-1.0.14-cvs/README.platform files. The scanner mod-
|
||||
ule is on longer available on Linux 2.6 and later. Use libusb instead.
|
||||
/usr/local/doc/sane-1.0.15/README.platform files. The scanner module is
|
||||
on longer available on Linux 2.6 and later. Use libusb instead.
|
||||
|
||||
Generally speaking, if your scanner works with one method, there is no
|
||||
Generally speaking, if your scanner works with one method, there is no
|
||||
need to switch to the other one.
|
||||
|
||||
Libusb is the more general approach and is able to access any scanner.
|
||||
Libusb is the more general approach and is able to access any scanner.
|
||||
Also, it supports more platforms.
|
||||
|
||||
Autodetecting scanners and using USB control messages with the kernel
|
||||
Autodetecting scanners and using USB control messages with the kernel
|
||||
access method only works with recent (>=v2.4.12) Linux kernels. If you
|
||||
need one of these two features on a different platform, use libusb
|
||||
instead. Also, the kernel scanner driver may be removed from Linux
|
||||
need one of these two features on a different platform, use libusb
|
||||
instead. Also, the kernel scanner driver may be removed from Linux
|
||||
2.5/2.6 in future so libusb will be the only access method.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>LIBUSB</H2><PRE>
|
||||
SANE can only use libusb 0.1.6 or newer. It needs to be installed at
|
||||
SANE can only use libusb 0.1.6 or newer. It needs to be installed at
|
||||
build-time.
|
||||
|
||||
Libusb can only access your scanner if it's not claimed by the kernel
|
||||
scanner driver. If you want to use libusb, unload the kernel driver
|
||||
Libusb can only access your scanner if it's not claimed by the kernel
|
||||
scanner driver. If you want to use libusb, unload the kernel driver
|
||||
(e.g. rmmod scanner under Linux) or disable the driver when compiling a
|
||||
new kernel. For Linux, your kernel needs support for the USB filesystem
|
||||
(usbfs). For kernels older than 2.4.19, replace "usbfs" with "usbdevfs"
|
||||
because the name has changed. This filesystem must be mounted. That's
|
||||
done automatically at boot time, if /etc/fstab contains a line like
|
||||
because the name has changed. This filesystem must be mounted. That's
|
||||
done automatically at boot time, if /etc/fstab contains a line like
|
||||
this:
|
||||
|
||||
none /proc/bus/usb usbfs defaults 0 0
|
||||
|
||||
The permissions for the device files used by libusb must be adjusted
|
||||
for user access. Otherwise only root can use SANE devices. For <I>Linux</I>,
|
||||
the devices are located in /proc/bus/usb/. There are directories named
|
||||
e.g. "001" (the bus name) containing files "001", "002" etc. (the
|
||||
The permissions for the device files used by libusb must be adjusted
|
||||
for user access. Otherwise only root can use SANE devices. For <I>Linux</I>,
|
||||
the devices are located in /proc/bus/usb/. There are directories named
|
||||
e.g. "001" (the bus name) containing files "001", "002" etc. (the
|
||||
device files). The right device files can be found out by running scan-
|
||||
image -L as root. Setting permissions with "chmod" is not permanent,
|
||||
however. They will be resetted after reboot or replugging the scanner.
|
||||
In Linux versions before 2.6 it was also possible to mount the usbfs
|
||||
with the option "devmode=0666", e.g. by using the following line in
|
||||
image -L as root. Setting permissions with "chmod" is not permanent,
|
||||
however. They will be resetted after reboot or replugging the scanner.
|
||||
In Linux versions before 2.6 it was also possible to mount the usbfs
|
||||
with the option "devmode=0666", e.g. by using the following line in
|
||||
/etc/fstab:
|
||||
|
||||
none /proc/bus/usb usbfs defaults,devmode=0666 0 0
|
||||
|
||||
<B>DUE</B> <B>TO</B> <B>A</B> <B>KERNEL</B> <B>BUG</B> <B>THIS</B> <B>WON'T</B> <B>WORK</B> <B>WITH</B> <B>CURRENT</B> <B>2.6</B> <B>KERNELS.</B> <B>USE</B> <B>HOT-</B>
|
||||
<B>DUE</B> <B>TO</B> <B>A</B> <B>KERNEL</B> <B>BUG</B> <B>THIS</B> <B>WON'T</B> <B>WORK</B> <B>WITH</B> <B>CURRENT</B> <B>2.6</B> <B>KERNELS.</B> <B>USE</B> <B>HOT-</B>
|
||||
<B>PLUG</B> <B>INSTEAD</B>
|
||||
|
||||
However, this way everyone has access to all USB devices. Another way
|
||||
to set permissions is to use the hotplug utilities (<I>http://linux-hot-</I>
|
||||
However, this way everyone has access to all USB devices. Another way
|
||||
to set permissions is to use the hotplug utilities (<I>http://linux-hot-</I>
|
||||
<I>plug.sourceforge.net/</I>), which support dynamic setting of access permis-
|
||||
sions. SANE comes with hotplug scripts in the directory tools/hotplug.
|
||||
They can be used for setting permissions. Last, the frontends can be
|
||||
sions. SANE comes with hotplug scripts in the directory tools/hotplug.
|
||||
They can be used for setting permissions. Last, the frontends can be
|
||||
run as root. However, that's not recommended for security reasons.
|
||||
|
||||
For the <B>BSDs</B>, the device files are named <I>/dev/ugen*</I>. Use chmod to
|
||||
For the <B>BSDs</B>, the device files are named <I>/dev/ugen*</I>. Use chmod to
|
||||
apply appropriate permissions.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>GENERIC KERNEL SCANNER DRIVER</H2><PRE>
|
||||
Ensure that the access permissions for the USB device are set appropri-
|
||||
ately. We recommend to add a group "scanner" to <I>/etc/group</I> which con-
|
||||
ately. We recommend to add a group "scanner" to <I>/etc/group</I> which con-
|
||||
tains all users that should have access to the scanner. The permission
|
||||
of the device should then be set to allow group read and write access.
|
||||
For example, if the scanner is at USB device <B>/dev/usb/scanner0</B>, then
|
||||
of the device should then be set to allow group read and write access.
|
||||
For example, if the scanner is at USB device <B>/dev/usb/scanner0</B>, then
|
||||
the following two commands would set the permission correctly:
|
||||
|
||||
$ chgrp scanner /dev/usb/scanner0
|
||||
$ chmod 660 /dev/usb/scanner0
|
||||
|
||||
If your scanner isn't detected automatically by your operating system's
|
||||
scanner driver, you need to tell the kernel the vendor and product ids
|
||||
of your scanner. For <B>Linux</B>, this can be done with modprobe parameters:
|
||||
First, remove the scanner module (<I>rmmod</I> <I>scanner</I>), then load it again:
|
||||
<I>modprobe</I> <I>scanner</I> <I>vendor=0x0001</I> <I>product=0x0002</I>. Use the appropriate
|
||||
vendor and product ids (e.g. from <I>/var/log/messages</I>, <I>dmesg</I>, or <I>cat</I>
|
||||
<I>/proc/bus/usb/devices</I>). Some scanners supported by the gt68xx backend
|
||||
scanner driver, you need to tell the kernel the vendor and product ids
|
||||
of your scanner. For <B>Linux</B>, this can be done with modprobe parameters:
|
||||
First, remove the scanner module (<I>rmmod</I> <I>scanner</I>), then load it again:
|
||||
<I>modprobe</I> <I>scanner</I> <I>vendor=0x0001</I> <I>product=0x0002</I>. Use the appropriate
|
||||
vendor and product ids (e.g. from <I>/var/log/messages</I>, <I>dmesg</I>, or <I>cat</I>
|
||||
<I>/proc/bus/usb/devices</I>). Some scanners supported by the gt68xx backend
|
||||
are not supported by the current version of the generic scanner driver.
|
||||
See <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B> for details. For these scanners, there will be a
|
||||
See <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B> for details. For these scanners, there will be a
|
||||
message concerning "only 2 or three endpoints" in syslog.
|
||||
|
||||
For OpenBSD the kernel may need to be recompiled. For details look at
|
||||
/usr/local/doc/sane-1.0.14-cvs/README.openbsd. Similar approaches
|
||||
should be used for the other BSDs.
|
||||
For OpenBSD the kernel may need to be recompiled. For details look at
|
||||
/usr/local/doc/sane-1.0.15/README.openbsd. Similar approaches should be
|
||||
used for the other BSDs.
|
||||
|
||||
Linux kernel messages in syslog like "kernel: scanner.c: open_scan-
|
||||
Linux kernel messages in syslog like "kernel: scanner.c: open_scan-
|
||||
<B><A HREF="ner.1.html">ner(1)</A></B>: Unable to access minor data" can be ignored. They are generated
|
||||
when SANE scans all available USB devices for scanners.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>SANE ISSUES</H2><PRE>
|
||||
This section assumes that your scanner is detected by sane-find-scan-
|
||||
ner. It doesn't make sense to go on, if this is not the case. While
|
||||
sane-find-scanner is able to detect any USB scanner, actual scanning
|
||||
will only work if the scanner is supported by a SANE backend. Informa-
|
||||
tion on the level of support can be found on the SANE webpage
|
||||
This section assumes that your scanner is detected by sane-find-scan-
|
||||
ner. It doesn't make sense to go on, if this is not the case. While
|
||||
sane-find-scanner is able to detect any USB scanner, actual scanning
|
||||
will only work if the scanner is supported by a SANE backend. Informa-
|
||||
tion on the level of support can be found on the SANE webpage
|
||||
(<I>http://www.sane-project.org/</I>), and the individual backend manpages.
|
||||
|
||||
Most backends can detect USB scanners automatically using "usb" config-
|
||||
uration file lines. This method allows to identify scanners by the USB
|
||||
vendor and product numbers. The syntax for specifying a scanner this
|
||||
uration file lines. This method allows to identify scanners by the USB
|
||||
vendor and product numbers. The syntax for specifying a scanner this
|
||||
way is:
|
||||
|
||||
usb <I>VENDOR</I> <I>PRODUCT</I>
|
||||
|
||||
where <I>VENDOR</I> is the USB vendor id, and <I>PRODUCT</I> is the USB product id of
|
||||
the scanner. Both ids are non-negative integer numbers in decimal or
|
||||
the scanner. Both ids are non-negative integer numbers in decimal or
|
||||
hexadecimal format. The correct values for these fields can be found by
|
||||
looking into the syslog (e.g., /var/log/messages) or under Linux by
|
||||
issuing the command "cat /proc/bus/usb/devices/". This is an example
|
||||
looking into the syslog (e.g., /var/log/messages) or under Linux by
|
||||
issuing the command "cat /proc/bus/usb/devices/". This is an example
|
||||
of a config file line:
|
||||
|
||||
usb 0x055f 0x0006
|
||||
|
||||
would have the effect that all USB devices in the system with a vendor
|
||||
id of 0x55f and a product id of 0x0006 would be probed and recognized
|
||||
would have the effect that all USB devices in the system with a vendor
|
||||
id of 0x55f and a product id of 0x0006 would be probed and recognized
|
||||
by the backend.
|
||||
|
||||
If your scanner is not detected automatically, it may be necessary to
|
||||
edit the appropriate backend configuration file before using SANE for
|
||||
the first time. For most systems, the configuration file should list
|
||||
If your scanner is not detected automatically, it may be necessary to
|
||||
edit the appropriate backend configuration file before using SANE for
|
||||
the first time. For most systems, the configuration file should list
|
||||
the name of the USB device file that the scanner is connected to (e.g.,
|
||||
under Linux, <B>/dev/usb/scanner0</B> or <B>/dev/usbscanner0</B> is such a USB
|
||||
device, the device file for FreeBSD is e.g. <B>/dev/uscanner0</B>). If
|
||||
libusb is used, the device name looks like the following example:
|
||||
under Linux, <B>/dev/usb/scanner0</B> or <B>/dev/usbscanner0</B> is such a USB
|
||||
device, the device file for FreeBSD is e.g. <B>/dev/uscanner0</B>). If
|
||||
libusb is used, the device name looks like the following example:
|
||||
<B>libusb:001:002</B>.
|
||||
|
||||
For a detailed description of each backend's configuration file, please
|
||||
refer to the relevant backend manual page (e.g. <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B> for
|
||||
Mustek USB scanners).
|
||||
|
||||
Do <B>not</B> create a symlink from <I>/dev/scanner</I> to the USB device because
|
||||
this link is used by the SCSI backends. The scanner may be confused if
|
||||
Do <B>not</B> create a symlink from <I>/dev/scanner</I> to the USB device because
|
||||
this link is used by the SCSI backends. The scanner may be confused if
|
||||
it receives SCSI commands.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_DEBUG_SANEI_USB</B>
|
||||
If the library was compiled with debug support enabled, this
|
||||
environment variable controls the debug level for the USB I/O
|
||||
If the library was compiled with debug support enabled, this
|
||||
environment variable controls the debug level for the USB I/O
|
||||
subsystem. E.g., a value of 128 requests all debug output to be
|
||||
printed. Smaller levels reduce verbosity. Values greater than 4
|
||||
enable libusb debugging (if available). Example: export
|
||||
enable libusb debugging (if available). Example: export
|
||||
SANE_DEBUG_SANEI_USB=4.
|
||||
|
||||
|
||||
|
|
@ -222,7 +222,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
Henning Meier-Geinitz
|
||||
|
||||
sane-backends 1.0.14-cvs 8 Mar 2004 <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>
|
||||
sane-backends 1.0.15 8 Mar 2004 <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -105,7 +105,7 @@
|
|||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="xcam.1.html">xcam(1)</A></B>.
|
||||
|
||||
sane-backends 1.0.14-cvs 28 Aug 2002 <B><A HREF="sane-v4l.5.html">sane-v4l(5)</A></B>
|
||||
sane-backends 1.0.15 28 Aug 2002 <B><A HREF="sane-v4l.5.html">sane-v4l(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
586
man/sane.7.html
586
man/sane.7.html
|
|
@ -1,586 +0,0 @@
|
|||
<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-project.org/</I>). Information about other frontends and
|
||||
backends can be found on the frontend page
|
||||
(<I>http://www.sane-project.org/sane-frontends.html</I>).
|
||||
|
||||
|
||||
</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.14-cvs/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.14-cvs/</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-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.14-cvs/.
|
||||
|
||||
<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. 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>http://www.sane-project.org/mail-</I>
|
||||
<I>ing-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.
|
||||
|
||||
<B>Compiling</B> <B>and</B> <B>installing</B> <B>SANE</B>
|
||||
Look at <I>/usr/local/doc/sane-1.0.14-cvs/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><A HREF="sane-scsi.5.html">sane-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.1.html">saned(1)</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><A HREF="sane-apple.5.html">sane-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><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B> for details.
|
||||
|
||||
<B>coolscan2</B>
|
||||
This is a SANE backend for Nikon Coolscan film-scanners. See
|
||||
<B><A HREF="sane-coolscan2.5.html">sane-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 Fujitsu 3091, 3093, 3096 and
|
||||
fi-4340 SCSI scanners. See <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(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><A HREF="sane-hp.5.html">sane-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>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><A HREF="sane-ibm.5.html">sane-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>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><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B> for details.
|
||||
|
||||
<B>mustek_pp</B>
|
||||
The mustek_pp backend provides access to Mustek parallel port flatbed
|
||||
scannersr. 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>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>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>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><A HREF="sane-sharp.5.html">sane-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>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>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><A HREF="sane-umax1220u.5.html">sane-umax1220u(5)</A></B> for details.
|
||||
|
||||
Also, have a look at the backend information page at
|
||||
<I>http://www.sane-project.org/sane-supported-devices.html</I> and the list of
|
||||
projects in <I>/usr/local/doc/sane-1.0.14-cvs/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
|
||||
supported cameras.) Gphoto2 supports over 140 different camera mod-
|
||||
els. 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>.
|
||||
|
||||
Also, have a look at the backend information page at
|
||||
<I>http://www.sane-project.org/sane-supported-devices.html</I> and the list of
|
||||
projects in <I>/usr/local/doc/sane-1.0.14-cvs/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><A HREF="sane-net.5.html">sane-net(5)</A></B> and <B><A HREF="saned.1.html">saned(1)</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><A HREF="sane-test.5.html">sane-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-project.org/sane-supported-devices.html</I> and the list of
|
||||
projects in <I>/usr/local/doc/sane-1.0.14-cvs/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.14-cvs/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.14-cvs/backend-writing.txt</I>. Most of the inter-
|
||||
nal <B>SANE</B> routines (<B>sanei</B>) are documented using doxygen:
|
||||
<I>http://www.sane-project.org/sanei/</I>. Before a new backend or frontend
|
||||
project is started, have a look at
|
||||
<I>/usr/local/doc/sane-1.0.14-cvs/PROJECTS</I> for projects that are planned
|
||||
or not yet included into the <B>SANE</B> distribution and at our bug-tracking
|
||||
system: <I>http://www.http://www.sane-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.14-cvs/*</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>>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 alook 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.14-cvs/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/mail-</I>
|
||||
<I>ing-lists.html</I> for details).
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="saned.1.html">saned(1)</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><A HREF="sane-agfafocus.5.html">sane-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><A HREF="sane-canon630u.5.html">sane-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-gphoto2.5.html">sane-gphoto2(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-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-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-ma1509.5.html">sane-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><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-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>sane-plus-</B>
|
||||
<B><A HREF="tek_pp.5.html">tek_pp(5)</A></B>, <B><A HREF="sane-pnm.5.html">sane-pnm(5)</A></B>, <B><A HREF="sane-qcam.5.html">sane-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-snapscan.5.html">sane-snapscan(5)</A></B>, <B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B>, <B><A HREF="sane-st400.5.html">sane-st400(5)</A></B>, <B><A HREF="sane-tamarack.5.html">sane-tamarack(5)</A></B>,
|
||||
<B><A HREF="sane-teco1.5.html">sane-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><A HREF="sane-v4l.5.html">sane-v4l(5)</A></B>
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>AUTHOR</H2><PRE>
|
||||
David Mosberger-Tang and many many more (see
|
||||
<I>/usr/local/doc/sane-1.0.14-cvs/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.14-cvs 06 Jan 2004 <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>
|
||||
|
|
@ -115,7 +115,7 @@
|
|||
|
||||
The <B>--accept-md5-only</B> option only accepts user authorization requests
|
||||
that support MD5 security. The <B>SANE</B> network daemon (<B>saned</B>) is capable
|
||||
of doing such requests. See <B><A HREF="saned.1.html">saned(1)</A></B>.
|
||||
of doing such requests. See <B><A HREF="saned.8.html">saned(8)</A></B>.
|
||||
|
||||
The <B>-n</B> or <B>--dont-scan</B> option requests that <B>scanimage</B> only sets the
|
||||
options provided by the user but doesn't actually perform a scan. This
|
||||
|
|
@ -274,7 +274,7 @@
|
|||
For vector options, the help output currently has no indication as to
|
||||
how many elements a vector-value should have.
|
||||
|
||||
sane-backends 1.0.14-cvs 22 Feb 2004 <B><A HREF="scanimage.1.html">scanimage(1)</A></B>
|
||||
sane-backends 1.0.15 22 Feb 2004 <B><A HREF="scanimage.1.html">scanimage(1)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
Ładowanie…
Reference in New Issue