kopia lustrzana https://gitlab.com/sane-project/website
Updated manual pages from sane-backends 1.0.17.
Henning Geinitz
rodzic
be2a903a2f
commit
4d38b54f35
|
|
@ -71,7 +71,7 @@
|
|||
<H2>EMAIL-CONTACT</H2><PRE>
|
||||
Oliver.Rauch@Rauch-Domain.DE
|
||||
|
||||
sane-backends 1.0.16 11 Sep 2002 <B><A HREF="gamma4scanimage.1.html">gamma4scanimage(1)</A></B>
|
||||
sane-backends 1.0.17 11 Sep 2002 <B><A HREF="gamma4scanimage.1.html">gamma4scanimage(1)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -27,8 +27,8 @@
|
|||
with this backend, or if you own an Abaton scanner that does not work
|
||||
with this backend, please contact <I>sane-devel@lists.alioth.debian.org</I>
|
||||
with the model number, so that arrangements can be made to include sup-
|
||||
port for it. Have a look at http://www.sane-project.org/mail-
|
||||
ing-lists.html concerning subscription to sane-devel.
|
||||
port for it. Have a look at http://www.sane-project.org/mailing-
|
||||
lists.html concerning subscription to sane-devel.
|
||||
|
||||
Abaton is out of business, and these scanners are not supported by
|
||||
Everex (the parent company of Abaton), nor is there any programming
|
||||
|
|
@ -118,8 +118,8 @@
|
|||
|
||||
If you have found something that you think is a bug, please attempt to
|
||||
recreate it with the SANE_DEBUG_ABATON environment variable set to 255,
|
||||
and send a report detailing the conditions surrounding the bug to
|
||||
<I>sane-devel@lists.alioth.debian.org</I>.
|
||||
and send a report detailing the conditions surrounding the bug to <I>sane-</I>
|
||||
<I>devel@lists.alioth.debian.org</I>.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -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.16 19 Nov 1998 <B><A HREF="sane-abaton.5.html">sane-abaton(5)</A></B>
|
||||
sane-backends 1.0.17 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.16 17 Oct 1998 <B><A HREF="sane-agfafocus.5.html">sane-agfafocus(5)</A></B>
|
||||
sane-backends 1.0.17 17 Oct 1998 <B><A HREF="sane-agfafocus.5.html">sane-agfafocus(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -28,10 +28,9 @@
|
|||
|
||||
If you own a Apple scanner other than the ones listed above that works
|
||||
with this backend, please let us know by sending the scanner's model
|
||||
name, SCSI id, and firmware revision to
|
||||
<I>sane-devel@lists.alioth.debian.org</I>. See
|
||||
http://www.sane-project.org/mailing-lists.html for details on how to
|
||||
subscribe to sane-devel.
|
||||
name, SCSI id, and firmware revision to <I>sane-</I>
|
||||
<I>devel@lists.alioth.debian.org</I>. See http://www.sane-project.org/mail-
|
||||
ing-lists.html for details on how to subscribe to sane-devel.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -40,39 +39,39 @@
|
|||
|
||||
<I>special</I>
|
||||
|
||||
Where <I>special</I> is either the path-name for the special device that cor-
|
||||
responds to a SCSI scanner. For SCSI scanners, the special device name
|
||||
must be a generic SCSI device or a symlink to such a device. Under
|
||||
Linux, such a device name could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example.
|
||||
Where <I>special</I> is either the path-name for the special device that cor-
|
||||
responds to a SCSI scanner. For SCSI scanners, the special device name
|
||||
must be a generic SCSI device or a symlink to such a device. Under
|
||||
Linux, such a device name could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example.
|
||||
See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONFIGURATION</H2><PRE>
|
||||
The contents of the <I>apple.conf</I> file is a list of options and device
|
||||
names that correspond to Apple scanners. Empty lines and lines start-
|
||||
ing with a hash mark (#) are ignored. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> on details of
|
||||
The contents of the <I>apple.conf</I> file is a list of options and device
|
||||
names that correspond to Apple scanners. Empty lines and lines start-
|
||||
ing with a hash mark (#) are ignored. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> on details of
|
||||
what constitutes a valid device name.
|
||||
|
||||
Options come in two flavors: global and positional ones. Global
|
||||
options apply to all devices managed by the backend whereas positional
|
||||
options apply just to the most recently mentioned device. Note that
|
||||
Options come in two flavors: global and positional ones. Global
|
||||
options apply to all devices managed by the backend whereas positional
|
||||
options apply just to the most recently mentioned device. Note that
|
||||
this means that the order in which the options appear matters!
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>SCSI ADAPTER TIPS</H2><PRE>
|
||||
SCSI scanners are typically delivered with an ISA SCSI adapter. Unfor-
|
||||
tunately, that adapter is not worth much since it is not interrupt
|
||||
driven. It is (sometimes) possible to get the supplied card to work,
|
||||
but without interrupt line, scanning will put so much load on the sys-
|
||||
tunately, that adapter is not worth much since it is not interrupt
|
||||
driven. It is (sometimes) possible to get the supplied card to work,
|
||||
but without interrupt line, scanning will put so much load on the sys-
|
||||
tem, that it becomes almost unusable for other tasks.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>FILES</H2><PRE>
|
||||
<I>/usr/local/etc/sane.d/apple.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-apple.a</I>
|
||||
|
|
@ -88,34 +87,34 @@
|
|||
<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_APPLE</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 255 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 255 requests all debug output to be printed.
|
||||
Smaller levels reduce verbosity.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CURRENT STATUS</H2><PRE>
|
||||
The apple backend is now in version 0.3 (Tue Jul 21 1998). Since I only
|
||||
have the AppleScanner and not the other models (OneScanner, ColorOneS-
|
||||
have the AppleScanner and not the other models (OneScanner, ColorOneS-
|
||||
canner) I can only develop/test for the AppleScanner effectively. How-
|
||||
ever with this release I almost complete the gui part of all scanners.
|
||||
Most of the functionality is there. At least OneScanner should scan at
|
||||
the AppleScanner's compatible modes (LineArt, HalfTone, Gray16). My
|
||||
ever with this release I almost complete the gui part of all scanners.
|
||||
Most of the functionality is there. At least OneScanner should scan at
|
||||
the AppleScanner's compatible modes (LineArt, HalfTone, Gray16). My
|
||||
personal belief is that with a slight touch of debugging the OneScanner
|
||||
could be actually usable. The ColorOneScanner needs more work. AppleS-
|
||||
could be actually usable. The ColorOneScanner needs more work. AppleS-
|
||||
canner is of course almost fully supported.
|
||||
|
||||
|
||||
|
|
@ -131,44 +130,44 @@
|
|||
|
||||
<B>ColorOneScanner</B>
|
||||
Cannot up/download halftone pattern, calibration vectors, custom
|
||||
Color Correction Table (CCT) and of course custom gamma tables.
|
||||
Color Correction Table (CCT) and of course custom gamma tables.
|
||||
|
||||
<B>Park/UnPark</B> <B>(OneScanner,</B> <B>ColorOneScanner)</B>
|
||||
|
||||
The above functionalities are not only missing because I don't actually
|
||||
have the hardware to experiment on it. Another reason is the lack of
|
||||
have the hardware to experiment on it. Another reason is the lack of
|
||||
understanding of how SANE API could provide enaugh means to me to actu-
|
||||
ally describe other array types than the gamma one.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>UNSUPPORTED FEATURES.</H2><PRE>
|
||||
The following "features" will never be supported. At least as I am
|
||||
<H2>UNSUPPORTED FEATURES</H2><PRE>
|
||||
The following "features" will never be supported. At least as I am
|
||||
maintaining the sane-apple backend.
|
||||
|
||||
<B>NoHome</B> <B>(AppleScanner)</B>
|
||||
The scanner lamp stays on and the carriage assembly remains
|
||||
The scanner lamp stays on and the carriage assembly remains
|
||||
where it stops at the end of the scan. After two minutes, if the
|
||||
scanner does not receive another SCAN command the lamp goes off
|
||||
scanner does not receive another SCAN command the lamp goes off
|
||||
and the carriage returns to the home position.
|
||||
|
||||
<B>Compression</B> <B>(AppleScanner)</B>
|
||||
The Scanner can compress data with CCITT Group III, one dimen-
|
||||
The Scanner can compress data with CCITT Group III, one dimen-
|
||||
sional algorithm (fax), and the Skip White Line algorithm.
|
||||
|
||||
<B>Multiple</B> <B>Windows</B> <B>(AppleScanner)</B>
|
||||
AppleScanner may support multiple windows. It would be a cool
|
||||
feature and a challenge for me to code it if you could intermix
|
||||
different options for different windows (scan areas). This way
|
||||
you could scan a document in LineArt mode but the figures in it
|
||||
on Gray and in a different resolution. Unfortunately this is
|
||||
AppleScanner may support multiple windows. It would be a cool
|
||||
feature and a challenge for me to code it if you could intermix
|
||||
different options for different windows (scan areas). This way
|
||||
you could scan a document in LineArt mode but the figures in it
|
||||
on Gray and in a different resolution. Unfortunately this is
|
||||
impossible.
|
||||
|
||||
<B>Scan</B> <B>Direction</B> <B>(OneScanner)</B>
|
||||
It controls the scan direction. (?)
|
||||
|
||||
<B>Status/Reset</B> <B>Button</B> <B>(OneScanner)</B>
|
||||
This option controls the status of the button in OneScanner
|
||||
This option controls the status of the button in OneScanner
|
||||
model. You can also reset the button status by software.
|
||||
|
||||
|
||||
|
|
@ -177,56 +176,52 @@
|
|||
The bugs in a sane backend are divided in two classes. We have <B>GUI</B> bugs
|
||||
and <B>scanner</B> <B>specific</B> bugs.
|
||||
|
||||
We know we have a GUI bug when a parameter is not showing up itself
|
||||
We know we have a GUI bug when a parameter is not showing up itself
|
||||
when it should (active) or vice versa. To find out which parameters are
|
||||
active accross various Apple modes and models from the documentation
|
||||
active accross various Apple modes and models from the documentation
|
||||
<B>ftp://ftpdev.info.apple.com/devworld/Technical_Documentation/Peripher-</B>
|
||||
<B>als_Documentation/</B> is an interesting exercise. I may missed some depen-
|
||||
dancies. For example for the threshold parameter the Apple Scanners
|
||||
Programming guide says nothing. I had to assume that is valid only in
|
||||
dancies. For example for the threshold parameter the Apple Scanners
|
||||
Programming guide says nothing. I had to assume that is valid only in
|
||||
LineArt mode.
|
||||
|
||||
Scanner specific bugs are mostly due to mandatory round offs in order
|
||||
to scan. In the documentation in some place states that the width of
|
||||
the scan area should be a byte multiple. In an other place says that
|
||||
the width of the scan area should be an even byte multiple. Go fig-
|
||||
Scanner specific bugs are mostly due to mandatory round offs in order
|
||||
to scan. In the documentation in some place states that the width of
|
||||
the scan area should be a byte multiple. In an other place says that
|
||||
the width of the scan area should be an even byte multiple. Go fig-
|
||||
ure...
|
||||
|
||||
Other source of bugs are due to scsi communcation, scsi connects and
|
||||
disconnects. However the classical bugs are still there. So you may
|
||||
Other source of bugs are due to scsi communcation, scsi connects and
|
||||
disconnects. However the classical bugs are still there. So you may
|
||||
encouter buffer overruns, null pointers, memory corruption and <B>SANE</B> API
|
||||
violations.
|
||||
|
||||
<B>SIGSEGV</B> <B>on</B> <B>SliceBars</B>
|
||||
When you try to modify the scan area from the slice bar you have
|
||||
a nice little cute core dump. I don't know why. If you select
|
||||
a nice little cute core dump. I don't know why. If you select
|
||||
the scan are from the preview window, or by hand typing the num-
|
||||
bers everything is fine. The SIGSEGV happens deep in gtk library
|
||||
(gdk). I really cannot debug it.
|
||||
|
||||
<B>Options</B> <B>too</B> <B>much</B>
|
||||
It is possible, especially for the ColorOneScanner, that the
|
||||
backend's options panel to exceed from your screen. It happens
|
||||
with mine and I am running at 1024x768 my X Server. What can I
|
||||
It is possible, especially for the ColorOneScanner, that the
|
||||
backend's options panel to exceed from your screen. It happens
|
||||
with mine and I am running at 1024x768 my X Server. What can I
|
||||
say? Try smaller fonts in the X server, or virtual screens.
|
||||
|
||||
<B>Weird</B> <B>SCSI</B> <B>behaviour.</B>
|
||||
<B>Weird</B> <B>SCSI</B> <B>behaviour</B>
|
||||
I am quoting David Myers Here...
|
||||
|
||||
>> OS: FreeBSD 2.2.6
|
||||
>> CC: egcs-1.02
|
||||
>Just wanted to follow up on this... I recently changed my SCSI
|
||||
card from
|
||||
>the Adaptec 2940UW to a dual-channel Symbios 786 chipset. When
|
||||
I started up
|
||||
>SANE with your driver, I managed to scan line art drawings
|
||||
okay, but Gray16
|
||||
>scans led to a stream of SCSI error messages on the console,
|
||||
ultimately
|
||||
>hanging with a message saying the scanner wasn't releasing the
|
||||
SCSI bus.
|
||||
>This may be that the Symbios is simply less tolerant of ancient
|
||||
>hardware, or may be bugs in your driver or in SANE itself...
|
||||
Just wanted to follow up on this... I recently changed my SCSI
|
||||
card from the Adaptec 2940UW to a dual-channel Symbios 786
|
||||
chipset. When I started up SANE with your driver, I managed to
|
||||
scan line art drawings okay, but Gray16 scans led to a stream of
|
||||
SCSI error messages on the console, ultimately hanging with a
|
||||
message saying the scanner wasn't releasing the SCSI bus. This
|
||||
may be that the Symbios is simply less tolerant of ancient hard-
|
||||
ware, or may be bugs in your driver or in SANE itself...
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -275,7 +270,7 @@
|
|||
Firikis. It is mostly based on the mustek backend from David Mosberger
|
||||
and Andreas Czechanowski
|
||||
|
||||
sane-backends 1.0.16 13 May 1998 <B><A HREF="sane-apple.5.html">sane-apple(5)</A></B>
|
||||
sane-backends 1.0.17 13 May 1998 <B><A HREF="sane-apple.5.html">sane-apple(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -22,21 +22,14 @@
|
|||
present, the following scanners are known to work at least partially
|
||||
with this backend:
|
||||
|
||||
* Artec A6000C
|
||||
|
||||
* Artec A6000C PLUS
|
||||
|
||||
* Artec ViewStation AT3
|
||||
|
||||
* BlackWidow BW4800SP (rebadged Artec AT3)
|
||||
|
||||
* Artec ViewStation AT6
|
||||
|
||||
* Artec ViewStation AT12
|
||||
|
||||
* Artec AM12S
|
||||
|
||||
* Plustek 19200S (rebadged Artec AM12S)
|
||||
* Artec A6000C
|
||||
* Artec A6000C PLUS
|
||||
* Artec ViewStation AT3
|
||||
* BlackWidow BW4800SP (rebadged Artec AT3)
|
||||
* Artec ViewStation AT6
|
||||
* Artec ViewStation AT12
|
||||
* Artec AM12S
|
||||
* Plustek 19200S (rebadged Artec AM12S)
|
||||
|
||||
Although this manual page is generally updated with each release, up-
|
||||
to-date information on new releases and extraneous helpful hints are
|
||||
|
|
@ -177,7 +170,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
Chris Pinkham (cpinkham@corp.infi.net)
|
||||
|
||||
sane-backends 1.0.16 24 Jan 2000 <B><A HREF="sane-artec.5.html">sane-artec(5)</A></B>
|
||||
sane-backends 1.0.17 24 Jan 2000 <B><A HREF="sane-artec.5.html">sane-artec(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -83,7 +83,7 @@
|
|||
|
||||
Every usb section can have additional options
|
||||
|
||||
<B>artecFirmwareFile</B> <B><path>/Artec48.usb</B>
|
||||
<B>artecFirmwareFile</B> <B>/usr/local/share/sane/artec_eplus48u/Artec48.usb</B>
|
||||
The path to the firmware file. This option is required.
|
||||
|
||||
<B>redGamma</B> <B>1.0</B>
|
||||
|
|
@ -186,7 +186,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.16 19 Nov 2002 <B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B>
|
||||
sane-backends 1.0.17 19 Nov 2002 <B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -50,7 +50,7 @@
|
|||
<H2>EMAIL-CONTACT</H2><PRE>
|
||||
yossarian@users.sourceforge.net
|
||||
|
||||
sane-backends 1.0.16 Dec 14th, 2003 <B><A HREF="sane-as6e.5.html">sane-as6e(5)</A></B>
|
||||
sane-backends 1.0.17 Dec 14th, 2003 <B><A HREF="sane-as6e.5.html">sane-as6e(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -52,8 +52,6 @@
|
|||
option force-a3
|
||||
option disable-gamma-table
|
||||
option disable-calibration
|
||||
option one-calib-only
|
||||
option old-calibration
|
||||
|
||||
#scsi Vendor Model Type Bus Channel ID LUN
|
||||
scsi AVISION
|
||||
|
|
@ -81,18 +79,6 @@
|
|||
Disables the scanner's color calibration. You might try this if
|
||||
your scans hang or only produces random garbage.
|
||||
|
||||
one-calib-only:
|
||||
When this option is enabled, the backend will only perform a
|
||||
calibration when the backend is initialized and not before each
|
||||
scan. This might extend the life of the CCD, but does not work
|
||||
reliable with the newer USB scanners (they hang sometimes or
|
||||
return garbage image data). So this option should be used with
|
||||
care.
|
||||
|
||||
old-calibration:
|
||||
This enables the use of the old calibration code for testing
|
||||
purposes.
|
||||
|
||||
Note: Any option above modifies the default code-flow for your scan-
|
||||
ner. The options should only be used when you encounter problems
|
||||
with the default be- haviour of the backend. Please report the
|
||||
|
|
@ -157,9 +143,9 @@
|
|||
current working directory (".") and then in
|
||||
/usr/local/etc/sane.d. If the value of the environment variable
|
||||
ends with the directory separator character, then the default
|
||||
directories are searched after the explicitly specified directo-
|
||||
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
|
||||
would result in directories "tmp/config", ".", and
|
||||
directories are searched after the explicitly specified
|
||||
directories. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/con-
|
||||
fig:" would result in directories "tmp/config", ".", and
|
||||
"/usr/local/etc/sane.d" being searched (in this order).
|
||||
|
||||
<B>SANE_DEBUG_AVISION</B>
|
||||
|
|
@ -182,7 +168,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
René Rebe and Meino Christian Cramer
|
||||
|
||||
sane-backends 1.0.16 04 Mar 2003 <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B>
|
||||
sane-backends 1.0.17 04 Mar 2003 <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -34,11 +34,11 @@
|
|||
|
||||
If you have a Bell+Howell scanner and are able to test it with this
|
||||
backend, please contact <I>sane-devel@lists.alioth.debian.org</I> with the
|
||||
model number and testing results. Have a look at
|
||||
http://www.sane-project.org/mailing-lists.html concerning subscription
|
||||
to sane-devel. Additionally, the author is curious as to the likelihood
|
||||
of using this backend with the newer 4000 and 8000 series scanners. If
|
||||
you have such a beast, please let me know.
|
||||
model number and testing results. Have a look at http://www.sane-
|
||||
project.org/mailing-lists.html concerning subscription to sane-devel.
|
||||
Additionally, the author is curious as to the likelihood of using this
|
||||
backend with the newer 4000 and 8000 series scanners. If you have such
|
||||
a beast, please let me know.
|
||||
|
||||
The Bell+Howell Copiscan II series document scanners are high volume,
|
||||
high throughput scanners designed for document scanning applications.
|
||||
|
|
@ -486,8 +486,8 @@
|
|||
|
||||
If you have found something that you think is a bug, please attempt to
|
||||
recreate it with the SANE_DEBUG_BH environment variable set to 255, and
|
||||
send a report detailing the conditions surrounding the bug to
|
||||
<I>sane-devel@lists.alioth.debian.org</I>.
|
||||
send a report detailing the conditions surrounding the bug to <I>sane-</I>
|
||||
<I>devel@lists.alioth.debian.org</I>.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -502,7 +502,7 @@
|
|||
Reifschneider of tummy.com ltd. Some 8000 enhancements added by Mark
|
||||
Temple.
|
||||
|
||||
sane-backends 1.0.16 15 Sep 1999 <B><A HREF="sane-bh.5.html">sane-bh(5)</A></B>
|
||||
sane-backends 1.0.17 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.16 03 May 2001 <B><A HREF="sane-canon.5.html">sane-canon(5)</A></B>
|
||||
sane-backends 1.0.17 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.16 06 Apr 2002 <B><A HREF="sane-canon630u.5.html">sane-canon630u(5)</A></B>
|
||||
sane-backends 1.0.17 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.16 1 October 2002 <B><A HREF="sane-canon_pp.5.html">sane-canon_pp(5)</A></B>
|
||||
sane-backends 1.0.17 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.16 8 Jan 2004 <B><A HREF="sane-config.1.html">sane-config(1)</A></B>
|
||||
sane-backends 1.0.17 8 Jan 2004 <B><A HREF="sane-config.1.html">sane-config(1)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -131,7 +131,7 @@
|
|||
<H2>EMAIL-CONTACT</H2><PRE>
|
||||
andreas.rick@free.fr
|
||||
|
||||
sane-backends 1.0.16 4 July 2000 <B><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B>
|
||||
sane-backends 1.0.17 4 July 2000 <B><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -193,7 +193,7 @@
|
|||
The backend is written and maintained by András Major
|
||||
(andras@users.sourceforge.net).
|
||||
|
||||
sane-backends 1.0.16 22/08/2002 <B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B>
|
||||
sane-backends 1.0.17 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.16 15 July 2000 <B><A HREF="sane-dc210.5.html">sane-dc210(5)</A></B>
|
||||
sane-backends 1.0.17 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.16 23 March 2001 <B><A HREF="sane-dc240.5.html">sane-dc240(5)</A></B>
|
||||
sane-backends 1.0.17 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.16 12 April 1999 <B><A HREF="sane-dc25.5.html">sane-dc25(5)</A></B>
|
||||
sane-backends 1.0.17 12 April 1999 <B><A HREF="sane-dc25.5.html">sane-dc25(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -148,7 +148,7 @@
|
|||
David Mosberger
|
||||
|
||||
|
||||
sane-backends 1.0.16 4 Dec 2002 <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>
|
||||
sane-backends 1.0.17 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.16 13 May 1998 <B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B>
|
||||
sane-backends 1.0.17 13 May 1998 <B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -289,7 +289,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.16 27-Dec-2000 <B><A HREF="sane-epson.5.html">sane-epson(5)</A></B>
|
||||
sane-backends 1.0.17 27-Dec-2000 <B><A HREF="sane-epson.5.html">sane-epson(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -75,7 +75,7 @@
|
|||
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 available but the scanner
|
||||
itsself isn't.
|
||||
itself isn't.
|
||||
|
||||
<B>devname</B> Test device file "devname". No other devices are checked if
|
||||
devname is given.
|
||||
|
|
@ -120,7 +120,7 @@
|
|||
No support for most parallel port scanners yet.
|
||||
Detection of USB chipsets is limited to a few chipsets.
|
||||
|
||||
sane-backends 1.0.16 4 Oct 2004 <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>
|
||||
sane-backends 1.0.17 4 Oct 2004 <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -93,7 +93,7 @@
|
|||
brightness b
|
||||
Only supported for M3096
|
||||
|
||||
treshold t
|
||||
threshold t
|
||||
Only supported for M3096
|
||||
|
||||
duplex d
|
||||
|
|
@ -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.16 17 Apr 2002 <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>
|
||||
sane-backends 1.0.17 17 Apr 2002 <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -26,6 +26,7 @@
|
|||
Medion MD6228
|
||||
Medion MD6274
|
||||
Hewlett-Packard HP2300C
|
||||
Canon LiDE 35/40/50/60
|
||||
|
||||
This is BETA software. Especially if you test new or untested scanners,
|
||||
keep your hand at the scanner's plug and unplug it, if the head bumps
|
||||
|
|
@ -39,34 +40,33 @@
|
|||
from the models mentioned above, please let me know.
|
||||
|
||||
If you own a scanner that isn't detected by the genesys backend but has
|
||||
a GL646 or GL841 chipset, you can try to add it to the backend. Cur-
|
||||
rently, support for GL841 scanners is not implemented.
|
||||
a GL646 or GL841 chipset, you can try to add it to the backend.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>SYSTEM ISSUES</H2><PRE>
|
||||
This backend needs libusb-0.1.6 or later installed, and hasn't tested
|
||||
This backend needs libusb-0.1.6 or later installed, and hasn't tested
|
||||
in other configuration than a linux kernel 2.6.9 or higher. However, it
|
||||
should work any system with libusb where the SANE package can be com-
|
||||
piled. For setting permissions and general USB information look at
|
||||
should work any system with libusb where the SANE package can be com-
|
||||
piled. For setting permissions and general USB information look at
|
||||
<B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONFIGURATION</H2><PRE>
|
||||
The contents of the <I>genesys.conf</I> file is a list of usb lines containing
|
||||
vendor and product ids that correspond to USB scanners. The file can
|
||||
also contain option lines. Empty lines and lines starting with a hash
|
||||
mark (#) are ignored. The scanners are autodetected by <B>usb</B> <B>vendor_id</B>
|
||||
<B>product_id</B> statements which are already included into <I>genesys.conf</I> <I>.</I>
|
||||
"vendor_id" and "product_id" are hexadecimal numbers that identfy the
|
||||
vendor and product ids that correspond to USB scanners. The file can
|
||||
also contain option lines. Empty lines and lines starting with a hash
|
||||
mark (#) are ignored. The scanners are autodetected by <B>usb</B> <B>vendor_id</B>
|
||||
<B>product_id</B> statements which are already included into <I>genesys.conf</I>.
|
||||
"vendor_id" and "product_id" are hexadecimal numbers that identfy the
|
||||
scanner.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>FILES</H2><PRE>
|
||||
<I>/usr/local/etc/sane.d/genesys.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-genesys.a</I>
|
||||
|
|
@ -82,29 +82,36 @@
|
|||
<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_GENESYS</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
|
||||
available that are normally hidden. Handle them with care. This
|
||||
will print messages related to core genesys functions.
|
||||
<B>SANE_DEBUG_GENESYS_GL646</B> This environment variable controls the
|
||||
debug level for the specific GL646 code part.
|
||||
debug level is set to 1 or higher, some debug options become
|
||||
available that are normally hidden. Handle them with care. This
|
||||
will print messages related to core genesys functions.
|
||||
|
||||
Example (full and highly verbose output): export
|
||||
SANE_DEBUG_GENESYS=255 export SANE_DEBUG_GENESYS_GL646=255
|
||||
<B>SANE_DEBUG_GENESYS_GL646</B>
|
||||
This environment variable controls the debug level for the spe-
|
||||
cific GL646 code part.
|
||||
|
||||
<B>SANE_DEBUG_GENESYS_GL841</B>
|
||||
This environment variable controls the debug level for the spe-
|
||||
cific GL841 code part.
|
||||
|
||||
Example (full and highly verbose output for gl646):
|
||||
export SANE_DEBUG_GENESYS=255
|
||||
export SANE_DEBUG_GENESYS_GL646=255
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -125,7 +132,7 @@
|
|||
<H2>BUGS</H2><PRE>
|
||||
Support for buttons is missing.
|
||||
|
||||
sane-backends 1.0.16 3 July 2005 <B><A HREF="sane-genesys.5.html">sane-genesys(5)</A></B>
|
||||
sane-backends 1.0.17 20 Nov 2005 <B><A HREF="sane-genesys.5.html">sane-genesys(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.16 04 September 2001 <B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>
|
||||
sane-backends 1.0.17 04 September 2001 <B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@
|
|||
backend that provides access to USB flatbed scanners based on the
|
||||
Grandtech GT-6801 and GT-6816 chips. A list of supported scanners can
|
||||
be found on the gt68xx backend homepage: <I>http://www.meier-</I>
|
||||
<I>geinitz.de/sane/gt68xx/</I>.
|
||||
<I>geinitz.de/sane/gt68xx-backend/</I>.
|
||||
|
||||
This is BETA software. Especially if you test new or untested scanners,
|
||||
keep your hand at the scanner's plug and unplug it, if the head bumps
|
||||
|
|
@ -41,8 +41,8 @@
|
|||
|
||||
|
||||
</PRE>
|
||||
<H2>KERNEL ISSUES</H2><PRE>
|
||||
Please use libusb-0.1.6 or later. Without libusb or with older libusb
|
||||
<H2>LIBUSB ISSUES</H2><PRE>
|
||||
Please use libusb-0.1.8 or later. Without libusb or with older libusb
|
||||
versions all kinds of trouble can be expected. The scanner should be
|
||||
found by sane-find-scanner without further actions. For setting permis-
|
||||
sions and general USB information looks at <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>.
|
||||
|
|
@ -161,9 +161,9 @@
|
|||
|
||||
</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-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.16/gt68xx/gt68xx.CHANGES</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-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B> <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>, <B>sane-</B>
|
||||
<B><A HREF="ma1509.5.html">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.17/gt68xx/gt68xx.CHANGES</I>
|
||||
<I>http://www.meier-geinitz.de/sane/gt68xx</I>
|
||||
|
||||
|
||||
|
|
@ -177,10 +177,6 @@
|
|||
|
||||
</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
|
||||
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-
|
||||
|
|
@ -189,12 +185,12 @@
|
|||
Support for buttons is missing.
|
||||
|
||||
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
|
||||
page <I>http://www.meier-geinitz.de/sane/gt68xx-backend/</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
|
||||
SANE_DEBUG_GT68XX above).
|
||||
|
||||
sane-backends 1.0.16 29 May 2005 <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>
|
||||
sane-backends 1.0.17 29 September 2005 <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -45,8 +45,8 @@
|
|||
PhotoSmart C5100A R029,R030,R032 SCSI
|
||||
|
||||
Support for models 5100C/5200C connected to the parallel port requires
|
||||
the ppSCSI driver available at <I>http://www.torque.net/par-</I>
|
||||
<I>port/ppscsi.html</I> (under development)
|
||||
the ppSCSI driver available at <I>http://cyberelk.net/tim/par-</I>
|
||||
<I>port/ppscsi.html</I> and <I>http://penguin-breeder.org/kernel/download/</I>.
|
||||
|
||||
Support for models 5200C/62X0C/63X0C connected to the USB require the
|
||||
kernel scanner driver or libusb. See <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B> for more details.
|
||||
|
|
@ -60,8 +60,8 @@
|
|||
SCL (beside the OfficeJets), the above list of supported scanners is
|
||||
complete. Other HP scanners are not supported by the "hp" backend, but
|
||||
might be supported by another one. See <I>http://www.sane-project.org/</I>.
|
||||
You can also watch the sane-devel mailinglist at
|
||||
<I>http://www.sane-project.org/mailing-lists.html</I>.
|
||||
You can also watch the sane-devel mailinglist at <I>http://www.sane-</I>
|
||||
<I>project.org/mailing-lists.html</I>.
|
||||
|
||||
More details about the hp backend can be found on its homepage
|
||||
<I>http://www.kirchgessner.net/sane.html</I>.
|
||||
|
|
@ -217,9 +217,9 @@
|
|||
ADF and then change option scan source to 'ADF'. Press 'change
|
||||
document' to load a sheet. Then press 'scan' to start a scan.
|
||||
Maybe it is sufficient to press 'scan' without 'change document'
|
||||
for repeated scans. The use of the preview window is not recom-
|
||||
mended when working with the ADF. Setting a window to scan from
|
||||
ADF is not supported with <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>. Try <B><A HREF="xsane.1.html">xsane(1)</A></B>.
|
||||
for repeated scans. The use of the preview window is not
|
||||
recommended when working with the ADF. Setting a window to scan
|
||||
from ADF is not supported with <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>. Try <B><A HREF="xsane.1.html">xsane(1)</A></B>.
|
||||
|
||||
<B>Immediate</B> <B>actions</B>
|
||||
Some actions in <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B> (i.e. unload, select media, cali-
|
||||
|
|
@ -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.16 27 Mar 2004 <B><A HREF="sane-hp.5.html">sane-hp(5)</A></B>
|
||||
sane-backends 1.0.17 27 Mar 2004 <B><A HREF="sane-hp.5.html">sane-hp(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -114,7 +114,7 @@
|
|||
Send bug reports to the sane-devel mailing list: sane-
|
||||
devel@lists.alioth.debian.org.
|
||||
|
||||
sane-backends 1.0.16-cvs 14 August 2005 <B><A HREF="sane-hp4200.5.html">sane-hp4200(5)</A></B>
|
||||
sane-backends 1.0.17 14 August 2005 <B><A HREF="sane-hp4200.5.html">sane-hp4200(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.16 17 Apr 2003 <B><A HREF="sane-hp5400.5.html">sane-hp5400(5)</A></B>
|
||||
sane-backends 1.0.17 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.16 24 Feb 2002 <B><A HREF="sane-hpsj5s.5.html">sane-hpsj5s(5)</A></B>
|
||||
sane-backends 1.0.17 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.16 15 Apr 2003 <B><A HREF="sane-ibm.5.html">sane-ibm(5)</A></B>
|
||||
sane-backends 1.0.17 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.
|
||||
<I>http://www.zago.net/sane/#leo</I>
|
||||
|
||||
sane-backends 1.0.16 16 April 2002 <B><A HREF="sane-leo.5.html">sane-leo(5)</A></B>
|
||||
sane-backends 1.0.17 16 April 2002 <B><A HREF="sane-leo.5.html">sane-leo(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -0,0 +1,143 @@
|
|||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>sane-lexmark.5</TITLE>
|
||||
</HEAD>
|
||||
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="/images/sane.png" HEIGHT=117 WIDTH=346></H1>
|
||||
<H1>sane-lexmark.5</H1>
|
||||
<HR>
|
||||
<PRE>
|
||||
<!-- Manpage converted by man2html 3.0.1 -->
|
||||
<B><A HREF="sane-lexmark.5.html">sane-lexmark(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-lexmark.5.html">sane-lexmark(5)</A></B>
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>NAME</H2><PRE>
|
||||
sane-lexmark - SANE backend for Lexmark X1100 Series scanners
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>DESCRIPTION</H2><PRE>
|
||||
The <B>sane-lexmark</B> library implements a SANE (Scanner Access Now Easy)
|
||||
backend that provides access to the scanner part of Lexmark X1100 AIOs.
|
||||
This backend should be considered <B>beta-quality</B> software!
|
||||
|
||||
The scanners that should work with this backend are:
|
||||
|
||||
Vendor Model status
|
||||
---------------------- -----------
|
||||
Lexmark X1110 untested
|
||||
Lexmark X1140 untested
|
||||
Lexmark X1150 untested
|
||||
Lexmark X1170 untested
|
||||
Lexmark X1180 basic
|
||||
Lexmark X1185 basic
|
||||
|
||||
The options the backend supports can either be selected through command
|
||||
line options to programs like scanimage or through GUI elements in
|
||||
xscanimage or xsane.
|
||||
|
||||
If you have any strange behavior, please report to the backend main-
|
||||
tainer or to the SANE mailing list.
|
||||
|
||||
Valid command line options and their syntax can be listed by using
|
||||
scanimage --help -d lexmark:usb:<usb port>
|
||||
|
||||
<B>Scan</B> <B>Mode</B> <B>Options</B>
|
||||
|
||||
<B>--mode</B> selects the basic mode of operation of the scanner valid choices
|
||||
are <I>Color</I>, <I>Gray</I> and <I>Lineart</I> The default mode is Color. The Lin-
|
||||
eart mode is black and white only (1 bit). Grayscale will pro-
|
||||
duce 256 levels of gray (8 bits). Color mode allows for over 16
|
||||
million different colors produced from 24 bits of color informa-
|
||||
tion.
|
||||
|
||||
<B>--resolution</B>
|
||||
selects the resolution for a scan. The horizontal and vertical
|
||||
resolutions are set by the value of this option. The scanner is
|
||||
capable of the following resolutions for the specified option
|
||||
value:
|
||||
|
||||
Value Hor. Resolution Vert. Resolution
|
||||
----- --------------- -------------------
|
||||
75 75dpi 75dpi
|
||||
150 150dpi 150dpi
|
||||
300 300dpi 300dpi
|
||||
600 600dpi 600dpi
|
||||
1200 600dpi 1200dpi
|
||||
|
||||
<B>--preview</B>
|
||||
requests a preview scan. The resolution used for that scan is 75
|
||||
dpi and the scan area and the scan mode are as specified through
|
||||
their options, or the default if not specified. The default
|
||||
value for preview mode is "no".
|
||||
|
||||
|
||||
<B>--paper-size</B>
|
||||
selects the size of the area to be scanned. Valid sizes are <I>Wal-</I>
|
||||
<I>let</I>, <I>3x5</I>, <I>4x6</I>, <I>5x7</I>, <I>8x10</I>, <I>Letter</I>, the default size is 3x5.
|
||||
|
||||
<B>--threshold</B>
|
||||
selects the minimum-brightness to get a white point. The
|
||||
threshold is only used with Lineart mode scans. It is specified
|
||||
as a percentage in the range 0..100% (in steps of 1). The
|
||||
default value of the threshold option is 50.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONFIGURATION FILE</H2><PRE>
|
||||
The configuration file /usr/local/etc/sane.d/lexmark.conf contains only
|
||||
the usb device id (eg usb 0x043d 0x007c).
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>FILES</H2><PRE>
|
||||
<I>/usr/local/lib/sane/libsane-lexmark.a</I>
|
||||
The static library implementing this backend.
|
||||
|
||||
<I>/usr/local/lib/sane/libsane-lexmark.so</I>
|
||||
The shared library implementing this backend (present on systems
|
||||
that support dynamic loading).
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_DEBUG_LEXMARK</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.
|
||||
Smaller levels reduce verbosity.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>LIMITATIONS</H2><PRE>
|
||||
The windows TWAIN driver has many more options than this SANE backend.
|
||||
However they are only software adjustments. This backend only imple-
|
||||
ments what the scanner can support.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>BUGS</H2><PRE>
|
||||
Jerky movement on 600dpi gray 8x10 scan.
|
||||
Color calibration not implemented.
|
||||
Dark compensation not implemented.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane-scsi.5.html">sane-scsi(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><A HREF="sane.7.html">sane(7)</A></B>
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>AUTHOR</H2><PRE>
|
||||
The package is actively maintained by Fred Odendaal.
|
||||
<I>http://ca.geocities.com/freshshelf@rogers.com/</I>
|
||||
|
||||
sane-backends 1.0.17 02 September 2005 <B><A HREF="sane-lexmark.5.html">sane-lexmark(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
Man(1) output converted with
|
||||
<a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a>
|
||||
</ADDRESS>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
|
@ -55,7 +55,7 @@
|
|||
</PRE>
|
||||
<H2>CONFIGURATION</H2><PRE>
|
||||
The contents of the <I>ma1509.conf</I> file is a list of options and device
|
||||
names that correspond to Mustek BearPAw 1200F scanners. Empty lines
|
||||
names that correspond to Mustek BearPaw 1200F scanners. Empty lines
|
||||
and lines starting with a hash mark (#) are ignored.
|
||||
|
||||
Instead of using the device name, the scanner can be autodetected by
|
||||
|
|
@ -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.16 24 Feb 2003 <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>
|
||||
sane-backends 1.0.17 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.
|
||||
<I>http://www.zago.net/sane/#matsushita</I>
|
||||
|
||||
sane-backends 1.0.16 February 11th, 2004 <B><A HREF="sane-matsushita.5.html">sane-matsushita(5)</A></B>
|
||||
sane-backends 1.0.17 February 11th, 2004 <B><A HREF="sane-matsushita.5.html">sane-matsushita(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -163,10 +163,10 @@
|
|||
|
||||
More general comments, suggestions, and inquiries about frontends or
|
||||
SANE should go to <B>sane-devel@lists.alioth.debian.org</B>, the SANE Develop-
|
||||
ers mailing list. Have a look at http://www.sane-project.org/mail-
|
||||
ing-lists.html concerning subscription to sane-devel.
|
||||
ers mailing list. Have a look at http://www.sane-project.org/mailing-
|
||||
lists.html concerning subscription to sane-devel.
|
||||
|
||||
sane-backends 1.0.16 February 8, 2000 <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B>
|
||||
sane-backends 1.0.17 February 8, 2000 <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -54,60 +54,61 @@
|
|||
of the above.
|
||||
|
||||
The parport scanners work with the ppscsi + onscsi kernel modules. See
|
||||
<B>http://www.torque.net/parport/ppscsi.html</B>
|
||||
<I>http://cyberelk.net/tim/parport/ppscsi.html</I> and <I>http://penguin-</I>
|
||||
<I>breeder.org/kernel/download/</I>.
|
||||
|
||||
The USB scanners work with the microtek kernel module. You may have to
|
||||
add the vendor and model codes to microtek.c if they aren't yet listed
|
||||
The USB scanners work with the microtek kernel module. You may have to
|
||||
add the vendor and model codes to microtek.c if they aren't yet listed
|
||||
there.
|
||||
|
||||
Both parport and USB scanners need the generic SCSI support, so check
|
||||
Both parport and USB scanners need the generic SCSI support, so check
|
||||
if you have loaded the scsi_mod and sg modules!
|
||||
|
||||
If you try your scanner for the first time keep an eye on it. If it
|
||||
If you try your scanner for the first time keep an eye on it. If it
|
||||
gets commands that it doesn't understand the scanhead may go beyond the
|
||||
scan area. The scanner then makes strange noises. In this case imme-
|
||||
dieately switch off the scanner or disconnect its power cable to pre-
|
||||
scan area. The scanner then makes strange noises. In this case imme-
|
||||
dieately switch off the scanner or disconnect its power cable to pre-
|
||||
vent damages!
|
||||
|
||||
If your scanner is a different one than the models mentioned above and
|
||||
it is working please tell the author about it. It would be nice if you
|
||||
If your scanner is a different one than the models mentioned above and
|
||||
it is working please tell the author about it. It would be nice if you
|
||||
add a logfile to this information (creation of the logfile: see below).
|
||||
|
||||
If your scanner is not working properly you also should create a log-
|
||||
file and send it to the author. He will use the information to improve
|
||||
If your scanner is not working properly you also should create a log-
|
||||
file and send it to the author. He will use the information to improve
|
||||
the backend and possibly make your scanner work.
|
||||
|
||||
How to create the logfile?
|
||||
|
||||
- put the line
|
||||
"option dump 2" into your <I>microtek2.conf</I> file or change the
|
||||
"option dump 2" into your <I>microtek2.conf</I> file or change the
|
||||
existing "option dump" to "2"
|
||||
|
||||
- in a terminal (bash) type
|
||||
"export SANE_DEBUG_MICROTEK2=30" and then
|
||||
"scanimage -l0 -t0 -x100 -y20 2>scan.log >sout.pnm"
|
||||
You get two files: scan.log contains the logfile and sout.pnm
|
||||
the scanned image (if there was scanned something). Zip them
|
||||
You get two files: scan.log contains the logfile and sout.pnm
|
||||
the scanned image (if there was scanned something). Zip them
|
||||
before sending.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>FRONTEND OPTIONS</H2><PRE>
|
||||
This backend dynamically enables the options for the frontend, that are
|
||||
supported by the scanner in dependence of the scanning-mode and other
|
||||
supported by the scanner in dependence of the scanning-mode and other
|
||||
options. Not supported options are disabled.
|
||||
|
||||
The following options are supported by the Microtek2-driver:
|
||||
|
||||
Color, grayscale, halftone and lineart scans.
|
||||
|
||||
Highlight, midtone, shadow, contrast, brightness, exposure time con-
|
||||
trol, gamma correction, threshold (dependent of the scan mode and the
|
||||
Highlight, midtone, shadow, contrast, brightness, exposure time con-
|
||||
trol, gamma correction, threshold (dependent of the scan mode and the
|
||||
scanner capabilities)
|
||||
|
||||
Transparency media adapter, automatic document feeder
|
||||
|
||||
Additional options can be enabled or disabled in the <I>microtek2.conf</I>
|
||||
Additional options can be enabled or disabled in the <I>microtek2.conf</I>
|
||||
file. See the configuration section of this manpage.
|
||||
|
||||
|
||||
|
|
@ -117,9 +118,9 @@
|
|||
|
||||
<I>special</I>
|
||||
|
||||
Where <I>special</I> is the UNIX path-name for the special device that corre-
|
||||
sponds to the scanner. The special device name must be a generic SCSI
|
||||
device or a symlink to such a device. Under Linux, such a device name
|
||||
Where <I>special</I> is the UNIX path-name for the special device that corre-
|
||||
sponds to the scanner. The special device name must be a generic SCSI
|
||||
device or a symlink to such a device. Under Linux, such a device name
|
||||
could be <I>/dev/sga</I> or <I>/dev/sge</I> for example.
|
||||
|
||||
|
||||
|
|
@ -128,16 +129,16 @@
|
|||
The configuration file for this backend resides in
|
||||
<I>/usr/local/etc/sane.d/microtek2.conf</I>.
|
||||
|
||||
Its contents is a list of device names that correspond to Microtek
|
||||
scanners with SCSI-2 interface. Empty lines and lines starting with a
|
||||
Its contents is a list of device names that correspond to Microtek
|
||||
scanners with SCSI-2 interface. Empty lines and lines starting with a
|
||||
hash mark (#) are ignored.
|
||||
|
||||
The configuration file may also contain options. Global options that
|
||||
are valid for all devices are placed above the device names. Device-
|
||||
specific options are placed under the device name. Note that, except
|
||||
for option dump <n> and option strip-height <n>, the entry in the
|
||||
microtek2.conf file only enables the corresponding option for being
|
||||
showed in the frontend. There, in the frontend, you can switch the
|
||||
The configuration file may also contain options. Global options that
|
||||
are valid for all devices are placed above the device names. Device-
|
||||
specific options are placed under the device name. Note that, except
|
||||
for option dump <n> and option strip-height <n>, the entry in the
|
||||
microtek2.conf file only enables the corresponding option for being
|
||||
showed in the frontend. There, in the frontend, you can switch the
|
||||
options on and off. Currently the following options are supported:
|
||||
|
||||
option dump <n>
|
||||
|
|
@ -149,29 +150,29 @@
|
|||
option backend-calibration <on/off>
|
||||
option colorbalance-adjust <on/off>
|
||||
|
||||
<I>option</I> <I>dump</I> <I><n></I> enables printing of additional information about the
|
||||
SCSI commands that are sent to the scanner to stderr. This option is
|
||||
primarily useful for debugging purpose. This option has to be a global
|
||||
<I>option</I> <I>dump</I> <I><n></I> enables printing of additional information about the
|
||||
SCSI commands that are sent to the scanner to stderr. This option is
|
||||
primarily useful for debugging purpose. This option has to be a global
|
||||
option and is best placed at the top of the <I>microtek2.conf</I> file.
|
||||
|
||||
If n=1 the contents of the command blocks and the results for the
|
||||
If n=1 the contents of the command blocks and the results for the
|
||||
INQUIRY and READ SCANNER ATTRIBUTES command are printed to stderr.
|
||||
|
||||
If n=2 the contents of the command blocks for all other SCSI commands
|
||||
are printed to stderr, too. If n=3 the contents of the gamma table is
|
||||
If n=2 the contents of the command blocks for all other SCSI commands
|
||||
are printed to stderr, too. If n=3 the contents of the gamma table is
|
||||
printed, too. If n=4 all scan data is additionally printed to stderr.
|
||||
|
||||
The default is n=1.
|
||||
|
||||
<I>option</I> <I>strip-height</I> <I><n></I> , where <n> is a floating point number, limits
|
||||
<I>option</I> <I>strip-height</I> <I><n></I> , where <n> is a floating point number, limits
|
||||
the amount of data that is read from the scanner with one read command.
|
||||
The unit is inch and <n> defaults to 1.0, if this option is not set in
|
||||
The unit is inch and <n> defaults to 1.0, if this option is not set in
|
||||
the configuration file. If less than <n> inch of data fit into the SCSI
|
||||
buffer, then the smaller value is used and this option has no effect.
|
||||
|
||||
If your system has a big SCSI buffer and you want to make use of the
|
||||
If your system has a big SCSI buffer and you want to make use of the
|
||||
whole buffer, increase the value for <n>. For example, if <n> is set to
|
||||
14.0, no restrictions apply for scanners with a letter, legal or A4
|
||||
14.0, no restrictions apply for scanners with a letter, legal or A4
|
||||
sized scan area.
|
||||
|
||||
The following options enable or disable additional frontend options. If
|
||||
|
|
@ -179,26 +180,26 @@
|
|||
tend.
|
||||
|
||||
<I>option</I> <I>no-backtrack-option</I> <I><on/off></I> prevents the scanner head from mov-
|
||||
ing backwards between the read commands. This speeds up scanning. Try
|
||||
ing backwards between the read commands. This speeds up scanning. Try
|
||||
it.
|
||||
|
||||
<I>option</I> <I>lightlid-35</I> <I><on/off></I> If you use the LightLid-35 transparency
|
||||
adapter you get an advanced option which switches off the flatbed lamp
|
||||
<I>option</I> <I>lightlid-35</I> <I><on/off></I> If you use the LightLid-35 transparency
|
||||
adapter you get an advanced option which switches off the flatbed lamp
|
||||
during the scan.
|
||||
|
||||
<I>option</I> <I>toggle-lamp</I> <I><on/off></I> You get a button in the frontend where you
|
||||
<I>option</I> <I>toggle-lamp</I> <I><on/off></I> You get a button in the frontend where you
|
||||
can switch on and off the flatbed lamp.
|
||||
|
||||
<I>option</I> <I>lineart-autoadjust</I> <I><on/off></I> You can tell the backend to try to
|
||||
<I>option</I> <I>lineart-autoadjust</I> <I><on/off></I> You can tell the backend to try to
|
||||
determine a good value for the lineart threshold.
|
||||
|
||||
<I>option</I> <I>backend-calibration</I> <I><on/off></I> Some scanners (e.g. Phantom 330CX
|
||||
and 636CX) need to have calibrated the data by the backend. Try this
|
||||
<I>option</I> <I>backend-calibration</I> <I><on/off></I> Some scanners (e.g. Phantom 330CX
|
||||
and 636CX) need to have calibrated the data by the backend. Try this
|
||||
option if you see vertical stripes in your pictures.
|
||||
|
||||
<I>option</I> <I>colorbalance-adjust</I> <I><on/off></I> Some scanners (e.g. Phantom 330CX
|
||||
and 636CX) need to have corrected the color balance. If this option is
|
||||
enabled you get advanced options where you can balance the colors. And
|
||||
<I>option</I> <I>colorbalance-adjust</I> <I><on/off></I> Some scanners (e.g. Phantom 330CX
|
||||
and 636CX) need to have corrected the color balance. If this option is
|
||||
enabled you get advanced options where you can balance the colors. And
|
||||
you will have a button to use the values that the firmware of the scan-
|
||||
ner provides.
|
||||
|
||||
|
|
@ -212,9 +213,9 @@
|
|||
/dev/sge
|
||||
option lightlid-35 on
|
||||
|
||||
This backend also supports the new configuration file format which
|
||||
makes it easier to detect scanners under Linux. If you have only one
|
||||
scanner it would be best to use the following configuration file for
|
||||
This backend also supports the new configuration file format which
|
||||
makes it easier to detect scanners under Linux. If you have only one
|
||||
scanner it would be best to use the following configuration file for
|
||||
this backend:
|
||||
|
||||
option dump 1
|
||||
|
|
@ -251,11 +252,11 @@
|
|||
</PRE>
|
||||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_DEBUG_MICROTEK2</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 255 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 255 requests all debug output to be printed.
|
||||
Smaller levels reduce verbosity. To see error messages on stderr
|
||||
set SANE_DEBUG_MICROTEK2 to 1 (Remark: The whole debugging lev-
|
||||
set SANE_DEBUG_MICROTEK2 to 1 (Remark: The whole debugging lev-
|
||||
els should be better revised).
|
||||
E.g. just say:
|
||||
export SANE_DEBUG_MICROTEK2=128
|
||||
|
|
@ -271,7 +272,7 @@
|
|||
Bernd Schroeder (not active anymore)
|
||||
Karsten Festag karsten.festag@gmx.de
|
||||
|
||||
sane-backends 1.0.16 28 Jan 2002 <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B>
|
||||
sane-backends 1.0.17 28 Jan 2002 <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -70,17 +70,17 @@
|
|||
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.16/PROBLEMS</I> file.
|
||||
the <I>/usr/local/doc/sane-1.0.17/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-
|
||||
ner's exact model name (look at the front and back of the scanner) and
|
||||
a debug output to <I>sane-devel@lists.alioth.debian.org</I>. You can get the
|
||||
debug output by setting the environment variable <B>SANE_DEBUG_MUSTEK</B> to 5
|
||||
and showing the list of available scanners with scanimage -L . Please
|
||||
and showing the list of available scanners with scanimage -L. Please
|
||||
send all of it to the mailing list. You must be subscribed to sane-
|
||||
devel before you can send mail to the list. See
|
||||
<I>http://www.sane-project.org/mailing-lists.html</I> for details.
|
||||
devel before you can send mail to the list. See <I>http://www.sane-</I>
|
||||
<I>project.org/mailing-lists.html</I> for details.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -235,35 +235,36 @@
|
|||
These scanners can be configured by listing the port number of the
|
||||
adapter or the parallel port in the mustek.conf file. Valid port num-
|
||||
bers for the 600 II N are <I>0x26b</I>, <I>0x2ab</I>, <I>0x2eb</I>, <I>0x22b</I>, <I>0x32b</I>, <I>0x36b</I>,
|
||||
<I>0x3ab</I>, <I>0x3eb</I>. For the 600 II EP use one of these: <I>0x378</I>, <I>0x278</I>, <I>0x3bc</I>.
|
||||
Pick one that doesn't conflict with the other hardware in your com-
|
||||
puter. Put only one number on a single line. Example:
|
||||
<I>0x3ab</I>, <I>0x3eb</I>. For the 600 II EP use one of these: <I>parport0</I>, <I>parport1</I>,
|
||||
<I>parport2</I>, <I>0x378</I>, <I>0x278</I>, <I>0x3bc</I>. Pick one that doesn't conflict with the
|
||||
other hardware in your computer. Put only one number on a single line.
|
||||
Example:
|
||||
|
||||
<I>0x3eb</I>
|
||||
|
||||
Note that for these scanners usually root privileges are required to
|
||||
Note that for these scanners usually root privileges are required to
|
||||
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
|
||||
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.8.html">saned(8)</A></B>.
|
||||
|
||||
If the Mustek backend blocks while sending the inqiury command to the
|
||||
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>.
|
||||
|
||||
Also note that after a while of no activity, some scanners themselves
|
||||
Also note that after a while of no activity, some scanners themselves
|
||||
(not the SANE backend) turns off their CCFL lamps. This shutdown is not
|
||||
always perfect with the result that the lamp sometimes continues to
|
||||
glow dimly at one end. This doesn't appear to be dangerous since as
|
||||
always perfect with the result that the lamp sometimes continues to
|
||||
glow dimly at one end. This doesn't appear to be dangerous since as
|
||||
soon as you use the scanner again, the lamp turns back on to the normal
|
||||
high brightness. However, the first image scanned after such a shutdown
|
||||
may have stripes and appear to be over-exposed. When this happens,
|
||||
may have stripes and appear to be over-exposed. When this happens,
|
||||
just take another scan, and the image will be fine.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>FILES</H2><PRE>
|
||||
<I>/usr/local/etc/sane.d/mustek.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-mustek.a</I>
|
||||
|
|
@ -279,20 +280,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
|
||||
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
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the
|
||||
configuration 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_MUSTEK</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.
|
||||
|
||||
Value Description
|
||||
|
|
@ -308,15 +309,15 @@
|
|||
|
||||
</PRE>
|
||||
<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="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.16/mustek/mustek.CHANGES</I>
|
||||
<I>/usr/local/doc/sane-1.0.17/mustek/mustek.CHANGES</I>
|
||||
<I>http://www.meier-geinitz.de/sane/mustek-backend/</I>
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>AUTHOR</H2><PRE>
|
||||
David Mosberger, Andreas Czechanowski, Andreas Bolsch (SE extensions),
|
||||
David Mosberger, Andreas Czechanowski, Andreas Bolsch (SE extensions),
|
||||
Henning Meier-Geinitz, James Perry (600 II EP).
|
||||
|
||||
|
||||
|
|
@ -327,13 +328,13 @@
|
|||
|
||||
Some scanners (e.g. Paragon 1200 A3 + Pro, SE A3) need more testing.
|
||||
|
||||
The gamma table supports only 256 colors, even if some scanners can do
|
||||
The gamma table supports only 256 colors, even if some scanners can do
|
||||
more.
|
||||
|
||||
More detailed bug information is available at the Mustek backend home-
|
||||
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.16 25 Dec 2002 <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>
|
||||
sane-backends 1.0.17 18 Sep 2005 <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -65,43 +65,48 @@
|
|||
Funline TS6EP 600 CP yes
|
||||
Trust
|
||||
Easy Connect 9600+ 600 CP yes
|
||||
Cybercom
|
||||
9352 1200 CP yes (***)
|
||||
|
||||
(*) Calibration problems existed with earlier version of this
|
||||
(*) Calibration problems existed with earlier version of this
|
||||
driver. They seem to be solved now.
|
||||
|
||||
(**) Problems have been reported in the past for the MD/LT9850 type
|
||||
(striped scans, head moving in wrong direction at some resolu-
|
||||
tions). It is not known whether the current version of the
|
||||
(striped scans, head moving in wrong direction at some
|
||||
resolutions). It is not known whether the current version of the
|
||||
driver still has these problems.
|
||||
<B>IF</B> <B>YOU</B> <B>HEAR</B> <B>LOUD</B> <B>CLICKING</B> <B>NOISES,</B> <B>IMMEDIATELY</B> <B>UNPLUG</B> <B>THE</B> <B>SCANNER</B>
|
||||
<B>!</B> (This holds for any type of scanner).
|
||||
|
||||
(***) Possibly, the engine_delay parameter has to be set to 1 ms for
|
||||
accurate engine movements.
|
||||
|
||||
Please note that this backend is still under construction. Certain mod-
|
||||
els are currently not supported and some may never be because the com-
|
||||
els are currently not supported and some may never be because the com-
|
||||
munication protocol is still unknown (eg., SE 12000 P).
|
||||
|
||||
Some scanners work faster when <B>EPP/ECP</B> is enabled in the BIOS. EPP mode
|
||||
however may lead to hard-locks on some Linux systems. If that is the
|
||||
however may lead to hard-locks on some Linux systems. If that is the
|
||||
case for you, you can either disable ECP/EPP in your BIOS or disable it
|
||||
in the backend itself (see GLOBAL OPTIONS).
|
||||
|
||||
Note that the backend needs to run as root or has to have appropriate
|
||||
access rights to /dev/parport* if libieee1284 support is compiled in.
|
||||
Note that the backend needs to run as root or has to have appropriate
|
||||
access rights to /dev/parport* if libieee1284 support is compiled in.
|
||||
To allow user access to the 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>sharing</I>, i.e. if you try printing while scan-
|
||||
ning, your computer may crash. To enable parport sharing, you have to
|
||||
enable libieee1284 at compile time. This backend also conflicts with
|
||||
the <I>sane-musteka4s2</I> backend. You can only enable one of them in your
|
||||
dll.conf. However, you have to enable the backend explicitly in your
|
||||
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>sharing</I>, i.e. if you try printing while scan-
|
||||
ning, your computer may crash. To enable parport sharing, you have to
|
||||
enable libieee1284 at compile time. This backend also conflicts with
|
||||
the <I>sane-musteka4s2</I> backend. You can only enable one of them in your
|
||||
dll.conf. However, you have to enable the backend explicitly in your
|
||||
dll.conf, just remove the hash mark in the line "mustek_pp".
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>DEVICE DEFINITION</H2><PRE>
|
||||
This backend allows multiple devices being defined and configured via
|
||||
the <B>mustek_pp.conf</B> file (even simultaneously, provided that they are
|
||||
connected to different parallel ports). Please make sure to edit this
|
||||
This backend allows multiple devices being defined and configured via
|
||||
the <B>mustek_pp.conf</B> file (even simultaneously, provided that they are
|
||||
connected to different parallel ports). Please make sure to edit this
|
||||
file <B>before</B> you use the backend.
|
||||
|
||||
A device can be defined as follows:
|
||||
|
|
@ -113,26 +118,26 @@
|
|||
<B><name></B> is an arbitrary name for the device, optionally enclosed by dou-
|
||||
ble quotes, for instance "LifeTec 9350".
|
||||
|
||||
<B><port</B> <B>name></B> is the name of the parallel port to which the device is
|
||||
connected. In case libieee1284 is used for communication with
|
||||
the port <I>(default</I> <I>setup)</I>, valid port names are <B>parport0</B>, <B>par-</B>
|
||||
<B><port</B> <B>name></B> is the name of the parallel port to which the device is
|
||||
connected. In case libieee1284 is used for communication with
|
||||
the port <I>(default</I> <I>setup)</I>, valid port names are <B>parport0</B>, <B>par-</B>
|
||||
<B>port1</B>, and <B>parport2</B>.
|
||||
|
||||
In case the backend is configured for raw IO <I>(old</I> <I>setup)</I>, port
|
||||
addresses have to be used instead of port names: <B>0x378</B>, <B>0x278</B>,
|
||||
or <B>0x3BC</B>. The mapping of parallel ports (lp0, lp1, and lp2) to
|
||||
In case the backend is configured for raw IO <I>(old</I> <I>setup)</I>, port
|
||||
addresses have to be used instead of port names: <B>0x378</B>, <B>0x278</B>,
|
||||
or <B>0x3BC</B>. The mapping of parallel ports (lp0, lp1, and lp2) to
|
||||
these addresses can be different for different Linux kernel ver-
|
||||
sions. For instance, if you are using a Kernel 2.2.x or better
|
||||
and you have only one parallel port, this port is named lp0
|
||||
regardless of the base address. However, this backend requires
|
||||
the base address of your port. If you are not sure which port
|
||||
sions. For instance, if you are using a Kernel 2.2.x or better
|
||||
and you have only one parallel port, this port is named lp0
|
||||
regardless of the base address. However, this backend requires
|
||||
the base address of your port. If you are not sure which port
|
||||
your scanner is connected to, have a look at your /etc/conf.mod-
|
||||
ules, /etc/modules.conf and/or /proc/ioports.
|
||||
|
||||
If you are unsure which port to use, you can use the magic value
|
||||
<B>*</B> to probe for your scanner.
|
||||
|
||||
<B><driver></B> is the driver to use for this device. Currently available
|
||||
<B><driver></B> is the driver to use for this device. Currently available
|
||||
drivers are:
|
||||
|
||||
<B>cis600</B> : for 600 CP, 96 CP & OEM versions
|
||||
|
|
@ -142,16 +147,16 @@
|
|||
|
||||
<B>Choosing</B> <B>the</B> <B>wrong</B> <B>driver</B> <B>can</B> <B>damage</B> <B>your</B> <B>scanner!</B>
|
||||
Especially, using the 1200CP settings on a 600CP can be harmful.
|
||||
If the scanner starts making a loud noice, turn it off immedi-
|
||||
If the scanner starts making a loud noice, turn it off immedi-
|
||||
ately !!!
|
||||
Using the cis600 driver on a 1200CP or a 1200CP+ is probably not
|
||||
dangerous. The cis1200+ driver also works for the 1200CP, and
|
||||
using the cis1200 driver on a 1200CP+ will typically result in
|
||||
scans that cover only half of the width of the scan area (also
|
||||
dangerous. The cis1200+ driver also works for the 1200CP, and
|
||||
using the cis1200 driver on a 1200CP+ will typically result in
|
||||
scans that cover only half of the width of the scan area (also
|
||||
not dangerous).
|
||||
If unsure about the exact model of your OEM version, check the
|
||||
optical resolution in the manual or on the box: the 600CP has a
|
||||
maximum optical resolution of 300x600 DPI, whereas the 1200CP
|
||||
If unsure about the exact model of your OEM version, check the
|
||||
optical resolution in the manual or on the box: the 600CP has a
|
||||
maximum optical resolution of 300x600 DPI, whereas the 1200CP
|
||||
and 1200CP+ have a maximum optical resolution of 600x1200 DPI.
|
||||
|
||||
Examples:
|
||||
|
|
@ -162,8 +167,8 @@
|
|||
|
||||
scanner Mustek_600IIIEP * ccd300
|
||||
|
||||
If in doubt which port you have to use, or whether your scanner is
|
||||
detected at all, you can use <B>sane-find-scanner</B> <B>-p</B> to probe all config-
|
||||
If in doubt which port you have to use, or whether your scanner is
|
||||
detected at all, you can use <B>sane-find-scanner</B> <B>-p</B> to probe all config-
|
||||
ured ports.
|
||||
|
||||
|
||||
|
|
@ -171,20 +176,20 @@
|
|||
<H2>CONFIGURATION</H2><PRE>
|
||||
The contents of the <B>mustek_pp.conf</B> file is a list of device definitions
|
||||
and device options that correspond to Mustek scanners. Empty lines and
|
||||
lines starting with a hash mark (#) are ignored. Options have the fol-
|
||||
lines starting with a hash mark (#) are ignored. Options have the fol-
|
||||
lowing format:
|
||||
|
||||
<I>option</I> <I><name></I> <I>[<value>]</I>
|
||||
|
||||
Depending on the nature of the option, a value may or may not be
|
||||
present. Options always apply to the scanner definition that preceeds
|
||||
them. There are no global options. Options are also driver-specific:
|
||||
Depending on the nature of the option, a value may or may not be
|
||||
present. Options always apply to the scanner definition that preceeds
|
||||
them. There are no global options. Options are also driver-specific:
|
||||
not all drivers support all possible options.
|
||||
|
||||
<B>Common</B> <B>options</B>
|
||||
|
||||
<B>bw</B> <B><value></B> Black/white discrimination value to be used during lin-
|
||||
eart scanning. Pixel values below this value are assumed to
|
||||
<B>bw</B> <B><value></B> Black/white discrimination value to be used during lin-
|
||||
eart scanning. Pixel values below this value are assumed to
|
||||
be black, values above are assumed to be white.
|
||||
Default value: 127
|
||||
Minimum: 0
|
||||
|
|
@ -194,12 +199,12 @@
|
|||
|
||||
<B>CIS</B> <B>driver</B> <B>options</B>
|
||||
|
||||
<B>top_adjust</B> <B><value></B> Vertical adjustment of the origin, expressed in
|
||||
millimeter (floating point). This option can be used to
|
||||
<B>top_adjust</B> <B><value></B> Vertical adjustment of the origin, expressed in
|
||||
millimeter (floating point). This option can be used to
|
||||
calibrate the position of the origin, within certain limits.
|
||||
Note that CIS scanners are probably temperature sensitive,
|
||||
and that a certain inaccuracy may be hard to avoid. Differ-
|
||||
ences in offset between runs in the order of 1 to 2 mm are
|
||||
Note that CIS scanners are probably temperature sensitive,
|
||||
and that a certain inaccuracy may be hard to avoid. Differ-
|
||||
ences in offset between runs in the order of 1 to 2 mm are
|
||||
not unusual.
|
||||
Default value: 0.0
|
||||
Minimum: -5.0
|
||||
|
|
@ -207,19 +212,42 @@
|
|||
|
||||
Example: option top_adjust -2.5
|
||||
|
||||
<B>slow_skip</B> Turns fast skipping to the start of the scan region off.
|
||||
When the region to scan does not start at the origin, the
|
||||
driver will try to move the scanhead to the start of the
|
||||
scan area at the fastest possible speed. On some models,
|
||||
this may not work, resulting in large inaccuracies (up to
|
||||
centimeters). By setting this option, the driver is forced
|
||||
to use normal speed during skipping, which can circumvent
|
||||
the accuracy problems. Currently, there are no models for
|
||||
<B>slow_skip</B> Turns fast skipping to the start of the scan region off.
|
||||
When the region to scan does not start at the origin, the
|
||||
driver will try to move the scanhead to the start of the
|
||||
scan area at the fastest possible speed. On some models,
|
||||
this may not work, resulting in large inaccuracies (up to
|
||||
centimeters). By setting this option, the driver is forced
|
||||
to use normal speed during skipping, which can circumvent
|
||||
the accuracy problems. Currently, there are no models for
|
||||
which these inaccuracy problems are known to occur.
|
||||
By default, fast skipping is used.
|
||||
|
||||
Example: option slow_skip
|
||||
|
||||
<B>engine_delay</B> <B><value></B> Under normal circumstances, it is sufficient
|
||||
for the driver to wait for the scanner signaling that the
|
||||
engine is stable, before a new engine command can be trans-
|
||||
mitted. In rare cases, certain scanners and/or parallel port
|
||||
chipsets appear to prevent reliable detection of the engine
|
||||
state. As a result, engine commands are transmitted too soon
|
||||
and the movement of the scanner head becomes unreliable.
|
||||
Inaccuracies ranging up to 10 cm over the whole vertical
|
||||
scan range have been reported. To work around this problem,
|
||||
the engine_delay option can be set. If it is set, the driver
|
||||
waits an additional amount of time after every engine com-
|
||||
mand, equal to the engine_delay parameter, expressed in mil-
|
||||
liseconds. It practice an engine_delay of 1 ms is usually
|
||||
sufficient. The maximum delay is 100 ms.
|
||||
Note that every additional ms of delay can add up to 14 sec-
|
||||
onds to the total scanning time (highest resolution), so an
|
||||
as small as possible value is prefered.
|
||||
Default value: 0
|
||||
Minimum: 0
|
||||
Maximum: 100
|
||||
|
||||
Example: option engine_delay 1
|
||||
|
||||
<B>CCD</B> <B>driver</B> <B>options</B>
|
||||
|
||||
<B>top</B> <B><value></B> Number of scanlines to skip to the start of the scan
|
||||
|
|
@ -377,10 +405,10 @@
|
|||
|
||||
</PRE>
|
||||
<H2>BUGS</H2><PRE>
|
||||
Too many... please send bug reports to
|
||||
<I>sane-devel@lists.alioth.debian.org</I> (note that you have to subscribe
|
||||
first to the list before you can send emails... see
|
||||
http://www.sane-project.org/mailing-lists.html)
|
||||
Too many... please send bug reports to <I>sane-</I>
|
||||
<I>devel@lists.alioth.debian.org</I> (note that you have to subscribe first to
|
||||
the list before you can send emails... see http://www.sane-
|
||||
project.org/mailing-lists.html)
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
|
|||
|
|
@ -148,8 +148,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.16/mustek</I><B>_</B><I>usb/mustek</I><B>_</B><I>usb.CHANGES</I>,
|
||||
<I>/usr/local/doc/sane-1.0.16/mustek</I><B>_</B><I>usb/mustek</I><B>_</B><I>usb.TODO</I>
|
||||
<I>/usr/local/doc/sane-1.0.17/mustek</I><B>_</B><I>usb/mustek</I><B>_</B><I>usb.CHANGES</I>,
|
||||
<I>/usr/local/doc/sane-1.0.17/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>
|
||||
|
||||
|
||||
|
|
@ -175,7 +175,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.16 3 Mar 2004 <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>
|
||||
sane-backends 1.0.17 3 Mar 2004 <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -0,0 +1,114 @@
|
|||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>sane-mustek_usb2.5</TITLE>
|
||||
</HEAD>
|
||||
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="/images/sane.png" HEIGHT=117 WIDTH=346></H1>
|
||||
<H1>sane-mustek_usb2.5</H1>
|
||||
<HR>
|
||||
<PRE>
|
||||
<!-- Manpage converted by man2html 3.0.1 -->
|
||||
<B><A HREF="sane-mustek_usb2.5.html">sane-mustek_usb2(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-mustek_usb2.5.html">sane-mustek_usb2(5)</A></B>
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>NAME</H2><PRE>
|
||||
sane-mustek_usb2 - SANE backend for SQ113 based USB flatbed scanners
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>DESCRIPTION</H2><PRE>
|
||||
The <B>sane-mustek_usb2</B> library implements a SANE (Scanner Access Now
|
||||
Easy) backend that provides access to USB flatbed scanners based on the
|
||||
Service & Quality SQ113 chipset. At the moment, only the Mustek BearPaw
|
||||
2448 TA Pro is supported. It's planned to add support for other scan-
|
||||
ners that are based on the SQ113 and maybe SQ11 chip. For more details,
|
||||
see the mustek_usb2 backend homepage: <I>http://www.meier-</I>
|
||||
<I>geinitz.de/sane/mustek</I><B>_</B><I>usb2-backend/</I>.
|
||||
|
||||
This is BETA software. Especially if you test new or untested scanners,
|
||||
keep your hand at the scanner's plug and unplug it, if the head bumps
|
||||
at the end of the scan area.
|
||||
|
||||
If you own a scanner other than the ones listed on the mustek_usb2
|
||||
homepage that works with this backend, please let me know this by send-
|
||||
ing the scanner's exact model name and the USB vendor and device ids
|
||||
(e.g. from <I>sane-find-scanner</I> or syslog) to me. Even if the scanner's
|
||||
name is only slightly different from the models already listed as sup-
|
||||
ported, please let me know.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>LIBUSB ISSUES</H2><PRE>
|
||||
Please use libusb-0.1.8 or later. Without libusb or with older libusb
|
||||
versions all kinds of trouble can be expected. The scanner should be
|
||||
found by sane-find-scanner without further actions. For setting permis-
|
||||
sions and general USB information looks at <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>FILES</H2><PRE>
|
||||
<I>/usr/local/etc/sane.d/mustek</I><B>_</B><I>usb2.conf</I>
|
||||
The backend configuration file (see also description of
|
||||
<B>SANE_CONFIG_DIR</B> below).
|
||||
|
||||
<I>/usr/local/lib/sane/libsane-mustek</I><B>_</B><I>usb2.a</I>
|
||||
The static library implementing this backend.
|
||||
|
||||
<I>/usr/local/lib/sane/libsane-mustek</I><B>_</B><I>usb2.so</I>
|
||||
The shared library implementing this backend (present on systems
|
||||
that support dynamic loading).
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in
|
||||
/usr/local/etc/sane.d. If the value of the environment variable
|
||||
ends with the directory separator character, then the default
|
||||
directories are searched after the explicitly specified directo-
|
||||
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
|
||||
would result in directories "tmp/config", ".", and
|
||||
"/usr/local/etc/sane.d" being searched (in this order).
|
||||
|
||||
<B>SANE_DEBUG_MUSTEK_USB2</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.
|
||||
|
||||
Example: export SANE_DEBUG_MUSTEK_USB2=4
|
||||
|
||||
|
||||
</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>, <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>, <B>sane-</B>
|
||||
<B><A HREF="mustek_usb.5.html">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.17/mustek</I><B>_</B><I>usb2/mustek</I><B>_</B><I>usb2.CHANGES</I>
|
||||
<I>http://www.meier-geinitz.de/sane/mustek</I><B>_</B><I>usb2-backend/</I>
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>AUTHOR</H2><PRE>
|
||||
The driver has been written Roy Zhou, Jack Xu, and Vinci Cen from
|
||||
Mustek. Adjustments to SANE by Henning Meier-Geinitz.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>BUGS</H2><PRE>
|
||||
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 SANE_DEBUG_MUSTEK_USB2 above).
|
||||
|
||||
sane-backends 1.0.17 29 Sep 2005 <B><A HREF="sane-mustek_usb2.5.html">sane-mustek_usb2(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
Man(1) output converted with
|
||||
<a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a>
|
||||
</ADDRESS>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
|
@ -67,7 +67,7 @@
|
|||
<H2>AUTHORS</H2><PRE>
|
||||
Kazuya Fukuda
|
||||
|
||||
sane-backends 1.0.16 17 Feb 2000 <B><A HREF="sane-nec.5.html">sane-nec(5)</A></B>
|
||||
sane-backends 1.0.17 17 Feb 2000 <B><A HREF="sane-nec.5.html">sane-nec(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -131,7 +131,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
David Mosberger and Andreas Beck
|
||||
|
||||
sane-backends 1.0.16 8 Oct 2002 <B><A HREF="sane-net.5.html">sane-net(5)</A></B>
|
||||
sane-backends 1.0.17 8 Oct 2002 <B><A HREF="sane-net.5.html">sane-net(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -54,8 +54,8 @@
|
|||
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.
|
||||
together with Linux kernel <B>2.6</B>, kernel version <B>2.6.8</B> or newer is neces-
|
||||
sary.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -78,7 +78,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
Bertrik Sikken <bertrik@zonnet.nl>
|
||||
|
||||
sane-backends 1.0.16 29 July 2004 <B><A HREF="sane-niash.5.html">sane-niash(5)</A></B>
|
||||
sane-backends 1.0.17 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.16 7 Sept 2000 <B><A HREF="sane-pie.5.html">sane-pie(5)</A></B>
|
||||
sane-backends 1.0.17 7 Sept 2000 <B><A HREF="sane-pie.5.html">sane-pie(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -30,10 +30,9 @@
|
|||
|
||||
If have successfully used the PINT driver with your scanner, but it
|
||||
does not work using this SANE backend, please let us know. To do this,
|
||||
send a mail with the relevant information for your scanner to
|
||||
<I>sane-devel@lists.alioth.debian.org</I>. Have a look at
|
||||
http://www.sane-project.org/mailing-lists.html concerning subscription
|
||||
to sane-devel.
|
||||
send a mail with the relevant information for your scanner to <I>sane-</I>
|
||||
<I>devel@lists.alioth.debian.org</I>. Have a look at http://www.sane-
|
||||
project.org/mailing-lists.html concerning subscription to sane-devel.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -42,16 +41,16 @@
|
|||
|
||||
<I>special</I>
|
||||
|
||||
Where <I>special</I> is the UNIX path-name for the special device that corre-
|
||||
sponds to the scanner. The special device name must be a PINT device
|
||||
or a symlink to such a device. For example, under NetBSD or OpenBSD,
|
||||
Where <I>special</I> is the UNIX path-name for the special device that corre-
|
||||
sponds to the scanner. The special device name must be a PINT device
|
||||
or a symlink to such a device. For example, under NetBSD or OpenBSD,
|
||||
such a device name could be <I>/dev/ss0</I> or <I>/dev/scan0</I>.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONFIGURATION</H2><PRE>
|
||||
The contents of the <I>pint.conf</I>. file is a list of device names that
|
||||
correspond to PINT scanners. Empty lines and lines starting with a
|
||||
The contents of the <I>pint.conf</I>. file is a list of device names that
|
||||
correspond to PINT scanners. Empty lines and lines starting with a
|
||||
hash mark (#) are ignored. A sample configuration file is shown below:
|
||||
|
||||
/dev/scanner
|
||||
|
|
@ -62,7 +61,7 @@
|
|||
</PRE>
|
||||
<H2>FILES</H2><PRE>
|
||||
<I>/usr/local/etc/sane.d/pint.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-pint.a</I>
|
||||
|
|
@ -78,21 +77,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_PINT</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.
|
||||
|
||||
|
||||
|
|
@ -109,33 +108,33 @@
|
|||
|
||||
</PRE>
|
||||
<H2>BUGS</H2><PRE>
|
||||
There are minor roundoff errors when adjusting the ranges, since PINT
|
||||
uses units of 1/1200 of an inch, and SANE normally uses millimeters.
|
||||
Symptoms of these errors are skewed images. This should really be
|
||||
There are minor roundoff errors when adjusting the ranges, since PINT
|
||||
uses units of 1/1200 of an inch, and SANE normally uses millimeters.
|
||||
Symptoms of these errors are skewed images. This should really be
|
||||
fixed (no pun intended) as soon as possible, but I just don't know/care
|
||||
enough about fixed-point representation and roundoff errors to do this
|
||||
enough about fixed-point representation and roundoff errors to do this
|
||||
correctly. Workaround: use inches as the scanning unit, and everything
|
||||
usually works fine.
|
||||
|
||||
The PINT 0.5e interface does not provide a way to determine valid
|
||||
ranges for DPI, modes, and scan sizes. So, the SANE backend queries
|
||||
the PINT device, and dynamically discovers valid ranges by doing a
|
||||
binary search. This means that the driver takes longer to initialize
|
||||
The PINT 0.5e interface does not provide a way to determine valid
|
||||
ranges for DPI, modes, and scan sizes. So, the SANE backend queries
|
||||
the PINT device, and dynamically discovers valid ranges by doing a
|
||||
binary search. This means that the driver takes longer to initialize
|
||||
than seems necessary.
|
||||
|
||||
Resetting the scanner does not seem to work (at least not on my HP
|
||||
ScanJet 4p). For that reason, the driver sends a SCIOCRESTART, then
|
||||
Resetting the scanner does not seem to work (at least not on my HP
|
||||
ScanJet 4p). For that reason, the driver sends a SCIOCRESTART, then
|
||||
gobbles up any remaining input until it hits EOF.
|
||||
|
||||
Not all of the scanners have been identified (i.e. whether they are
|
||||
Not all of the scanners have been identified (i.e. whether they are
|
||||
flatbed or handheld).
|
||||
|
||||
X and Y resolutions are assumed to be the same.
|
||||
|
||||
No testing has been done on three-pass or handheld scanners, or with
|
||||
No testing has been done on three-pass or handheld scanners, or with
|
||||
Automatic Document Feeder support.
|
||||
|
||||
sane-backends 1.0.16 13 May 1998 <B><A HREF="sane-pint.5.html">sane-pint(5)</A></B>
|
||||
sane-backends 1.0.17 13 May 1998 <B><A HREF="sane-pint.5.html">sane-pint(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -102,6 +102,7 @@
|
|||
CanoScan N670/676U LM9833 600x1200dpi 48bit 512Kb 0x220D
|
||||
CanoScan N1240U LM9833 1200x2400dpi 48bit 512Kb 0x220E
|
||||
CanoScan LIDE20 LM9833 600x1200dpi 48bit 512Kb 0x220D
|
||||
CanoScan LIDE25 LM9833 1200x2400dpi 48bit 512Kb 0x2220
|
||||
CanoScan LIDE30 LM9833 1200x2400dpi 48bit 512Kb 0x220E
|
||||
|
||||
|
||||
|
|
@ -130,18 +131,15 @@
|
|||
</PRE>
|
||||
<H2>CONFIGURATION</H2><PRE>
|
||||
To use your scanner with this backend, you need at least two entries in
|
||||
the configuration file
|
||||
<I>/usr/local/etc/sane.d/plustek.conf</I>
|
||||
the configuration file <I>/usr/local/etc/sane.d/plustek.conf</I>
|
||||
<I>[usb]</I> <I>vendor-id</I> <I>product-id</I>
|
||||
<I>device</I> <I>/dev/usbscanner</I>
|
||||
|
||||
<I>[usb]</I> <I>vendor-id</I> <I>product-id</I>
|
||||
|
||||
<I>device</I> <I>/dev/usbscanner</I>
|
||||
|
||||
<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.
|
||||
<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 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.
|
||||
|
||||
|
|
@ -283,7 +281,7 @@
|
|||
</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-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.16/plustek/Plustek-USB.changes</I>
|
||||
<I>/usr/local/doc/sane-1.0.17/plustek/Plustek-USB.changes</I>
|
||||
<I>http://www.gjaeger.de/scanner/plustek/</I>
|
||||
|
||||
|
||||
|
|
@ -327,7 +325,7 @@
|
|||
|
||||
* Negative/Slide scanning quality is poor.
|
||||
|
||||
sane-backends 1.0.16 02 July 2004 <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
|
||||
sane-backends 1.0.17 08 August 2005 <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -119,23 +119,17 @@
|
|||
</PRE>
|
||||
<H2>CONFIGURATION</H2><PRE>
|
||||
This section decribes the backends' configuration file entries. The
|
||||
file is located at:
|
||||
|
||||
<I>/usr/local/etc/sane.d/plustek</I><B>_</B><I>pp.conf</I>
|
||||
file is located at: <I>/usr/local/etc/sane.d/plustek</I><B>_</B><I>pp.conf</I>
|
||||
|
||||
For a proper setup, you will need at least two entries:
|
||||
|
||||
<I>[direct]</I>
|
||||
|
||||
<I>device</I> <I>0x378</I>
|
||||
<I>[direct]</I>
|
||||
<I>device</I> <I>0x378</I>
|
||||
|
||||
or
|
||||
<I>[kernel]</I>
|
||||
<I>device</I> <I>/dev/pt</I><B>_</B><I>drv</I>
|
||||
|
||||
<I>[kernel]</I>
|
||||
|
||||
<I>device</I> <I>/dev/pt</I><B>_</B><I>drv</I>
|
||||
|
||||
<I>direct</I> tells the backend, that the following devicename (here <I>0x378</I> )
|
||||
<I>direct</I> tells the backend, that the following devicename (here <I>0x378</I>)
|
||||
has to be interpreted as parallel port scanner device. In fact it is
|
||||
the address to use, alternatively you can use <I>/dev/parport0</I> if the
|
||||
backend has been compiled with libieee1284 support. <I>kernel</I> should only
|
||||
|
|
@ -205,14 +199,13 @@
|
|||
<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
|
||||
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/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>
|
||||
the options to the file <B>/etc/modules.conf</B> <B>(kernel</B> <B><</B> <B>2.6.x)</B> or
|
||||
<B>/etc/modprobe.conf</B> <B>(kernel</B> <B>>=</B> <B>2.6.x)</B>
|
||||
|
||||
<B>The</B> <B>Options:</B>
|
||||
lampoff=lll
|
||||
|
|
@ -345,10 +338,11 @@
|
|||
Example: export SANE_DEBUG_PLUSTEK_PP=10
|
||||
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>,
|
||||
<I>/usr/local/doc/sane-1.0.16/plustek/Plustek-PARPORT.changes</I>
|
||||
<I>/usr/local/doc/sane-1.0.17/plustek/Plustek-PARPORT.changes</I>
|
||||
<I>http://www.gjaeger.de/scanner/plustek</I><B>_</B><I>pp/</I>
|
||||
|
||||
|
||||
|
|
@ -410,7 +404,7 @@
|
|||
|
||||
* The scanquality of the A3I is poor
|
||||
|
||||
sane-backends 1.0.16 18 June 2004 <B><A HREF="sane-plustek_pp.5.html">sane-plustek_pp(5)</A></B>
|
||||
sane-backends 1.0.17 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.16 22 April 2001 <B><A HREF="sane-pnm.5.html">sane-pnm(5)</A></B>
|
||||
sane-backends 1.0.17 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.16 25 October 1997 <B><A HREF="sane-qcam.5.html">sane-qcam(5)</A></B>
|
||||
sane-backends 1.0.17 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.16 24 Jun 2000 <B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B>
|
||||
sane-backends 1.0.17 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.16 24 Jun 2000 <B><A HREF="sane-s9036.5.html">sane-s9036(5)</A></B>
|
||||
sane-backends 1.0.17 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.
|
||||
<I>http://www.zago.net/sane/#sceptre</I>
|
||||
|
||||
sane-backends 1.0.16 April 21st, 2002 <B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B>
|
||||
sane-backends 1.0.17 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.16 28 Oct 2003 <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>
|
||||
sane-backends 1.0.17 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.16 21 Nov 2000 <B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B>
|
||||
sane-backends 1.0.17 21 Nov 2000 <B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@
|
|||
backend that provides access to some Microtek scanners with the Toshiba
|
||||
M011 custom USB chip. This backend should be considered alpha.
|
||||
|
||||
There exist a backends for Microtek scanners with SCSI command set.
|
||||
There are also backends for Microtek scanners with SCSI command set.
|
||||
Refer to <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B> and <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B> for details.
|
||||
|
||||
At present, the following scanners are known positively to work with
|
||||
|
|
@ -70,23 +70,6 @@
|
|||
that support dynamic loading).
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>PERMISSIONS AND INTERFACES</H2><PRE>
|
||||
The backend uses <B>libusb</B> and it's pseudo files in <I>/proc/bus/usb/*</I>. Since
|
||||
<B>libusb</B> versions 0.1.3b and 0.1.4 have incompatible binary data struc-
|
||||
tures, You must be shure not to have obsolete header files. When You
|
||||
mix wrong versions, the scanner detection code will raise a "segment
|
||||
violation".
|
||||
|
||||
These files are normally owned by <B>root</B> and You are responsible to get
|
||||
access to these files, for example <B>chown</B>-ing them to Yourself. If You
|
||||
have no right permissions, the backend will find the device, but You'll
|
||||
get an I/O error.
|
||||
|
||||
The better way is to use automatical <B>hotplugging</B>. See
|
||||
<I>http://sm3600.sf.net/hotplug.html</I> for instructions and useful links.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_DEBUG_SM3600</B>
|
||||
|
|
@ -110,7 +93,7 @@
|
|||
Marian Eichholz (eichholz@computer.org)
|
||||
Glenn Ramsey (glenn@componic.com)
|
||||
|
||||
sane-backends 1.0.16 10.02.2002 <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B>
|
||||
sane-backends 1.0.17 16 August 2005 <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -98,7 +98,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
Earle F. Philhower III (earle@ziplabel.com)
|
||||
|
||||
sane-backends 1.0.16 Mar 15, 2005 <B><A HREF="sane-sm3840.5.html">sane-sm3840(5)</A></B>
|
||||
sane-backends 1.0.17 Mar 15, 2005 <B><A HREF="sane-sm3840.5.html">sane-sm3840(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@
|
|||
firmware upload before scanning add a line starting with "firmware"
|
||||
followed by the fully qualified path to your firmware file, e.g.
|
||||
|
||||
firmware /path/to/my/firmware.bin
|
||||
firmware /usr/local/share/sane/snapscan/firmware.bin
|
||||
|
||||
For further details read http://snapscan.sourceforge.net.
|
||||
|
||||
|
|
@ -114,7 +114,7 @@
|
|||
Man page by Henning Meier-Geinitz (mostly based on the web pages and
|
||||
source code).
|
||||
|
||||
sane-backends 1.0.16 26 May 2001 <B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B>
|
||||
sane-backends 1.0.17 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.16 17 Apr 2002 <B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B>
|
||||
sane-backends 1.0.17 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.16 08 Mar 1999 <B><A HREF="sane-st400.5.html">sane-st400(5)</A></B>
|
||||
sane-backends 1.0.17 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.16 24 Jun 2000 <B><A HREF="sane-tamarack.5.html">sane-tamarack(5)</A></B>
|
||||
sane-backends 1.0.17 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.16 August 30th, 2002 <B><A HREF="sane-teco1.5.html">sane-teco1(5)</A></B>
|
||||
sane-backends 1.0.17 August 30th, 2002 <B><A HREF="sane-teco1.5.html">sane-teco1(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -214,7 +214,7 @@
|
|||
Christoph.Hoeffner for testing the support for the VM3564 (Relisys AVEC
|
||||
II S3 firmware 1.09).
|
||||
|
||||
sane-backends 1.0.16 29 July 2005 <B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B>
|
||||
sane-backends 1.0.17 29 July 2005 <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.
|
||||
<I>http://www.zago.net/sane/#teco3</I>
|
||||
|
||||
sane-backends 1.0.16 25 July 2002 <B><A HREF="sane-teco3.5.html">sane-teco3(5)</A></B>
|
||||
sane-backends 1.0.17 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.16 24 Jul 2002 <B><A HREF="sane-test.5.html">sane-test(5)</A></B>
|
||||
sane-backends 1.0.17 24 Jul 2002 <B><A HREF="sane-test.5.html">sane-test(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -52,17 +52,14 @@
|
|||
</PRE>
|
||||
<H2>CONFIGURATION</H2><PRE>
|
||||
To use your scanner with this backend, you need at least two entries in
|
||||
the configuration file
|
||||
<I>/usr/local/etc/sane.d/u12.conf</I>
|
||||
|
||||
<I>[usb]</I> <I>vendor-id</I> <I>product-id</I>
|
||||
|
||||
<I>device</I> <I>/dev/usbscanner</I>
|
||||
the configuration file <I>/usr/local/etc/sane.d/u12.conf</I>
|
||||
<I>[usb]</I> <I>vendor-id</I> <I>product-id</I>
|
||||
<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
|
||||
<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
|
||||
its own. If device is set to <I>auto</I> then the next matching device is
|
||||
used.
|
||||
|
||||
<B>The</B> <B>Options:</B>
|
||||
|
|
@ -78,6 +75,7 @@
|
|||
<I>b</I> specifies the behaviour when closing the backend, 1 --> switch
|
||||
lamps off, 0 --> do not change lamp status
|
||||
|
||||
|
||||
See the u12.conf file for examples.
|
||||
|
||||
<B>Note:</B>
|
||||
|
|
@ -130,7 +128,7 @@
|
|||
</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.16/u12/U12.changes</I>
|
||||
<I>/usr/local/doc/sane-1.0.17/u12/U12.changes</I>
|
||||
<I>http://www.gjaeger.de/scanner/u12/</I>
|
||||
|
||||
|
||||
|
|
@ -161,7 +159,7 @@
|
|||
* When using libusb, it might be, that the backend hangs. In that
|
||||
case, reconnect the scanner.
|
||||
|
||||
sane-backends 1.0.16 18 June 2004 <B><A HREF="sane-u12.5.html">sane-u12(5)</A></B>
|
||||
sane-backends 1.0.17 18 June 2004 <B><A HREF="sane-u12.5.html">sane-u12(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -244,7 +244,7 @@
|
|||
<H2>EMAIL-CONTACT</H2><PRE>
|
||||
Oliver.Rauch@Rauch-Domain.DE
|
||||
|
||||
sane-backends 1.0.16 29 november 2002 <B><A HREF="sane-umax.5.html">sane-umax(5)</A></B>
|
||||
sane-backends 1.0.17 29 november 2002 <B><A HREF="sane-umax.5.html">sane-umax(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -135,7 +135,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.16 6 Jan 2002 <B><A HREF="sane-umax1220u.5.html">sane-umax1220u(5)</A></B>
|
||||
sane-backends 1.0.17 6 Jan 2002 <B><A HREF="sane-umax1220u.5.html">sane-umax1220u(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -114,8 +114,8 @@
|
|||
names that correspond to Umax scanners. Empty lines and lines starting
|
||||
with a hash mark (#) are ignored.
|
||||
|
||||
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>.
|
||||
The height options supported are <B>red-gain</B>, <B>green-gain</B>, <B>blue-gain</B>, <B>red-</B>
|
||||
<B>offset</B>, <B>green-offset</B>, <B>blue-offset</B>, <B>astra</B>, and <B>buffer</B>.
|
||||
|
||||
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
|
||||
|
|
@ -247,7 +247,7 @@
|
|||
better), or you think I should know something, please include
|
||||
it.
|
||||
|
||||
sane-backends 1.0.16 23 August 2004 <B><A HREF="sane-umax_pp.5.html">sane-umax_pp(5)</A></B>
|
||||
sane-backends 1.0.17 23 August 2004 <B><A HREF="sane-umax_pp.5.html">sane-umax_pp(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -21,12 +21,10 @@
|
|||
USB interface. It focusses on two main topics: getting the scanner
|
||||
detected by the operating system kernel and using it with SANE.
|
||||
|
||||
This page applies to most backends and scanners, as they use the
|
||||
generic sanei_usb interface. However, there are some exceptions: USB
|
||||
This page applies to USB most backends and scanners, as they use the
|
||||
generic sanei_usb interface. However, there is one exceptions: USB
|
||||
Scanners supported by the microtek2 backend need a special USB kernel
|
||||
driver, see <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B> for details. The sm3600 backend accesses
|
||||
scanners over libusb dierctly. See the appropriate section in this man-
|
||||
page and <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B>.
|
||||
driver, see <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B> for details.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -77,69 +75,68 @@
|
|||
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
|
||||
scanimage -L as root. Setting permissions with "chmod" is not perma-
|
||||
nent, however. They will be reset after reboot or replugging the scan-
|
||||
ner.
|
||||
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 reset after reboot or replugging the scanner.
|
||||
|
||||
Usually the the hotplug utilities (<I>http://linux-hotplug.source-</I>
|
||||
<I>forge.net/</I>) are used, 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. Precompiled SANE packages
|
||||
Usually the the hotplug utilities (<I>http://linux-hotplug.source-</I>
|
||||
<I>forge.net/</I>) are used, 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. Precompiled SANE packages
|
||||
may have already installed such hotplug scrips in /etc/hotplug/.
|
||||
|
||||
For the <B>BSDs</B>, the device files used by libusb are named <I>/dev/ugen*</I>.
|
||||
For the <B>BSDs</B>, the device files used by libusb are named <I>/dev/ugen*</I>.
|
||||
Use chmod to apply appropriate permissions.
|
||||
|
||||
|
||||
</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
|
||||
running sane-find-scanner, looking into the syslog (e.g., /var/log/mes-
|
||||
sages) or under Linux by issuing the command "cat
|
||||
sages) 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 a detailed description of each backend's configu-
|
||||
ration file, please refer to the relevant backend manual page (e.g.
|
||||
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 a detailed description of each backend's configu-
|
||||
ration 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.
|
||||
|
||||
|
||||
|
|
@ -148,12 +145,11 @@
|
|||
<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>sane-"backendname"</B>(5), <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>
|
||||
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>AUTHOR</H2><PRE>
|
||||
Henning Meier-Geinitz <henning@meier-geinitz.de>
|
||||
|
||||
sane-backends 1.0.16 29 May 2005 <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>
|
||||
sane-backends 1.0.17 16 August 2005 <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -95,9 +95,9 @@
|
|||
<H2>BUGS:</H2><PRE>
|
||||
If more than one video card is present, a crash may occur. Frequency
|
||||
and geometry selection is missing.
|
||||
Send bug reports to the SANE mailing list:
|
||||
sane-devel@lists.alioth.debian.org. You must be subscribed to the list
|
||||
to send mail. See http://www.sane-project.org/mailing-lists.html for
|
||||
Send bug reports to the SANE mailing list: sane-
|
||||
devel@lists.alioth.debian.org. You must be subscribed to the list to
|
||||
send mail. See http://www.sane-project.org/mailing-lists.html for
|
||||
details.
|
||||
|
||||
|
||||
|
|
@ -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.16 28 Aug 2002 <B><A HREF="sane-v4l.5.html">sane-v4l(5)</A></B>
|
||||
sane-backends 1.0.17 28 Aug 2002 <B><A HREF="sane-v4l.5.html">sane-v4l(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
324
man/sane.7.html
324
man/sane.7.html
|
|
@ -47,9 +47,9 @@
|
|||
(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 also be found on the <B>SANE</B> homepage.
|
||||
can be downloaded from the <B>SANE</B> homepage (<I>http://www.sane-</I>
|
||||
<I>project.org/</I>). Information about other frontends and backends can also
|
||||
be found on the <B>SANE</B> homepage.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -58,15 +58,15 @@
|
|||
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.16/sane.tex</I>' are references to text files that
|
||||
`<I>/usr/local/doc/sane-1.0.17/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.16/</I>) during installation. Everything else is a
|
||||
(<I>/usr/local/doc/sane-1.0.17/</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>.
|
||||
the SANE FAQ can be found on the SANE homepage: <I>http://www.sane-</I>
|
||||
<I>project.org/</I>.
|
||||
|
||||
<B>SANE</B> <B>device</B> <B>lists</B>
|
||||
The <B>SANE</B> device lists contain information about the status of <B>SANE</B>
|
||||
|
|
@ -75,7 +75,7 @@
|
|||
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.16/.
|
||||
are also installed on your system at /usr/local/doc/sane-1.0.17/.
|
||||
|
||||
<B>SANE</B> <B>mailing</B> <B>list</B>
|
||||
There is a mailing list for the purpose of discussing the SANE stan-
|
||||
|
|
@ -95,12 +95,12 @@
|
|||
server, etc.).
|
||||
|
||||
<B>Compiling</B> <B>and</B> <B>installing</B> <B>SANE</B>
|
||||
Look at <I>/usr/local/doc/sane-1.0.16/README</I> and the os-dependent README
|
||||
Look at <I>/usr/local/doc/sane-1.0.17/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>.
|
||||
For information about various systems and SCSI controllers see <B>sane-</B>
|
||||
<B><A HREF="scsi.5.html">scsi(5)</A></B>.
|
||||
|
||||
<B>USB</B> <B>configuration</B>
|
||||
For information about USB configuration see <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>.
|
||||
|
|
@ -137,8 +137,8 @@
|
|||
|
||||
<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.
|
||||
scanners: AppleScanner, OneScanner and ColorOneScanner. See <B>sane-</B>
|
||||
<B><A HREF="apple.5.html">apple(5)</A></B> for details.
|
||||
|
||||
<B>artec</B>
|
||||
The SANE Artec backend supports several Artec/Ultima SCSI flatbed
|
||||
|
|
@ -177,12 +177,12 @@
|
|||
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.
|
||||
This is a SANE backend for Nikon Coolscan film-scanners. See <B>sane-</B>
|
||||
<B><A HREF="coolscan.5.html">coolscan(5)</A></B> for details.
|
||||
|
||||
<B>coolscan2</B>
|
||||
This is a SANE backend for Nikon Coolscan film-scanners. See
|
||||
<B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B> or <I>http://coolscan2.sourceforge.net</I> for details.
|
||||
This is a SANE backend for Nikon Coolscan film-scanners. See <B>sane-</B>
|
||||
<B><A HREF="coolscan2.5.html">coolscan2(5)</A></B> or <I>http://coolscan2.sourceforge.net</I> for details.
|
||||
|
||||
<B>epson</B>
|
||||
The SANE epson backend provides support for Epson SCSI, parallel port
|
||||
|
|
@ -207,25 +207,33 @@
|
|||
|
||||
<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.
|
||||
ners which support SCL (Scanner Control Language by HP). See <B>sane-</B>
|
||||
<B><A HREF="hp.5.html">hp(5)</A></B> for details.
|
||||
|
||||
<B>hpsj5s</B>
|
||||
The SANE backend for the Hewlett-Packard ScanJet 5S scanner. See
|
||||
<B><A HREF="sane-hpsj5s.5.html">sane-hpsj5s(5)</A></B> for details.
|
||||
|
||||
<B>hp4200</B>
|
||||
The SANE backend for the Hewlett-Packard ScanJet 4200 series. See
|
||||
<B><A HREF="sane-hp4200.5.html">sane-hp4200(5)</A></B> for details.
|
||||
|
||||
<B>hp5400</B>
|
||||
The SANE backend for the Hewlett-Packard ScanJet 54XXC series. See
|
||||
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.
|
||||
The SANE backend for some IBM and Ricoh SCSI scanners. See <B>sane-</B>
|
||||
<B><A HREF="ibm.5.html">ibm(5)</A></B> for details.
|
||||
|
||||
<B>leo</B>
|
||||
This backend supports the Leo S3 and the Across FS-1130, which is a
|
||||
This backend supports the Leo S3 and the Across FS-1130, which is a
|
||||
re-badged LEO FS-1130 scanner. See <B><A HREF="sane-leo.5.html">sane-leo(5)</A></B> for details.
|
||||
|
||||
<B>lexmark</B>
|
||||
This backend supports the Lexmark X1100 series of USB scanners. See
|
||||
<B><A HREF="sane-lexmark.5.html">sane-lexmark(5)</A></B> for details.
|
||||
|
||||
<B>ma1509</B>
|
||||
The ma1509 backend supports the Mustek BearPaw 1200F USB flatbed
|
||||
scanner. See <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B> for details.
|
||||
|
|
@ -246,8 +254,8 @@
|
|||
<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.
|
||||
II EP (non-SCSI). Some Trust scanners are also supported. See <B>sane-</B>
|
||||
<B><A HREF="mustek.5.html">mustek(5)</A></B> for details.
|
||||
|
||||
<B>mustek_pp</B>
|
||||
The mustek_pp backend provides access to Mustek parallel port flatbed
|
||||
|
|
@ -257,6 +265,11 @@
|
|||
The mustek_usb backend provides access to some Mustek ScanExpress USB
|
||||
flatbed scanners. See <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B> for details.
|
||||
|
||||
<B>mustek_usb2</B>
|
||||
The mustek_usb2 backend provides access to scanners using the SQ113
|
||||
chipset like the Mustek BearPaw 2448 TA Pro USB flatbed scanner. See
|
||||
<B><A HREF="sane-mustek_usb2.5.html">sane-mustek_usb2(5)</A></B> for details.
|
||||
|
||||
<B>nec</B>
|
||||
The SANE nec backend supports the NEC PC-IN500/4C SCSI scanner. See
|
||||
<B><A HREF="sane-nec.5.html">sane-nec(5)</A></B> for details.
|
||||
|
|
@ -296,8 +309,8 @@
|
|||
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.
|
||||
The SANE sharp backend supports Sharp SCSI scanners. See <B>sane-</B>
|
||||
<B><A HREF="sharp.5.html">sharp(5)</A></B> for details.
|
||||
|
||||
<B>sm3600</B>
|
||||
The SANE sm3600 backend supports the Microtek ScanMaker 3600 USB
|
||||
|
|
@ -328,22 +341,28 @@
|
|||
usually sold under the Relisys, Trust, Primax, Piotech, Dextra names.
|
||||
See <B><A HREF="sane-teco1.5.html">sane-teco1(5)</A></B>, <B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B> and <B><A HREF="sane-teco3.5.html">sane-teco3(5)</A></B> for details.
|
||||
|
||||
<B>u12</B>
|
||||
The sane-u12 backend provides USB flatbed scanners based on Plustek's
|
||||
ASIC 98003 (parallel-port ASIC) and a GeneSys Logics' USB-parport
|
||||
bridge chip like the Plustek OpticPro U(T)12. See <B><A HREF="sane-u12.5.html">sane-u12(5)</A></B> for
|
||||
details.
|
||||
|
||||
<B>umax</B>
|
||||
The sane-umax backend provides access to several UMAX-SCSI-scanners
|
||||
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
|
||||
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.
|
||||
The sane-umax1220u backend supports the UMAX Astra 1220U (USB)
|
||||
flatbed scanner (and also the UMAX Astra 2000U, sort of). See <B>sane-</B>
|
||||
<B><A HREF="umax1220u.5.html">umax1220u(5)</A></B> for details.
|
||||
|
||||
Also, have a look at the backend information page at
|
||||
<I>http://www.sane-project.org/sane-supported-devices.html</I> and the list of
|
||||
projects in <I>/usr/local/doc/sane-1.0.16/PROJECTS</I>.
|
||||
Also, have a look at the backend information page at <I>http://www.sane-</I>
|
||||
<I>project.org/sane-supported-devices.html</I> and the list of projects in
|
||||
<I>/usr/local/doc/sane-1.0.17/PROJECTS</I>.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -358,96 +377,96 @@
|
|||
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>.
|
||||
Backend for the Polaroid Digital Microscope Camera. See <B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B>.
|
||||
|
||||
<B>gphoto2</B>
|
||||
Backend for digital cameras supported by the gphoto2 library package.
|
||||
(See <I>http://www.gphoto.org</I> for more information and a list of sup-
|
||||
ported cameras.) Gphoto2 supports over 140 different camera models.
|
||||
However, please note that more development and testing is needed
|
||||
before all of these cameras will be supported by <B>SANE</B> backend. See
|
||||
(See <I>http://www.gphoto.org</I> for more information and a list of sup-
|
||||
ported cameras.) Gphoto2 supports over 140 different camera models.
|
||||
However, please note that more development and testing is needed
|
||||
before all of these cameras will be supported by <B>SANE</B> backend. See
|
||||
<B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>.
|
||||
|
||||
<B>qcam</B>
|
||||
Backend for Connectix QuickCam cameras. See <B><A HREF="sane-qcam.5.html">sane-qcam(5)</A></B>.
|
||||
|
||||
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.16/PROJECTS</I>.
|
||||
Also, have a look at the backend information page at <I>http://www.sane-</I>
|
||||
<I>project.org/sane-supported-devices.html</I> and the list of projects in
|
||||
<I>/usr/local/doc/sane-1.0.17/PROJECTS</I>.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>MISCELLANEOUS BACKENDS</H2><PRE>
|
||||
<B>dll</B>
|
||||
The sane-dll library implements a <B>SANE</B> backend that provides access
|
||||
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.8.html">saned(8)</A></B>.
|
||||
The <B>SANE</B> network daemon saned provides access to scanners located on
|
||||
different computers in connection with the net backend. See <B>sane-</B>
|
||||
<B><A HREF="net.5.html">net(5)</A></B> and <B><A HREF="saned.8.html">saned(8)</A></B>.
|
||||
|
||||
<B>pnm</B>
|
||||
PNM image reader pseudo-backend. The purpose of this backend is pri-
|
||||
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>.
|
||||
Backend for scanners that use the <B>PINT</B> (Pint Is Not Twain) device
|
||||
driver. The <B>PINT</B> driver is being actively developed on the OpenBSD
|
||||
platform, and has been ported to a few other *nix-like operating
|
||||
systems. See <B><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>.
|
||||
tion. It provides test pictures and various test options. See <B>sane-</B>
|
||||
<B><A HREF="test.5.html">test(5)</A></B>.
|
||||
|
||||
<B>v4l</B>
|
||||
The sane-v4l library implements a <B>SANE</B> backend that provides generic
|
||||
access to video cameras and similar equipment using the <B>V4L</B> (Video
|
||||
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.16/PROJECTS</I>.
|
||||
Also, have a look at the backend information page at <I>http://www.sane-</I>
|
||||
<I>project.org/sane-supported-devices.html</I> and the list of projects in
|
||||
<I>/usr/local/doc/sane-1.0.17/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
|
||||
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
|
||||
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.
|
||||
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.16/sane.ps</I> (if latex is installed on
|
||||
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.17/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.16/backend-writing.txt</I>. Most of the internal
|
||||
<B>SANE</B> routines (<B>sanei</B>) are documented using doxygen: <I>http://www.sane-</I>
|
||||
<I>project.org/sanei/</I>. Before a new backend or frontend project is
|
||||
started, have a look at <I>/usr/local/doc/sane-1.0.16/PROJECTS</I> for
|
||||
projects that are planned or not yet included into the <B>SANE</B> distribu-
|
||||
tion and at our bug-tracking system:
|
||||
<I>http://www.http://www.sane-project.org/bugs.html</I>.
|
||||
There is some more information for programmers in
|
||||
<I>/usr/local/doc/sane-1.0.17/backend-writing.txt</I>. Most of the internal
|
||||
<B>SANE</B> routines (<B>sanei</B>) are documented using doxygen: <I>http://www.sane-</I>
|
||||
<I>project.org/sanei/</I>. Before a new backend or frontend project is
|
||||
started, have a look at <I>/usr/local/doc/sane-1.0.17/PROJECTS</I> for
|
||||
projects that are planned or not yet included into the <B>SANE</B> distribu-
|
||||
tion and at our bug-tracking system: <I>http://www.http://www.sane-</I>
|
||||
<I>project.org/bugs.html</I>.
|
||||
|
||||
There are some links on how to find out about the protocol of a scan-
|
||||
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>
|
||||
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.
|
||||
|
||||
|
|
@ -461,134 +480,135 @@
|
|||
The static libraries implementing the backends.
|
||||
|
||||
<I>/usr/local/lib/sane/libsane-*.so</I>
|
||||
The shared libraries implementing the backends (present on sys-
|
||||
The shared libraries implementing the backends (present on sys-
|
||||
tems that support dynamic loading).
|
||||
|
||||
<I>/usr/local/doc/sane-1.0.16/*</I>
|
||||
<B>SANE</B> documentation: The standard, READMEs, text files for back-
|
||||
<I>/usr/local/doc/sane-1.0.17/*</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
|
||||
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,
|
||||
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
|
||||
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
|
||||
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 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
|
||||
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
|
||||
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
|
||||
<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>
|
||||
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
|
||||
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
|
||||
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
|
||||
your distribution in <I>/usr</I> and one you installed from source in
|
||||
<I>/usr/local/</I>. Make sure that only one version is installed. Another
|
||||
possible reason is, that your system's dynamic loader can't find the
|
||||
<B>SANE</B> libraries. For Linux, make sure that <I>/etc/ld.so.conf</I> contains
|
||||
<I>/usr/local/lib</I> and does <B>not</B> contain <I>/usr/local/lib/sane</I>. See also the
|
||||
documentation of the frontends.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>HOW CAN YOU HELP SANE</H2><PRE>
|
||||
We appreciate any help we can get. Please have a look at our web page
|
||||
We appreciate any help we can get. Please have a look at our web page
|
||||
about contributing to <B>SANE</B>: <I>http://www.sane-project.org/contrib.html</I>
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONTACT</H2><PRE>
|
||||
For reporting bugs or requesting new features, please use our bug-
|
||||
tracking system: <I>http://www.sane-project.org/bugs.html</I>. You can also
|
||||
contact the author of your backend directly. Usually the email address
|
||||
can be found in the <I>/usr/local/doc/sane-1.0.16/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).
|
||||
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.17/AUTHORS</I> file or the
|
||||
backend's manpage. For general discussion about SANE, please use the
|
||||
<B>SANE</B> mailing list sane-devel (see <I>http://www.sane-project.org/mailing-</I>
|
||||
<I>lists.html</I> for details).
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="saned.8.html">saned(8)</A></B>, <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="sane-abaton.5.html">sane-abaton(5)</A></B>,
|
||||
<B><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>sane-mat-</B>
|
||||
<B><A HREF="sushita.5.html">sushita(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-niash.5.html">sane-niash(5)</A></B>, <B><A HREF="sane-pie.5.html">sane-pie(5)</A></B>, <B><A HREF="sane-pint.5.html">sane-pint(5)</A></B>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>, <B>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>
|
||||
<B><A HREF="saned.8.html">saned(8)</A></B>, <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="sane-abaton.5.html">sane-abaton(5)</A></B>, <B>sane-</B>
|
||||
<B><A HREF="agfafocus.5.html">agfafocus(5)</A></B>, <B><A HREF="sane-apple.5.html">sane-apple(5)</A></B>, <B><A HREF="sane-artec.5.html">sane-artec(5)</A></B>, <B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B>,
|
||||
<B><A HREF="sane-as6e.5.html">sane-as6e(5)</A></B>, <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B>, <B><A HREF="sane-bh.5.html">sane-bh(5)</A></B>, <B><A HREF="sane-canon.5.html">sane-canon(5)</A></B>, <B>sane-</B>
|
||||
<B><A HREF="canon630u.5.html">canon630u(5)</A></B>, <B><A HREF="sane-canon_pp.5.html">sane-canon_pp(5)</A></B>, <B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B>, <B><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B>,
|
||||
<B><A HREF="sane-dc210.5.html">sane-dc210(5)</A></B>, <B><A HREF="sane-dc240.5.html">sane-dc240(5)</A></B>, <B><A HREF="sane-dc25.5.html">sane-dc25(5)</A></B>, <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>, <B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B>,
|
||||
<B><A HREF="sane-epson.5.html">sane-epson(5)</A></B>, <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>, <B><A HREF="sane-genesys.5.html">sane-genesys(5)</A></B>, <B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>, <B>sane-</B>
|
||||
<B><A HREF="gt68xx.5.html">gt68xx(5)</A></B>, <B><A HREF="sane-hp.5.html">sane-hp(5)</A></B>, <B><A HREF="sane-hpsj5s.5.html">sane-hpsj5s(5)</A></B>, <B><A HREF="sane-hp4200.5.html">sane-hp4200(5)</A></B>, <B><A HREF="sane-hp5400.5.html">sane-hp5400(5)</A></B>,
|
||||
<B><A HREF="sane-ibm.5.html">sane-ibm(5)</A></B>, <B><A HREF="sane-leo.5.html">sane-leo(5)</A></B>, <B><A HREF="sane-lexmark.5.html">sane-lexmark(5)</A></B>, <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>, <B>sane-mat-</B>
|
||||
<B><A HREF="sushita.5.html">sushita(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>sane-</B>
|
||||
<B><A HREF="mustek_pp.5.html">mustek_pp(5)</A></B>, <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B><A HREF="sane-mustek_usb2.5.html">sane-mustek_usb2(5)</A></B>, <B><A HREF="sane-nec.5.html">sane-nec(5)</A></B>,
|
||||
<B><A HREF="sane-net.5.html">sane-net(5)</A></B>, <B><A HREF="sane-niash.5.html">sane-niash(5)</A></B>, <B><A HREF="sane-pie.5.html">sane-pie(5)</A></B>, <B><A HREF="sane-pint.5.html">sane-pint(5)</A></B>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>,
|
||||
<B><A HREF="sane-plustek_pp.5.html">sane-plustek_pp(5)</A></B>, <B><A HREF="sane-pnm.5.html">sane-pnm(5)</A></B>, <B><A HREF="sane-qcam.5.html">sane-qcam(5)</A></B>, <B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B>, <B>sane-</B>
|
||||
<B><A HREF="s9036.5.html">s9036(5)</A></B>, <B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B>, <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B>,
|
||||
<B><A HREF="sane-sm3840.5.html">sane-sm3840(5)</A></B>, <B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B>, <B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B>, <B><A HREF="sane-st400.5.html">sane-st400(5)</A></B>, <B>sane-</B>
|
||||
<B><A HREF="tamarack.5.html">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>sane-</B>
|
||||
<B><A HREF="usb.5.html">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.16/AUTHORS</I> for details). This man page was
|
||||
written by Henning Meier-Geinitz. Quite a lot of text was taken from
|
||||
David Mosberger-Tang and many many more (see
|
||||
<I>/usr/local/doc/sane-1.0.17/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.16 29 May 2005 <B><A HREF="sane.7.html">sane(7)</A></B>
|
||||
|
||||
sane-backends 1.0.17 16 October 2005 <B><A HREF="sane.7.html">sane(7)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -179,7 +179,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
David Mosberger
|
||||
|
||||
sane-backends 1.0.16 30 May 2004 <B><A HREF="saned.8.html">saned(8)</A></B>
|
||||
sane-backends 1.0.17 30 May 2004 <B><A HREF="saned.8.html">saned(8)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -21,8 +21,8 @@
|
|||
<I>profile</I>] [<B>-L</B>|<B>--list-devices</B>] [<B>-f</B>|<B>--formatted-device-list</B> <I>format</I>]
|
||||
[<B>--batch</B> [=<I>format</I>]] [<B>--batch-start</B> <I>start</I>] [<B>--batch-count</B> <I>count</I>]
|
||||
[<B>--batch-increment</B> <I>increment</I>] [<B>--batch-double</B>] [<B>--accept-md5-only</B>]
|
||||
[<B>-n</B>|<B>--dont-scan</B>] [<B>-T</B>|<B>--test</B>] [<B>-h</B>|<B>--help</B>] [<B>-v</B>|<B>--verbose</B>] [<B>-B</B>|<B>--buffer-</B>
|
||||
<B>size</B>] [<B>-V</B>|<B>--version</B>] [<I>device-specific-options</I>]
|
||||
[<B>-p</B>|<B>--progress</B>] [<B>-n</B>|<B>--dont-scan</B>] [<B>-T</B>|<B>--test</B>] [<B>-h</B>|<B>--help</B>] [<B>-v</B>|<B>--verbose</B>]
|
||||
[<B>-B</B>|<B>--buffersize</B>] [<B>-V</B>|<B>--version</B>] [<I>device-specific-options</I>]
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -117,6 +117,10 @@
|
|||
that support MD5 security. The <B>SANE</B> network daemon (<B>saned</B>) is capable
|
||||
of doing such requests. See <B><A HREF="saned.8.html">saned(8)</A></B>.
|
||||
|
||||
The <B>-p</B> or <B>--progress</B> option requests that <B>scanimage</B> prints a progress
|
||||
counter. It shows how much image data of the current image has already
|
||||
been received by <B>scanimage</B> (in percent).
|
||||
|
||||
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
|
||||
option can be used to e.g. turn off the scanner's lamp (if supported by
|
||||
|
|
@ -269,7 +273,9 @@
|
|||
|
||||
</PRE>
|
||||
<H2>AUTHOR</H2><PRE>
|
||||
David Mosberger, Andreas Beck, Gordon Matzigkeit and Caskey Dickson
|
||||
David Mosberger, Andreas Beck, Gordon Matzigkeit, Caskey Dickson, and
|
||||
many others. For questions and comments contact the sane-devel mail-
|
||||
inglist (see http://www.sane-project.org/mailing-lists.html).
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -277,7 +283,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.16 15 April 2005 <B><A HREF="scanimage.1.html">scanimage(1)</A></B>
|
||||
sane-backends 1.0.17 23 Sep 2005 <B><A HREF="scanimage.1.html">scanimage(1)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
Ładowanie…
Reference in New Issue