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

Update for sane-backends-1.3.1 release

master
Ralph Little 2024-05-22 23:23:04 -07:00
rodzic 22d4e59d47
commit 2f22053a7a
100 zmienionych plików z 24928 dodań i 2422 usunięć
Pokaż statystyki Ściągnij plik aktualizacji Ściągnij plik porównania Expand all files Collapse all files

3
index.html
Wyświetl plik

@ -36,6 +36,9 @@
<h3>Latest News</h3>
<h4>Backends</h4>
<p>
<strong>2024-05-22:</strong> <a href="https://gitlab.com/sane-project/backends/-/releases/1.3.1"><tt>sane-backends-1.3.1</tt></a> has been released.
</p>
<p>
<strong>2023-02-05:</strong> <a href="https://gitlab.com/sane-project/backends/-/releases/1.2.1"><tt>sane-backends-1.2.1</tt></a> has been released.
</p>
<p>

24
man/sane-abaton.5.html
Wyświetl plik

@ -30,9 +30,9 @@
port for it. Have a look at <I>http://www.sane-project.org/mail-</I>
<I>ing-lists.html</I> 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
information to be found. This driver is therefore based on information
Abaton is out of business, and these scanners are not supported by Ev-
erex (the parent company of Abaton), nor is there any programming in-
formation to be found. This driver is therefore based on information
obtained by running Abaton's scanning desk accessory under MacsBug and
tracing the MacOS SCSI Manager calls it made during image acquisition.
@ -86,17 +86,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_ABATON</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 en-
vironment 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.

28
man/sane-agfafocus.5.html
Wyświetl plik

@ -61,8 +61,8 @@
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>agfafocus.conf</I> file is a list of device names that
correspond to AGFA Focus scanners. Empty lines and lines starting with
a hash mark (#) are ignored. A sample configuration file is shown
below:
a hash mark (#) are ignored. A sample configuration file is shown be-
low:
/dev/scanner
# this is a comment
@ -91,17 +91,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_AGFAFOCUS</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 en-
vironment 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. <B>SANE_DEBUG_AGFAFOCUS</B> values:
@ -143,9 +143,9 @@
the Artec backend is disabled. Somehow, this backend causes at least
my scanner not to respond correctly to SCSI inquiry commands.
If you encounter a bug please set the environment variable
<B>SANE_DEBUG_AGFAFOCUS</B> to 128 and try to regenerate the problem. Then
send me a report with the log attached.
If you encounter a bug please set the environment variable <B>SANE_DE-</B>
<B>BUG_AGFAFOCUS</B> to 128 and try to regenerate the problem. Then send me a
report with the log attached.
If you encounter a SCSI bus error or trimmed and/or displaced images
please also set the environment variable <B>SANE_DEBUG_SANEI_SCSI</B> to 128

145
man/sane-apple.5.html
Wyświetl plik

@ -28,9 +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@alioth-</I>
<I>lists.debian.net</I>. See <I>http://www.sane-project.org/mailing-lists.html</I>
for details on how to subscribe to sane-devel.
name, SCSI id, and firmware revision to <I>sane-devel@alioth-lists.de-</I>
<I>bian.net</I>. See <I>http://www.sane-project.org/mailing-lists.html</I> for de-
tails on how to subscribe to sane-devel.
</PRE>
@ -53,8 +53,8 @@
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 come in two flavors: global and positional ones. Global op-
tions 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!
@ -85,34 +85,33 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable is list of directories where SANE
This environment variable is a list of directories where SANE
looks for the configuration file. On *NIX systems, directory
names are separated by a colon (`:'), under OS/2 by a semi-colon
(`;'). If SANE_CONFIG_DIR is not set, SANE defaults to search-
ing the current working directory (".") and then
<I>/usr/local/etc/sane.d</I>. If the value of $SANE_CONFIG_DIR ends
with the separator character, the default directories are
searched after the directory list. For example, setting
<B>SANE_CONFIG_DIR</B> to "/tmp/config:" would result in directories
<I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> being searched (in that
order).
ing the current working directory (".") and then <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of $SANE_CONFIG_DIR ends with the
separator character, the default directories are searched after
the directory list. For example, setting <B>SANE_CONFIG_DIR</B> to
"/tmp/config:" would result in directories <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in that order).
<B>SANE_DEBUG_APPLE</B>
Controls the debug level. A value of 255 prints all debug out-
put. Smaller values reduce verbosity. Requires a library com-
Controls the debug level. A value of 255 prints all debug out-
put. Smaller values reduce verbosity. Requires a library com-
piled with debug support.
</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 completed 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
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.
@ -127,85 +126,83 @@
Cannot up/download halftone patterns or calibration vectors.
<B>ColorOneScanner</B>
Cannot up/download halftone patterns, calibration vectors, cus-
tom Color Correction Tables (CCT) and of course custom gamma
tables.
Cannot up/download halftone patterns, calibration vectors, cus-
tom Color Correction Tables (CCT) and of course custom gamma ta-
bles.
<B>Park/UnPark</B> <B>(OneScanner,</B> <B>ColorOneScanner)</B>
Some capabilities are missing.
The above functionalities are missing because I don't have the hardware
to experiment on. Another reason is my lack of understanding as to how
or if the SANE API provide means to describe any array type besides
or if the SANE API provide means to describe any array type besides
gamma.
</PRE>
<H2>UNSUPPORTED FEATURES</H2><PRE>
The following "features" will never be supported, at least while I
The following "features" will never be supported, at least while I
maintain 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
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
AppleScanner may support multiple windows. It would be a cool
feature and a challenge for me to code if it could intermix dif-
ferent options for different windows (scan areas). This way it
could scan a document in LineArt mode but the figures in it in
Gray and at a different resolution. Unfortunately this is
impossible.
ferent options for different windows (scan areas). This way it
could scan a document in LineArt mode but the figures in it in
Gray and at a different resolution. Unfortunately this is im-
possible.
<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 on the OneScanner
This option controls the status of the button on the OneScanner
model. You can also reset the button status by software.
</PRE>
<H2>BUGS</H2><PRE>
SANE backend bugs are divided in two classes. We have <B>GUI</B> bugs and
SANE backend bugs 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 when it
should (active) or vice versa. Finding out which parameters are active
across various Apple modes and models from the documentation
<I>ftp://ftpdev.info.apple.com/devworld/Technical</I><B>_</B><I>Documentation/Peripher-</I>
<I>als</I><B>_</B><I>Documentation/</I> is an interesting exercise. I may have missed some
dependencies. For example of the threshold parameter the Apple Scanners
Programming Guide says nothing. I had to assume it is valid only in
LineArt mode.
We know we have a GUI bug when a parameter is not showing up when it
should (active) or vice versa. Finding out which parameters are active
across various Apple modes and models from the documentation is an in-
teresting exercise. I may have missed some dependencies. For example of
the threshold parameter the Apple Scanners Programming Guide says noth-
ing. I had to assume it is valid only in LineArt mode.
Scanner specific bugs are mostly due to mandatory round-offs in order
Scanner specific bugs are mostly due to mandatory round-offs in order
to scan. In the documentation in one place states that the width of the
scan area should be a byte multiple. In another place it says that the
scan area should be a byte multiple. In another place it says that the
width of the scan area should be an even byte multiple. Go figure...
Other sources of bugs are due to scsi communication, scsi connects and
disconnects. However the classical bugs are still there. So you may
encounter buffer overruns, null pointers, memory corruption and <B>SANE</B>
API violations.
Other sources of bugs are due to scsi communication, scsi connects and
disconnects. However the classical bugs are still there. So you may en-
counter 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 area 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, for the
It is possible, especially for the ColorOneScanner, for the
backend's options panel to extend beyond your screen. It happens
with mine and I am running my X Server at 1024x768. What can I
with mine and I am running my X Server at 1024x768. What can I
say? Try smaller fonts in the X server, or virtual screens.
<B>Weird</B> <B>SCSI</B> <B>behaviour</B>
@ -213,48 +210,48 @@
&gt;&gt; OS: FreeBSD 2.2.6
&gt;&gt; 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
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
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>
<H2>DEBUG</H2><PRE>
If you encounter a GUI bug please set the environmental variable
<B>SANE_DEBUG_APPLE</B> to 255 and rerun the exact sequence of keystrokes and
menu selections to reproduce it. Then send me a report with the log
attached.
If you encounter a GUI bug please set the environmental variable
<B>SANE_DEBUG_APPLE</B> to 255 and rerun the exact sequence of keystrokes and
menu selections to reproduce it. Then send me a report with the log at-
tached.
If you have an Apple Macintosh with the AppleScanners driver installed,
reporting to me which options are grayed out (inactive) in what modes
reporting to me which options are grayed out (inactive) in what modes
would be very helpful.
If you want to offer some help but you don't have a scanner, or you
don't have the model you would like to help with, or you are a SANE
developer and you just want to take a look at how the apple backend
looks like, goto to <I>apple.h</I> and #define the <B>NEUTRALIZE_BACKEND</B> macro.
You can select the scanner model through the APPLE_MODEL_SELECT macro.
Available options are <B>APPLESCANNER</B>, <B>ONESCANNER</B>, and <B>COLORONESCANNER</B>.
If you want to offer some help but you don't have a scanner, or you
don't have the model you would like to help with, or you are a SANE de-
veloper and you just want to take a look at how the apple backend looks
like, goto to <I>apple.h</I> and #define the <B>NEUTRALIZE_BACKEND</B> macro. You can
select the scanner model through the <B>APPLE_MODEL_SELECT</B> macro. Avail-
able options are <B>APPLESCANNER</B>, <B>ONESCANNER</B>, and <B>COLORONESCANNER</B>.
If you encounter a SCSI bus error or trimmed and/or displaced images
please set the environment variable SANE_DEBUG_SANEI_SCSI to 255 before
If you encounter a SCSI bus error or trimmed and/or displaced images
please set the environment variable <B>SANE_DEBUG_SANEI_SCSI</B> to 255 before
sending me the report.
</PRE>
<H2>TODO</H2><PRE>
<B>Non</B> <B>Blocking</B> <B>Support</B>
Make <B>sane-apple</B> a non blocking backend. Properly support
<B>sane_set_io_mode</B>() and <B>sane_get_select_fd</B>()
Make <B>sane-apple</B> a non blocking backend. Properly support
<B>sane_set_io_mode</B>() and <B>sane_get_select_fd</B>().
<B>Scan</B> Make scanning possible for all models in all supported modes.
Add other missing functionality
Add other missing functionality.
</PRE>
@ -264,9 +261,9 @@
</PRE>
<H2>AUTHOR</H2><PRE>
The <B>sane-apple</B> backend was written not entirely from scratch by Milon
Firikis. It is mostly based on the <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B> backend from David
Mosberger and Andreas Czechanowski
The <B>sane-apple</B> backend was written not entirely from scratch by Milon
Firikis. It is mostly based on the <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B> backend from David
Mosberger and Andreas Czechanowski.
11 Jul 2008 <B><A HREF="sane-apple.5.html">sane-apple(5)</A></B>
</PRE>

18
man/sane-artec.5.html
Wyświetl plik

@ -106,17 +106,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_ARTEC</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 en-
vironment 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: <B>SANE_DEBUG_ARTEC</B> values:

30
man/sane-artec_eplus48u.5.html
Wyświetl plik

@ -19,8 +19,8 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-artec_eplus48u</B> library implements a SANE (Scanner Access Now
Easy) backend that provides access to several USB flatbed scanners
using the GT6816 chipset like the Artec E+ 48U. These scanners have a
Easy) backend that provides access to several USB flatbed scanners us-
ing the GT6816 chipset like the Artec E+ 48U. These scanners have a
contact image sensor (CIS).
A complete list of supported devices can be found on
@ -41,8 +41,8 @@
</PRE>
<H2>KERNEL ISSUES</H2><PRE>
If libusb-0.1.6 or later is installed, this section can be skipped. The
scanner should be found by <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B> without further
actions. For setting permissions and general USB information look at
scanner should be found by <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B> without further ac-
tions. For setting permissions and general USB information look at
<B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>.
When you are using the scanner module, a Linux kernel 2.4.12 or newer
@ -62,7 +62,7 @@
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>artec</I><B>_</B><I>eplus48u.conf</I> file is a list of usb lines
The contents of the <I>artec</I><B>_</B><I>eplus48u.conf</I> file is a list of <I>usb</I> 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 <I>usb</I>
@ -70,7 +70,7 @@
<I>artec</I><B>_</B><I>eplus48u.conf</I> <I>.</I> "vendor_id" and "product_id" are hexadecimal
numbers that identify the scanner.
Every usb section can have additional options.
Every <I>usb</I> section can have additional options.
<B>artecFirmwareFile</B> <B>/usr/local/share/sane/artec_eplus48u/Artec48.usb</B>
The path to the firmware file. This option is required.
@ -131,17 +131,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_ARTEC_EPLUS48U</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 en-
vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_ARTEC_EPLUS48U=3

30
man/sane-avision.5.html
Wyświetl plik

@ -31,8 +31,8 @@
</PRE>
<H2>CONFIGURATION</H2><PRE>
The configuration file for this backend resides in
<I>/usr/local/etc/sane.d/avision.conf</I>.
The configuration file for this backend resides in <I>/usr/lo-</I>
<I>cal/etc/sane.d/avision.conf</I>.
Its contents is a list of device names that correspond to Avision and
Avision compatible scanners and backend-options. Empty lines and lines
@ -68,8 +68,8 @@
by the scanner (ADF not present, but ADF model number non-zero).
Without this option, the backend will make several attempts to
reset the ADF and retry the query in this situation, and will
fail with a "not supported" error if the ADF still doesn't
respond.
fail with a "not supported" error if the ADF still doesn't re-
spond.
disable-gamma-table:
Disables the usage of the scanner's gamma-table. You might try
@ -98,8 +98,8 @@
the device that corresponds to a SCSI scanner. The special device name
must be a generic SCSI device or a symlink to such a device, for exam-
ple on Linux <I>/dev/sga</I> or <I>/dev/sg0</I>. The device ID is the ID returned by
the scanner, for example "HP" or "AVISION". See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for
details.
the scanner, for example "HP" or "AVISION". See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for de-
tails.
Note: Since the backend now includes native USB access, it is no
longer needed - even considered obsolete - to access USB scanner
@ -140,17 +140,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_AVISION</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
If the library was compiled with debug support enabled, this en-
vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output. The
debug level 7 is the author's preferred value to debug backend
problems.

149
man/sane-bh.5.html
Wyświetl plik

@ -76,12 +76,12 @@
<B>Scan</B> <B>Mode</B> <B>Options:</B>
<B>--preview[=(yes|no)]</B> <B>[no]</B>
Request a preview-quality scan. When preview is set to yes
image compression is disabled and the image is delivered in a
Request a preview-quality scan. When preview is set to yes im-
age compression is disabled and the image is delivered in a
<B>SANE_FRAME_GRAY</B> frame.
<B>--mode</B> <B>lineart|halftone</B> <B>[lineart]</B>
Selects the scan mode (e.g., lineart,monochrome, or color).
Selects the scan mode (e.g., lineart, monochrome, or color).
<B>--resolution</B> <B>200|240|300dpi</B> <B>[200]</B>
Sets the resolution of the scanned image. Each scanner model
@ -130,9 +130,9 @@
<B>--source</B> <B>Automatic</B> <B>Document</B> <B>Feeder|Manual</B> <B>Feed</B> <B>Tray</B> <B>[Automatic</B> <B>Document</B>
<B>Feeder]</B>
Selects the scan source (such as a document feeder). This
option is provided to allow multiple image scans with
<B><A HREF="xsane.1.html">xsane(1)</A></B>;<B>it</B>has<B>no</B>other<B>purpose.</B>
Selects the scan source (such as a document feeder). This op-
tion is provided to allow multiple image scans with <B><A HREF="xsane.1.html">xsane(1)</A></B>; it
has no other purpose.
<B>--batch[=(yes|no)]</B> <B>[no]</B>
Enable/disable batch mode scanning. Batch mode allows scanning
@ -158,7 +158,7 @@
on the scanner model.
<B>--check-adf[=(yes|no)]</B> <B>[no]</B>
Check ADF Status prior to starting scan using the OBJECT POSI-
Check ADF status prior to starting scan using the OBJECT POSI-
TION command. Note that this feature requires RSC firmware
level 1.5 or higher and dip switch 4 must be in the on position.
NOTE: This option has not been tested extensively and may pro-
@ -168,10 +168,10 @@
<B>--control-panel[=(yes|no)]</B> <B>[yes]</B>
Enables the scanner's control panel for selecting image enhance-
ment parameters. When the option is set to no the following
options are used to control image enhancement. See the
Bell+Howell scanner users' guide for complete information on ACE
functionality.
ment parameters. When the option is set to no the following op-
tions are used to control image enhancement. See the Bell+How-
ell scanner users' guide for complete information on ACE func-
tionality.
<B>--ace-function</B> <B>-4..4</B> <B>[3]</B>
Specify the Automatic Contrast Enhancement (ACE) Function.
@ -253,8 +253,8 @@
<B>--section</B> <B>&lt;string&gt;</B> <B>[]</B>
Specifies a series of image sections. A section can be used to
gather a subset image or to provide a small area for barcode
decoding. Each section is specified in the following format
gather a subset image or to provide a small area for barcode de-
coding. Each section is specified in the following format
(units are in millimeters):
<B>&lt;width&gt;x&lt;height&gt;+&lt;top-left-x&gt;+&lt;top-left-y&gt;[:functioncode...]</B>
@ -317,24 +317,24 @@
The contents of the <I>bh.conf</I> file is a list of device names that corre-
spond to Bell+Howell scanners. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> on details of what
constitutes a valid device name. Additionally, options can be speci-
fied; these lines begin with the word "option". Each option is
described in detail below. Empty lines and lines starting with a hash
fied; these lines begin with the word "option". Each option is de-
scribed in detail below. Empty lines and lines starting with a hash
mark (#) are ignored.
</PRE>
<H2>OPTIONS</H2><PRE>
The following options can be specified in the <I>bh.conf</I> file.
The following options can be specified in the <I>bh.conf</I> file:
<B>disable-optional-frames</B>
This option prevents the backend from sending any optional
frames. This option may be useful when dealing with frontends
which do not support these optional frames. When this option is
in effect, the data is sent in a <B>SANE_FRAME_GRAY</B> frame. The
optional frames sent by this backend are: <B>SANE_FRAME_G31D</B>,
in effect, the data is sent in a <B>SANE_FRAME_GRAY</B> frame. The op-
tional frames sent by this backend are: <B>SANE_FRAME_G31D</B>,
<B>SANE_FRAME_G32D</B>, <B>SANE_FRAME_G42D</B> and <B>SANE_FRAME_TEXT</B>. These
frames are generated based on the compression and barcode
options. These frames are never sent in preview mode.
frames are generated based on the compression and barcode op-
tions. These frames are never sent in preview mode.
<B>fake-inquiry</B>
This option is used for debugging purposes and its use is not
@ -366,17 +366,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_BH</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 en-
vironment 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.
@ -387,32 +387,32 @@
With document scanners, automatic document feeder (ADF) support
is a key feature. The backend supports the ADF by default and
returns <B>SANE_STATUS_NO_DOCS</B> when the out-of-paper condition is
detected. The SANE frontend <B><A HREF="scanadf.1.html">scanadf(1)</A></B> is a command line fron-
tend that supports multi-page scans. It has been used success-
fully with this backend. The SANE frontend <B><A HREF="xsane.1.html">xsane(1)</A></B> is an
improved GUI frontend by Oliver Rauch. Support for multi-page
detected. The SANE frontend <B><A HREF="scanadf.1.html">scanadf(1)</A></B> is a command line front-
end that supports multi-page scans. It has been used success-
fully with this backend. The SANE frontend <B><A HREF="xsane.1.html">xsane(1)</A></B> is an im-
proved GUI frontend by Oliver Rauch. Support for multi-page
scans is included in xsane version 0.35 and above.
<B>Duplex</B> <B>scanning</B>
Some models, such as the COPISCAN II 6338, support duplex scan-
ning. That is, they scan both sides of the document during a
single pass through the scanner (the scanner has two cameras).
This backend supports duplex scanning (with the <B>--duplex</B>
option). The front and back page images are delivered consecu-
This backend supports duplex scanning (with the <B>--duplex</B> op-
tion). The front and back page images are delivered consecu-
tively as if they were separately scanned pages.
<B>Hardware</B> <B>compression</B>
The scanner is capable of compressing the data into several
industry standard formats (CCITT G3, CCITT G3-2D, CCITT G4).
This results in increased performance as less data is passed
from the scanner to the host over the SCSI bus. The backend
supports these compression formats via the <B>--g31d,</B> <B>--g32d,</B>
<B>--g42d</B> options, respectively. Many SANE frontends are not
equipped to deal with these formats, however. The SANE frontend
<B><A HREF="scanadf.1.html">scanadf(1)</A></B> supports these optional frame formats. The com-
pressed image data is written directly to a file and can then be
processed by a scan-script using the <B>--scan-script</B> option.
Examples of this are given on the <B><A HREF="scanadf.1.html">scanadf(1)</A></B> homepage.
The scanner is capable of compressing the data into several in-
dustry standard formats (CCITT G3, CCITT G3-2D, CCITT G4). This
results in increased performance as less data is passed from the
scanner to the host over the SCSI bus. The backend supports
these compression formats via the <B>--g31d,</B> <B>--g32d,</B> <B>--g42d</B> op-
tions, respectively. Many SANE frontends are not equipped to
deal with these formats, however. The SANE frontend <B><A HREF="scanadf.1.html">scanadf(1)</A></B>
supports these optional frame formats. The compressed image
data is written directly to a file and can then be processed by
a scan-script using the <B>--scan-script</B> option. Examples of this
are given on the <B><A HREF="scanadf.1.html">scanadf(1)</A></B> homepage.
<B>Automatic</B> <B>Border</B> <B>Detection</B>
The scanner can automatically detect the paper size and adjust
@ -426,21 +426,21 @@
<B>Icon</B> <B>Generation</B>
The Icon function generates a thumbnail of the full page image,
that can be transferred as if it were a separate page. This
allows the host to quickly display a thumbnail representation
during the scanning operation. Perhaps this would be a great
way of implementing a preview scan, but since a normal scan is
so quick, it might not be worth the trouble.
that can be transferred as if it were a separate page. This al-
lows the host to quickly display a thumbnail representation dur-
ing the scanning operation. Perhaps this would be a great way
of implementing a preview scan, but since a normal scan is so
quick, it might not be worth the trouble.
<B>Multiple</B> <B>Sections</B>
Multiple sections (scanning sub-windows) can be defined for the
front and back pages. Each section can have different charac-
teristics (e.g. geometry, compression). The sections are
returned as if they were separately scanned images. Addition-
ally sections can be used to greatly enhance the accuracy and
efficiency of the barcode/patchcode decoding process by limiting
the search area to a small subset of the page. Most Copiscan II
series scanners support up to 8 user-defined sections.
teristics (e.g. geometry, compression). The sections are re-
turned as if they were separately scanned images. Additionally
sections can be used to greatly enhance the accuracy and effi-
ciency of the barcode/patchcode decoding process by limiting the
search area to a small subset of the page. Most Copiscan II se-
ries scanners support up to 8 user-defined sections.
<B>Support</B> <B>Barcode/Patchcode</B> <B>Decoding</B>
The RSC unit can recognize Bar and Patch Codes of various types
@ -460,8 +460,8 @@
a time. While the code generally supports this as well, the
<B>--barcode-search-bar</B> option only allows the user to specify a
single barcode type. Perhaps another option which allows a
comma separated list of barcode type codes could be added to
address this.
comma separated list of barcode type codes could be added to ad-
dress this.
<B>Scanning</B> <B>a</B> <B>fixed</B> <B>number</B> <B>of</B> <B>pages</B> <B>in</B> <B>batch</B> <B>mode</B>
The separation of front and back end functionality in SANE
@ -471,28 +471,27 @@
will be the last, can cancel batch mode prior to initiating the
last scan command. Currently, there is no mechanism available
for the frontend to pass this knowledge to the backend. If
batch mode is enabled and the <B>--end-count</B> terminates a scanadf
session, an extra page will be pulled through the scanner, but
is neither read nor delivered to the frontend. The issue can be
avoided by specifying <B>--batch=no</B> when scanning a fixed number of
pages.
batch mode is enabled and the <B>--end-count</B> terminates a
<B><A HREF="scanadf.1.html">scanadf(1)</A></B> session, an extra page will be pulled through the
scanner, but is neither read nor delivered to the frontend. The
issue can be avoided by specifying <B>--batch=no</B> when scanning a
fixed number of pages.
<B>Revision</B> <B>1.2</B> <B>Patch</B> <B>detector</B>
There is an enhanced patchcode detection algorithm available in
the RSC with revision 1.2 or higher that is faster and more
reliable than the standard Bar/Patch code decoder. This is not
the RSC with revision 1.2 or higher that is faster and more re-
liable than the standard Bar/Patch code decoder. This is not
currently supported.
</PRE>
<H2>BUGS</H2><PRE>
This is a new backend; detailed bug reports are welcome -- and expected
;)
Detailed bug reports are welcome -- and expected ;)
If you have found something that you think is a bug, please attempt to
If you have found something that you think is a bug, please attempt to
recreate it with the <B>SANE_DEBUG_BH</B> environment variable set to 255, and
send a report detailing the conditions surrounding the bug to
<I>sane-devel@alioth-lists.debian.net</I>.
send a report detailing the conditions surrounding the bug to <I>sane-de-</I>
<I>vel@alioth-lists.debian.net</I>.
</PRE>
@ -502,10 +501,10 @@
</PRE>
<H2>AUTHOR</H2><PRE>
The <B>sane-bh</B> <B>backend</B> was written by Tom Martone, based on the
<B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B> backend by Feico W. Dillema and the bnhscan program by
Sean Reifschneider of tummy.com ltd. Some 8000 enhancements added by
Mark Temple.
The <B>sane-bh</B> <B>backend</B> was written by Tom Martone, based on the <B>sane-ri-</B>
<B><A HREF="coh.5.html">coh(5)</A></B> backend by Feico W. Dillema and the bnhscan program by Sean
Reifschneider of tummy.com ltd. Some 8000 enhancements added by Mark
Temple.
10 Jul 2008 <B><A HREF="sane-bh.5.html">sane-bh(5)</A></B>
</PRE>

18
man/sane-canon.5.html
Wyświetl plik

@ -34,11 +34,11 @@
IMPORTANT: This is beta code. We tested the code on the scanners listed
above, using the computers and operating systems available to us, but
we cannot guarantee that the backend will work smoothly with future
operating systems, SCSI adapters, SANE frontend programs, or Canon
scanners not contained in the list above. In some cases your computer
might even hang. It cannot be excluded (although we consider it
extremely unlikely) that your scanner will be damaged.
we cannot guarantee that the backend will work smoothly with future op-
erating systems, SCSI adapters, SANE frontend programs, or Canon scan-
ners not contained in the list above. In some cases your computer might
even hang. It cannot be excluded (although we consider it extremely
unlikely) that your scanner will be damaged.
That said, TESTERS ARE WELCOME. Send your bug reports and comments to
Manuel Panea <I>&lt;mpd@rzg.mpg.de&gt;</I>; for questions concerning the FB620 and
@ -53,8 +53,8 @@
and blue). It is recommended to use the automatic exposure controls of
the frontend <B><A HREF="xsane.1.html">xsane(1)</A></B> for best results.
The "Auto Focus" function triggers a special pass to determine the
focus value. After that, the real scanning pass takes place.
The "Auto Focus" function triggers a special pass to determine the fo-
cus value. After that, the real scanning pass takes place.
Even with "Auto Focus" turned on, the scanned image is often a bit too
blurred. Using the <B><A HREF="gimp.1.html">gimp(1)</A></B> to do a "Filter-&gt;Enhance-&gt;Sharpen" at about
@ -88,8 +88,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_CANON</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 en-
vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_CANON=4

22
man/sane-canon630u.5.html
Wyświetl plik

@ -59,8 +59,8 @@
seems to be a hardware specific issue, although I dsane-uson't know
what exactly the problem is. If you are having problems, please send
me the info in <I>/proc/bus/usb/devices</I>, <I>/proc/pci</I>, the kernel <I>scanner.c</I>
driver version from <I>/var/log/messages</I>, and the output from
<I>SANE</I><B>_</B><I>DEBUG</I><B>_</B><I>CANON630U=12</I> <I>scanimage</I> <I>&gt;</I> <I>/dev/null</I>
driver version from <I>/var/log/messages</I>, and the output from <I>SANE</I><B>_</B><I>DE-</I>
<I>BUG</I><B>_</B><I>CANON630U=12</I> <I>scanimage</I> <I>&gt;</I> <I>/dev/null</I>
</PRE>
@ -90,17 +90,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_CANON630U</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 en-
vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example:

81
man/sane-canon_dr.5.html
Wyświetl plik

@ -71,12 +71,12 @@
Additionally, several 'software' options are exposed by the backend.
These are reimplementations of features provided natively by larger
scanners, but running on the host computer. This enables smaller
machines to have similar capabilities. Please note that these features
are somewhat simplistic, and may not perform as well as the native
implementations. Note also that these features all require that the
driver cache the entire image in memory. This will almost certainly
result in a reduction of scanning speed.
scanners, but running on the host computer. This enables smaller ma-
chines to have similar capabilities. Please note that these features
are somewhat simplistic, and may not perform as well as the native im-
plementations. Note also that these features all require that the
driver cache the entire image in memory. This will almost certainly re-
sult in a reduction of scanning speed.
<B>--swcrop</B>
Requests the driver to detect the extremities of the paper
@ -91,81 +91,80 @@
smaller from the image, and fill the space with the average sur-
rounding color.
Use 'scanimage --help' to get a list, but be aware that some
options may be settable only when another option has been set,
and that advanced options may be hidden by some frontend pro-
grams.
Use 'scanimage --help' to get a list, but be aware that some op-
tions may be settable only when another option has been set, and
that advanced options may be hidden by some frontend programs.
</PRE>
<H2>CONFIGURATION FILE</H2><PRE>
The configuration file <I>canon</I><B>_</B><I>dr.conf</I> is used to tell the backend how to
look for scanners, and provide options controlling the operation of the
backend. This file is read each time the frontend asks the backend for
a list of scanners, generally only when the frontend starts. If the
backend. This file is read each time the frontend asks the backend for
a list of scanners, generally only when the frontend starts. If the
configuration file is missing, the backend will fail to run.
Scanners can be specified in the configuration file in 4 ways:
"scsi CANON DR"
Requests backend to search all scsi buses in the system for a
device which reports itself to be a scanner made by 'CANON',
Requests backend to search all scsi buses in the system for a
device which reports itself to be a scanner made by 'CANON',
with a model name starting with 'DR'.
"scsi /dev/sg0" (or other scsi device file)
Requests backend to open the named scsi device. Only useful if
you have multiple compatible scanners connected to your system,
and need to specify one. Probably should not be used with the
Requests backend to open the named scsi device. Only useful if
you have multiple compatible scanners connected to your system,
and need to specify one. Probably should not be used with the
other "scsi" line above.
"usb 0x04a9 0x1603" (or other vendor/product ids)
Requests backend to search all usb buses in the system for a
device which uses that vendor and product id. The device will
then be queried to determine if it is a Canon scanner.
Requests backend to search all usb buses in the system for a de-
vice which uses that vendor and product id. The device will then
be queried to determine if it is a Canon scanner.
"usb /dev/usb/scanner0" (or other device file)
Some systems use a kernel driver to access usb scanners. This
Some systems use a kernel driver to access usb scanners. This
method is untested.
Besides the 'scsi' and 'usb' lines, the configuration file supports the
following 'option' lines:
"option buffer-size [number of bytes]"
Set the number of bytes in the data buffer to something other
than the compiled-in default of 4MB. Large values may cause
Set the number of bytes in the data buffer to something other
than the compiled-in default of 4MB. Large values may cause
timeouts or hangs, small values may cause slow scans.
Note: The backend does not place an upper bound on this value,
as some users required it to be quite large. Values above the
default are not recommended, and may crash your OS or lockup
Note: The backend does not place an upper bound on this value,
as some users required it to be quite large. Values above the
default are not recommended, and may crash your OS or lockup
your scsi card driver. You have been warned.
"option vendor-name [string of text]"
"option model-name [string of text]"
"option version-name [string of text]"
These options can be used collectively to override the values
These options can be used collectively to override the values
provided by the scanner, or to provide the values when the scan-
ner cannot.
"option padded-read [0|1]"
Some scanners prepend all data transmitted to host with 12
bytes. Enable this option if the scanner fails to respond to
Some scanners prepend all data transmitted to host with 12
bytes. Enable this option if the scanner fails to respond to
commands.
"option duplex-offset [integer]"
Some scanners pad the upper edge of one side of a duplex scan.
There is some variation in the amount of padding. Modify this
Some scanners pad the upper edge of one side of a duplex scan.
There is some variation in the amount of padding. Modify this
option if your unit shows an unwanted band of image data on only
one side.
<B>NOTE</B>: "option" lines may appear multiple times in the configuration
file. They only apply to scanners discovered by the next 'scsi/usb'
<B>NOTE</B>: "option" lines may appear multiple times in the configuration
file. They only apply to scanners discovered by the next 'scsi/usb'
line.
</PRE>
<H2>ENVIRONMENT</H2><PRE>
The backend uses a single environment variable, <B>SANE_DEBUG_CANON_DR</B>,
The backend uses a single environment variable, <B>SANE_DEBUG_CANON_DR</B>,
which enables debugging output to stderr. Valid values are:
5 Errors
@ -179,25 +178,25 @@
</PRE>
<H2>KNOWN ISSUES</H2><PRE>
This backend was entirely reverse engineered from usb traces of the
proprietary driver. Various advanced features of the machines may not
be enabled. Many machines have not been tested. Their protocol is
unknown.
This backend was entirely reverse engineered from usb traces of the
proprietary driver. Various advanced features of the machines may not
be enabled. Many machines have not been tested. Their protocol is un-
known.
</PRE>
<H2>CREDITS</H2><PRE>
The various authors of the <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B> backend provided useful
The various authors of the <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B> backend provided useful
code.
Yabarana Corp. <I>www.yabarana.com</I> provided significant funding.
EvriChart, Inc. <I>www.evrichart.com</I> provided funding and loaned equip-
EvriChart, Inc. <I>www.evrichart.com</I> provided funding and loaned equip-
ment.
Canon, USA. <I>www.usa.canon.com</I> loaned equipment.
HPrint <I>hprint.com.br</I> provided funding and testing for DR-2510 support.
Stone-IT <I>www.stone-it.com</I> provided funding for DR-2010 and DR-2050 sup-
port.
Gerhard Pfeffer provided access and testing for P-208 and P-215.
Special thanks to: Alejandro Imass, Andre Shimakawa, Martijn van Brum-
Special thanks to: Alejandro Imass, Andre Shimakawa, Martijn van Brum-
melen, Thanos Diacakis and Junren Shi for testing and feedback.

4
man/sane-canon_lide70.5.html
Wyświetl plik

@ -93,8 +93,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_CANON_LIDE70</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 en-
vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example:

147
man/sane-canon_pp.5.html
Wyświetl plik

@ -32,8 +32,8 @@
No USB scanners are supported and there are no plans to support them in
the future. Other projects are working on support for USB scanners.
See the <I>PROJECTS</I> file for more detail. The FB310P and FB610P are re-
badged Avision scanners which use a different command set, so are
unlikely to be supported by this backend in the future.
badged Avision scanners which use a different command set, so are un-
likely to be supported by this backend in the future.
IMPORTANT: this is alpha code. While we have made every effort to make
it as reliable as possible, it will not always work as expected. Feed-
@ -43,9 +43,9 @@
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form presented by
<B><A HREF="libieee1284.3.html">libieee1284(3)</A></B>. These names are highly dependent on operating system
and version.
This backend expects device names of the form presented by <B>li-</B>
<B><A HREF="bieee1284.3.html">bieee1284(3)</A></B>. These names are highly dependent on operating system and
version.
On Linux 2.4 kernels this will be of the form <I>parport0</I> or older (2.2
and before) kernels may produce names like <I>0x378</I> (the base address of
@ -64,38 +64,43 @@
The supported options are currently <B>ieee1284</B>, <B>calibrate</B>, <B>init_mode</B>, and
<B>force_nibble</B>
Option <B>ieee1284</B> <I>port-name</I> defines which port to use. The format of
port-name is OS dependent, based on the names presented by libieee1284.
Please only have one of these lines, or all but one will be ignored.
<B>ieee1284</B> <B>port-name</B>
Defines which port to use. The format of port-name is OS depen-
dent, based on the names presented by <B><A HREF="libieee1284.3.html">libieee1284(3)</A></B>. Please
only have one of these lines, or all but one will be ignored.
Option <B>calibrate</B> <I>cal-file</I> <I>[port-name]</I> defines which calibration file to
use on a per-port basis. If you only have one parport, the port-name
argument may be omitted - but be careful as this will cause problems on
multi-scanner systems. You may have as many of these lines as you
like, as long as each has a unique port name. The tilde (`~') charac-
ter is acceptable and will be expanded to the value of the HOME envi-
ronment.
<B>calibrate</B> <B>cal-file</B> <B>[port-name]</B>
Defines which calibration file to use on a per-port basis. If
you only have one parport, the port-name argument may be omitted
- but be careful as this will cause problems on multi-scanner
systems. You may have as many of these lines as you like, as
long as each has a unique port name. The tilde (`~') character
is acceptable and will be expanded to the value of the <B>HOME</B> en-
vironment variable.
Option <B>init_mode</B> <I>&lt;AUTO|FB620P|FB630P&gt;</I> <I>[portname]</I> defines which initial-
isation (wake-up) mode to use on a per-port basis. If you only have
one parport, the portname argument may be omitted - but be careful as
this may cause problems on multi-scanner systems. You may have as many
of these lines as you like, as long as each has a unique port name.
The valid initialisation modes are FB620P (which strobes 10101010 and
01010101 on the data pins), FB630P (which strobes 11001100 and 00110011
on the data pins) and AUTO, which will try FB630P mode first then
FB620P mode second. The FB620P mode is also used by the FB320P. The
FB630P mode is used by the FB330P, N340P, and N640P.
<B>init_mode</B> <B>&lt;AUTO|FB620P|FB630P&gt;</B> <B>[port-name]</B>
Defines which initialisation (wake-up) mode to use on a per-port
basis. If you only have one parport, the port-name argument may
be omitted - but be careful as this may cause problems on multi-
scanner systems. You may have as many of these lines as you
like, as long as each has a unique port name. The valid ini-
tialisation modes are FB620P (which strobes 10101010 and
01010101 on the data pins), FB630P (which strobes 11001100 and
00110011 on the data pins) and AUTO, which will try FB630P mode
first then FB620P mode second. The FB620P mode is also used by
the FB320P. The FB630P mode is used by the FB330P, N340P, and
N640P.
Option <B>force_nibble</B> forces the driver to use nibble mode even if ECP
mode is reported to work by libieee1284. This works-around the rare
issue of ECP mode being reported to work by the library, then not work-
ing.
<B>force_nibble</B>
Forces the driver to use nibble mode even if ECP mode is re-
ported to work by <B><A HREF="libieee1284.3.html">libieee1284(3)</A></B>. This works-around the rare
issue of ECP mode being reported to work by the library, then
not working.
</PRE>
<H2>TIPS</H2><PRE>
Hit the "Calibrate" button before scanning. It vastly improves the
Hit the "Calibrate" button before scanning. It vastly improves the
quality of scans.
To enable automatic detection of your scanner, uncomment the "canon_pp"
@ -105,7 +110,7 @@
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/canon</I><B>_</B><I>pp.conf</I>
The backend configuration file (see also description of
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-canon</I><B>_</B><I>pp.a</I>
@ -122,19 +127,19 @@
This environment variable specifies the list of directories that
may contain the configuration file. On *NIX systems, the direc-
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
arated 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 <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_CANON_PP</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
If the library was compiled with debug support enabled, this en-
vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_CANON_PP=4
@ -145,68 +150,68 @@
<B>Features</B> <B>available</B> <B>in</B> <B>the</B> <B>Windows</B> <B>interface</B>
<B>Brightness</B> <B>and</B> <B>Contrast</B>
These are not implemented, and probably never will be. These
appear to be implemented entirely in software. Use GIMP or a
These are not implemented, and probably never will be. These
appear to be implemented entirely in software. Use GIMP or a
similar program if you need these features.
<B>Descreen</B> <B>Mode</B>
This appears on our first analysis to be just oversampling with
an anti-aliasing filter. Again, it seems to be implemented
entirely in software, so GIMP is your best bet for now.
This appears on our first analysis to be just oversampling with
an anti-aliasing filter. Again, it seems to be implemented en-
tirely in software, so GIMP is your best bet for now.
<B>Gamma</B> <B>Tables</B>
This is under investigation, but for now only a simple gamma
profile (ie: the one returned during calibration) will be
This is under investigation, but for now only a simple gamma
profile (ie: the one returned during calibration) will be
loaded.
<B>Communication</B> <B>Problems</B>
ECP mode in libieee1284 doesn't always work properly, even with new
hardware. We believe that this is a ppdev problem. If you change the
configuration file to include <B>force_nibble</B> , the problem will go away,
ECP mode in <B><A HREF="libieee1284.3.html">libieee1284(3)</A></B> doesn't always work properly, even with new
hardware. We believe that this is a ppdev problem. If you change the
configuration file to include <B>force_nibble</B> , the problem will go away,
but you will only be able to scan in nibble mode.
Sometimes the scanner can be left in a state where our code cannot
revive it. If the backend reports no scanner present, try unplugging
the power and plugging it back in. Also try unplugging printers from
the pass-through port.
Sometimes the scanner can be left in a state where our code cannot re-
vive it. If the backend reports no scanner present, try unplugging the
power and plugging it back in. Also try unplugging printers from the
pass-through port.
The scanner will not respond correctly to our commands when you first
plug in the power. You may find if you try a scan very soon after
The scanner will not respond correctly to our commands when you first
plug in the power. You may find if you try a scan very soon after
plugging in the power that the backend will incorrectly report that you
have no scanner present. To avoid this, give it about 10 seconds to
have no scanner present. To avoid this, give it about 10 seconds to
reset itself before attempting any scans.
<B>Repeated</B> <B>Lines</B>
Sometimes at high resolutions (ie. 600dpi) you will notice lines which
appear twice. These lines correspond to points where the scanner head
Sometimes at high resolutions (ie. 600dpi) you will notice lines which
appear twice. These lines correspond to points where the scanner head
has stopped during the scan (it stops every time the internal 64kb buf-
fer is full). Basically it's a mechanical problem inside the scanner,
that the tolerance of movement for a start/stop event is greater than
1/600 inches. I've never tried the windows driver so I'm not sure how
(or if) it works around this problem, but as we don't know how to
rewind the scanner head to do these bits again, there's currently no
fer is full). Basically it's a mechanical problem inside the scanner,
that the tolerance of movement for a start/stop event is greater than
1/600 inches. I've never tried the windows driver so I'm not sure how
(or if) it works around this problem, but as we don't know how to
rewind the scanner head to do these bits again, there's currently no
nice way to deal with the problem.
<B>Grey-scale</B> <B>Scans</B>
Be aware that the scanner uses the green LEDs to read grey-scale scans,
meaning green coloured things will appear lighter than normal, and red
meaning green coloured things will appear lighter than normal, and red
and blue coloured items will appear darker than normal. For high-accu-
racy grey-scale scans of colour items, it's best just to scan in colour
and convert to grey-scale in graphics software such as the GIMP.
<B>FB620P/FB320P</B> <B>Caveats</B>
These models can not be reset in the same way as the others. The win-
dows driver doesn't know how to reset them either - when left with an
These models can not be reset in the same way as the others. The win-
dows driver doesn't know how to reset them either - when left with an
inconsistent scanner, it will start scanning half way down the page!
Aborting is known to work correctly on the FB*30P models, and is known
Aborting is known to work correctly on the FB*30P models, and is known
to be broken on the FB*20P models. The FB620P which I tested on simply
returns garbage after a scan has been aborted using the method we know.
Aborting is able to leave the scanner in a state where it can be shut
Aborting is able to leave the scanner in a state where it can be shut
down, but not where another scan can be made.

10
man/sane-cardscan.5.html
Wyświetl plik

@ -50,9 +50,9 @@
Scanners can be specified in the configuration file in 2 ways:
"usb 0x04c5 0x1042" (or other vendor/product ids)
Requests backend to search all usb buses in the system for a
device which uses that vendor and product id. The device will
then be queried to determine if it is a cardscan scanner.
Requests backend to search all usb buses in the system for a de-
vice which uses that vendor and product id. The device will then
be queried to determine if it is a cardscan scanner.
"usb /dev/usb/scanner0" (or other device file)
Some systems use a kernel driver to access usb scanners. This
@ -62,8 +62,8 @@
tocol used by the backend:
"lines_per_block 16" (or other number from 1 to 32)
Controls the number of lines of image data which will be
acquired in each pass. Older scanners will require this number
Controls the number of lines of image data which will be ac-
quired in each pass. Older scanners will require this number
set lower, often 1.
"has_cal_buffer 1" (1 or 0)

4
man/sane-config.1.html
Wyświetl plik

@ -45,8 +45,8 @@
SANE frontend to libsane.
<B>--ldflags</B>
Print the linker flags that are necessary to link a SANE fron-
tend to libsane.
Print the linker flags that are necessary to link a SANE front-
end to libsane.
<B>--cflags</B>
Print the compiler flags that are necessary to compile a SANE

16
man/sane-coolscan.5.html
Wyświetl plik

@ -35,12 +35,12 @@
</PRE>
<H2>CONFIGURATION</H2><PRE>
The configuration file for this backend resides in
<I>/usr/local/etc/sane.d/coolscan.conf</I>.
The configuration file for this backend resides in <I>/usr/lo-</I>
<I>cal/etc/sane.d/coolscan.conf</I>.
Its content is a list of device names that correspond to Nikon Coolscan
scanners. Empty lines and lines starting with a hash mark (#) are
ignored. A sample configuration file is shown below:
scanners. Empty lines and lines starting with a hash mark (#) are ig-
nored. A sample configuration file is shown below:
#scsi Vendor Model Type
scsi Nikon * Scanner
@ -57,8 +57,8 @@
Some SCSI-adapters and low-level SCSI drivers do not work correctly
with this backend and the Coolscan scanners. These systems hang when
the autofocus command is send to the Scanner. To see a list of which
card/driver combinations work or don't work have a look at:
<I>http://andreas.rick.free.fr/sane/autofocus.html.</I>
card/driver combinations work or don't work have a look at: <I>http://an-</I>
<I>dreas.rick.free.fr/sane/autofocus.html.</I>
</PRE>
@ -77,8 +77,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_COOLSCAN</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 en-
vironment 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.

48
man/sane-coolscan2.5.html
Wyświetl plik

@ -20,8 +20,8 @@
The <B>sane-coolscan2</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to Nikon Coolscan film scanners. Some
functions of this backend should be considered <B>beta-quality</B> software.
Most functions have been stable for a long time, but of course new
development can not and will not function properly from the very first
Most functions have been stable for a long time, but of course new de-
velopment can not and will not function properly from the very first
day. Please report any strange behaviour to the maintainer of the back-
end.
@ -50,9 +50,9 @@
scanimage --help -d coolscan2:&lt;interface&gt;:&lt;device&gt;
where &lt;interface&gt; and &lt;device&gt; specify the device in question, as in
the configuration file (see next section). The <B>-d</B> parameter and its
argument can be omitted to obtain information on the first scanner
identified. Use the command:
the configuration file (see next section). The <B>-d</B> parameter and its ar-
gument can be omitted to obtain information on the first scanner iden-
tified. Use the command:
scanimage -L
@ -71,8 +71,8 @@
start the frontend).
<B>--subframe</B> <B>&lt;x&gt;</B>
This option shifts the scan window by the specified amount
(default unit is mm).
This option shifts the scan window by the specified amount (de-
fault unit is mm).
<B>--infrared=yes/no</B>
If set to "yes", the scanner will read the infrared channel,
@ -115,10 +115,10 @@
<B>--reset</B>
Reset scanner. The scanner will perform the same action as when
power is turned on: it will eject the film strip (with the
SF-200 bulk feeder) and calibrate itself. Use this whenever the
scanner refuses to load a film strip properly, as a result of
which <B>--eject</B> does not work.
power is turned on: it will eject the slide (with the SF-200
bulk feeder) and calibrate itself. Use this whenever the scanner
refuses to load a slide properly, as a result of which <B>--eject</B>
does not work.
</PRE>
@ -138,8 +138,8 @@
<I>containing</I> <I>only</I> <I>the</I> <I>word</I> <I>"auto"</I>
This instructs the backend to probe for a scanner by scanning
the buses for devices with known identifiers. This is the
default action when no configuration file is present.
the buses for devices with known identifiers. This is the de-
fault action when no configuration file is present.
<I>a</I> <I>line</I> <I>of</I> <I>the</I> <I>form</I> <I>&lt;interface&gt;:&lt;device&gt;</I>
Here &lt;interface&gt; can be one of "scsi" or "usb", and &lt;device&gt; is
@ -165,8 +165,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_COOLSCAN2</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
If the library was compiled with debug support enabled, this en-
vironment 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.
@ -178,13 +178,13 @@
</PRE>
<H2>BUGS</H2><PRE>
Currently, the SANE protocol does not allow automatically updating
options whenever the hardware changes. Thus the number of choices for
the <B>--frame</B> option will be fixed when the backend is initialized (usu-
ally when the user runs the frontend). In particular, if there is no
film strip in the automatic film strip feeder when the backend is ini-
tialized, the <B>--frame</B> option will not appear at all. Also, restarting
the frontend after swapping film adapters is strongly recommended.
Currently, the SANE protocol does not allow automatically updating op-
tions whenever the hardware changes. Thus the number of choices for the
<B>--frame</B> option will be fixed when the backend is initialized (usually
when the user runs the frontend). In particular, if there is no film
strip in the automatic film strip feeder when the backend is initial-
ized, the <B>--frame</B> option will not appear at all. Also, restarting the
frontend after swapping film adapters is strongly recommended.
Linux kernels prior to 2.4.19 had a patch that truncated INQUIRY data
from IEEE 1394 scanners to 36 bytes, discarding vital information about
@ -197,8 +197,8 @@
</PRE>
<H2>AUTHORS</H2><PRE>
The backend is written and maintained by Andr<B>a</B>s Major
<I>&lt;andras@users.sourceforge.net&gt;</I>.
The backend is written and maintained by Andr<B>a</B>s Major <I>&lt;an-</I>
<I>dras@users.sourceforge.net&gt;</I>.
11 Jul 2008 <B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B>
</PRE>

50
man/sane-coolscan3.5.html
Wyświetl plik

@ -20,8 +20,8 @@
The <B>sane-coolscan3</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to Nikon Coolscan film scanners. Some
functions of this backend should be considered <B>beta-quality</B> software.
Most functions have been stable for a long time, but of course new
development can not and will not function properly from the very first
Most functions have been stable for a long time, but of course new de-
velopment can not and will not function properly from the very first
day.
At present, the following scanners are known to work with this backend:
@ -50,9 +50,9 @@
scanimage --help -d coolscan3:&lt;interface&gt;:&lt;device&gt;
where &lt;interface&gt; and &lt;device&gt; specify the device in question, as in
the configuration file (see next section). The <B>-d</B> parameter and its
argument can be omitted to obtain information on the first scanner
identified. Use the command:
the configuration file (see next section). The <B>-d</B> parameter and its ar-
gument can be omitted to obtain information on the first scanner iden-
tified. Use the command:
scanimage -L
@ -71,16 +71,16 @@
start the frontend).
<B>--subframe</B> <B>&lt;x&gt;</B>
This option shifts the scan window by the specified amount
(default unit is mm).
This option shifts the scan window by the specified amount (de-
fault unit is mm).
<B>--infrared=yes/no</B>
If set to "yes", the scanner will read the infrared channel,
thus allowing defect removal in software. The infrared image is
read during a second scan, with no options altered. The backend
must not be restarted between the scans. If you use scanimage,
perform a batch scan with <B>--batch-count=2</B> to obtain the IR
information.
must not be restarted between the scans. If you use <B>scanim-</B>
<B><A HREF="age.1.html">age(1)</A></B>, perform a batch scan with <B>--batch-count=2</B> to obtain the
IR information.
<B>--depth</B> <B>&lt;n&gt;</B>
Here &lt;n&gt; can either be 8 or the maximum number of bits supported
@ -115,10 +115,10 @@
<B>--reset</B>
Reset scanner. The scanner will perform the same action as when
power is turned on: it will eject the film strip (with the
SF-200 bulk loader) and calibrate itself. Use this whenever the
scanner refuses to load a film strip properly, as a result of
which <B>--eject</B> does not work.
power is turned on: it will eject the slide (with the SF-200
bulk loader) and calibrate itself. Use this whenever the scanner
refuses to load a slide properly, as a result of which <B>--eject</B>
does not work.
</PRE>
@ -138,8 +138,8 @@
<I>containing</I> <I>only</I> <I>the</I> <I>word</I> <I>"auto"</I>
This instructs the backend to probe for a scanner by scanning
the buses for devices with known identifiers. This is the
default action when no configuration file is present.
the buses for devices with known identifiers. This is the de-
fault action when no configuration file is present.
<I>a</I> <I>line</I> <I>of</I> <I>the</I> <I>form</I> <I>&lt;interface&gt;:&lt;device&gt;</I>
Here &lt;interface&gt; can be one of "scsi" or "usb", and &lt;device&gt; is
@ -165,8 +165,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_COOLSCAN3</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 en-
vironment 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.
@ -178,13 +178,13 @@
</PRE>
<H2>BUGS</H2><PRE>
Currently, the SANE protocol does not allow automatically updating
options whenever the hardware changes. Thus the number of choices for
the <B>--frame</B> option will be fixed when the backend is initialized (usu-
ally when the user runs the frontend). In particular, if there is no
film strip in the automatic film strip feeder when the backend is ini-
tialized, the <B>--frame</B> option will not appear at all. Also, restarting
the frontend after swapping film adapters is strongly recommended.
Currently, the SANE protocol does not allow automatically updating op-
tions whenever the hardware changes. Thus the number of choices for the
<B>--frame</B> option will be fixed when the backend is initialized (usually
when the user runs the frontend). In particular, if there is no film
strip in the automatic film strip feeder when the backend is initial-
ized, the <B>--frame</B> option will not appear at all. Also, restarting the
frontend after swapping film adapters is strongly recommended.
Linux kernels prior to 2.4.19 had a patch that truncated INQUIRY data
from IEEE 1394 scanners to 36 bytes, discarding vital information about

18
man/sane-dc210.5.html
Wyświetl plik

@ -18,8 +18,8 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-dc210</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to the Kodak DC210 camera. THIS IS
EXTREMELY ALPHA CODE! USE AT YOUR OWN RISK!!
backend that provides access to the Kodak DC210 camera. THIS IS EX-
TREMELY ALPHA CODE! USE AT YOUR OWN RISK!!
</PRE>
@ -82,13 +82,13 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d.</I> 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d.</I> If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_DC210</B>
If the library was compiled with debugging support enabled, this

24
man/sane-dc240.5.html
Wyświetl plik

@ -18,8 +18,8 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-dc240</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to the Kodak DC240 camera. THIS IS
EXTREMELY ALPHA CODE! USE AT YOUR OWN RISK!!
backend that provides access to the Kodak DC240 camera. THIS IS EX-
TREMELY ALPHA CODE! USE AT YOUR OWN RISK!!
</PRE>
@ -82,13 +82,13 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d.</I> 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d.</I> If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_DC240</B>
If the library was compiled with debugging support enabled, this
@ -115,9 +115,9 @@
</PRE>
<H2>BUGS</H2><PRE>
The major limitation that I know of is that the backend assumes the
directory in the camera is 100dc240. Once the camera has taken more
than 9999 pictures, the directory will increment to 101dc240. Not only
The major limitation that I know of is that the backend assumes the di-
rectory in the camera is 100dc240. Once the camera has taken more than
9999 pictures, the directory will increment to 101dc240. Not only
should we check for the additional directory, but pictures may actually
be found in multiple directories.

18
man/sane-dc25.5.html
Wyświetl plik

@ -42,8 +42,8 @@
The dumpinquiry line causes some information about the camera to be
printed to stderr during startup. Note: This is not compatible with
saned, so make sure you don't have any dumpinquiry lines if you are
using saned (i.e. scanning on a remote machine using a network).
saned, so make sure you don't have any dumpinquiry lines if you are us-
ing saned (i.e. scanning on a remote machine using a network).
Empty lines and lines starting with a hash mark (#) are ignored. A
sample configuration file is shown below:
@ -76,13 +76,13 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_DC25</B>
If the library was compiled with debugging support enabled, this

43
man/sane-dll.5.html
Wyświetl plik

@ -19,8 +19,8 @@
<H2>DESCRIPTION</H2><PRE>
The <B>sane-dll</B> library implements a SANE (Scanner Access Now Easy) back-
end that provides access to an arbitrary number of other SANE backends.
These backends may either be pre-loaded at the time the <B>sane-dll</B>
library is built or, on systems that support dynamic loading of shared
These backends may either be pre-loaded at the time the <B>sane-dll</B> li-
brary is built or, on systems that support dynamic loading of shared
libraries, the backends may be loaded at runtime. In the latter case,
adding support for a new backend simply involves installing the rele-
vant library in <I>/usr/local/lib/sane</I> and adding an entry to the <I>dll.conf</I>
@ -45,8 +45,8 @@
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>dll.conf</I> file is a list of backend names that may
be loaded dynamically upon demand. Empty lines are ignored, also
everything after a hash mark (#). A sample configuration file is shown
be loaded dynamically upon demand. Empty lines are ignored, also ev-
erything after a hash mark (#). A sample configuration file is shown
below:
net
@ -70,8 +70,8 @@
After changing the value of this macro, it is necessary to reconfigure,
rebuild, and reinstall SANE for the change to take effect.
Aliases are defined in the config file <I>dll.aliases</I>. It can contain
entries of the form
Aliases are defined in the config file <I>dll.aliases</I>. It can contain en-
tries of the form
alias SomeName SaneDeviceName
alias "Some Name" SaneDeviceName
@ -90,9 +90,8 @@
The idea is that users don't have to deal with complicated device names
(especially for networked devices), and to hide other exported devices
which might confuse them. Note that a hidden device can still be
accessed if the device name is known, it just doesn't appear on the
list.
which might confuse them. Note that a hidden device can still be ac-
cessed if the device name is known, it just doesn't appear on the list.
</PRE>
@ -101,7 +100,7 @@
The list of aliased or hidden backends.
<I>/usr/local/etc/sane.d/dll.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-dll.a</I>
@ -118,20 +117,20 @@
This environment variable specifies the list of directories that
may contain the configuration file. On *NIX systems, the direc-
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
arated 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 <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_DLL</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 en-
vironment 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.
Value Description

26
man/sane-dmc.5.html
Wyświetl plik

@ -60,8 +60,8 @@
by filtering and interpolating the "raw" image. The filtering
and interpolation is done in software, so this mode is very
slow. Also, this mode places restrictions on how the image is
read which means that the "preview" mode of xscanimage does not
work in Super Resolution mode. (<B><A HREF="xcam.1.html">xcam(1)</A></B> and the non-preview
read which means that the "preview" mode of <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B> does
not work in Super Resolution mode. (<B><A HREF="xcam.1.html">xcam(1)</A></B> and the non-preview
modes of <B><A HREF="scanimage.1.html">scanimage(1)</A></B> and <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B> work fine, however.)
@ -115,17 +115,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_DMC</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 en-
vironment 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.
@ -155,9 +155,9 @@
</PRE>
<H2>AUTHOR</H2><PRE>
David F. Skoll
Dianne Skoll &lt;dianne@skoll.ca&gt;
The backend is derived from <B><A HREF="sane-hp.5.html">sane-hp(5)</A></B> by David Mosberger
The backend is derived from <B><A HREF="sane-hp.5.html">sane-hp(5)</A></B> by David Mosberger.
13 Jul 2008 <B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B>
</PRE>

22
man/sane-epjitsu.5.html
Wyświetl plik

@ -12,7 +12,7 @@
</PRE>
<H2>NAME</H2><PRE>
sane-epjitsu - SANE backend for Epson-based Fujitsu USB scanners.
sane-epjitsu - SANE backend for Epson-based Fujitsu USB scanners
</PRE>
@ -49,15 +49,15 @@
Selects the mode for the scan. Options may include "Lineart",
"Gray", "Color".
<B>resolution,</B> <B>y-resolution</B>
<B>resolution</B>, <B>y-resolution</B>
Controls scan resolution. Setting <B>--resolution</B> also sets
<B>--y-resolution,</B> though this behavior is overridden by some fron-
tends.
<B>--y-resolution</B>, though this behavior is overridden by some
frontends.
Other options will be available based on the capabilities of the scan-
ner. Use <I>'scanimage</I> <I>--help'</I> to get a list. Be aware that some options
may appear only when another option has been set, and that advanced
options may be hidden by the frontend.
may appear only when another option has been set, and that advanced op-
tions may be hidden by the frontend.
</PRE>
@ -72,17 +72,17 @@
Scanners can be specified in the configuration file in two ways:
"usb 0x04c5 0x10c7" (or other vendor/product ids)
Requests backend to search all usb buses in the system for a
device which uses that vendor and product id. The device will
then be queried to determine if it is a supported scanner.
Requests backend to search all usb buses in the system for a de-
vice which uses that vendor and product id. The device will then
be queried to determine if it is a supported scanner.
"usb /dev/usb/scanner0" (or other device file)
Some systems use a kernel driver to access usb scanners. This
method is untested.
The only configuration option supported is "firmware /PATH/TO/FILE",
allowing you to set the location of the firmware file you have
extracted from the Windows driver.
allowing you to set the location of the firmware file you have ex-
tracted from the Windows driver.
<B>Note:</B> This firmware is a copyrighted work of Fujitsu, so cannot be pro-
vided by the backend or the author. Please do not ask.

68
man/sane-epson.5.html
Wyświetl plik

@ -17,11 +17,11 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-epson</B> library implements a SANE Scanner Access Now Easy) back-
end that provides access to Epson flatbed scanners. Some functions of
this backend should be considered <B>beta-quality</B> software! Most functions
have been stable for a long time, but of course new development can not
and often times will not function properly from the very first day.
The <B>sane-epson</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to Epson flatbed scanners. Some functions
of this backend should be considered <B>beta-quality</B> software! Most func-
tions have been stable for a long time, but of course new development
can not and often will not function properly from the very first day.
Please report any strange behavior to the maintainer of the backend.
At present, the following scanners are known to work with this backend:
@ -80,18 +80,18 @@
The <B>--depth</B> option selects the bit depth the scanner is using.
This option is only available for scanners that support more
than one bit depth. Older scanners will always transfer the
image in 8bit mode. Newer scanners allow one to select either 8
than one bit depth. Older scanners will always transfer the im-
age in 8bit mode. Newer scanners allow one to select either 8
bits, 12 or 14 bits per color channel. For a color scan this
means an effective color depth of 36 or 42 bits over all three
channels. The valid choices depend on the scanner model.
The <B>--halftoning</B> switch selects the mode that is used in Binary
mode. Valid options are "None", "Halftone A (Hard Tone)",
"Halftone B (Soft Tone)", "Halftone C (Net Screen)", "Dither A
(4x4 Bayer)", "Dither B (4x4 Spiral)", "Dither C (4x4 Net
Screen)", "Dither D (8x4 Net Screen)", "Text Enhanced Technol-
ogy", "Download pattern A", and "Download pattern B".
mode. Valid options are "None", "Halftone A (Hard Tone)", "Half-
tone B (Soft Tone)", "Halftone C (Net Screen)", "Dither A (4x4
Bayer)", "Dither B (4x4 Spiral)", "Dither C (4x4 Net Screen)",
"Dither D (8x4 Net Screen)", "Text Enhanced Technology", "Down-
load pattern A", and "Download pattern B".
The <B>--dropout</B> switch selects the so called dropout color. Valid
options are None, Red, Green and Blue. The default is None. The
@ -135,13 +135,13 @@
speed up the scan if this option is supported.
The <B>--auto-area-segmentation</B> switch activates the automatic area
segmentation for monochrome scans. The scanner will try to
determine which areas are text and which contain images. The
image areas will be halftoned, and the text will be improved.
Valid options are "yes" and "no". The default is "yes".
segmentation for monochrome scans. The scanner will try to de-
termine which areas are text and which contain images. The image
areas will be halftoned, and the text will be improved. Valid
options are "yes" and "no". The default is "yes".
The <B>--gamma-table</B> parameter can be used to download a user
defined gamma table. The option takes 256 values from the range
The <B>--gamma-table</B> parameter can be used to download a user de-
fined gamma table. The option takes 256 values from the range
0-255. In color mode this option equally affects the red, green,
and blue channel.
@ -171,17 +171,17 @@
the default is "no".
The geometry options <B>-l</B> <B>-t</B> <B>-x</B> <B>-y</B> control the scan area: <B>-l</B> sets
the top left x coordinate, <B>-t</B> the top left y coordinate, <B>-x</B>
selects the width and <B>-y</B> the height of the scan area. All param-
eters are specified in millimeters.
the top left x coordinate, <B>-t</B> the top left y coordinate, <B>-x</B> se-
lects the width and <B>-y</B> the height of the scan area. All parame-
ters are specified in millimeters.
The <B>--quick-format</B> option lets the user select a scan area with
predefined sizes. Valid parameters are "CD", "A5 portrait", "A5
landscape", "Letter", "A4" and "max". The default is "max",
which selects the largest possible area.
The <B>--source</B> option selects the scan source. Valid options
depend on the installed options. The default is "Flatbed".
The <B>--source</B> option selects the scan source. Valid options de-
pend on the installed options. The default is "Flatbed".
The <B>--auto-eject</B> option will eject a page after scanning from
the document feeder.
@ -219,7 +219,7 @@
the IO address of the parallel port. To make it clearer that a
configured IO address is a parallel port the port address can be
preceded by the string "PIO". The PIO connection does not use a
special device file in the /dev directory. The IO address can be
special device file in the <I>/dev</I> directory. The IO address can be
specified in hex mode (prefixed with "0x").
<I>USB</I> A device file that is preceded by the string "USB" is treated as
@ -242,14 +242,14 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_EPSON</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 en-
vironment 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.
<B>SANE_DEBUG_EPSON_SCSI</B>
If the library was compiled with debug support enabled, this
environment variable controls the SCSI related debug level for
If the library was compiled with debug support enabled, this en-
vironment variable controls the SCSI related debug level for
this backend. Only a value of 2 is supported.
<B>SANE_EPSON_CMD_LVL</B>
@ -275,16 +275,16 @@
</PRE>
<H2>UNSUPPORTED DEVICES</H2><PRE>
The backend may be used with Epson scanners that are not yet listed
under the list of supported devices. A scanner that is not recognized
may default to the function level B3, which means that not all func-
tions that the scanner may be capable of are accessible.
The backend may be used with Epson scanners that are not yet listed un-
der the list of supported devices. A scanner that is not recognized may
default to the function level B3, which means that not all functions
that the scanner may be capable of are accessible.
If the scanner is not even recognized as an Epson scanner this is prob-
ably because the device name reported by the scanner is not in the cor-
rect format. Please send this information to the backend maintainer
(email address is in the AUTHOR section of this man page or in the
AUTHORS file of the SANE distribution).
(email address is in the AUTHOR section of this man page or in the AU-
THORS file of the SANE distribution).
The Perfection 600, Perfection 650, Perfection 660, Perfection 1250 and
Perfection 1260 are not supported by this backend.

78
man/sane-epson2.5.html
Wyświetl plik

@ -19,15 +19,15 @@
<H2>DESCRIPTION</H2><PRE>
The <B>sane-epson2</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to Epson flatbed scanners. This library
supports a similar set of scanners as the sane-epson driver but was
developed to support a wider range of connections to the scanner;
include network access.
supports a similar set of scanners as the sane-epson driver but was de-
veloped to support a wider range of connections to the scanner; include
network access.
Because <B>sane-epson</B> and <B>sane-epson2</B> drivers support many of the same
devices, if one driver gives you problems you may try disabling it to
try the other. This can be done by removing the driver name from the
<I>dll.conf</I> or perhaps by commenting out the options in <I>epson.conf</I> or
<I>epson2.conf.</I>
Because <B>sane-epson</B> and <B>sane-epson2</B> drivers support many of the same de-
vices, if one driver gives you problems you may try disabling it to try
the other. This can be done by removing the driver name from the
<I>dll.conf</I> or perhaps by commenting out the options in <I>epson.conf</I> or <I>ep-</I>
<I>son2.conf.</I>
At present, the following scanners are known to work with this backend:
@ -121,18 +121,18 @@
The <B>--depth</B> option selects the bit depth the scanner is using.
This option is only available for scanners that support more
than one bit depth. Older scanners will always transfer the
image in 8bit mode. Newer scanners allow one to select either 8
than one bit depth. Older scanners will always transfer the im-
age in 8bit mode. Newer scanners allow one to select either 8
bits, 12 or 14 bits per color channel. For a color scan this
means an effective color depth of 36 or 42 bits over all three
channels. The valid choices depend on the scanner model.
The <B>--halftoning</B> switch selects the mode that is used in Binary
mode. Valid options are "None", "Halftone A (Hard Tone)",
"Halftone B (Soft Tone)", "Halftone C (Net Screen)", "Dither A
(4x4 Bayer)", "Dither B (4x4 Spiral)", "Dither C (4x4 Net
Screen)", "Dither D (8x4 Net Screen)", "Text Enhanced Technol-
ogy", "Download pattern A", and "Download pattern B".
mode. Valid options are "None", "Halftone A (Hard Tone)", "Half-
tone B (Soft Tone)", "Halftone C (Net Screen)", "Dither A (4x4
Bayer)", "Dither B (4x4 Spiral)", "Dither C (4x4 Net Screen)",
"Dither D (8x4 Net Screen)", "Text Enhanced Technology", "Down-
load pattern A", and "Download pattern B".
The <B>--dropout</B> switch selects the so called dropout color. Valid
options are None, Red, Green and Blue. The default is None. The
@ -175,10 +175,10 @@
Valid options are "yes" and "no". The default is "no".
The <B>--auto-area-segmentation</B> switch activates the automatic area
segmentation for monochrome scans. The scanner will try to
determine which areas are text and which contain images. The
image areas will be halftoned, and the text will be improved.
Valid options are "yes" and "no". The default is "yes".
segmentation for monochrome scans. The scanner will try to de-
termine which areas are text and which contain images. The image
areas will be halftoned, and the text will be improved. Valid
options are "yes" and "no". The default is "yes".
The <B>--red-gamma-table</B> parameter can be used to download a user
defined gamma table for the red channel. The valid options are
@ -206,12 +206,12 @@
"yes" and "no". The default is "no".
The geometry options <B>-l</B> <B>-t</B> <B>-x</B> <B>-y</B> control the scan area: <B>-l</B> sets
the top left x coordinate, <B>-t</B> the top left y coordinate, <B>-x</B>
selects the width and <B>-y</B> the height of the scan area. All param-
eters are specified in millimeters.
the top left x coordinate, <B>-t</B> the top left y coordinate, <B>-x</B> se-
lects the width and <B>-y</B> the height of the scan area. All parame-
ters are specified in millimeters.
The <B>--source</B> option selects the scan source. Valid options
depend on the installed options. The default is "Flatbed".
The <B>--source</B> option selects the scan source. Valid options de-
pend on the installed options. The default is "Flatbed".
The <B>--auto-eject</B> option will eject a page after scanning from
the document feeder.
@ -229,7 +229,7 @@
option is only functional for selected scanners, all other scan-
ners will ignore this option.
The <B>--bay</B> option selects which bay to scan
The <B>--bay</B> option selects which bay to scan.
The <B>--eject</B> option ejects the sheet in the ADF.
@ -282,21 +282,21 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_EPSON2</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 en-
vironment 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.
<B>SANE_DEBUG_EPSON2_SCSI</B>
If the library was compiled with debug support enabled, this
environment variable controls the SCSI related debug level for
If the library was compiled with debug support enabled, this en-
vironment variable controls the SCSI related debug level for
this backend. Only a value of 2 is supported.
<B>SANE_DEBUG_EPSON2_NET</B>
If the library was compiled with debug support enabled, this
environment variable controls the network related debug level
for this backend. E.g., a value of 128 requests all debug out-
put to be printed. Smaller levels reduce verbosity.
If the library was compiled with debug support enabled, this en-
vironment variable controls the network related debug level for
this backend. E.g., a value of 128 requests all debug output to
be printed. Smaller levels reduce verbosity.
<B>SANE_EPSON2_CMD_LVL</B>
This allows one to override the function or command level that
@ -321,16 +321,16 @@
</PRE>
<H2>UNSUPPORTED DEVICES</H2><PRE>
The backend may be used with Epson scanners that are not yet listed
under the list of supported devices. A scanner that is not recognized
may default to the function level B3, which means that not all func-
tions that the scanner may be capable of are accessible.
The backend may be used with Epson scanners that are not yet listed un-
der the list of supported devices. A scanner that is not recognized may
default to the function level B3, which means that not all functions
that the scanner may be capable of are accessible.
If the scanner is not even recognized as an Epson scanner this is prob-
ably because the device name reported by the scanner is not in the cor-
rect format. Please send this information to the backend maintainer
(email address is in the AUTHOR section of this man page or in the
AUTHORS file of the SANE distribution).
(email address is in the AUTHOR section of this man page or in the AU-
THORS file of the SANE distribution).
</PRE>

18
man/sane-epsonds.5.html
Wyświetl plik

@ -37,8 +37,8 @@
The <B>--depth</B> option selects the bit depth the scanner is using.
This option is only available for scanners that support more
than one bit depth. Older scanners will always transfer the
image in 8bit mode. Newer scanners allow one to select either 8
than one bit depth. Older scanners will always transfer the im-
age in 8bit mode. Newer scanners allow one to select either 8
bits, 12 or 14 bits per color channel. For a color scan this
means an effective color depth of 36 or 42 bits over all three
channels. The valid choices depend on the scanner model.
@ -50,12 +50,12 @@
<B><A HREF="age.1.html">age(1)</A></B>.
The geometry options <B>-l</B> <B>-t</B> <B>-x</B> <B>-y</B> control the scan area: <B>-l</B> sets
the top left x coordinate, <B>-t</B> the top left y coordinate, <B>-x</B>
selects the width and <B>-y</B> the height of the scan area. All param-
eters are specified in millimeters.
the top left x coordinate, <B>-t</B> the top left y coordinate, <B>-x</B> se-
lects the width and <B>-y</B> the height of the scan area. All parame-
ters are specified in millimeters.
The <B>--source</B> option selects the scan source. Valid options
depend on the installed options. The default is "Flatbed".
The <B>--source</B> option selects the scan source. Valid options de-
pend on the installed options. The default is "Flatbed".
The <B>--eject</B> option ejects the sheet in the ADF.
@ -91,8 +91,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_EPSONDS</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 en-
vironment 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. Values around 11-16 will usu-
ally be enough for a bug report.

10
man/sane-escl.5.html
Wyświetl plik

@ -44,9 +44,9 @@
RICOH SP3710S
XEROX VERSALINK C7220
The. <B>sane-escl</B> backend for SANE supports AirScan/eSCL devices that
announce themselves on mDNS as _uscan._utcp or _uscans._utcp. If the
device is available, the <B>sane-escl</B> backend recovers these capacities.
The. <B>sane-escl</B> backend for SANE supports AirScan/eSCL devices that an-
nounce themselves on mDNS as _uscan._utcp or _uscans._utcp. If the de-
vice is available, the <B>sane-escl</B> backend recovers these capacities.
The user configures and starts scanning. A list of devices that use
the eSCL protocol can be found at <I>https://support.apple.com/en-</I>
<I>us/HT201311</I>. While these devices are expected to work, your mileage
@ -69,8 +69,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_ESCL</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 en-
vironment 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.

34
man/sane-find-scanner.1.html
Wyświetl plik

@ -17,8 +17,8 @@
</PRE>
<H2>SYNOPSIS</H2><PRE>
<B>sane-find-scanner</B> [<B>-?</B>|<B>-h</B>|<B>--help</B>] [<B>-v</B>] [<B>-q</B>] [<B>-p</B>] [<B>-f</B>] [<B>-F</B> <I>filename</I>]
[<I>devname</I>]
<B>sane-find-scanner</B> [<B>-?</B>|<B>-h</B>|<B>--help</B>] [<B>-v</B>] [<B>-q</B>] [<B>-p</B>] [<B>-f</B>] [<B>-F</B> <I>filename</I>] [<I>de-</I>
<I>vname</I>]
</PRE>
@ -40,18 +40,18 @@
the operating system supports this feature. Currently USB scanners are
only found this way if they are supported by the Linux scanner module
or the FreeBSD or OpenBSD uscanner driver. After that test,
<B>sane-find-scanner</B> tries to scan for USB devices found by the USB
library libusb (if available). There is no special USB class for scan-
ners, so the heuristics used to distinguish scanners from other USB
devices is not perfect. <B>sane-find-scanner</B> also tries to find out the
<B>sane-find-scanner</B> tries to scan for USB devices found by the USB li-
brary libusb (if available). There is no special USB class for scan-
ners, so the heuristics used to distinguish scanners from other USB de-
vices is not perfect. <B>sane-find-scanner</B> also tries to find out the
type of USB chip used in the scanner. If detected, it will be printed
after the vendor and product ids. <B>sane-find-scanner</B> will even find USB
scanners, that are not supported by any SANE backend.
<B>sane-find-scanner</B> won't find most parallel port scanners, or scanners
connected to proprietary ports. Some <B>parallel</B> <B>port</B> scanners may be
detected by <I>sane-find-scanner</I> <I>-p</I> <I>.</I> At the time of writing this will
only detect Mustek parallel port scanners.
connected to proprietary ports. Some <B>parallel</B> <B>port</B> scanners may be de-
tected by <I>sane-find-scanner</I> <I>-p</I> <I>.</I> At the time of writing this will only
detect Mustek parallel port scanners.
</PRE>
@ -59,17 +59,17 @@
<B>-?,</B> <B>-h,</B> <B>--help</B>
Prints a short usage message.
<B>-v</B> Verbose output. If used once, <B>sane-find-scanner</B> shows every
device name and the test result. If used twice, SCSI inquiry
information and the USB device descriptors are also printed.
<B>-v</B> Verbose output. If used once, <B>sane-find-scanner</B> shows every de-
vice name and the test result. If used twice, SCSI inquiry in-
formation and the USB device descriptors are also printed.
<B>-q</B> Be quiet. Print only the devices, no comments.
<B>-p</B> Probe parallel port scanners.
<B>-f</B> Force opening all explicitly given devices as SCSI and USB
devices. That's useful if <B>sane-find-scanner</B> is wrong in deter-
mining the device type.
<B>-f</B> Force opening all explicitly given devices as SCSI and USB de-
vices. That's useful if <B>sane-find-scanner</B> is wrong in determin-
ing the device type.
<B>-F</B> <B>filename</B>
filename is a file that contains USB descriptors in the format
@ -79,8 +79,8 @@
put of <I>cat</I> <I>/proc/bus/usb/devices</I> is available but the scanner
itself isn't.
<B>devname</B> Test device file "devname". No other devices are checked if
devname is given.
<B>devname</B> Test device file "devname". No other devices are checked if de-
vname is given.
</PRE>

52
man/sane-fujitsu.5.html
Wyświetl plik

@ -12,36 +12,36 @@
</PRE>
<H2>NAME</H2><PRE>
sane-fujitsu - SANE backend for Fujitsu flatbed and ADF scanners
sane-fujitsu - SANE backend for Fujitsu and Ricoh fi series scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-fujitsu</B> library implements a SANE (Scanner Access Now Easy)
backend which provides access to most Fujitsu flatbed and ADF scanners.
backend which provides access to most Fujitsu flatbed and ADF scanners,
and the subsequent Ricoh models.
This document describes backend version 139, which initially shipped
with SANE 1.1.2.
This document describes backend version 140.
</PRE>
<H2>SUPPORTED HARDWARE</H2><PRE>
This version supports every known model which speaks the Fujitsu SCSI
and SCSI-over-USB protocols. Specifically, the SCSI M309x and M409x
series, the SCSI fi-series, and most of the USB fi-, ScanSnap, &amp; iX
series scanners are supported. Please see the list at
and SCSI-over-USB protocols. Specifically, the SCSI M309x and M409x se-
ries, the SCSI fi-series, and most of the USB fi-, ScanSnap, &amp; iX se-
ries scanners are supported. Please see the list at
<I>http://www.sane-project.org/sane-supported-devices.html</I> for details.
This backend may support other Fujitsu scanners. The best way to deter-
mine level of support is to test the scanner directly, or to collect a
trace of the windows driver in action. Please contact the author for
help or with test results.
This backend may support other Fujitsu or newer Ricoh scanners. The
best way to determine level of support is to test the scanner directly,
or to collect a trace of the windows driver in action. Please contact
the author for help or with test results.
</PRE>
<H2>UNSUPPORTED HARDWARE</H2><PRE>
The following scanners are known NOT to work with this backend, either
because they have a non-Fujitsu chipset, or an unsupported interface
because they have an unsupported chipset, or an unsupported interface
type. Some of these scanners may be supported by another backend.
--------------------------------------
@ -71,8 +71,8 @@
<B>resolution,</B> <B>y-resolution</B>
Controls scan resolution. Setting <B>--resolution</B> also sets
<B>--y-resolution,</B> though this behavior is overridden by some fron-
tends.
<B>--y-resolution,</B> though this behavior is overridden by some
frontends.
<B>tl-x,</B> <B>tl-y,</B> <B>br-x,</B> <B>br-y</B>
Sets scan area upper left and lower right coordinates. These are
@ -90,12 +90,12 @@
Additionally, several 'software' options are exposed by the backend.
These are reimplementations of features provided natively by larger
scanners, but running on the host computer. This enables smaller
machines to have similar capabilities. Please note that these features
are somewhat simplistic, and may not perform as well as the native
implementations. Note also that these features all require that the
driver cache the entire image in memory. This will almost certainly
result in a reduction of scanning speed.
scanners, but running on the host computer. This enables smaller ma-
chines to have similar capabilities. Please note that these features
are somewhat simplistic, and may not perform as well as the native im-
plementations. Note also that these features all require that the
driver cache the entire image in memory. This will almost certainly re-
sult in a reduction of scanning speed.
<B>swcrop</B>
Requests the driver to detect the extremities of the paper
@ -111,8 +111,8 @@
rounding color.
Use <I>'scanimage</I> <I>--help'</I> to get a list, but be aware that some options
may be settable only when another option has been set, and that
advanced options may be hidden by some frontend programs.
may be settable only when another option has been set, and that ad-
vanced options may be hidden by some frontend programs.
</PRE>
@ -137,9 +137,9 @@
other "scsi" line above.
"usb 0x04c5 0x1042" (or other vendor/product ids)
Requests backend to search all usb buses in the system for a
device which uses that vendor and product id. The device will
then be queried to determine if it is a Fujitsu scanner.
Requests backend to search all usb buses in the system for a de-
vice which uses that vendor and product id. The device will then
be queried to determine if it is a supported scanner.
"usb /dev/usb/scanner0" (or other device file)
Some systems use a kernel driver to access usb scanners. This
@ -236,7 +236,7 @@
<H2>AUTHOR</H2><PRE>
m. allan noah: &lt;kitno455 a t gmail d o t com&gt;
15 Nov 2022 <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>
24 Mar 2023 <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>
</PRE>
<HR>
<ADDRESS>

74
man/sane-genesys.5.html
Wyświetl plik

@ -55,19 +55,19 @@
To give correct image quality, sheet fed scanners need to be calibrated
using the calibration sheet sold with the scanner. To do calibration,
you must insert this target in the feeder then start calibration either
by passing the --calibrate option to scanimage or by clicking on the
by passing the --calibrate option to <B><A HREF="scanimage.1.html">scanimage(1)</A></B> or by clicking on the
available 'calibrate' button in the 'advanced options' in a graphical
frontend. The result of the calibration is stored in a file in the home
directory of the user doing it. If you plug the scanner in another
machine or use it with another account, calibration will have to be
redone, unless you use the --calibration-file option. If no home
directory is defined, <B>USERAPPPROFILE</B> will be used, then <B>TMPDIR</B> or <B>TMP.</B>
If none of these directories exist, the backend will try to write in
the current working directory. Flatbed scanners also make use of the
calibration file as a cache to avoid calibration before each scan. Cal-
ibration file name is the name of the scanner model if only one scanner
is detected. In the case of several identical model, the file name will
be the name of the logical USB device name. The expiration time manages
directory of the user doing it. If you plug the scanner in another ma-
chine or use it with another account, calibration will have to be re-
done, unless you use the --calibration-file option. If no home direc-
tory is defined, <B>USERAPPPROFILE</B> will be used, then <B>TMPDIR</B> or <B>TMP.</B> If
none of these directories exist, the backend will try to write in the
current working directory. Flatbed scanners also make use of the cali-
bration file as a cache to avoid calibration before each scan. Calibra-
tion file name is the name of the scanner model if only one scanner is
detected. In the case of several identical model, the file name will be
the name of the logical USB device name. The expiration time manages
the time a calibration is valid in cache. A value of -1 means forever,
0 means no cache.
@ -96,8 +96,8 @@
<B>--disable-interpolation</B> <B>yes|no</B>
When using high resolutions where the horizontal resolution is
smaller than vertical resolution, data is expanded by software
to preserve picture geometry. This can be disabled by this
option to get real scanned data.
to preserve picture geometry. This can be disabled by this op-
tion to get real scanned data.
<B>--disable-dynamic-lineart</B> <B>yes|no</B>
Disable use of a software adaptive algorithm to generate lineart
@ -106,8 +106,8 @@
<B>--color-filter</B> <B>None|Red|Green|Blue</B>
When using gray or lineart this option selects the used color.
Using a color filter will give a monochrome scan. CIS based
scanners can to true gray when no filter (None value) is
selected.
scanners can do true gray when no filter (None value) is se-
lected.
<B>--lamp-off-scan</B>
The lamp will be turned off during the scan. Calibration is
@ -128,17 +128,17 @@
Specify the time (in minutes) a cached calibration is considered
valid. If older than the given value, a new calibration is done.
A value of -1 means no expiration and cached value are kept for-
ever unless cleared by userwith the calibration clear option. A
ever unless cleared by user with the calibration clear option. A
value of 0 means cache is disabled.
Additionally, several 'software' options are exposed by the backend.
These are reimplementations of features provided natively by larger
scanners, but running on the host computer. This enables smaller
machines to have similar capabilities. Please note that these features
are somewhat simplistic, and may not perform as well as the native
implementations. Note also that these features all require that the
driver cache the entire image in memory. This will almost certainly
result in a reduction of scanning speed.
scanners, but running on the host computer. This enables smaller ma-
chines to have similar capabilities. Please note that these features
are somewhat simplistic, and may not perform as well as the native im-
plementations. Note also that these features all require that the
driver cache the entire image in memory. This will almost certainly re-
sult in a reduction of scanning speed.
<B>--swcrop</B>
Requests the driver to detect the extremities of the paper
@ -202,25 +202,25 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing 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 en-
vironment 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_IMAGE</B>
If the library was compiled with debug support enabled, this
environment variable enables logging of intermediate image data.
If the library was compiled with debug support enabled, this en-
vironment variable enables logging of intermediate image data.
To enable this mode, set the environmental variable to 1.
Example (full and highly verbose output for gl646):
@ -238,9 +238,8 @@
Syscan/Ambir DocketPORT 467/485/487/665/685
Xerox Travel Scanner 100, Onetouch 2400
cncsolutions
(<I>http://www.cncsolutions.com.br</I>) sponsored and supported the
work on the Panasonic KV-SS080.
cncsolutions sponsored and supported the work on the Panasonic KV-
SS080.
Brian Paavo from Benthic Science Limited for donating a Canoscan LiDE
700F.
@ -266,7 +265,6 @@
Alexey Osipov &lt;<I>simba@lerlan.ru</I>&gt; for HP2400 final support
</PRE>
<H2>LIMITATIONS</H2><PRE>
Powersaving isn't implemented for gl646 based scanner. Dynamic (emu-
@ -275,7 +273,7 @@
ners, due to the way image sensors are built.
This backend will be much slower if not using libusb-1.0. So be sure
that sane-backends is built with the <B>--enable-libusb_1_0</B> <B>option.</B>
that sane-backends is built with the <B>--enable-libusb_1_0</B> option.
</PRE>

24
man/sane-gphoto2.5.html
Wyświetl plik

@ -38,10 +38,10 @@
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>gphoto2.conf</I> specify the characteristics of the
camera to be used. Resolutions (high resolution, low resolution, and
thumbnail size) are required since they are needed by the sane fron-
tends, but can't be obtained through the gphoto2 interface. Valid
ports and cameras can be obtained by <I>gphoto2</I> <I>--list-cameras</I> and <I>gphoto2</I>
<I>--list-ports</I> <I>.</I>
thumbnail size) are required since they are needed by the sane front-
ends, but can't be obtained through the gphoto2 interface. Valid ports
and cameras can be obtained by <I>gphoto2</I> <I>--list-cameras</I> and <I>gphoto2</I>
<I>--list-ports</I>.
The <B>dumpinquiry</B> line causes some information about the camera to be
printed.
@ -91,13 +91,13 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated by a semi-colon (`;'). If this variable is not set, the
configuration file is searched in two default directories:
first, the current working directory (<I>.</I>) and then in
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (<I>.</I>) and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_GPHOTO2</B>
If the library was compiled with debugging support enabled, this
@ -112,7 +112,7 @@
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B><B>,</B> <B><A HREF="scanimage.1.html">scanimage(1)</A></B><B>,</B> <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B><B>,</B> <B><A HREF="libgphoto2.3.html">libgphoto2(3)</A></B>
<B><A HREF="sane.7.html">sane(7)</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="libgphoto2.3.html">libgphoto2(3)</A></B>
</PRE>

36
man/sane-gt68xx.5.html
Wyświetl plik

@ -101,13 +101,13 @@
the same vendor/product ids so you can set the "correct" name here.
The <B>afe</B> option allows one to set custom offset and gain values for the
Analog FrontEnd of the scanner. This option can be either used to
select the AFE values if automatic coarse calibration is disabled, or
to make automatic coarse calibration faster. For the latter usage,
enable debug level 3 (see below), scan an image and look for debug line
string with "afe". Copy this line to <I>gt68xx.conf</I>. The option has six
parameters: red offset, red gain, green offset, green gain, blue off-
set, and blue gain.
Analog FrontEnd of the scanner. This option can be either used to se-
lect the AFE values if automatic coarse calibration is disabled, or to
make automatic coarse calibration faster. For the latter usage, enable
debug level 3 (see below), scan an image and look for debug line string
with "afe". Copy this line to <I>gt68xx.conf</I>. The option has six parame-
ters: red offset, red gain, green offset, green gain, blue offset, and
blue gain.
A sample configuration file is shown below:
@ -141,17 +141,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_GT68XX</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
If the library was compiled with debug support enabled, this en-
vironment 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.
@ -187,8 +187,8 @@
More detailed bug information is available at the gt68xx backend home-
page <I>http://www.meier-geinitz.de/sane/gt68xx-backend/</I>.
Please contact us if you find a bug or missing feature:
&lt;<I>sane-devel@alioth-lists.debian.net</I>&gt;.
Please contact us if you find a bug or missing feature: &lt;<I>sane-de-</I>
<I>vel@alioth-lists.debian.net</I>&gt;.
Please send a debug log if your scanner isn't detected correctly (see
<B>SANE_DEBUG_GT68XX</B> above).

111
man/sane-hp.5.html
Wyświetl plik

@ -45,16 +45,17 @@
PhotoSmart C5100A R029,R030,R032 SCSI
Support for models 5100C/5200C connected to the parallel port requires
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>.
the ppSCSI driver available at <I>http://cyberelk.net/tim/parport/pp-</I>
<I>scsi.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.
Support for models 5200C/62X0C/63X0C connected to USB requires libusb.
See <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B> for more details.
The <B>sane-hp</B> backend no longer supports OfficeJet multi-function periph-
erals. For these devices use the external "hpoj" backend in version
0.90 and later of the "HP OfficeJet Linux driver", available at
<I>http://hpoj.sourceforge.net</I>
erals. For these devices use the external "hplip" packages available
at: <I>https://developers.hp.com/hp-linux-imaging-and-printing/</I>. For in-
formation about the previous hpoj driver, see: <I>http://hpoj.source-</I>
<I>forge.net/</I>.
Because Hewlett-Packard does no longer produce scanners that support
SCL (beside the OfficeJets), the above list of supported scanners is
@ -64,7 +65,8 @@
ing list at <I>http://www.sane-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>.
<I>http://web.archive.org/web/20070206115546/http://www.kirchgess-</I>
<I>ner.net/sane.html</I>.
</PRE>
@ -73,57 +75,57 @@
<I>special</I>
Where <I>special</I> is the UNIX path-name for the special device that corre-
sponds to the 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/sg2</I>, for example. If the
Where <I>special</I> is the UNIX path-name for the special device that corre-
sponds to the 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/sg2</I>, for example. If the
special device name contains "usb", "uscanner" or "ugen", it is assumed
that the scanner is connected by USB. For the HP ScanJet Plus the spe-
cial device name must be the device that corresponds to the parallel
interface card that was shipped with the scanner. That is <I>/dev/hpscan</I>.
A special driver is required for this card. See
cial device name must be the device that corresponds to the parallel
interface card that was shipped with the scanner. That is <I>/dev/hpscan</I>.
A special driver is required for this card. See
<I>ftp://rvs.ctrl-c.liu.se/pub/wingel/hpscan</I> for details. If the link does
not work, try <I>ftp://sunsite.unc.edu/pub/Linux/kernel/patches/scanners</I>.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>hp.conf</I> file is a list of options and device names
The contents of the <I>hp.conf</I> file is a list of options and device names
that correspond to HP ScanJet scanners. Empty lines and lines starting
with a hash mark (#) are ignored. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> and <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B> on
with a hash mark (#) are ignored. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> and <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B> on
details of what constitutes a valid device name.
Options specified in front of the first line that contains a device
name are defaults for all devices. Options specified below a line that
contains a device name apply just to the most recently mentioned
device.
Options specified in front of the first line that contains a device
name are defaults for all devices. Options specified below a line that
contains a device name apply just to the most recently mentioned de-
vice.
Supported options are <B>connect-scsi</B>, <B>connect-device</B>,
<B>enable-image-buffering</B>, and <B>dumb-read</B>.
Supported options are <B>connect-scsi</B>, <B>connect-device</B>, <B>enable-im-</B>
<B>age-buffering</B>, and <B>dumb-read</B>.
Option <B>connect-scsi</B> specifies that the scanner is connected to the sys-
tem by SCSI. Input/output is performed using SCSI-commands. This is
the default. But if your SCSI device name contains "usb", "uscanner"
or "ugen", option connect-scsi must be specified. Otherwise it is
assumed that the scanner is connected by USB.
tem by SCSI. Input/output is performed using SCSI-commands. This is
the default. But if your SCSI device name contains "usb", "uscanner"
or "ugen", option connect-scsi must be specified. Otherwise it is as-
sumed that the scanner is connected by USB.
Option <B>connect-device</B> specifies that the scanner is connected to the
system by a special device. Input/output is performed by
<B>read</B>()/<B>write</B>()-operations on the device. This option must be used for
Option <B>connect-device</B> specifies that the scanner is connected to the
system by a special device. Input/output is performed by
<B>read</B>()/<B>write</B>()-operations on the device. This option must be used for
HP ScanJet Plus or scanners connected to USB which are accessed through
a named device (e.g. <I>/dev/usb/scanner0</I>). For device names that con-
a named device (e.g. <I>/dev/usb/scanner0</I>). For device names that con-
tain "usb", "uscanner" or "ugen", it is not necessary to specify option
connect-device.
Option <B>enable-image-buffering</B> stores the scanned image in memory before
passing it to the frontend. Could be used in case of forward/backward
passing it to the frontend. Could be used in case of forward/backward
moving scanner lamp.
Option <B>dumb-read</B> can be used to work around problems with "Error during
device I/O". These problems may occur with certain SCSI-to-USB convert-
ers or Buslogic SCSI cards. The option should not be used for SCSI
devices which are working correctly. Otherwise startup of frontends
and changing parameters might be slower.
ers or Buslogic SCSI cards. The option should not be used for SCSI de-
vices which are working correctly. Otherwise startup of frontends and
changing parameters might be slower.
A sample configuration file is shown below:
@ -138,7 +140,7 @@
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/hp.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-hp.a</I>
@ -149,11 +151,10 @@
that support dynamic loading).
<I>$HOME/.sane/calib-hp:&lt;device&gt;.dat</I>
Calibration data for HP PhotoSmart PhotoScanner that is
retrieved from the scanner after calibration. The data is
uploaded to the scanner at start of the backend if it is in
media mode 'print media' or if the media mode is changed to
'print media'.
Calibration data for HP PhotoSmart PhotoScanner that is re-
trieved from the scanner after calibration. The data is uploaded
to the scanner at start of the backend if it is in media mode
'print media' or if the media mode is changed to 'print media'.
</PRE>
@ -164,24 +165,24 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated by a semi-colon (`;'). If this variable is not set, the
configuration file is searched in two default directories:
first, the current working directory (<I>.</I>) and then in
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (<I>.</I>) and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_HP</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 en-
vironment 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.
<B>SANE_HOME_HP</B>
Only used for OS/2 and along with use of HP PhotoSmart Photo-
Scanner. Must be set to the directory where the directory .sane
is located. Is used to save and read the calibration file.
Scanner. Must be set to the directory where the directory <I>.sane</I>
is located. Is used to save and read the calibration file.
<B>SANE_HP_KEEPOPEN_SCSI</B>
@ -208,9 +209,9 @@
In media mode 'slide' and 'negative', scan resolutions are
rounded to multiple of 300 dpi. The scanner does not scale the
data correctly on other resolutions. Some newer models (firmware
code R030 and later) do not support adjustment of con-
trast/intensity level and tone map. The backend will simulate
this by software, but only for gray and 24 bit color.
code R030 and later) do not support adjustment of contrast/in-
tensity level and tone map. The backend will simulate this by
software, but only for gray and 24 bit color.
<B>Automatic</B> <B>Document</B> <B>Feeder</B> <B>(ADF)</B>
For use of the ADF with <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, first place paper in the

4
man/sane-hp3500.5.html
Wyświetl plik

@ -51,8 +51,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_HP3500</B> If the library was compiled with debug support
enabled, this environment variable controls the debug level for this
<B>SANE_DEBUG_HP3500</B> If the library was compiled with debug support en-
abled, this environment variable controls the debug level for this
backend. Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_HP3500=4

22
man/sane-hp3900.5.html
Wyświetl plik

@ -52,8 +52,8 @@
The contents of the <I>hp3900.conf</I> file is a list of usb lines containing
vendor and product ids that correspond to USB scanners. The file can
also contain the names of device files that correspond to an HP 39XX
scanner. 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>
scanner. Empty lines and lines starting with a hash mark (#) are ig-
nored. The scanners are autodetected by <B>usb</B> <B>vendor_id</B> <B>product_id</B>
statements which are already included into <I>hp3900.conf</I>. "vendor_id"
and "product_id" are hexadecimal numbers that identify the scanner. If
autodetection does not work, add the device name of your scanner to the
@ -82,17 +82,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated by a semi-colon (`;'). If this variable is not set, the
configuration file is searched in two default directories:
first, the current working directory (<I>.</I>) and then in
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (<I>.</I>) and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_HP3900</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 en-
vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_HP3900=4

22
man/sane-hp4200.5.html
Wyświetl plik

@ -44,8 +44,8 @@
The contents of the <I>hp4200.conf</I> file is a list of usb lines containing
vendor and product ids that correspond to USB scanners. The file can
also contain the names of device files that correspond to an HP 4200
scanner. 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>
scanner. Empty lines and lines starting with a hash mark (#) are ig-
nored. The scanners are autodetected by <B>usb</B> <B>vendor_id</B> <B>product_id</B>
statements which are already included into <I>hp4200.conf</I>. "vendor_id"
and "product_id" are hexadecimal numbers that identify the scanner. If
autodetection does not work, add the device name of your scanner to the
@ -74,17 +74,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated by a semi-colon (`;'). If this variable is not set, the
configuration file is searched in two default directories:
first, the current working directory (<I>.</I>) and then in
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (<I>.</I>) and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_HP4200</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 en-
vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_HP4200=4

22
man/sane-hp5400.5.html
Wyświetl plik

@ -45,8 +45,8 @@
The contents of the <I>hp5400.conf</I> file is a list of usb lines containing
vendor and product ids that correspond to USB scanners. The file can
also contain the names of device files that correspond to an HP 54XX
scanner. 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>
scanner. Empty lines and lines starting with a hash mark (#) are ig-
nored. The scanners are autodetected by <B>usb</B> <B>vendor_id</B> <B>product_id</B>
statements which are already included into <I>hp5400.conf</I>. "vendor_id"
and "product_id" are hexadecimal numbers that identify the scanner. If
autodetection does not work, add the device name of your scanner to the
@ -75,17 +75,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated by a semi-colon (`;'). If this variable is not set, the
configuration file is searched in two default directories:
first, the current working directory (<I>.</I>) and then in
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (<I>.</I>) and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_HP5400</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 en-
vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_HP5400=4

8
man/sane-hpljm1005.5.html
Wyświetl plik

@ -49,12 +49,12 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_HPLJM1005</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 en-
vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
There is not currently a great deal of diagnostic output, it
being mainly confined to error conditions.
There is not currently a great deal of diagnostic output, it be-
ing mainly confined to error conditions.
</PRE>

40
man/sane-hpsj5s.5.html
Wyświetl plik

@ -28,12 +28,12 @@
LIMITATIONS: For now this backend works only on Linux. This limitation
is due to dependence on the <B><A HREF="libieee1284.3.html">libieee1284(3)</A></B> library. If your system sup-
ports <B><A HREF="libieee1284.3.html">libieee1284(3)</A></B> too, this backend should work. If you ported
<B><A HREF="libieee1284.3.html">libieee1284(3)</A></B> for your platform, please let me know. Your system
should support <B>EPP</B> (or <B>EPP+ECP</B>) mode to operate this scanner. Future
versions will support ECP and SPP (Nibble and Byte) modes also. It's
planned to support scanners not only at daisy-chain position 0, but
anywhere. Support for multiple scanners could be implemented too.
ports <B><A HREF="libieee1284.3.html">libieee1284(3)</A></B> too, this backend should work. If you ported <B>li-</B>
<B><A HREF="bieee1284.3.html">bieee1284(3)</A></B> for your platform, please let me know. Your system should
support <B>EPP</B> (or <B>EPP+ECP</B>) mode to operate this scanner. Future versions
will support ECP and SPP (Nibble and Byte) modes also. It's planned to
support scanners not only at daisy-chain position 0, but anywhere. Sup-
port for multiple scanners could be implemented too.
Current version implements only gray scale scanning. True Color and B/W
modes are not supported for now.
@ -48,9 +48,9 @@
<I>special</I>
Where <I>special</I> is the parallel port name in form, <B><A HREF="libieee1284.3.html">libieee1284(3)</A></B>
expects. It seems to be system dependent. Under Linux it's parport0,
parport1, etc.
Where <I>special</I> is the parallel port name in form, <B><A HREF="libieee1284.3.html">libieee1284(3)</A></B> ex-
pects. It seems to be system dependent. Under Linux it's parport0, par-
port1, etc.
</PRE>
@ -65,8 +65,8 @@
</PRE>
<H2>TIPS</H2><PRE>
It seems that HP ScanJet 5S scanner uses software noise correction.
This feature, along with gamma correction and calibration, are not
implemented for now. They will be handled in future versions. Native
This feature, along with gamma correction and calibration, are not im-
plemented for now. They will be handled in future versions. Native
resolution for this scanner is 300 DPI. Other modes may present alias-
ing artifacts.
@ -93,17 +93,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_HPSJ5S</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 en-
vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.

50
man/sane-hs2p.5.html
Wyświetl plik

@ -70,27 +70,27 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_HS2P</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
A value of 255 prints all debug output. Smaller values reduce
If the library was compiled with debug support enabled, this en-
vironment variable controls the debug level for this backend. A
value of 255 prints all debug output. Smaller values reduce
verbosity.
</PRE>
<H2>CURRENT STATUS</H2><PRE>
The <B>sane-hs2p</B> backend is now in version 1.00. All major scanning-
related features are supported, except for those features requiring the
optional IPU. Scanning from the flatbed or ADF (either simplex or
duplex) is supported. Lineart, halftone, 4-bit gray, and 8-bit gray are
The <B>sane-hs2p</B> backend is now in version 1.00. All major scanning-re-
lated features are supported, except for those features requiring the
optional IPU. Scanning from the flatbed or ADF (either simplex or du-
plex) is supported. Lineart, halftone, 4-bit gray, and 8-bit gray are
supported. Pre-set gamma tables and halftone patterns are supported, as
well as brightness, threshold, contrast. Also supported is scan wait
mode, binary and gray filtering, negative scanning, and absolute or
@ -110,17 +110,17 @@
</PRE>
<H2>MISSING FUNCTIONALITY</H2><PRE>
The SCSI commands for uploading (2AH) or downloading (28H) custom
halftone patterns (02H) and gamma vectors (03H) should work, but
require implementing the SANE Option-Value code to allow the user to
create the tables to be uploaded to the scanner. No support for Mainte-
nance Data (80H) is planned as this functionality is more suited to a
stand-alone utility to be used by a technician when replacing the lamp
or ADF unit. Nor is support for reading or changing IPU (93H) parame-
ters and adjustments planned, since my IS450 lacks such a unit. The
31-byte Auto Photo/Letter struct and 21-byte Dynamic threshold struct
are documented in the <I>hs2p-scsi.h</I> file should someone wish to use their
IPU for image data processing.
The SCSI commands for uploading (2AH) or downloading (28H) custom half-
tone patterns (02H) and gamma vectors (03H) should work, but require
implementing the SANE Option-Value code to allow the user to create the
tables to be uploaded to the scanner. No support for Maintenance Data
(80H) is planned as this functionality is more suited to a stand-alone
utility to be used by a technician when replacing the lamp or ADF unit.
Nor is support for reading or changing IPU (93H) parameters and adjust-
ments planned, since my IS450 lacks such a unit. The 31-byte Auto
Photo/Letter struct and 21-byte Dynamic threshold struct are documented
in the <I>hs2p-scsi.h</I> file should someone wish to use their IPU for image
data processing.
</PRE>

18
man/sane-ibm.5.html
Wyświetl plik

@ -70,17 +70,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_IBM</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 en-
vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.

4
man/sane-kodak.5.html
Wyświetl plik

@ -71,8 +71,8 @@
to detect double feed errors.
Other options will be available based on the capabilities of the scan-
ner. Use <I>scanimage</I> <I>--help</I> to get a list, but be aware that some
options may be settable only when another option has been set, and that
ner. Use <I>scanimage</I> <I>--help</I> to get a list, but be aware that some op-
tions may be settable only when another option has been set, and that
advanced options may be hidden by some frontend programs.

4
man/sane-kodakaio.5.html
Wyświetl plik

@ -48,8 +48,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_KODAKAIO</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 en-
vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.

4
man/sane-kvs40xx.5.html
Wyświetl plik

@ -29,8 +29,8 @@
regarding the capabilities or reliability of the backend. All informa-
tion contained here is suspect.
The backend uses pthreads directly, and so requires pthreads to be
enabled.
The backend uses pthreads directly, and so requires pthreads to be en-
abled.
</PRE>

4
man/sane-leo.5.html
Wyświetl plik

@ -107,8 +107,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_LEO</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 en-
vironment 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.

8
man/sane-lexmark.5.html
Wyświetl plik

@ -79,8 +79,8 @@
<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.
as a percentage in the range 0..100% (in steps of 1). The de-
fault value of the threshold option is 50.
</PRE>
@ -102,8 +102,8 @@
</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.
If the library was compiled with debug support enabled, this en-
vironment 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.

75
man/sane-lexmark_x2600.5.html 100644
Wyświetl plik

@ -0,0 +1,75 @@
<HTML>
<HEAD>
<TITLE>sane-lexmark_x2600.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="/images/sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-lexmark_x2600.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-lexmark_x2600.5.html">sane-lexmark_x2600(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-lexmark_x2600.5.html">sane-lexmark_x2600(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-lexmark_x2600 - SANE backend for Lexmark X2600 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 X2600 AIOs.
The scanners that should work with this backend are:
Vendor Model status
---------------------- -----------
Lexmark X2670 good
The options the backend supports can either be selected through command
line options to programs like <B><A HREF="scanimage.1.html">scanimage(1)</A></B> or through GUI elements in
<B><A HREF="xscanimage.1.html">xscanimage(1)</A></B> , <B><A HREF="xsane.1.html">xsane(1)</A></B>. or <B><A HREF="simple-scan.1.html">simple-scan(1)</A></B>.
If you notice any strange behavior, please report to the backend main-
tainer or to the SANE mailing list.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/lib/sane/libsane-lexmark</I><B>_</B><I>x2600.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-lexmark</I><B>_</B><I>x2600.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_LEXMARK_X2600</B>
If the library was compiled with debug support enabled, this en-
vironment 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>AUTHOR</H2><PRE>
The backend was originally written by Benoit Juin.
&lt;<I>benoit.juin@gmail.com</I>&gt;
</PRE>
<H2>CREDITS</H2><PRE>
Many thanks go to:
@skelband aka Ralph Little who help me to dive in the sane-back-
encode and reviewed the sources.
23 Dec 2023 <B><A HREF="sane-lexmark_x2600.5.html">sane-lexmark_x2600(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>

30
man/sane-ma1509.5.html
Wyświetl plik

@ -35,8 +35,8 @@
the operating system. See <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B> for details.
If you own a scanner other than the Mustek BearPaw 1200F that works
with this backend, please let me know this by sending the scanner's
exact model name and the USB vendor and device ids (e.g. from
with this backend, please let me know this by sending the scanner's ex-
act model name and the USB vendor and device ids (e.g. from
<I>/proc/bus/usb/devices</I> or syslog) to me.
@ -61,12 +61,12 @@
<B>usb</B> <B>vendor_id</B> <B>product_id</B> statements which are already included into
<I>ma1509.conf</I>. This is only supported with Linux 2.4.8 and higher and
all systems that support libsub. "vendor_id" and "product_id" are hexa-
decimal numbers that identify the scanner. If this doesn't work, a
device name must be placed in <I>ma1509.conf</I> as described above.
decimal numbers that identify the scanner. If this doesn't work, a de-
vice name must be placed in <I>ma1509.conf</I> as described above.
To set the time the lamp needs for warm-up, use <B>option</B> <B>warmup-time</B> in
<I>ma1509.conf</I>. The time is given in seconds after the option. The
default is 30 seconds.
<I>ma1509.conf</I>. The time is given in seconds after the option. The de-
fault is 30 seconds.
</PRE>
@ -91,17 +91,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_MA1509</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 en-
vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.

18
man/sane-magicolor.5.html
Wyświetl plik

@ -69,17 +69,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>/tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>/tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I>
being searched (in this order).
<B>SANE_DEBUG_MAGICOLOR</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 en-
vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_MAGICOLOR=127

74
man/sane-matsushita.5.html
Wyświetl plik

@ -33,16 +33,16 @@
KV-S2065L (*)
(*) WARNING: None of the advanced options of these scanners are avail-
able (ie no color, no high resolution, no automatic cropping). Basi-
able (i.e. no color, no high resolution, no automatic cropping). Basi-
cally, the driver does no more than what it does for the KV-SS25. I
don't have access to such scanners, and thus cannot add these options.
Other Panasonic high speed scanners may or may not work with that back-
end.
Valid command line options and their syntax can be listed by using
Valid command line options and their syntax can be listed by using:
scanimage --help -d matsushita
<I>scanimage</I> <I>--help</I> <I>-d</I> <I>matsushita</I>
<B>Scan</B> <B>Mode</B>
@ -62,60 +62,59 @@
<B>Geometry</B>
<B>--paper-size</B> <B>A4|...|Legal|Letter</B> <B>[A4]</B>
options selects the area to scan. It adjust the <B>-l</B> <B>-t</B> <B>-x</B> <B>-y</B>
options accordingly. It does not need to be the real size of the
paper.
selects the area to scan. It adjusts the <B>-l</B> <B>-t</B> <B>-x</B> <B>-y</B> options ac-
cordingly. It does not need to be the real size of the paper.
<B>-l</B> <B>-t</B> <B>-x</B> <B>-y</B>
control the scan area: -l sets the top left x coordinate, -t the
top left y coordinate, -x selects the width and -y the height of
the scan area. All parameters are specified in millimeters. It
is possible to use the option <I>--paper-size</I> instead.
controls the scan area: -l sets the top left x coordinate, -t
the top left y coordinate, -x selects the width and -y the
height of the scan area. All parameters are specified in mil-
limeters. It is possible to use the option <I>--paper-size</I> instead.
<B>Enhancement</B>
<B>--brightness</B>
controls the brightness of the acquired image. The value varies
controls the brightness of the acquired image. The value varies
from 1 to 255, or less, depending on the scanner model.
<B>--contrast</B>
controls the contrast of the acquired image. Some models do not
controls the contrast of the acquired image. Some models do not
support that option.
<B>--automatic-threshold</B>
automatically sets brightness, contrast, white level, gamma,
automatically sets brightness, contrast, white level, gamma,
noise reduction and image emphasis. These options are not avail-
able when automatic-threshold is in use.
<B>--halftone-pattern</B>
option sets the tonal gradation for the halftone mode. Pattern
downloading is not implemented by the backend.
sets the tonal gradation for the halftone mode. Pattern down-
loading is not implemented by the backend.
<B>--autoseparation</B>
provides automatic separation of text and images.
<B>--white-level</B>
option indicate the source of the white base.
indicates the source of the white base.
<B>--noise-reduction</B>
reduces the isolated dot noise. This option is not supported by
reduces the isolated dot noise. This option is not supported by
all scanners.
<B>--image-emphasis</B>
option sets the image emphasis. Some selection are not available
on all scanners.
sets the image emphasis. Some selection are not available on all
scanners.
<B>--gamma</B>
options set the gamma curve. It is only valid for Gray modes,
and is not available on all scanners. Gamma downloading is not
implemented by the backend.
sets the gamma curve. It is only valid for Gray modes, and is
not available on all scanners. Gamma downloading is not imple-
mented by the backend.
</PRE>
<H2>CONFIGURATION FILE</H2><PRE>
The configuration file <I>/usr/local/etc/sane.d/matsushita.conf</I> supports
the device name to use (eg <I>/dev/scanner</I>) and the SCSI option to auto-
detect the scanners supported.
The configuration file <I>/usr/local/etc/sane.d/matsushita.conf</I> supports
the device name to use (e.g. <I>/dev/scanner</I>) and the SCSI option to
auto-detect the scanners supported.
</PRE>
@ -131,22 +130,23 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_MATSUSHITA</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 en-
vironment 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>
<B>Memory</B> <B>in</B> <B>the</B> <B>KV-SS</B> <B>25</B>
The KV-SS 25 has not enough internal memory to scan a whole A4
The KV-SS 25 has not enough internal memory to scan a whole A4
page in duplex mode at high resolution. The frontend will return
a memory error in that case. Apparently, the KV-SS 25D has not
a memory error in that case. Apparently, the KV-SS 25D has not
that problem.
<B>Pattern</B> <B>and</B> <B>gamma</B> <B>downloading</B>
The scanner, with the proper firmware, can download a halftone
The scanner, with the proper firmware, can download a halftone
pattern and a gamma table. This is not implemented.
<B>Sub-areas</B>
@ -154,20 +154,20 @@
some more precise enhancement options. This is not implemented.
<B>Duplex</B> <B>mode</B>
The backend does not support the setting of different options
for each side. The scan will occur with the same options
(halftone pattern, brightness, image emphasis) for both sides.
The backend does not support the setting of different options
for each side. The scan will occur with the same options (half-
tone pattern, brightness, image emphasis) for both sides.
</PRE>
<H2>SCANNING EXAMPLE</H2><PRE>
To date, the only frontend capable of using this scanner at full speed
To date, the only frontend capable of using this scanner at full speed
is <B><A HREF="scanadf.1.html">scanadf(1)</A></B>.
A <B><A HREF="scanadf.1.html">scanadf(1)</A></B> command line would be:
scanadf -d matsushita --output-file scan%04d.pbm --start-count 0
--duplex --resolution 300 --feeder-mode="All pages" --paper-size="A4"
scanadf -d matsushita --output-file scan%04d.pbm --start-count 0 --du-
plex --resolution 300 --feeder-mode="All pages" --paper-size="A4"
</PRE>

16
man/sane-microtek.5.html
Wyświetl plik

@ -84,7 +84,7 @@
/dev/sge
The configuration file may also contain the special tokens <I>norealcal</I> or
<I>noprecal.</I> <I>norealcal</I> will disable the use of magic, undocumented scan-
<I>noprecal</I>. <I>norealcal</I> will disable the use of magic, undocumented scan-
ner calibration commands which are known to work on the E6, but may not
work with other models. <I>noprecal</I> will disable logic which tries to
avoid scanner precalibration. This logic would only have been acti-
@ -113,13 +113,13 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_MICROTEK</B>
If the library was compiled with debugging support enabled, this

137
man/sane-microtek2.5.html
Wyświetl plik

@ -21,16 +21,15 @@
The <B>sane-microtek2</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to Microtek scanners with a SCSI-2 command
set. This backend can be considered alpha to beta. Some scanner models
are reported to work well, others not. New development versions of this
backend can be obtained from <I>http://karstenfestag.gmxhome.de</I>.
are reported to work well, others not.
There exists a different backend for Microtek scanners with SCSI-1 com-
mand set. Refer to <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B> for details.
And there is work in progress for the ScanMaker 3600. See
And there is partial progress for the ScanMaker 3600. See
<I>http://sourceforge.net/projects/sm3600</I>.
At present, the following scanners are known positively to work with
At present, the following scanners are known positively to work with
this backend:
Vendor Product id Remark
@ -61,67 +60,67 @@
Additional information can be found at <I>http://www.sane-project.org/</I>.
If you own a Microtek scanner other than the ones listed above, it may
or may not work with SANE! Because equal scanners are sold under dif-
If you own a Microtek scanner other than the ones listed above, it may
or may not work with SANE! Because equal scanners are sold under dif-
ferent names in different countries your model may be equivalent to one
of the above.
The parport scanners work with the ppscsi + onscsi kernel modules. See
The parport scanners work with the ppscsi + onscsi kernel modules. See
<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 immedi-
ately switch off the scanner or disconnect its power cable to prevent
ately switch off the scanner or disconnect its power cable to prevent
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
existing "option dump" to "2"
"option dump 2" into your <I>microtek2.conf</I> file or change the ex-
isting "option dump" to "2"
- in a terminal (bash) type
"export SANE_DEBUG_MICROTEK2=30" and then
"scanimage -l0 -t0 -x100 -y20 2&gt;scan.log &gt;sout.pnm"
You get two files: scan.log contains the logfile and sout.pnm
the scanned image (if there was scanned something). Zip them
before sending.
You get two files: scan.log contains the logfile and sout.pnm
the scanned image (if there was scanned something). Zip them be-
fore 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 <B>sane-microtek2</B> 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.
@ -131,28 +130,28 @@
<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.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The configuration file for this backend resides in
<I>/usr/local/etc/sane.d/microtek2.conf</I>.
The configuration file for this backend resides in <I>/usr/lo-</I>
<I>cal/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 &lt;n&gt; and option strip-height &lt;n&gt;, 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:
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 &lt;n&gt; and option strip-height &lt;n&gt;, the entry in the <I>mi-</I>
<I>crotek2.conf</I> file only enables the corresponding option for being
showed in the frontend. There, in the frontend, you can switch the op-
tions on and off. Currently the following options are supported:
option dump &lt;n&gt;
option strip-height &lt;n&gt;
@ -163,56 +162,56 @@
option backend-calibration &lt;on/off&gt;
option colorbalance-adjust &lt;on/off&gt;
<I>option</I> <I>dump</I> <I>&lt;n&gt;</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>&lt;n&gt;</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
INQUIRY and READ SCANNER ATTRIBUTES command are printed to stderr.
If n=1 the contents of the command blocks and the results for the IN-
QUIRY 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>&lt;n&gt;</I> , where &lt;n&gt; is a floating point number, limits
<I>option</I> <I>strip-height</I> <I>&lt;n&gt;</I> , where &lt;n&gt; 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 &lt;n&gt; defaults to 1.0, if this option is not set in
The unit is inch and &lt;n&gt; defaults to 1.0, if this option is not set in
the configuration file. If less than &lt;n&gt; 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 &lt;n&gt;. For example, if &lt;n&gt; 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
an option is set to &lt;on&gt; an appropriate option will appear in the fron-
tend.
an option is set to &lt;on&gt; an appropriate option will appear in the
frontend.
<I>option</I> <I>no-backtrack-option</I> <I>&lt;on/off&gt;</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>&lt;on/off&gt;</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>&lt;on/off&gt;</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>&lt;on/off&gt;</I> You get a button in the frontend where you
<I>option</I> <I>toggle-lamp</I> <I>&lt;on/off&gt;</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>&lt;on/off&gt;</I> You can tell the backend to try to
<I>option</I> <I>lineart-autoadjust</I> <I>&lt;on/off&gt;</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>&lt;on/off&gt;</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>&lt;on/off&gt;</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>&lt;on/off&gt;</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>&lt;on/off&gt;</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.
@ -226,9 +225,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
@ -265,11 +264,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 en-
vironment 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 <B>SANE_DEBUG_MICROTEK2</B> to 1 (Remark: The whole debugging lev-
set <B>SANE_DEBUG_MICROTEK2</B> to 1 (Remark: The whole debugging lev-
els should be better revised).
E.g. just say:
export SANE_DEBUG_MICROTEK2=128

50
man/sane-mustek.5.html
Wyświetl plik

@ -65,8 +65,8 @@
<B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>, and <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>.
Mustek scanners have no protection against exceeding the physical scan
area height. That is, if a scan is attempted with a height that
exceeds the height of the scan surface, the scanner begins making loud
area height. That is, if a scan is attempted with a height that ex-
ceeds the height of the scan surface, the scanner begins making loud
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
@ -78,8 +78,8 @@
a debug output to <I>sane-devel@alioth-lists.debian.net</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 <I>scanimage</I> <I>-L</I>. 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
send all of it to the mailing list. You must be subscribed to sane-de-
vel before you can send mail to the list. See
<I>http://www.sane-project.org/mailing-lists.html</I> for details.
@ -92,11 +92,11 @@
Where <I>special</I> is either the path-name for the special device that cor-
responds to a SCSI scanner or the port number at which the parallel
port scanners can be found (see section <B>PARALLEL</B> <B>PORT</B> <B>SCANNERS</B> below).
For SCSI scanners, the special device name must be a generic SCSI
device or a symlink to such a device. The program <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>
For SCSI scanners, the special device name must be a generic SCSI de-
vice or a symlink to such a device. The program <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>
helps to find out the correct device. Under Linux, such a device name
could be <I>/dev/sg0</I> or <I>/dev/sg3</I>, for example. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for
details.
could be <I>/dev/sg0</I> or <I>/dev/sg3</I>, for example. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for de-
tails.
</PRE>
@ -110,8 +110,8 @@
<B>buffersize</B>, <B>blocksize</B>, <B>strip-height</B>, <B>disable-double-buffering</B>, <B>dis-</B>
<B>able-backtracking</B>, and <B>force-wait</B>.
Options come in two flavors: global and positional ones. Global
options apply to all devices managed by the backend whereas positional
Options come in two flavors: global and positional ones. Global op-
tions 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!
@ -144,15 +144,15 @@
value set for the maximum amount of data scanned in one block. The buf-
fer size is specified in kilobytes. Some scanners freeze if this value
is bigger than 2048. The default value is 1 GB (so effectively no
limit) for most scanners. Don't change this value if you don't know
exactly what you do.
limit) for most scanners. Don't change this value if you don't know ex-
actly what you do.
Option <B>strip-height</B> is a global option that limits the maximum height
of the strip scanned with a single SCSI read command. The height is
specified in inches and may contain a fractional part (e.g., 1.5).
Setting the strip-height to a small value (one inch, for example)
reduces the likelihood of encountering problems with SCSI driver time-
outs and/or timeouts with other devices on the same SCSI bus. Unfortu-
Setting the strip-height to a small value (one inch, for example) re-
duces the likelihood of encountering problems with SCSI driver timeouts
and/or timeouts with other devices on the same SCSI bus. Unfortu-
nately, it also increases scan times. With current SCSI adapters and
drivers this option shouldn't be needed any more.
@ -244,7 +244,7 @@
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
and <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B> setuid root (generally not recommended for security
reasons) or, alternatively, access this backend through the network
daemon <B><A HREF="saned.8.html">saned(8)</A></B>.
@ -283,17 +283,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing 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 en-
vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Value Description

173
man/sane-mustek_pp.5.html
Wyświetl plik

@ -92,20 +92,19 @@
Note that the backend needs to run as root or has to have appropriate
access rights to <I>/dev/parport*</I> 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
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 <B><A HREF="sane-musteka4s2.5.html">sane-musteka4s2(5)</A></B> backend. You can only enable one of them in your
<I>dll.conf</I>. However, you have to enable the backend explicitly in your
<I>dll.conf</I>, just remove the hash mark in the line "mustek_pp".
enable <B><A HREF="libieee1284.3.html">libieee1284(3)</A></B> at compile time. You may also have to enable the
backend explicitly in your <I>dll.conf</I>. 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 <I>mustek</I><B>_</B><I>pp.conf</I> 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 <I>mustek</I><B>_</B><I>pp.conf</I> 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:
@ -117,25 +116,25 @@
<B>&lt;name&gt;</B> is an arbitrary name for the device, optionally enclosed by dou-
ble quotes, for instance "LifeTec 9350".
<B>&lt;port</B> <B>name&gt;</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>&lt;port</B> <B>name&gt;</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 these
addresses can be different for different Linux kernel versions. 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 <I>/etc/conf.modules</I>, <I>/etc/modules.conf</I> and/or <I>/proc/ioports</I>.
In case the backend is configured for raw IO <I>(old</I> <I>setup)</I>, port ad-
dresses 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 versions. 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
<I>/etc/conf.modules</I>, <I>/etc/modules.conf</I> and/or <I>/proc/ioports</I>.
If you are unsure which port to use, you can use the magic value <B>*</B> to
If you are unsure which port to use, you can use the magic value <B>*</B> to
probe for your scanner.
<B>&lt;driver&gt;</B> is the driver to use for this device. Currently available
<B>&lt;driver&gt;</B> is the driver to use for this device. Currently available
drivers are:
<B>cis600</B> : for 600 CP, 96 CP &amp; OEM versions
@ -145,17 +144,17 @@
<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 noise, turn it off immedi-
If the scanner starts making a loud noise, turn it off immedi-
ately !!!
Using the cis600 driver on a 1200CP or a 1200CP+ is probably not dan-
gerous. The cis1200+ driver also works for the 1200CP, and using the
cis1200 driver on a 1200CP+ will typically result in scans that cover
Using the cis600 driver on a 1200CP or a 1200CP+ is probably not dan-
gerous. 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
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 maxi-
resolution of 300x600 DPI, whereas the 1200CP and 1200CP+ have a maxi-
mum optical resolution of 600x1200 DPI.
Examples:
@ -166,29 +165,29 @@
scanner Mustek_600IIIEP * ccd300
If in doubt which port you have to use, or whether your scanner is
detected at all, you can use <I>sane-find-scanner</I> <I>-p</I> to probe all config-
ured ports.
If in doubt which port you have to use, or whether your scanner is de-
tected at all, you can use <I>sane-find-scanner</I> <I>-p</I> to probe all configured
ports.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>mustek</I><B>_</B><I>pp.conf</I> 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>&lt;name&gt;</I> <I>[&lt;value&gt;]</I>
Depending on the nature of the option, a value may or may not be
present. Options always apply to the scanner definition that precedes
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 precedes
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>&lt;value&gt;</B>
Black/white discrimination value to be used during lineart scan-
ning. Pixel values below this value are assumed to be black,
ning. Pixel values below this value are assumed to be black,
values above are assumed to be white.
Default value: 127
Minimum: 0
@ -198,11 +197,11 @@
<B>CIS</B> <B>driver</B> <B>options</B>
<B>top_adjust</B> <B>&lt;value&gt;</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. Differences in offset between
Vertical adjustment of the origin, expressed in millimeter
(floating point). This option can be used to calibrate the po-
sition of the origin, within certain limits. Note that CIS scan-
ners are probably temperature sensitive, and that a certain in-
accuracy may be hard to avoid. Differences in offset between
runs in the order of 1 to 2 mm are not unusual.
Default value: 0.0
Minimum: -5.0
@ -211,14 +210,14 @@
Example: option top_adjust -2.5
<B>slow_skip</B>
Turns fast skipping to the start of the scan region off. When
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
try to move the scanhead to the start of the scan area at the
fastest possible speed. On some models, this may not work, re-
sulting 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
there are no models for which these inaccuracy problems are
known to occur.
By default, fast skipping is used.
@ -226,22 +225,22 @@
Example: option slow_skip
<B>engine_delay</B> <B>&lt;value&gt;</B>
Under normal circumstances, it is sufficient for the driver to
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 transmitted. In rare cases, certain
scanners and/or parallel port chipsets appear to prevent reli-
a new engine command can be transmitted. In rare cases, certain
scanners and/or parallel port chipsets appear to prevent reli-
able 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,
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
command, equal to the engine_delay parameter, expressed in mil-
command, equal to the engine_delay parameter, expressed in mil-
liseconds. It practice an engine_delay of 1 ms is usually suffi-
cient. The maximum delay is 100 ms.
Note that every additional ms of delay can add up to 14 seconds
to the total scanning time (highest resolution), so an as small
Note that every additional ms of delay can add up to 14 seconds
to the total scanning time (highest resolution), so an as small
as possible value is preferred.
Default value: 0
@ -252,8 +251,8 @@
<B>CCD</B> <B>driver</B> <B>options</B>
<B>top</B> <B>&lt;value&gt;</B>
Number of scanlines to skip to the start of the scan area. The
number can be any positive integer. Values known to me are 47
Number of scanlines to skip to the start of the scan area. The
number can be any positive integer. Values known to me are 47
and 56.
Default value: 47
@ -263,7 +262,7 @@
Example: option top 56
<B>waitbank</B> <B>&lt;value&gt;</B>
The number of usecs to wait for a bank change. You should not
The number of usecs to wait for a bank change. You should not
touch this value actually. May be any positive integer
Default value: 700
@ -313,15 +312,15 @@
</PRE>
<H2>GLOBAL OPTIONS</H2><PRE>
You can control the overall behaviour of the <B>sane-stek_pp</B> backend by
global options which precede any scanner definition in the
You can control the overall behaviour of the <B>sane-stek_pp</B> backend by
global options which precede any scanner definition in the
<I>mustek</I><B>_</B><I>pp.conf</I> file.
Currently, there is only one global option:
<B>Global</B> <B>options</B>
<B>no_epp</B> Disable parallel port mode EPP: works around a known bug in the
Linux parport code. Enable this option, if the backend hangs
<B>no_epp</B> Disable parallel port mode EPP: works around a known bug in the
Linux parport code. Enable this option, if the backend hangs
when trying to access the parallel port in EPP mode.
Default value: use EPP
@ -332,7 +331,7 @@
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/mustek</I><B>_</B><I>pp.conf</I>
The backend configuration file (see also description of
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-mustek</I><B>_</B><I>pp.a</I>
@ -349,20 +348,20 @@
This environment variable specifies the list of directories that
may contain the configuration file. On *NIX systems, the direc-
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
arated 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 <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_MUSTEK_PP</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
E.g., a value of 128 requests all debug output to be printed.
If the library was compiled with debug support enabled, this en-
vironment variable controls the debug level for this backend.
E.g., a value of 128 requests all debug output to be printed.
Smaller levels reduce verbosity.
level debug output
@ -376,8 +375,8 @@
6 special debug information
<B>SANE_DEBUG_SANEI_PA4S2</B>
This variable sets the debug level for the SANE interface for
the Mustek chipset A4S2. Note that enabling this will spam your
This variable sets the debug level for the SANE interface for
the Mustek chipset A4S2. Note that enabling this will spam your
terminal with some million lines of debug output.
level debug output
@ -393,12 +392,13 @@
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-net.5.html">sane-net(5)</A></B>, <B><A HREF="saned.8.html">saned(8)</A></B>, <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>,
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-net.5.html">sane-net(5)</A></B>, <B><A HREF="saned.8.html">saned(8)</A></B>, <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>,
<B><A HREF="scanimage.1.html">scanimage(1)</A></B>
For latest bug fixes and information see
<I>http://www.penguin-breeder.org/sane/mustek</I><B>_</B><I>pp/</I>
For additional information on the CIS driver, see
<I>http://home.scarlet.be/eddy</I><B>_</B><I>de</I><B>_</B><I>greef/</I>
@ -413,10 +413,9 @@
</PRE>
<H2>BUGS</H2><PRE>
Too many... please send bug reports to <I>sane-devel@alioth-</I>
<I>lists.debian.net</I> (note that you have to subscribe first to the list
before you can send emails... see <I>http://www.sane-project.org/mail-</I>
<I>ing-lists.html</I>).
Too many... please send bug reports to <I>sane-devel@alioth-lists.de-</I>
<I>bian.net</I> (note that you have to subscribe first to the list before you
can send emails... see <I>http://www.sane-project.org/mailing-lists.html</I>).
</PRE>
@ -431,9 +430,9 @@
<I>the</I> <I>backend</I> <I>version</I> <I>and</I> <I>your</I> <I>scanner</I> <I>hardware</I>
Run <I>SANE</I><B>_</B><I>DEBUG</I><B>_</B><I>MUSTEK</I><B>_</B><I>PP=128</I> <I>scanimage</I> <I>-L</I> as root. If you don't
get any output from the <B>sane-mustek_pp</B> backend, make sure a line
"mustek_pp" is included into your
<I>/usr/local/etc/sane.d/dll.conf</I>. If your scanner isn't detected,
make sure you've defined the right port address in your
"mustek_pp" is included into your <I>/usr/lo-</I>
<I>cal/etc/sane.d/dll.conf</I>. If your scanner isn't detected, make
sure you've defined the right port address in your
<I>mustek</I><B>_</B><I>pp.conf</I>.
<I>the</I> <I>name</I> <I>of</I> <I>your</I> <I>scanner/vendor</I> <I>also</I> <I>a</I> <I>worthy</I> <I>information.</I> <I>Please</I> <I>also</I>

24
man/sane-mustek_usb.5.html
Wyświetl plik

@ -61,8 +61,8 @@
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>mustek</I><B>_</B><I>usb.conf</I> file is a list of options and
device names that correspond to Mustek USB scanners. Empty lines and
The contents of the <I>mustek</I><B>_</B><I>usb.conf</I> file is a list of options and de-
vice names that correspond to Mustek USB scanners. Empty lines and
lines starting with a hash mark (#) are ignored. If a device name is
placed in <I>mustek</I><B>_</B><I>usb.conf</I>, it must be followed by a line containing the
keyword <B>option</B> and an option specifying the scanner type. The following
@ -72,7 +72,7 @@
Instead of using the device name, the scanner can be autodetected by
<B>usb</B> <B>vendor_id</B> <B>product_id</B> statements which are already included into
<I>mustek</I><B>_</B><I>usb.conf</I>. This is only supported with Linux 2.4.8 and higher
and all systems that support libsub. "vendor_id" and "product_id" are
and all systems that support libusb. "vendor_id" and "product_id" are
hexadecimal numbers that identify the scanner. If this doesn't work, a
device name and the option specifying the scanner type must be placed
in <I>mustek</I><B>_</B><I>usb.conf</I> as described above.
@ -118,17 +118,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_MUSTEK_USB</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 en-
vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Value Description

4
man/sane-mustek_usb2.5.html
Wyświetl plik

@ -58,8 +58,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<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.
If the library was compiled with debug support enabled, this en-
vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_MUSTEK_USB2=4

4
man/sane-nec.5.html
Wyświetl plik

@ -55,8 +55,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_NEC</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 en-
vironment 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.

28
man/sane-net.5.html
Wyświetl plik

@ -68,9 +68,9 @@
The above list of hosts can be extended at run-time using environment
variable <B>SANE_NET_HOSTS</B>. This environment variable is a colon-sepa-
rated list of hostnames or IP addresses that should be contacted in
addition to the hosts mentioned in the configuration file. For exam-
ple, a user could set the environment variable to the string:
rated list of hostnames or IP addresses that should be contacted in ad-
dition to the hosts mentioned in the configuration file. For example,
a user could set the environment variable to the string:
new.scanner.com:[::1]:192.168.0.2:scanner.univ.edu
@ -78,8 +78,8 @@
<I>ner.univ.edu</I> are contacted in addition to the hosts listed above.
For this backend to function properly, it is also necessary to define
the <B>sane-port</B> service in <I>/etc/services</I>. The <B>sane</B> service should be
defined using a line of the following form:
the <B>sane-port</B> service in <I>/etc/services</I> using a line of the following
form:
sane-port 6566/tcp # SANE network scanner daemon
@ -106,13 +106,13 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_NET_HOSTS</B>
A colon-separated list of host names or IP addresses to be con-
@ -123,8 +123,8 @@
server for the initial connection request.
<B>SANE_DEBUG_NET</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 en-
vironment 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.

4
man/sane-niash.5.html
Wyświetl plik

@ -63,8 +63,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_NIASH</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
If the library was compiled with debug support enabled, this en-
vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_NIASH=255

32
man/sane-p5.5.html
Wyświetl plik

@ -22,8 +22,8 @@
scanner.
This backend handles 100, 150, 200, 300 and 600 dpi scan resolutions,
in color and gray modes. The 600 dpi is actually 300x600 with lines
enlarged to match the vertical resolution.
in color and gray modes. The 600 dpi is actually 300x600 with lines en-
larged to match the vertical resolution.
<B>EPP/ECP</B> <B>MODES</B> <B>ONLY</B> The current version of the backend uses only EPP or
ECP mode to communicate with the scanner. It is recommended that you
@ -38,7 +38,7 @@
<I>port</I> <I>value</I>
Where <B>value</B> is :
Where <B>value</B> is:
auto autodetect all parallel ports and probe them for scanner
@ -82,17 +82,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_P5</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 en-
vironment 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.
@ -137,10 +137,10 @@
<I>the</I> <I>backend</I> <I>version</I> <I>and</I> <I>your</I> <I>scanner</I> <I>hardware</I>
run <I>SANE</I><B>_</B><I>DEBUG</I><B>_</B><I>P5=255</I> <I>scanimage</I> <I>-L</I> <I>2&gt;log</I> as root. If you don't
get any output from the p5 backend, make sure a line "p5" is
included into your <I>/usr/local/etc/sane.d/dll.conf</I>. If your
scanner isn't detected, make sure you've defined the right port
address, or the correct device in your p5.conf.
get any output from the p5 backend, make sure a line "p5" is in-
cluded into your <I>/usr/local/etc/sane.d/dll.conf</I>. If your scan-
ner isn't detected, make sure you've defined the right port ad-
dress, or the correct device in your <I>p5.conf</I> file.
<I>the</I> <I>name</I> <I>of</I> <I>your</I> <I>scanner/vendor</I>
also a worthy information. Please also include the optical reso-

8
man/sane-pieusb.5.html
Wyświetl plik

@ -12,8 +12,8 @@
</PRE>
<H2>NAME</H2><PRE>
sane-pieusb - SANE backend for USB-connected PIE PowerSlide and
Reflecta DigitDia/CrystalScan/ProScan slide scanners
sane-pieusb - SANE backend for USB-connected PIE PowerSlide and Re-
flecta DigitDia/CrystalScan/ProScan slide scanners
</PRE>
@ -73,8 +73,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_PIEUSB</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 en-
vironment 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.

34
man/sane-pint.5.html
Wyświetl plik

@ -18,10 +18,10 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-pint</B> library implements a SANE (Scanner Access Now Easy) back-
end that provides generic access to hand-held and flatbed scanners
using the PINT (PINT Is Not Twain) device driver. The PINT driver is
being actively developed on the OpenBSD platform, and has been ported
to a few other *NIX-like operating systems.
end that provides generic access to hand-held and flatbed scanners us-
ing the PINT (PINT Is Not Twain) device driver. The PINT driver is be-
ing actively developed on the OpenBSD platform, and has been ported to
a few other *NIX-like operating systems.
PINT is designed to provide an <B><A HREF="ioctl.2.html">ioctl(2)</A></B> interface to many different
scanner types. However, this backend has only been tested with flatbed
@ -30,8 +30,8 @@
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@alioth-lists.debian.net</I>. Have a look at
send a mail with the relevant information for your scanner to <I>sane-de-</I>
<I>vel@alioth-lists.debian.net</I>. Have a look at
<I>http://www.sane-project.org/mailing-lists.html</I> concerning subscription
to sane-devel.
@ -81,17 +81,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <B>.</B>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <B>.</B>, and <I>/usr/local/etc/sane.d</I> be-
ing 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.
If the library was compiled with debug support enabled, this en-
vironment 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.
@ -119,8 +119,8 @@
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 device, and dynamically discovers valid ranges by doing a bi-
nary 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

228
man/sane-pixma.5.html
Wyświetl plik

@ -21,16 +21,17 @@
The <B>sane-pixma</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to Canon PIXMA / i-SENSYS / imageCLASS /
imageRUNNER multi-function devices (All-in-one printers) and the Canon
CanoScan Flatbed/TPU scanners. The backend implements both the USB
interface and network interface (using Canon's BJNP and MFNP proto-
cols). The network interface supports scanners over IPv4 as well as
IPv6 (MFNP over IPv6 is untested).
CanoScan Flatbed/TPU scanners. The backend implements both the USB in-
terface and network interface (using Canon's BJNP and MFNP protocols).
The network interface supports scanners over IPv4 as well as IPv6 (MFNP
over IPv6 is untested).
Currently, the following models work with this backend:
PIXMA E410, E510, E4500
PIXMA G600, G2000, G2010, G2100, G4000, G4511
PIXMA GX6000, GX7000
PIXMA G600, G2000, G2010, G2030, G2070, G2100, G3030, G3070,
G4000, G4070, G4511
PIXMA GX1000, GX2000, GX3000, GX4000, GX6000, GX6500, GX7000
PIXMA MG2100, MG2200, MG2400, MG2500, MG2900, MG3000, MG3100
PIXMA MG3200, MG3500, MG3600, MG4200, MG5100, MG5200, MG5300
PIXMA MG5400, MG5500, MG5600, MG5700, MG6100, MG6200, MG6300
@ -47,10 +48,11 @@
PIXMA MX300, MX310, MX330, MX340, MX350, MX360, MX370
PIXMA MX410, MX420, MX470, MX510, MX520, MX530, MX700, MX720
PIXMA MX850, MX860, MX870, MX882, MX885, MX890, MX920, MX7600
PIXMA TC-20M, TC-5200M
PIXMA TR4500, TR4600, TR4700
PIXMA TS2400, TS2600, TS3100, TS3300, TS3450, TS3451, TS3452
PIXMA TS3500, TS5000, TS5100, TS5350i, TS5400, TS6100, TS6200
PIXMA TS7530, TS7450i ,TS8000, TS8530, TS8200
PIXMA TS7530, TS7450i ,TS8000, TS8200, TS8530, TS8630, TS8630
PIXUS MP10
imageCLASS MF634Cdw, MF733Cdw
imageCLASS MF3110, MF3240, MF4010, MF4018
@ -68,15 +70,15 @@
CanoScan LiDE 300, 400
MAXIFY MB2000, MB2100, MB2300, MB2700, MB5000, MB5100, MB5400
The following models are not well tested and/or the scanner sometimes
The following models are not well tested and/or the scanner sometimes
hangs and must be switched off and on.
PIXMA MP760, MP770, MP780, MP790
The following models may use the same Pixma protocol as those listed
above, but have not yet been reported to work (or not). They are
declared in the backend so that they get recognized and activated.
Feedback in the sane-devel mailing list welcome.
The following models may use the same Pixma protocol as those listed
above, but have not yet been reported to work (or not). They are de-
clared in the backend so that they get recognized and activated. Feed-
back in the sane-devel mailing list welcome.
PIXMA E400, E460, E470, E480, E500, E560, E600, E610
PIXMA E3100, E3300, E3400, E4200
@ -85,27 +87,31 @@
PIXMA MP375R, MP493, MP740
PIXMA MX320, MX390, MX430, MX450, MX490, MX710
PIXMA G3000, G3010, G4010, G6000, G6080, G7000, GM4000, GM4080
PIXMA TR7500, TR7530, TR7600, TR8500, TR8530, TR8580, TR8600
PIXMA TR7500, TR7530, TR7600, TR7800, TR8500, TR8530, TR8580
TR8600
PIXMA TR8630, TR9530
PIXMA TS3400, TS5100, TS6000, TS6130, TS6180, TS6230, TS6280,
TS6300
PIXMA TS6330, TS6330, TS6380, TS6400, TS7330, TS7400, TS7430,
TS8100
PIXMA TS8130, TS8180, TS8230, TS8280, TS8300, TS8330, TS8380,
PIXMA TS6330, TS6330, TS6380, TS6400, TS6630, TS6730, TS7330,
TS7400,
PIXMA TS7430, TS7600i, TS7700, TS7700A, TS7700i, TS8100, TS8130
PIXMA TS8180, TS8230, TS8280, TS8300, TS8330, TS8380, TS8700,
TS9000
PIXMA TS9100, TS9180, TS9500, TS9580
PIXUS MP5, XK50, XK60, XK70, XK80, XK90, XK100, XK500
PIXUS MP5, XK50, XK60, XK70, XK80, XK90, XK100, XK110, XK120,
XK500
imageCLASS MF720, MF810/820, MF5630, MF5650, MF5750, MF8170c
imageCLASS MPC190, D550
i-SENSYS MF110, MF220, MF260, MF410, MF420, MF510, MF520, MF740
i-SENSYS MF110, MF220, MF260, MF410, MF420, MF510, MF520, MF740,
MF750
i-SENSYS MF5880dn, MF5900, MF6680dn, MF8500C
MAXIFY MB5300
The following models may use partly the same Pixma protocol as other
devices listed above, but may still need some work. They are declared
in the backend as experimental and need the environment variable
PIXMA_EXPERIMENT=1 to get recognized and activated. Snoop logs are
required to further investigate, please contact the sane-devel mailing
PIXMA_EXPERIMENT=1 to get recognized and activated. Snoop logs are re-
quired to further investigate, please contact the sane-devel mailing
list.
-- none --
@ -117,7 +123,7 @@
* color and grayscale mode, as well as lineart on certain mod-
els,
* a custom gamma table,
* Automatic Document Feeder, Simplex and Duplex.
* Automatic Document Feeder, Simplex and Duplex,
* Transparency Unit, 24 or 48 bits depth. Infrared channel on
certain models.
@ -134,12 +140,12 @@
peripheral.
This backend, based on cloning original Canon drivers protocols, is in
a production stage. Designed has been carried out without any applica-
ble manufacturer documentation, probably never available. However, we
have tested it as well as we could, but it may not work in all situa-
tions. You will find an up-to-date status at the project homepage. (See
below). Users feedback is essential to help improve features and per-
formances.
a production stage. Design has been carried out without any applicable
manufacturer documentation, probably never available. However, we have
tested it as well as we could, but it may not work in all situations.
You will find an up-to-date status at the project homepage. (See be-
low). Users feedback is essential to help improve features and perfor-
mances.
</PRE>
@ -161,13 +167,13 @@
This option can be used by applications (like <B><A HREF="scanadf.1.html">scanadf(1)</A></B> and
<B><A HREF="scanimage.1.html">scanimage(1)</A></B>) in batch mode, for example when you want to scan
many photos or multiple-page documents. If it is enabled (i.e.
is set to true or yes), the backend waits before every scan
until the user presses the "SCAN" button (for MP150) or the
color-scan button (for other models). Just put the first page in
the scanner, press the button, then the next page, press the
button and so on. When you finished, press the gray-scan button.
(For MP150 you have to stop the frontend by pressing Ctrl-C for
example.)
is set to true or yes), the backend waits before every scan un-
til the user presses the "SCAN" button (for MP150) or the color-
scan button (for other models). Just put the first page in the
scanner, press the button, then the next page, press the button
and so on. When you finished, press the gray-scan button. (For
MP150 you have to stop the frontend by pressing Ctrl-C for exam-
ple.)
<I>button-update</I> <I>(deprecated)</I>
(write only) In the past this option was required to be set to
@ -179,9 +185,9 @@
<I>button-1</I> <I>button-2</I>
(read only) These options will return the value of the respec-
tive buttons. value 0 means that the button was not pressed, 1
is returned when the button was pressed. Some scanners with more
than two buttons send the button number as target.
tive buttons. Value 0 means that the button was not pressed, 1
is returned when the button was pressed. Some scanners, with
more than two buttons, send the button number as target.
<I>original</I>
(read only) Returns the value of the type or size of original to
@ -239,54 +245,56 @@
auto-detected because they are on a different subnet shall be
listed here. If you do not use Linux and your OS does not allow
enumeration of interfaces (i.e. it does not support the <B>getifad-</B>
<B>drs</B>() qfunction) you also may need to add your scanner here as
<B>drs</B>() function) you also may need to add your scanner here as
well.
Scanners shall be listed in the configuration file as follows:
<I>&lt;method&gt;://&lt;host&gt;[:port][/timeout=&lt;value&gt;]</I>
where method indicates the protocol used (bjnp is used for
inkjet multi-functionals and mfnp is used for laser multi-func-
tionals).
<B>method</B> indicates the protocol used. <I>bjnp</I> is used for inkjet
multi-functionals and <I>mfnp</I> is used for laser multi-func-
tionals).
host is the hostname or IP address of the scanner, e.g.
bjnp://10.0.1.4 for IPv4,
bjnp://[2001:888:118e:18e2:21e:8fff:fe36:b64a] for a literal
IPv6-address or bjnp://myscanner.mydomain.org for a hostname.
<B>host</B> is the hostname or IP address of the scanner, e.g.
<I>bjnp://10.0.1.4</I> for IPv4,
<I>bjnp://[2001:888:118e:18e2:21e:8fff:fe36:b64a]</I> for a lit-
eral IPv6-address or <I>bjnp://myscanner.mydomain.org</I> for a
hostname.
The port number is optional and in normally implied by the
method. Port 8610 is the standard port for mfnp, 8612 for bjnp.
<B>port</B> is optional and is normally implied by the method. Port
8610 is the standard port for mfnp, 8612 for bjnp.
A scanner specific timeout value for the network protocol can be
set using the bjnp-timeout parameter. The value is in ms.
<B>timeout</B>
scanner-specific timeout value for the network protocol.
The value is in ms.
Define scanners each on a new line.
Define each scanner each on a separate line.
More globally applicable timeouts can be set using the bjnp-
More globally-applicable timeouts can be set using the bjnp-
timeout parameter as follows:
<I>bjnp-timeout=&lt;value&gt;</I>
A timeout defined using bjnp-timeout will apply to the following
scanner definitions in the file. If required the bjnp-timeout
setting can be defined multiple times, where each setting will
apply only to the scanners that follow the setting. The last
setting is used for the auto discovered scanners. If not
explicitly set, the default 1000ms setting will apply.
scanner definitions in the file. If required, the bjnp-timeout
setting can be defined multiple times, where each setting will
apply only to the scanners that follow the setting. The last
setting is used for auto-discovered scanners. If not explicitly
set, the default 1000ms setting will apply.
Setting timeouts should only be required in exceptional cases.
If so desired networking can be disabled as follows:
If so desired, networking can be disabled as follows:
- If the first non-commented line contains <B>networking=no</B>
all networking will be disabled. This will cause all
further statements in the configuration file to be
ignored.
<I>networking=no</I>
If the first non-commented line contains this entry all
networking will be disabled. All further statements in
the configuration file will be ignored.
- A line that contains <B>auto_detection=no</B> will cause auto-
detection to be skipped. Explicitly defined network scan-
ners will still be probed.
<I>auto</I><B>_</B><I>detection=no</I>
This line will cause auto-detection to be skipped. Ex-
plicitly defined network scanners will still be probed.
</PRE>
@ -296,62 +304,62 @@
</PRE>
<H2>NETWORKING SUPPORT</H2><PRE>
The <B>sane-pixma</B> backend supports network scanners using the so called
The <B>sane-pixma</B> backend supports network scanners using the so called
Canon BJNP and MFNP protocols.
Canon seems to be dropping support for these protocols in recent scan-
Canon seems to be dropping support for these protocols in recent scan-
ners. To verify if your scanner supports one of these protocols, check
the content of the _scanner._tcp service entry in mDNS/DNS-SD (using
for example <B><A HREF="avahi-discover.1.html">avahi-discover(1)</A></B>). If that does not list port 8610 or
the content of the _scanner._tcp service entry in mDNS/DNS-SD (using
for example <B><A HREF="avahi-discover.1.html">avahi-discover(1)</A></B>). If that does not list port 8610 or
8612 your scanner probably does not support the mfmp or bjnp protols.
Both IPv4 and IPv6 are supported, but IPv6 is as yet untested with
Both IPv4 and IPv6 are supported, but IPv6 is as yet untested with
MFNP. Please report your results on the mailing list.
Configuration is normally not required. The <B>sane-pixma</B> backend will
auto-detect your scanner if it is within the same subnet as your com-
Configuration is normally not required. The <B>sane-pixma</B> backend will
auto-detect your scanner if it is within the same subnet as your com-
puter if your OS does support this.
If your scanner can not be auto-detected, you can add it to the
If your scanner can not be auto-detected, you can add it to the
<B>sane-pixma</B> configuration file (see above).
</PRE>
<H2>FIREWALLING FOR NETWORKED SCANNERS</H2><PRE>
The <B>sane-pixma</B> backend communicates with port 8610 for MFNP or port
8612 for BJNP on the scanner. So you will have to allow outgoing traf-
The <B>sane-pixma</B> backend communicates with port 8610 for MFNP or port
8612 for BJNP on the scanner. So you will have to allow outgoing traf-
fic TO port 8610 or 8612 on the common subnet for scanning.
Scanner detection is slightly more complicated. The <B>sane-pixma</B> backend
Scanner detection is slightly more complicated. The <B>sane-pixma</B> backend
sends a broadcast on all direct connected subnets it can find (provided
your OS allows for enumeration of all network interfaces). The broad-
cast is sent FROM port 8612 TO port 8610 or 8612 on the broadcast
address of each interface. The outgoing packets will be allowed by the
your OS allows for enumeration of all network interfaces). The broad-
cast is sent FROM port 8612 TO port 8610 or 8612 on the broadcast ad-
dress of each interface. The outgoing packets will be allowed by the
rule described above.
Responses from the scanner are sent back to the computer TO port 8612.
Connection tracking however does not see a match as the response does
not come from the broadcast address but from the scanners own address.
For automatic detection of your scanner, you will therefore have to
allow incoming packets TO port 8612 on your computer. This applies to
Responses from the scanner are sent back to the computer TO port 8612.
Connection tracking however does not see a match as the response does
not come from the broadcast address but from the scanners own address.
For automatic detection of your scanner, you will therefore have to al-
low incoming packets TO port 8612 on your computer. This applies to
both MFNP and BJNP.
So in short: open the firewall for all traffic from your computer to
So in short: open the firewall for all traffic from your computer to
port 8610 (for MFNP) or 8612 (for BJNP) AND to port 8612 (for both BJNP
and MFNP) to your computer.
With the firewall rules above there is no need to add the scanner to
the <I>pixma.conf</I> file, unless the scanner is on a network that is not
directly connected to your computer.
With the firewall rules above there is no need to add the scanner to
the <I>pixma.conf</I> file, unless the scanner is on a network that is not di-
rectly connected to your computer.
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_PIXMA</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend
itself. Higher value increases the verbosity and includes the
information printed at the lower levels.
If the library was compiled with debug support enabled, this en-
vironment variable controls the debug level for this backend it-
self. Higher value increases the verbosity and includes the in-
formation printed at the lower levels.
0 print nothing (default)
1 print error and warning messages (recommended)
2 print informational messages
@ -361,10 +369,10 @@
21 full dump USB traffic
<B>SANE_DEBUG_BJNP</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for the <B>BJNP</B> <B>and</B>
<B>MFNP</B> network protocols for this backend. Higher value increases
the verbosity and includes the information printed at the lower
If the library was compiled with debug support enabled, this en-
vironment variable controls the debug level for the <B>BJNP</B> <B>and</B>
<B>MFNP</B> network protocols for this backend. Higher value increases
the verbosity and includes the information printed at the lower
levels.
0 print nothing (default)
1 Print error and warning messages (recommended)
@ -374,22 +382,22 @@
5 Print full protocol contents
<B>PIXMA_EXPERIMENT</B>
Setting to a non-zero value will enable the support for experi-
mental models. You should also set SANE_DEBUG_PIXMA to 11.
Setting to a non-zero value will enable experimental support for
further models. You should also set SANE_DEBUG_PIXMA to 11.
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. On *NIX systems, the direc-
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
arated 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 <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
</PRE>
@ -397,7 +405,7 @@
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="scanadf.1.html">scanadf(1)</A></B>, <B><A HREF="gamma4scanimage.1.html">gamma4scanimage(1)</A></B>,
<B><A HREF="getifaddrs.3.html">getifaddrs(3)</A></B>
In case of trouble with a recent Pixma model, try the latest code for
In case of trouble with a recent Pixma model, try the latest code for
the <B>sane-pixma</B> backend, available in the Sane git repository at:
<I>https://gitlab.com/sane-project/backends.git</I>
@ -406,11 +414,11 @@
</PRE>
<H2>AUTHORS</H2><PRE>
Wittawat Yamwong, Nicolas Martin, Dennis Lou, Louis Lagendijk, Rolf
Wittawat Yamwong, Nicolas Martin, Dennis Lou, Louis Lagendijk, Rolf
Bensch
We would like to thank all testers and helpers. Without them we could
not be able to write subdrivers for models we don't have. See also the
We would like to thank all testers and helpers. Without them we could
not be able to write subdrivers for models we don't have. See also the
project homepage.
15 Aug 2020 <B><A HREF="sane-pixma.5.html">sane-pixma(5)</A></B>

65
man/sane-plustek.5.html
Wyświetl plik

@ -167,8 +167,8 @@
<B>The</B> <B>Options:</B>
option warmup t
<I>t</I> specifies the warmup period in seconds, if set to -1, the
automatic warmup function will be used
<I>t</I> specifies the warmup period in seconds, if set to -1, the au-
tomatic warmup function will be used
option lampOff t
<I>t</I> is the time in seconds for switching off the lamps in standby
@ -259,13 +259,13 @@
set values of the AFE for each channel. The range is between 0
and 63. -1 means autocalibration.
See the plustek.conf file for examples.
See the <I>plustek.conf</I> file for examples.
<B>Note:</B>
You have to make sure, that the USB subsystem is loaded correctly and
you have access to the device-node. For more details see <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>
manpage. You might use <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B> to check that you have
access to your device.
manpage. You might use <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B> to check that you have ac-
cess to your device.
<B>Note:</B>
If there's no configuration file, the backend defaults to <B>device</B> <B>auto</B>
@ -292,17 +292,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_PLUSTEK</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 en-
vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_PLUSTEK=10
@ -310,7 +310,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>, <B><A HREF="sane-stek_pp.5.html">sane-stek_pp(5)</A></B>,
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-u12.5.html">sane-u12(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</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>
<I>/usr/local/share/doc/sane-backends/plustek/Plustek-USB.changes</I>
@ -320,35 +320,34 @@
Please send any information and bug-reports to:
<B>SANE</B> <B>Mailing</B> <B>List</B>
Additional info and hints can be obtained from our
Mailing-List archive at:
<I>http://www.sane-project.org/mailing-lists.html</I>
Additional info and hints can be obtained from our mailing-List archive
at: <I>http://www.sane-project.org/mailing-lists.html</I>.
To obtain debug messages from the backend, please set the environment-
variable <B>SANE_DEBUG_PLUSTEK</B> before calling your favorite scan-frontend
(i.e. <B><A HREF="scanimage.1.html">scanimage(1)</A></B>),<B>i.e.:</B>
To obtain debug messages from the backend, please set the environment-
variable <B>SANE_DEBUG_PLUSTEK</B> before calling your favorite SANE frontend
(e.g. <B><A HREF="scanimage.1.html">scanimage(1)</A></B>):
<I>export</I> <I>SANE</I><B>_</B><I>DEBUG</I><B>_</B><I>PLUSTEK=20</I> <I>;</I> <I>scanimage</I>
The value controls the verbosity of the backend. Please note, that val-
ues greater than 24 force the backend to output raw data files, which
could be rather large. The ending of these files is ".raw". For prob-
lem reports it should be enough the set the verbosity to 13.
The value controls the verbosity of the output. Please note that values
greater than 24 force the backend to output raw data files which could
be rather large. The suffix of these files is ".raw". For problem re-
ports it should be enough the set the verbosity to 13.
</PRE>
<H2>KNOWN BUGS & RESTRICTIONS</H2><PRE>
* The driver does not support these manic scalings up to 16 times the
physical resolution. The only scaling is done on resolutions between
the physical resolution of the CCD-/CIS-sensor and the stepper motor
* The driver does not support these manic scalings up to 16 times the
physical resolution. The only scaling is done on resolutions between
the physical resolution of the CCD-/CIS-sensor and the stepper motor
i.e. you have a 600x1200 dpi scanner and you are scanning using 800dpi,
so scaling is necessary, because the sensor only delivers 600dpi but
so scaling is necessary, because the sensor only delivers 600dpi but
the motor is capable to perform 1200dpi steps.
* Plusteks' model policy is somewhat inconsistent. They sell techni-
cally different devices under the same product name. Therefore it is
possible that some devices like the UT12 or U12 won't work - please
check the model list above and compare the product-id to the one your
* Plusteks' model policy is somewhat inconsistent. They sell techni-
cally different devices under the same product name. Therefore it is
possible that some devices like the UT12 or U12 won't work - please
check the model list above and compare the product-id to the one your
device has.
* Negative/Slide scanning quality is poor.

84
man/sane-plustek_pp.5.html
Wyświetl plik

@ -73,8 +73,8 @@
<B>ARIES</B> <B>SCANNERS</B>
There's one scanner sold as Aries Scanner, but is in fact a Plustek
device. The following table will show the relationship:
There's one scanner sold as Aries Scanner, but is in fact a Plustek de-
vice. The following table will show the relationship:
Model: Plustek Model: Remarks:
--------------------------- -------------- ------------
@ -141,25 +141,25 @@
<I>m</I> = 0 default: no override
<I>m</I> = 1 OpticPro 9630PL override (works if OP9630 has been
detected) forces legal size (14")
<I>m</I> = 1 OpticPro 9630PL override (works if OP9630 has been de-
tected) forces legal size (14")
<I>m</I> = 2 Primax 4800Direct override (works if OP600 has been
detected) swaps red/green color
<I>m</I> = 2 Primax 4800Direct override (works if OP600 has been de-
tected) swaps red/green color
<I>m</I> = 3 OpticPro 9636 override (works if OP9636 has been
detected) disables backends transparency/negative capa-
bilities
<I>m</I> = 3 OpticPro 9636 override (works if OP9636 has been de-
tected) disables backends transparency/negative capabili-
ties
<I>m</I> = 4 OpticPro 9636P override (works if OP9636 has been
detected) disables backends transparency/negative capa-
bilities
<I>m</I> = 4 OpticPro 9636P override (works if OP9636 has been de-
tected) disables backends transparency/negative capabili-
ties
<I>m</I> = 5 OpticPro A3I override (works if OP12000 has been
detected) enables A3 scanning
<I>m</I> = 5 OpticPro A3I override (works if OP12000 has been de-
tected) enables A3 scanning
<I>m</I> = 6 OpticPro 4800P override (works if OP600 has been
detected) swaps red/green color
<I>m</I> = 6 OpticPro 4800P override (works if OP600 has been de-
tected) swaps red/green color
<I>m</I> = 7 Primax 4800Direct 30bit override (works if OP4830 has
been detected)
@ -208,17 +208,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_PLUSTEK_PP</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
If the library was compiled with debug support enabled, this en-
vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_PLUSTEK_PP=10
@ -235,31 +235,31 @@
Please send any information and bug-reports to:
<B>SANE</B> <B>Mailing</B> <B>List</B>
Additional info and hints can be obtained from our
Mailing-List archive at:
<I>http://www.sane-project.org/mailing-lists.html</I>
Additional info and hints can be obtained from our mailing-List archive
at: <I>http://www.sane-project.org/mailing-lists.html</I>.
To obtain debug messages from the backend, please set the environment-
variable <B>SANE_DEBUG_PLUSTEK_PP</B> before calling your favorite SANE front-
end (e.g. <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>):
To obtain debug messages from the backend, please set the environment-
variable <B>SANE_DEBUG_PLUSTEK_PP</B> before calling your favorite scan-fron-
tend (i.e. <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>),<B>i.e.:</B>
<I>export</I> <I>SANE</I><B>_</B><I>DEBUG</I><B>_</B><I>PLUSTEK</I><B>_</B><I>PP=20</I> <I>;</I> <I>xscanimage</I>
The value controls the verbosity of the backend.
The value controls the verbosity of the output.
</PRE>
<H2>KNOWN BUGS & RESTRICTIONS</H2><PRE>
* The Halftoning works, but the quality is poor
* Printers (especially HP models) will start to print during scanning.
This in fact is a problem to other printers too, using bidirectional
* Printers (especially HP models) will start to print during scanning.
This in fact is a problem to other printers too, using bidirectional
protocol (see www.plustek.com (TAIWAN) page for further details)
* The driver does not support these manic scalings up to 16 times the
physical resolution. The only scaling is done on resolutions between
the physical resolution of the CCD-sensor and the stepper motor i.e.
you have a 600x1200 dpi scanner and you are scanning using 800dpi, so
scaling is necessary, because the sensor only delivers 600dpi but the
* The driver does not support these manic scalings up to 16 times the
physical resolution. The only scaling is done on resolutions between
the physical resolution of the CCD-sensor and the stepper motor i.e.
you have a 600x1200 dpi scanner and you are scanning using 800dpi, so
scaling is necessary, because the sensor only delivers 600dpi but the
motor is capable to perform 800dpi steps.
* On some devices, the pictures seems bluish
@ -268,7 +268,7 @@
* The 300dpi transparency and negative mode does not work correctly.
* There is currently no way to distinguish a model with and without
* There is currently no way to distinguish a model with and without
transparency unit.
* The scanned images seem to be too dark (P9636T)
@ -277,8 +277,8 @@
* 30bit mode is currently not supported.
* On low end systems under heavy system load the driver may lose data,
which can result in picture corruption or cause the sensor to hit the
* On low end systems under heavy system load the driver may lose data,
which can result in picture corruption or cause the sensor to hit the
scan bed.
* The scanning speed on 600x1200 dpi models is slow.

8
man/sane-pnm.5.html
Wyświetl plik

@ -20,8 +20,8 @@
The <B>sane-pnm</B> library implements a SANE (Scanner Access Now Easy) back-
end that provides access to PNM (Portable aNyMap files, which covers
PBM bitmap files, PGM grayscale files, and PPM pixmap files). The pur-
pose of this backend is primarily to aid in debugging of SANE fron-
tends. It also serves as an illustrative example of a minimal SANE
pose of this backend is primarily to aid in debugging of SANE front-
ends. It also serves as an illustrative example of a minimal SANE
backend.
@ -48,8 +48,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_PNM</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 en-
vironment 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.

18
man/sane-qcam.5.html
Wyświetl plik

@ -73,17 +73,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_QCAM</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 en-
vironment 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.

26
man/sane-ricoh.5.html
Wyświetl plik

@ -31,11 +31,11 @@
<I>special</I>
Where <I>special</I> is the path-name for the special device that corresponds
to a SCSI scanner. The special device name must be a generic SCSI
device or a symlink to such a device. The program <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>
to a SCSI scanner. The special device name must be a generic SCSI de-
vice or a symlink to such a device. The program <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>
helps to find out the correct 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.
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 de-
tails.
</PRE>
@ -60,17 +60,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_RICOH</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 en-
vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_RICOH=4

4
man/sane-ricoh2.5.html
Wyświetl plik

@ -56,8 +56,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_RICOH2</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 en-
vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.

12
man/sane-rts8891.5.html
Wyświetl plik

@ -46,8 +46,8 @@
choices are <I>Color</I>, <I>Gray</I> and <I>Lineart</I>. The default mode is <I>Color</I>.
The <I>Lineart</I> mode is for black and white only (1 bit). <I>Gray</I> will
produce 256 levels of gray (8 bits). <I>Color</I> mode allows for over
16 million different colors produced from 24 bits of color
information.
16 million different colors produced from 24 bits of color in-
formation.
<B>--resolution</B>
selects the resolution for a scan. The horizontal and vertical
@ -72,8 +72,8 @@
<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.
as a percentage in the range 0..100% (in steps of 1). The de-
fault value of the threshold option is 50.
</PRE>
@ -88,8 +88,8 @@
Option
<B>allowsharing</B>
enables or not the sharing of the scanner between multiple fron-
tends at the same time.
enables or not the sharing of the scanner between multiple
frontends at the same time.
<B>modelnumber</B>
is used to force the reported model by the backend and is only

26
man/sane-s9036.5.html
Wyświetl plik

@ -28,11 +28,11 @@
<I>special</I>
Where <I>special</I> is the path-name for the special device that corresponds
to a SCSI scanner. The special device name must be a generic SCSI
device or a symlink to such a device. The program <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>
to a SCSI scanner. The special device name must be a generic SCSI de-
vice or a symlink to such a device. The program <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>
helps to find out the correct 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.
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 de-
tails.
</PRE>
@ -57,17 +57,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_S9036</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 en-
vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_S9036=4

4
man/sane-sceptre.5.html
Wyświetl plik

@ -116,8 +116,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_SCEPTRE</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 en-
vironment 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.

60
man/sane-scsi.5.html
Wyświetl plik

@ -23,8 +23,8 @@
</PRE>
<H2>GENERAL INFO</H2><PRE>
For scanners with a SCSI interface, it may be necessary to edit the
appropriate backend configuration file before using SANE for the first
For scanners with a SCSI interface, it may be necessary to edit the ap-
propriate backend configuration file before using SANE for the first
time. For most systems, the configuration file should list the name of
the generic SCSI device that the scanner is connected to (e.g., under
Linux, <I>/dev/sg4</I> or <I>/dev/sge</I> is such a generic SCSI device). It is cus-
@ -45,7 +45,7 @@
scsi <I>VENDOR</I> <I>MODEL</I> <I>TYPE</I> <I>BUS</I> <I>CHANNEL</I> <I>ID</I> <I>LUN</I>
where <I>VENDOR</I> is the SCSI vendor string, <I>MODEL</I> is the SCSI model string,
<I>TYPE</I> is type SCSI device type string, <I>BUS</I> is the SCSI bus number (named
<I>TYPE</I> is the SCSI device type string, <I>BUS</I> is the SCSI bus number (named
"host" in <I>/proc/scsi/scsi</I>), <I>CHANNEL</I> is the SCSI channel number, <I>ID</I> is
the SCSI id, and <I>LUN</I> is the logical unit number of the scanner device.
The first two fields are strings which must be enclosed in double-
@ -77,9 +77,9 @@
would have the effect that all SCSI devices in the system with a vendor
string of MUSTEK would be probed and recognized by the backend.
If the remainder of a scsi-string consists of asterisks only, the
asterisks can be omitted. For example, the following line is equiva-
lent to the one specified previously:
If the remainder of a scsi-string consists of asterisks only, the as-
terisks can be omitted. For example, the following line is equivalent
to the one specified previously:
scsi MUSTEK
@ -89,8 +89,8 @@
When using a SCSI scanner, ensure that the access permission for the
generic SCSI device is set appropriately. We recommend to add a group
"scanner" to <I>/etc/group</I> which contains all users that should have
access to the scanner. The permission of the device should then be set
"scanner" to <I>/etc/group</I> which contains all users that should have ac-
cess to the scanner. The permission of the device should then be set
to allow group read and write access. For example, if the scanner is
at generic SCSI device <I>/dev/sg0</I>, then the following two commands would
set the permission correctly:
@ -132,8 +132,8 @@
Works on FreeBSD 2.2.5R and 3.0 using the <B>aic</B> driver,
provided that Plug-and-Play support is disabled on the
card. If there are no <I>uk</I> devices, just do a <I>sh</I> <I>MAKEDEV</I>
<I>uk0</I> in the <I>/dev</I> directory. The scanner should then be
accessible as <I>/dev/uk0</I> if it was probed during boot.
<I>uk0</I> in the <I>/dev</I> directory. The scanner should then be ac-
cessible as <I>/dev/uk0</I> if it was probed during boot.
Tekram DC390
Reported to work fine under FreeBSD 2.2.2R with the <B>amd</B>
@ -150,15 +150,15 @@
2.0 on, the maximum buffer size can be changed at program run time, and
there is no restriction in size. This driver version is part of the
Linux kernels from version 2.2.7 on. If the new SG driver is available
some backends (e.g. <B><A HREF="sane-umax.5.html">sane-umax(5)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B><B>,</B> <B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B>) auto-
some backends (e.g. <B><A HREF="sane-umax.5.html">sane-umax(5)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B>) auto-
matically request larger SCSI buffers. If a backend does not automati-
cally request a larger SCSI buffer, set the environment variable
<B>SANE_SG_BUFFERSIZE</B> to the desired buffer size in bytes. It is not rec-
ommended to use more than 1 MB, because for large values the probabil-
ity increases that the SG driver cannot allocate the necessary buf-
fer(s). For ISA cards, even 1 MB might be a too large value. For a
detailed discussion of memory issues of the SG driver, see
<I>http://www.torque.net/sg.</I>
fer(s). For ISA cards, even 1 MB might be a too large value. For a de-
tailed discussion of the Linux SG SCSI driver see:
<I>https://tldp.org/HOWTO/SCSI-Generic-HOWTO</I>.
For Linux kernels before version 2.2.7 the size of the buffer is only
32KB. This works, but for many cheaper scanners this causes scanning
@ -183,8 +183,8 @@
and the kernel will probe and recognize your scanner (this needs to be
done as root). It's also possible to dynamically remove a SCSI device
by using the ``remove-single-device'' command. For details, please
refer to to the SCSI-2.4-HOWTO.
by using the ``remove-single-device'' command. For details, please re-
fer to to the SCSI-2.4-HOWTO.
Scanners are known to work with the following SCSI adapters under
Linux. This list isn't complete, usually any SCSI adapter supported by
@ -196,10 +196,10 @@
be detected correctly. Use a current kernel.
Adaptec AHA-1505/AHA-1542/AHA-2940
Reported to work fine with Linux since v2.0. If you
encounter kernel freezes or other unexpected behaviour
get the latest Linux kernel (2.2.17 seems to work) or
reduce SCSI buffer size to 32 kB.
Reported to work fine with Linux since v2.0. If you en-
counter kernel freezes or other unexpected behaviour get
the latest Linux kernel (2.2.17 seems to work) or reduce
SCSI buffer size to 32 kB.
ASUS SC200
Reported to work fine with Linux v2.0.
@ -246,7 +246,7 @@
the form ``restart (ncr dead ?)'' in your <I>/var/log/mes-</I>
<I>sages</I> file or on the system console, it's an indication
that the timeout is too short. In this case, find the
line ``if (np-&gt;latetime&gt;10)'' in file <I>ncr53c8xx.</I> (nor-
line ``if (np-&gt;latetime&gt;10)'' in file <I>ncr53c8xx.c</I> (nor-
mally in directory <I>/usr/src/linux/drivers/scsi</I>) and
change the constant 10 to, say, 60 (one minute). Then
rebuild the kernel/module and try again.
@ -254,8 +254,8 @@
Tekram DC315
The driver can be downloaded from
<I>http://www.garloff.de/kurt/linux/dc395/</I>. For some older
scanners it may be necessary to disable all the more
advanced features by using e.g. <I>modprobe</I> <I>dc395x</I><B>_</B><I>trm</I>
scanners it may be necessary to disable all the more ad-
vanced features by using e.g. <I>modprobe</I> <I>dc395x</I><B>_</B><I>trm</I>
<I>dc395x</I><B>_</B><I>trm=7,5,1,32</I>.
Tekram DC390
@ -274,18 +274,18 @@
use, append the character 'a'+target-id to the special device name.
For example, the SCSI device connected to the first SCSI controller and
with target-id 0 would be called <I>/dev/sg0a</I>, and the device with target-
id 1 on that same bus would be called <I>/dev/sg0b,</I> and so on.
id 1 on that same bus would be called <I>/dev/sg0b</I>, and so on.
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_SANEI_SCSI</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for the generic
SCSI I/O subsystem. E.g., a value of 128 requests all debug
output to be printed by the backend. A value of 255 also prints
kernel messages from the SCSI subsystem (where available).
Smaller levels reduce verbosity.
If the library was compiled with debug support enabled, this en-
vironment variable controls the debug level for the generic SCSI
I/O subsystem. E.g., a value of 128 requests all debug output
to be printed by the backend. A value of 255 also prints kernel
messages from the SCSI subsystem (where available). Smaller
levels reduce verbosity.
<B>SANE_SCSICMD_TIMEOUT</B>
sets the timeout value for SCSI commands in seconds. Overriding

116
man/sane-sharp.5.html
Wyświetl plik

@ -50,10 +50,10 @@
<I>special</I>
where <I>special</I> is the path-name for the special device that corresponds
to a SCSI 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. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for
details.
to a SCSI scanner. The special device name must be a generic SCSI de-
vice 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 de-
tails.
</PRE>
@ -71,12 +71,12 @@
<B>--source</B>
Paper Source. This option is only available if an automatic doc-
ument feeder or a transparency adapter is installed. Possible
settings are: <I>Flatbed</I>, <I>Automatic</I> <I>Document</I> <I>Feeder</I>, and <I>Trans-</I>
<I>parency</I> <I>Adapter</I>. If an ADF or a transparency adapter is
installed, using it is the default selection.
settings are: <I>Flatbed</I>, <I>Automatic</I> <I>Document</I> <I>Feeder</I>, and <I>Transpar-</I>
<I>ency</I> <I>Adapter</I>. If an ADF or a transparency adapter is installed,
using it is the default selection.
<B>--custom-gamma</B>
Custom Gamma This option determines whether a builtin or a cus-
Custom Gamma. This option determines whether a builtin or a cus-
tom gamma table is used. Possible settings are: <I>yes</I> (enables
custom gamma tables) or <I>no</I> (enables a built gamma table).
@ -88,13 +88,13 @@
the backend.)
<B>--gamma-table</B>
Gamma Table. Allowed values: 0..255; 256 numbers must be
defined. The default values are 0, 1, 2, .. 255 (i.e., gamma ==
Gamma Table. Allowed values: 0..255; 256 numbers must be de-
fined. The default values are 0, 1, 2, .. 255 (i.e., gamma ==
1). This table is only used for gray scale scans.
<B>--red-gamma-table</B>
Red Gamma Table. Allowed values: 0..255; 256 numbers must be
defined. The default values are 0, 1, 2, .. 255 (i.e., gamma ==
Red Gamma Table. Allowed values: 0..255; 256 numbers must be de-
fined. The default values are 0, 1, 2, .. 255 (i.e., gamma ==
1).
<B>--green-gamma-table</B>
@ -118,8 +118,8 @@
(<B>-x</B>) and bottom right y position of scan area (<B>-y</B>). The possi-
ble settings depend on the scanner model and, for the JX-250 and
the JX-350, also on the usage of the automatic document feeder
resp. the transparency adapter. Please refer to the values
allowed by <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, or <B><A HREF="xsane.1.html">xsane(1)</A></B>. With <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, enter
resp. the transparency adapter. Please refer to the values al-
lowed by <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, or <B><A HREF="xsane.1.html">xsane(1)</A></B>. With <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, enter
one of the following commands in order to see the allowed param-
eter values for the scan window:
@ -136,26 +136,26 @@
<B>--threshold</B>
Sets the threshold for black and white pixels in lineart mode.
Possible values are 1..255. The default value is 128. This
option is only available in scan mode <I>lineart</I>.
Possible values are 1..255. The default value is 128. This op-
tion is only available in scan mode <I>lineart</I>.
<B>--threshold-red</B>
Sets the threshold for the red component of a pixel in in lin-
eart color scan mode. Possible values are 1..255. The default
value is 128. This option is only available in scan mode color
<I>lineart</I>.
Sets the threshold for the red component of a pixel in lineart
color scan mode. Possible values are 1..255. The default value
is 128. This option is only available in scan mode color <I>lin-</I>
<I>eart</I>.
<B>--threshold-green</B>
Sets the threshold for the green component of a pixel in in lin-
eart color scan mode. Possible values are 1..255. The default
value is 128. This option is only available in scan mode color
<I>lineart</I> <I>.</I>
Sets the threshold for the green component of a pixel in lineart
color scan mode. Possible values are 1..255. The default value
is 128. This option is only available in scan mode color <I>lin-</I>
<I>eart</I> <I>.</I>
<B>--threshold-blue</B>
Sets the threshold for the blue component of a pixel in in lin-
eart color scan mode. Possible values are 1..255. The default
value is 128. This option is only available in scan mode color
<I>lineart</I>.
Sets the threshold for the blue component of a pixel in lineart
color scan mode. Possible values are 1..255. The default value
is 128. This option is only available in scan mode color <I>lin-</I>
<I>eart</I>.
<B>--lightcolor</B>
Sets the color of the light source. Possible values are <I>white</I>,
@ -178,11 +178,11 @@
about device names.
Lines setting an option start with the key word <B>option,</B> followed by the
option's name and the option's value. At present, three options are
defined: <B>buffers,</B> <B>buffersize,</B> and <B>readqueue.</B>
option's name and the option's value. At present, three options are de-
fined: <B>buffers,</B> <B>buffersize,</B> and <B>readqueue.</B>
Options defined at the start of <I>sharp.conf</I> apply to all devices;
options defined after a device name apply to this device.
Options defined at the start of <I>sharp.conf</I> apply to all devices; op-
tions defined after a device name apply to this device.
The options <B>buffers</B> and <B>readqueue</B> are only significant if the backend
has been compiled so that for each scan a second process is forked
@ -227,10 +227,10 @@
Stops of the carriage can be caused by the following reasons:
- too much "traffic" on the SCSI bus
- too much "traffic" on the SCSI bus,
- slow responses by the backend to the scanner,
- a program which processes the data acquired by the backend too
slow.
- a program which processes the data acquired by the backend is
too slow.
Too much "traffic" on the SCSI bus: This happens for example, if hard
disks are connected to the same SCSI bus as the scanner, and when data
@ -248,8 +248,8 @@
could try to reduce the load of the system. Even while the backend and
the reader process need only a minor amount of processor time, other
running processes can cause an increase in the time delay between two
time slices given to the reader process. On slower systems, such an
increased delay can be enough to cause a carriage stop with the JX-250.
time slices given to the reader process. On slower systems, such an in-
creased delay can be enough to cause a carriage stop with the JX-250.
For Linux, the usage of the SG driver version 2.1.36 or above is recom-
mended, because it supports, in combination with the SCSI library of
Sane version 1.0.2, command queueing within the kernel. This queueing
@ -263,14 +263,14 @@
<B>buffers,</B> so that an entire image can be stored in these buffers.
In order to see, if the backend is too slow or if the further process-
ing of the data is too slow, set the environment variable
<B>SANE_DEBUG_SHARP</B> to 1. When a scan is finished, the backend writes the
line "buffer full conditions: <I>nn</I>" to stderr. If <I>nn</I> is zero, carriage
stops are caused by too slow responses of the backend or too much
"traffic" on the SCSI bus. If <I>nn</I> is greater than zero, the backend had
to wait <I>nn</I> times until a buffer has been processed by the frontend.
(Please note that <B>option</B> <B>buffers</B> must be greater than <B>option</B> <B>readqueue</B>
in order to get useful output for "buffer full conditions".)
ing of the data is too slow, set the environment variable <B>SANE_DE-</B>
<B>BUG_SHARP</B> to 1. When a scan is finished, the backend writes the line
"buffer full conditions: <I>nn</I>" to stderr. If <I>nn</I> is zero, carriage stops
are caused by too slow responses of the backend or too much "traffic"
on the SCSI bus. If <I>nn</I> is greater than zero, the backend had to wait <I>nn</I>
times until a buffer has been processed by the frontend. (Please note
that <B>option</B> <B>buffers</B> must be greater than <B>option</B> <B>readqueue</B> in order to
get useful output for "buffer full conditions".)
</PRE>
@ -289,8 +289,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_SHARP</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 en-
vironment 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.
@ -306,17 +306,17 @@
2. Threshold level does not work (only JX-610)
3. The maximum resolution is limited to 600 dpi(JX-610 supported to
3. The maximum resolution is limited to 600 dpi (JX-610 supported to
1200 dpi) resp. 400 dpi (JX-250)
4. If the JX250 is used with an ADF, the following situation can occur:
After several scans, the scanner moves, after loading a new sheet of
paper, the carriage to the idle position, and then back to the position
used for ADF scans. This happens for <I>every</I> scan, in contrast to the
calibration, which is done after 10 scans. (For the calibration, the
carriage is also moved to the idle position.) We do not know if this
behavior is caused by the backend, or if it is a bug in the firmware of
the scanner.
4. If the JX-250 is used with an ADF, the following situation can oc-
cur: After several scans, the scanner moves, after loading a new sheet
of paper, the carriage to the idle position, and then back to the posi-
tion used for ADF scans. This happens for <I>every</I> scan, in contrast to
the calibration, which is done after 10 scans. (For the calibration,
the carriage is also moved to the idle position.) We do not know if
this behavior is caused by the backend, or if it is a bug in the
firmware of the scanner.
5. Usage of a transparency adapter (film scan unit) is supported, but
not tested.
@ -335,10 +335,10 @@
</PRE>
<H2>CREDITS</H2><PRE>
The Sharp backend is based on the Canon backend written by Helmut Koe-
berle
berle.
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
berger-Tang, Andreas Czechanowski and Andreas Bolsch.
11 Jul 2008 <B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B>
</PRE>

8
man/sane-sm3600.5.html
Wyświetl plik

@ -40,8 +40,8 @@
</PRE>
<H2>FRONTEND OPTIONS</H2><PRE>
This backend dynamically enables the options for the frontend, that are
supported by the scanner dependent on the scanning-mode and other
options. Unsupported options are disabled.
supported by the scanner dependent on the scanning-mode and other op-
tions. Unsupported options are disabled.
The following options are supported by the <B>sane-sm3600</B> backend: Color,
grayscale, halftone and lineart scans. Also contrast, brightness, and
@ -71,8 +71,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_SM3600</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 en-
vironment 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. To see error messages on stderr
set <B>SANE_DEBUG_SM3600</B> to 1.

8
man/sane-sm3840.5.html
Wyświetl plik

@ -21,8 +21,8 @@
backend that provides access to some Microtek scanners with the SCAN08
USB chip.
There exist 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.
There exist backends for Microtek scanners with SCSI command set. Re-
fer 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.
There also exists a Microtek 3600 series driver, see <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B> for
details.
@ -82,8 +82,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_SM3840</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 en-
vironment 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. To see error messages on stderr
set <B>SANE_DEBUG_SM3840</B> to 1.

18
man/sane-snapscan.5.html
Wyświetl plik

@ -79,17 +79,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_SNAPSCAN</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 en-
vironment 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.

6
man/sane-sp15c.5.html
Wyświetl plik

@ -37,9 +37,9 @@
</PRE>
<H2>CONFIGURATION</H2><PRE>
A modest effort has been made to expose the standard options to the
API. This allows frontends such as <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B> to set scanning
region, resolution, bit-depth (and color), and enable the automatic
document feeder.
API. This allows frontends such as <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B> to set scanning re-
gion, resolution, bit-depth (and color), and enable the automatic docu-
ment feeder.
</PRE>

24
man/sane-st400.5.html
Wyświetl plik

@ -95,17 +95,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_ST400</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 en-
vironment 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.
@ -134,9 +134,9 @@
</PRE>
<H2>DEBUG</H2><PRE>
If you encounter a bug please set the environment variable
<B>SANE_DEBUG_ST400</B> to 128 and try to regenerate the problem. Then send me
a report with the log attached.
If you encounter a bug please set the environment variable <B>SANE_DE-</B>
<B>BUG_ST400</B> to 128 and try to regenerate the problem. Then send me a re-
port with the log attached.
If you encounter a SCSI bus error or trimmed and/or displaced images
please also set the environment variable <B>SANE_DEBUG_SANEI_SCSI</B> to 128

22
man/sane-stv680.5.html
Wyświetl plik

@ -19,8 +19,8 @@
<H2>DESCRIPTION</H2><PRE>
The <B>sane-stv680</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to some STV680 cameras. This backend
should be considered <B>beta-quality</B> software! STV680 cameras are sold
under various brands like Aiptek. This backend may or may not support
should be considered <B>beta-quality</B> software! STV680 cameras are sold un-
der various brands like Aiptek. This backend may or may not support
yours.
The cameras that should work with this backend are:
@ -37,8 +37,8 @@
For startup of this backend check that if present the stv680 kernel
module is removed or disabled.
Also before using, enable the backend by editing the
<I>/usr/local/etc/sane.d/dll.conf</I> file, change #stv680 to stv680.
Also before using, enable the backend by editing the <I>/usr/lo-</I>
<I>cal/etc/sane.d/dll.conf</I> file, change #stv680 to stv680.
For problems with the untested cameras, you should contact the author
for that.
@ -60,9 +60,9 @@
scanimage -B -d stv680:libusb:001:002 --batch=out%d.ppm --batch-
count 5 --mode "Color RGB"
If you have any success with a camera not listed here, or if you
observe any strange behavior, please report to the backend maintainer
or to the SANE mailing list.
If you have any success with a camera not listed here, or if you ob-
serve any strange behavior, please report to the backend maintainer or
to the SANE mailing list.
Valid command line options and their syntax can be listed by using:
@ -70,7 +70,7 @@
<B>Scan</B> <B>Mode</B>
<B>--mode</B> selects the basic mode of operation of the webcams valid
<B>--mode</B> selects the basic mode of operation of the webcam's valid
choices.
The read resolution mode is 8 bits, output resolution is 24
@ -98,7 +98,7 @@
<B>--white-level-g</B> <B>-32..+32</B>
Selects what green radiance level should be considered "white",
when scanning some sheets by changing the calibration i value
when scanning some sheets by changing the calibration value
loaded into the scanner. Scale -32 .. 0 .. +32 in steps of 1.
<B>--white-level-b</B> <B>-32..+32</B>
@ -126,8 +126,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_STV680</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 en-
vironment 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.

26
man/sane-tamarack.5.html
Wyświetl plik

@ -33,11 +33,11 @@
<I>special</I>
Where <I>special</I> is the path-name for the special device that corresponds
to a SCSI scanner. The special device name must be a generic SCSI
device or a symlink to such a device. The program <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>
to a SCSI scanner. The special device name must be a generic SCSI de-
vice or a symlink to such a device. The program <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>
helps to find out the correct 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.
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 de-
tails.
</PRE>
@ -62,17 +62,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_TAMARACK</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 en-
vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_TAMARACK=4

12
man/sane-teco1.5.html
Wyświetl plik

@ -58,8 +58,8 @@
line options to programs like <B><A HREF="scanimage.1.html">scanimage(1)</A></B> or through GUI elements in
<B><A HREF="xscanimage.1.html">xscanimage(1)</A></B> or <B><A HREF="xsane.1.html">xsane(1)</A></B>.
If you have any success with a scanner not listed here, or if you
notice any strange behavior, please report to the backend maintainer or
If you have any success with a scanner not listed here, or if you no-
tice any strange behavior, please report to the backend maintainer or
to the SANE mailing list.
Valid command line options and their syntax can be listed by using:
@ -112,8 +112,8 @@
<B>--preview</B>
Requests a preview scan. The resolution used is 22 dpi and the
scan area is the maximum allowed. The scan mode is user
selected. The default is "no".
scan area is the maximum allowed. The scan mode is user se-
lected. The default is "no".
</PRE>
@ -135,8 +135,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_TECO1</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 en-
vironment 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.

63
man/sane-teco2.5.html
Wyświetl plik

@ -55,8 +55,8 @@
line options to programs like <B><A HREF="scanimage.1.html">scanimage(1)</A></B> or through GUI elements in
<B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, <B><A HREF="xsane.1.html">xsane(1)</A></B>, <B><A HREF="quiteinsane.1.html">quiteinsane(1)</A></B> or <B><A HREF="kooka.1.html">kooka(1)</A></B>.
If you have any success with a scanner not listed here, or if you
notice any strange behavior, please report to the backend maintainer or
If you have any success with a scanner not listed here, or if you no-
tice any strange behavior, please report to the backend maintainer or
to the SANE mailing list.
@ -80,17 +80,18 @@
lutions between 1 and 600, in increments of 1, for <I>Lineart</I> and
<I>Gray</I>. For <I>Color</I>, a restricted set of resolutions are available.
<B>Note:</B> All values with ydpi &gt; 300 (300 x 600) or 600 (600 x 1200)
result in a wrong proportion for the scan. The proportion can be
adjusted with the following <B><A HREF="convert.1.html">convert(1)</A></B> command from imagemagick:
<B>Note:</B> All values with vertical resolution in dpi &gt; 300 (300 x
600) or 600 (600 x 1200) result in a wrong proportion for the
scan. The proportion can be adjusted with the following <B>con-</B>
<B><A HREF="vert.1.html">vert(1)</A></B> command from imagemagick:
<I>convert</I> <I>-geometry</I> <I>(dpi/max</I><B>_</B><I>xdpi</I> <I>*</I> <I>100%)x100%</I>
max_xdpi is for the vm3575 constant with 300 dpi e.g. 600dpi
adjust with: convert -geometry 200%x100%
max_xdpi is for the vm3575 constant with 300 dpi e.g. 600dpi ad-
just with: convert -geometry 200%x100%
<B>--preview</B>
requests a preview scan. The resolution used for that scan is 50
dpi (for VM356A and VM6575 75 dpi) and the scan area is the max-
imum allowed. The scan mode is user selected. The default is
imum allowed. The scan mode is user selected. The default is
"no".
<B>Geometry</B> <B>options</B>
@ -98,13 +99,13 @@
<B>-l,</B> <B>-t,</B> <B>-x,</B> <B>-y</B>
Control the scan area: <B>-l</B> sets the top left x coordinate, <B>-t</B> the
top left y coordinate, <B>-x</B> selects the width and <B>-y</B> the height of
the scan area. All parameters are specified in millimeters by
the scan area. All parameters are specified in millimeters by
default.
<B>Enhancement</B> <B>options</B>
<B>--custom-gamma</B> <B>(no</B> <B>custom</B> <B>gamma</B> <B>option</B> <B>for</B> <B>the</B> <B>VM3564</B> <B>and</B> <B>VM356A)</B>
(color mode only) allows the user to specify a gamma table (see
(color mode only) allows the user to specify a gamma table (see
the next 3 parameters).
@ -113,7 +114,7 @@
These options are valid for scan mode <I>Color</I> only.
<B>--red-gamma-table</B>
Can be used to download a user defined gamma table for the red
Can be used to download a user defined gamma table for the red
channel. The table must be 256 bytes long.
<B>--green-gamma-table</B>
@ -121,34 +122,34 @@
channel. The table must be 256 bytes long.
<B>--blue-gamma-table</B>
Can be used to download a user defined gamma table for the blue
Can be used to download a user defined gamma table for the blue
channel. The table must be 256 bytes long.
</PRE>
<H2>OPTIONS ONLY FOR VM3564, VM356A, VM3575 and VM6575</H2><PRE>
These options are only available for VM3564, VM356A, VM3575 and VM6575
These options are only available for VM3564, VM356A, VM3575 and VM6575
models.
<B>--white-level-r</B> <B>0..64</B>
Selects what red radiance level should be considered "white",
when scanning some sheets by changing the calibration value
Selects what red radiance level should be considered "white",
when scanning some sheets by changing the calibration value
loaded into the scanner. Scale 0..64 in steps of 1.
<B>--white-level-g</B> <B>0..64</B>
Selects what green radiance level should be considered "white",
when scanning some sheets by changing the calibration value
Selects what green radiance level should be considered "white",
when scanning some sheets by changing the calibration value
loaded into the scanner. Scale 0..64 in steps of 1.
<B>--white-level-b</B> <B>0..64</B>
Selects what blue radiance level should be considered "white",
when scanning some sheets by changing the calibration value
Selects what blue radiance level should be considered "white",
when scanning some sheets by changing the calibration value
loaded into the scanner. Scale 0..64 in steps of 1.
</PRE>
<H2>CONFIGURATION FILE</H2><PRE>
The configuration file <I>/usr/local/etc/sane.d/teco2.conf</I> supports only
The configuration file <I>/usr/local/etc/sane.d/teco2.conf</I> supports only
one item: the device name to use (eg <I>/dev/scanner</I>).
@ -165,22 +166,22 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_TECO2</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 en-
vironment 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.
<B>SANE_TECO2_CAL_ALGO</B>
Either 0 or 1. Selects the algorithm for the calibration. A
value of 1 seems to give better scans on the VM356A, VM3575.
Feedback on it is welcome. For VM3564, VM356A, VM3575, VM6575
Either 0 or 1. Selects the algorithm for the calibration. A
value of 1 seems to give better scans on the VM356A, VM3575.
Feedback on it is welcome. For VM3564, VM356A, VM3575, VM6575
default 1. For other supported types default 0.
</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-
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.
@ -207,15 +208,15 @@
<H2>CREDITS</H2><PRE>
Thanks to:
Gerard Klaver for his relentless VM3575 testings and contributed a
Gerard Klaver for his relentless VM3575 testings and contributed a
patch to support the VM3564 and VM356A.
Mark Plowman for providing the first SCSI traces from a VM3575.
Andreas Klaedtke for providing the first SCSI traces from a VM6586 and
Andreas Klaedtke for providing the first SCSI traces from a VM6586 and
for his testing, and to Stefan von Dombrowski for his testing.
Nicolas Peyresaubes for providing the first SCSI traces from a VM656A
Nicolas Peyresaubes for providing the first SCSI traces from a VM656A
and for his testing.
Dave Parker for testing the support for the VM6575.

8
man/sane-teco3.5.html
Wyświetl plik

@ -41,8 +41,8 @@
line options to programs like <B><A HREF="scanimage.1.html">scanimage(1)</A></B> or through GUI elements in
<B><A HREF="xscanimage.1.html">xscanimage(1)</A></B> or <B><A HREF="xsane.1.html">xsane(1)</A></B>.
If you have any success with a scanner not listed here, or if you
notice any strange behavior, please report to the backend maintainer or
If you have any success with a scanner not listed here, or if you no-
tice any strange behavior, please report to the backend maintainer or
to the SANE mailing list.
@ -117,8 +117,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_TECO3</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 en-
vironment 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.

103
man/sane-test.5.html
Wyświetl plik

@ -23,12 +23,12 @@
There is no support for real scanners or cameras. However, the backend
simulates scanning and setting options.
The idea is not only to find bugs in frontends but also to show all
capabilities of SANE. Therefore <B>sane-test</B> implements functions and
options that are not (or seldom) found in other backends.
The idea is not only to find bugs in frontends but also to show all ca-
pabilities of SANE. Therefore <B>sane-test</B> implements functions and op-
tions that are not (or seldom) found in other backends.
The backend is commented out in <I>/usr/local/etc/sane.d/dll.conf</I>, so
either the comment character must be removed or the backend must be
The backend is commented out in <I>/usr/local/etc/sane.d/dll.conf</I>, so ei-
ther the comment character must be removed or the backend must be
called explicitly. E.g. <I>scanimage</I> <I>-d</I> <I>test</I> or <I>xscanimage</I> <I>test</I>.
@ -103,8 +103,8 @@
pixels that are "lost" at the end of each line. That means, lines are
padded with unused data.
Option <B>fuzzy-parameters</B> selects that fuzzy (inexact) parameters are
returned as long as the scan hasn't been started. This option can be
Option <B>fuzzy-parameters</B> selects that fuzzy (inexact) parameters are re-
turned as long as the scan hasn't been started. This option can be
used to test if the frontend uses the parameters it got before the
start of the scan (which it shouldn't).
@ -148,21 +148,20 @@
means the option can't be set by the frontend but by the user (e.g. by
pressing a button at the device).
Option <B>bool-hard-select</B> (3/6) is a bool test option that has hard
select (and advanced) capabilities. That means the option can't be set
by the frontend but by the user (e.g. by pressing a button at the
device) and can't be read by the frontend.
Option <B>bool-hard-select</B> (3/6) is a bool test option that has hard se-
lect (and advanced) capabilities. That means the option can't be set
by the frontend but by the user (e.g. by pressing a button at the de-
vice) and can't be read by the frontend.
Option <B>bool-soft-detect</B> (4/6) is a bool test option that has soft
detect (and advanced) capabilities. That means the option is read-
only.
Option <B>bool-soft-detect</B> (4/6) is a bool test option that has soft de-
tect (and advanced) capabilities. That means the option is read-only.
Option <B>bool-soft-select-soft-detect-emulated</B> (5/6) is a Bool test
option that has soft select, soft detect, and emulated (and advanced)
capabilities.
Option <B>bool-soft-select-soft-detect-emulated</B> (5/6) is a Bool test op-
tion that has soft select, soft detect, and emulated (and advanced) ca-
pabilities.
Option <B>bool-soft-select-soft-detect-auto</B> (6/6) is a Bool test option
that has soft select, soft detect, and automatic (and advanced) capa-
Option <B>bool-soft-select-soft-detect-auto</B> (6/6) is a Bool test option
that has soft select, soft detect, and automatic (and advanced) capa-
bilities. This option can be automatically set by the backend.
@ -170,41 +169,41 @@
<H2>INT TEST OPTIONS</H2><PRE>
There are 7 int test options in total.
Option <B>int</B> (1/7) is an int test option with no unit and no constraint
Option <B>int</B> (1/7) is an int test option with no unit and no constraint
set.
Option <B>int-constraint-range</B> (2/7) is an int test option with unit pixel
and constraint range set. Minimum is 4, maximum 192, and quant is 2.
Option <B>int-constraint-word-list</B> (3/7) is an int test option with unit
Option <B>int-constraint-word-list</B> (3/7) is an int test option with unit
bits and constraint word list set.
Option <B>int-constraint-array</B> (4/7) is an int test option with unit mm
Option <B>int-constraint-array</B> (4/7) is an int test option with unit mm
and using an array without constraints.
Option <B>int-constraint-array-constraint-range</B> (5/7) is an int test
option with unit mm and using an array with a range constraint. Mini-
mum is 4, maximum 192, and quant is 2.
Option <B>int-constraint-array-constraint-range</B> (5/7) is an int test op-
tion with unit mm and using an array with a range constraint. Minimum
is 4, maximum 192, and quant is 2.
Option <B>int-constraint-array-constraint-word-list</B> (6/7) is an int test
option with unit percent and using an array a word list constraint.
Option <B>int-constraint-array-constraint-word-list</B> (6/7) is an int test
option with unit percent and using an array or word list constraint.
Option <B>int-inexact</B> (7/7) is an int test option that increments the
requested value and returns flag SANE_INFO_INEXACT.
Option <B>int-inexact</B> (7/7) is an int test option that increments the re-
quested value and returns flag SANE_INFO_INEXACT.
</PRE>
<H2>FIXED TEST OPTIONS</H2><PRE>
There are 3 fixed test options in total.
Option <B>fixed</B> (1/3) is a fixed test option with no unit and no con-
Option <B>fixed</B> (1/3) is a fixed test option with no unit and no con-
straint set.
Option <B>fixed-constraint-range</B> (2/3) is a fixed test option with unit
microsecond and constraint range set. Minimum is -42.17, maximum
Option <B>fixed-constraint-range</B> (2/3) is a fixed test option with unit
microsecond and constraint range set. Minimum is -42.17, maximum
32767.9999, and quant is 2.0.
Option <B>fixed-constraint-word-list</B> (3/3) is a Fixed test option with no
Option <B>fixed-constraint-word-list</B> (3/3) is a fixed test option with no
unit and constraint word list set.
@ -229,15 +228,15 @@
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/test.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below). The initial values of most of the basic
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below). The initial values of most of the basic
SANE options can be configured in this file. A template contain-
ing all the default values is provided together with this back-
end. One of the more interesting values may be <B>num-</B>
<B>ber_of_devices</B>. It can be used to check the frontend's ability
to show a long list of devices. The config values concerning
resolution and geometry can be useful to test the handling of
big file sizes.
ing all the default values is provided together with this back-
end. One of the more interesting values may be <B>number_of_de-</B>
<B>vices</B>. It can be used to check the frontend's ability to show a
long list of devices. The config values concerning resolution
and geometry can be useful to test the handling of big file
sizes.
<I>/usr/local/lib/sane/libsane-test.a</I>
The static library implementing this backend.
@ -253,19 +252,19 @@
This environment variable specifies the list of directories that
may contain the configuration file. On *NIX systems, the direc-
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
arated 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 <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_TEST</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 en-
vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_TEST=4

32
man/sane-u12.5.html
Wyświetl plik

@ -108,17 +108,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_U12</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 en-
vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_U12=10
@ -136,24 +136,24 @@
Please send any information and bug-reports to:
<B>SANE</B> <B>Mailing</B> <B>List</B>
Additional info and hints can be obtained from our
Mailing-List archive at:
<I>http://www.sane-project.org/mailing-lists.html</I>
Additional info and hints can be obtained from our mailing-List archive
at: <I>http://www.sane-project.org/mailing-lists.html</I>.
To obtain debug messages from the backend, please set the environment-
variable <B>SANE_DEBUG_U12</B> before calling your favorite scan-frontend
(i.e. <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>), i.e.:
To obtain debug messages from the backend, please set the environment-
variable <B>SANE_DEBUG_U12</B> before calling your favorite SANE frontend
(e.g. <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>):
<I>export</I> <I>SANE</I><B>_</B><I>DEBUG</I><B>_</B><I>U12=20</I> <I>;</I> <I>xscanimage</I>
The value controls the verbosity of the backend.
</PRE>
<H2>KNOWN BUGS & RESTRICTIONS</H2><PRE>
* The driver is in alpha state, so please don't expect too much!!!
* When using libusb, it might be, that the backend hangs. In that
* When using libusb, it might be, that the backend hangs. In that
case, reconnect the scanner.
14 Jul 2008 <B><A HREF="sane-u12.5.html">sane-u12(5)</A></B>

69
man/sane-umax.5.html
Wyświetl plik

@ -34,8 +34,8 @@
</PRE>
<H2>CONFIGURATION</H2><PRE>
The configuration file for this backend resides in
<I>/usr/local/etc/sane.d/umax.conf</I>.
The configuration file for this backend resides in <I>/usr/lo-</I>
<I>cal/etc/sane.d/umax.conf</I>.
Its contents is a list of device names that correspond to UMAX and UMAX
compatible scanners. Empty lines and lines starting with a hash mark
@ -81,17 +81,16 @@
default min = 32768, max = 131072
Especially the minimum value is very important. If this value
is set too small the backend is not able to send gamma tables to
the scanner or to do a correct color calibration. This may
result in strange color effects. If the minimum value is set too
the scanner or to do a correct color calibration. This may re-
sult in strange color effects. If the minimum value is set too
large then the backend is not able to allocate the requested
SCSI buffer size and aborts with out of memory error. The
default is 32KB, for some scanners it should be increased to
64KB.
SCSI buffer size and aborts with out of memory error. The de-
fault is 32KB, for some scanners it should be increased to 64KB.
scan-lines, preview-lines:
values: 1-65535
default: scan-lines = 40, preview-lines = 10
define the maximum number of lines that are scanned into one
define the maximum number of lines that are scanned into one
buffer
force-preview-bit-rgb:
@ -103,8 +102,8 @@
values: -1 = auto, 0 = disabled, 1 = enabled
default = -1
Dangerous options, needed for some scanners.
Do not change these options unless you really know what you are
doing otherwise you may destroy your scanner with invalid val-
Do not change these options unless you really know what you are
doing otherwise you may destroy your scanner with invalid val-
ues.
calibration-full-ccd:
@ -117,67 +116,67 @@
add an offset to the calculated width for image/ccd
calibration-bytes-pixel:
values: -1 = disabled, 0 = not set, 1 = 1 byte/pixel, 2 = 2
values: -1 = disabled, 0 = not set, 1 = 1 byte/pixel, 2 = 2
bytes/pixel
use # bytes per pixel for calibration
exposure-time-rgb-bind:
values: -1 = automatically set by driver - if known, 0 = dis-
values: -1 = automatically set by driver - if known, 0 = dis-
abled (own selection for red, green and blue), 1 = enabled (same
values for red, green and blue)
invert-shading-data:
values: -1 = automatically set by driver - if known, 0 = dis-
values: -1 = automatically set by driver - if known, 0 = dis-
abled, 1 = enabled
default = -1
invert shading data before sending it back to the scanner
lamp-control-available:
values: 0 = automatically set by driver - if known, 1 = avail-
values: 0 = automatically set by driver - if known, 1 = avail-
able
default = 0
gamma-lsb-padded:
values: -1 = automatically set by driver - if known, 0 = gamma
values: -1 = automatically set by driver - if known, 0 = gamma
data is msb padded, 1 = gamma data is lsb padded
default = -1
handle-bad-sense-error:
values: 0 = handle as device busy, 1 = handle as ok, 2 = handle
values: 0 = handle as device busy, 1 = handle as ok, 2 = handle
as i/o error, 3 = ignore bad error code - continue sense handler
default = 0
scsi-maxqueue:
values: 1..# (maximum defined at compile time)
default = 2
most SCSI drivers allow internal command queueing with a depth
of 2 commands. In most cases it does not improve anything when
you increase this value. When your SCSI driver does not support
most SCSI drivers allow internal command queueing with a depth
of 2 commands. In most cases it does not improve anything when
you increase this value. When your SCSI driver does not support
any command queueing you can try to set this value to 1.
The special device name must be a generic SCSI device or a symlink to
such a device. To find out to which device your scanner is assigned
and how you have to set the permissions of that device, have a look at
The special device name must be a generic SCSI device or a symlink to
such a device. To find out to which device your scanner is assigned
and how you have to set the permissions of that device, have a look at
<B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>.
</PRE>
<H2>SCSI ADAPTER TIPS</H2><PRE>
The ISA-SCSI-adapters that are shipped with some UMAX-scanners are not
supported very well by Linux (I suggest not to use it), the PCI-SCSI-
The ISA-SCSI-adapters that are shipped with some UMAX-scanners are not
supported very well by Linux (I suggest not to use it), the PCI-SCSI-
adapters that come with some UMAX-scanners are not supported at all (as
far as I know). On other platforms these SCSI-adapters are not sup-
ported. So you typically need to purchase another SCSI-adapter that is
supported by your platform. See the relevant hardware FAQs and HOWTOs
far as I know). On other platforms these SCSI-adapters are not sup-
ported. So you typically need to purchase another SCSI-adapter that is
supported by your platform. See the relevant hardware FAQs and HOWTOs
for your platform for more information.
The UMAX-scanners do block the SCSI-bus for a few seconds while scan-
ning. It is not necessary to connect the scanner to its own SCSI-
adapter. But if you need short response time for your SCSI-harddisk
(e.g. if your computer is a file-server) or other SCSI devices, I sug-
The UMAX-scanners do block the SCSI-bus for a few seconds while scan-
ning. It is not necessary to connect the scanner to its own SCSI-
adapter. But if you need short response time for your SCSI-harddisk
(e.g. if your computer is a file-server) or other SCSI devices, I sug-
gest you use an own SCSI-adapter for your UMAX-scanner.
If you have any problems with your UMAX scanner, check your SCSI chain
If you have any problems with your UMAX scanner, check your SCSI chain
(cable length, termination, ...).
See also: <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>
@ -199,9 +198,9 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_UMAX</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 en-
vironment 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. <B>SANE_DEBUG_UMAX</B> values:
Number Remark

14
man/sane-umax1220u.5.html
Wyświetl plik

@ -39,8 +39,8 @@
for this backend resides in <I>/usr/local/etc/sane.d/umax1220u.conf</I>.
Its content is a list of device names that correspond to UMAX Astra
scanners. Empty lines and lines starting with a hash mark (#) are
ignored. A sample configuration file is shown below:
scanners. Empty lines and lines starting with a hash mark (#) are ig-
nored. A sample configuration file is shown below:
#usb vendor product
usb 0x1606 0x0010
@ -68,8 +68,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_UMAX1220U</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 en-
vironment 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:
@ -99,9 +99,9 @@
There is no way to cancel a scan, since the driver ignores <B>sane_can-</B>
<B>cel</B>().
If you try scanning an image which is too small, you will get I/O
errors. Be sure to adjust the scan area before doing a scan, since by
default, the scan area is zero.
If you try scanning an image which is too small, you will get I/O er-
rors. Be sure to adjust the scan area before doing a scan, since by de-
fault, the scan area is zero.
</PRE>

50
man/sane-umax_pp.5.html
Wyświetl plik

@ -57,11 +57,11 @@
Note that if you don't use the ppdev character device, the backend
needs to run as root. To allow user access to the scanner run the back-
end through the network interface (See <B><A HREF="saned.8.html">saned(8)</A></B> and <B><A HREF="sane-net.5.html">sane-net(5)</A></B>). A
more relaxed solution (security wise) is to add suid bit to the fron-
tend (See <B><A HREF="chmod.1.html">chmod(1)</A></B>). The backend drop root privileges as soon as it
can, right after gaining direct access to IO ports, which lessen risks
when being root.
end through the network interface (see <B><A HREF="saned.8.html">saned(8)</A></B> and <B><A HREF="sane-net.5.html">sane-net(5)</A></B>). A
more relaxed solution (security wise) is to add suid bit to the front-
end (see <B><A HREF="chmod.1.html">chmod(1)</A></B>). The backend drops root privileges as soon as it
can, right after gaining direct access to I/O ports, which lessen risks
of being root.
</PRE>
@ -70,7 +70,7 @@
<I>port</I> <I>value</I>
Where <B>value</B> is :
Where <B>value</B> is:
auto autodetect all parallel ports and probe them for scanner
@ -89,8 +89,8 @@
<I>/dev/parport2</I>, ...
0x378 does direct hardware access on the given address. Usual
values are 0x378, 0x278, 0x3BC In this case, you have to
run the scanner as root (*BSD and Linux), or with
values are 0x378, 0x278, 0x3BC. In this case, you have
to run the backend as root (*BSD and Linux), or with
'IOPL=yes' on OS/2
<B>NOTE:</B> in all cases, you must have sufficient privileges to get access
@ -124,7 +124,7 @@
in the frontend, the backend does automatic gain calibration, and do
not use user provided values.
Options <B>red-offset</B> , <B>green-offset</B> and <B>blue-offset</B> allow you to adjust
Options <B>red-offset</B>, <B>green-offset</B> and <B>blue-offset</B> allow you to adjust
the offset of your scanner for the given color. Values range from 0
(lowest offset) to 15 (highest).
@ -139,9 +139,9 @@
aware that it will prevent scanner model autodetection.
Option <B>buffer</B> allows you to change the size of the scan buffer. The
size must be specified in bytes. The default value is 2 megabytes.
Decreasing this value will improve the smoothness of progress bar in
the frontend, but will stall the scan more often.
size must be specified in bytes. The default value is 2 megabytes. De-
creasing this value will improve the smoothness of progress bar in the
frontend, but will stall the scan more often.
</PRE>
@ -166,17 +166,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_UMAX_PP</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
If the library was compiled with debug support enabled, this en-
vironment 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.
@ -236,10 +236,10 @@
<I>the</I> <I>backend</I> <I>version</I> <I>and</I> <I>your</I> <I>scanner</I> <I>hardware</I>
Run <I>SANE</I><B>_</B><I>DEBUG</I><B>_</B><I>UMAX</I><B>_</B><I>PP=255</I> <I>scanimage</I> <I>-L</I> <I>2&gt;log</I> as root. If you
don't get any output from the <B>sane-umax_pp</B> backend, make sure a
line "umax_pp" is included into your
<I>/usr/local/etc/sane.d/dll.conf</I> file. If your scanner isn't
detected, make sure you've defined the right port address, or
the correct device in your <I>umax</I><B>_</B><I>pp.conf</I> file.
line "umax_pp" is included into your <I>/usr/lo-</I>
<I>cal/etc/sane.d/dll.conf</I> file. If your scanner isn't detected,
make sure you've defined the right port address, or the correct
device in your <I>umax</I><B>_</B><I>pp.conf</I> file.
<I>the</I> <I>name</I> <I>of</I> <I>your</I> <I>scanner/vendor</I>
also a worthy information. Please also include the optical reso-

44
man/sane-usb.5.html
Wyświetl plik

@ -18,8 +18,8 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
This manual page contains information on how to access scanners with a
USB interface. It focuses on two main topics: getting the scanner
detected by the operating system kernel and using it with SANE.
USB interface. It focuses on two main topics: getting the scanner de-
tected by the operating system kernel and using it with SANE.
This page applies to USB most backends and scanners, as they use the
generic sanei_usb interface. However, there is one exception: USB Scan-
@ -30,16 +30,16 @@
</PRE>
<H2>QUICK START</H2><PRE>
This is a short HOWTO-like section. For the full details, read the fol-
lowing sections. The goal of this section is to get the scanner
detected by <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>.
lowing sections. The goal of this section is to get the scanner de-
tected by <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>.
Run <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>. If it lists your scanner with the correct
vendor and product ids, you are done. See section <B>SANE</B> <B>ISSUES</B> for
details on how to go on.
vendor and product ids, you are done. See section <B>SANE</B> <B>ISSUES</B> for de-
tails on how to go on.
<B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B> doesn't list your scanner? Does it work as root?
If yes, there is a permission issue. See the <B>LIBUSB</B> section for
details.
If yes, there is a permission issue. See the <B>LIBUSB</B> section for de-
tails.
Nothing is found even as root? Check that your kernel supports USB and
that libusb is installed (see section <B>LIBUSB</B>).
@ -67,7 +67,7 @@
new kernel. For Linux, your kernel needs support for the USB filesystem
(usbfs). For kernels older than 2.4.19, replace "usbfs" with "usbdevfs"
because the name has changed. This filesystem must be mounted. That's
done automatically at boot time, if /etc/fstab contains a line like
done automatically at boot time, if <I>/etc/fstab</I> contains a line like
this:
none /proc/bus/usb usbfs defaults 0 0
@ -84,12 +84,12 @@
Usually <B><A HREF="udev.7.html">udev(7)</A></B> or for older distributions the hotplug utilities are
used, which support dynamic setting of access permissions. SANE comes
with udev and hotplug scripts in the directory <I>tools/udev</I> and
<I>tools/hotplug</I>. They can be used for setting permissions, see
<I>/usr/local/share/doc/sane-backends/README.linux</I>, <I>tools/README</I> and the
<I>README</I> in the <I>tools/hotplug</I> directory for more details.
<I>tools/hotplug</I>. They can be used for setting permissions, see <I>/usr/lo-</I>
<I>cal/share/doc/sane-backends/README.linux</I>, <I>tools/README</I> and the <I>README</I>
in the <I>tools/hotplug</I> directory for more details.
For the <B>BSDs</B>, the device files used by libusb are named <I>/dev/ugen*</I>.
Use chmod to apply appropriate permissions.
Use <B><A HREF="chmod.1.html">chmod(1)</A></B> to apply appropriate permissions.
</PRE>
@ -135,12 +135,12 @@
</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
subsystem. E.g., a value of 128 requests all debug output to be
If the library was compiled with debug support enabled, this en-
vironment variable controls the debug level for the USB I/O sub-
system. 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: <I>export</I>
<I>SANE</I><B>_</B><I>DEBUG</I><B>_</B><I>SANEI</I><B>_</B><I>USB=4</I>.
enable libusb debugging (if available). Example: <I>export</I> <I>SANE</I><B>_</B><I>DE-</I>
<I>BUG</I><B>_</B><I>SANEI</I><B>_</B><I>USB=4</I>.
<B>SANE_USB_WORKAROUND</B>
If your scanner does not work when plugged into a USB3 port, try
@ -148,6 +148,14 @@
may work around issues which happen with particular kernel ver-
sions. Example: <I>export</I> <I>SANE</I><B>_</B><I>USB</I><B>_</B><I>WORKAROUND=1.</I>
<B>SANE_XEROX_USB_HALT_WORKAROUND</B>
If your old (pre-2010) Xerox / Samsung / HP scanner is detected
only once and subsequent usage requires replugging the cable,
try setting the environment variable <B>SANE_XEROX_USB_HALT_WORK-</B>
<B>AROUND</B> to 1. This may work around issues which happen with par-
ticular USB controllers. Example: <I>export</I> <I>SANE</I><B>_</B><I>XE-</I>
<I>ROX</I><B>_</B><I>USB</I><B>_</B><I>HALT</I><B>_</B><I>WORKAROUND=1.</I>
</PRE>
<H2>SEE ALSO</H2><PRE>

22
man/sane-v4l.5.html
Wyświetl plik

@ -71,17 +71,17 @@
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
first, the current working directory (".") and then in <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
<B>SANE_DEBUG_V4L</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 en-
vironment 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.
@ -95,8 +95,8 @@
<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: <I>sane-devel@alioth-</I>
<I>lists.debian.net</I>. You must be subscribed to the list to send mail. See
Send bug reports to the SANE mailing list: <I>sane-devel@alioth-lists.de-</I>
<I>bian.net</I>. You must be subscribed to the list to send mail. See
<I>http://www.sane-project.org/mailing-lists.html</I> for details.

4
man/sane-xerox_mfp.5.html
Wyświetl plik

@ -54,8 +54,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_XEROX_MFP</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 en-
vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_XEROX_MFP=4

339
man/sane.7.html
Wyświetl plik

@ -44,8 +44,8 @@
</PRE>
<H2>SOFTWARE PACKAGES</H2><PRE>
The package <B>sane-backends</B> contains backends, documentation, networking
support, and the command line frontend <B><A HREF="scanimage.1.html">scanimage(1)</A></B>. The frontends
<B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, <B><A HREF="xcam.1.html">xcam(1)</A></B>, and <B><A HREF="scanadf.1.html">scanadf(1)</A></B> are included in the package
support, and the command line frontend <B><A HREF="scanimage.1.html">scanimage(1)</A></B>. The frontends <B>xs-</B>
<B><A HREF="canimage.1.html">canimage(1)</A></B>, <B><A HREF="xcam.1.html">xcam(1)</A></B>, and <B><A HREF="scanadf.1.html">scanadf(1)</A></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.
@ -53,14 +53,14 @@
</PRE>
<H2>GENERAL INFORMATION</H2><PRE>
The following sections provide short descriptions and links to more
information about several aspects of <B>SANE.</B> A name with a number in
The following sections provide short descriptions and links to more in-
formation 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
<I>man</I> <I>5</I> <I>sane-dll</I> will display the page. Entries like
<I>/usr/local/share/doc/sane-backends/README</I> are references to text files
that were copied to the <B>SANE</B> documentation directory
(<I>/usr/local/share/doc/sane-backends/</I>) during installation. Everything
else is a URL to a resource on the web.
<I>man</I> <I>5</I> <I>sane-dll</I> will display the page. Entries like <I>/usr/lo-</I>
<I>cal/share/doc/sane-backends/README</I> are references to text files that
were copied to the <B>SANE</B> documentation directory (<I>/usr/lo-</I>
<I>cal/share/doc/sane-backends/</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
@ -81,8 +81,8 @@
There is a mailing list for the purpose of discussing the SANE stan-
dard and its implementations: sane-devel. Despite its name, the list
is not only intended for developers, but also for users. There are
also some more lists for special topics. However, for users,
sane-devel is the right list. How to subscribe and unsubscribe:
also some more lists for special topics. However, for users, sane-de-
vel is the right list. How to subscribe and unsubscribe:
<I>http://www.sane-project.org/mailing-lists.html</I>.
<B>SANE</B> <B>IRC</B> <B>channel</B>
@ -137,14 +137,14 @@
<B><A HREF="sane-agfafocus.5.html">sane-agfafocus(5)</A></B> for details.
<B>apple</B>
Supports Apple flatbed scanners including the following scanners:
AppleScanner, OneScanner and ColorOneScanner. See <B><A HREF="sane-apple.5.html">sane-apple(5)</A></B> for
details.
Supports Apple flatbed scanners including the following scanners: Ap-
pleScanner, OneScanner and ColorOneScanner. See <B><A HREF="sane-apple.5.html">sane-apple(5)</A></B> for de-
tails.
<B>artec</B>
Supports several Artec/Ultima SCSI flatbed scanners as well as the
BlackWidow BW4800SP and the Plustek 19200S. See <B><A HREF="sane-artec.5.html">sane-artec(5)</A></B> for
details.
BlackWidow BW4800SP and the Plustek 19200S. See <B><A HREF="sane-artec.5.html">sane-artec(5)</A></B> for de-
tails.
<B>artec_eplus48u</B>
Supports the Artec E+ 48U scanner and re-badged models like Tevion MD
@ -158,8 +158,8 @@
<B>avision</B>
Supports several Avision based scanners including the original Avi-
sion scanners (like AV 630, AV 620, ...) as well as the HP ScanJet
53xx and 74xx series, Fujitsu ScanPartner, some Mitsubishi and
Minolta film-scanners. See <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B> for details.
53xx and 74xx series, Fujitsu ScanPartner, some Mitsubishi and Mi-
nolta film-scanners. See <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B> for details.
<B>bh</B>
Supports Bell+Howell Copiscan II series document scanners. See
@ -186,8 +186,8 @@
scanners. See <B><A HREF="sane-canon_pp.5.html">sane-canon_pp(5)</A></B> for details.
<B>cardscan</B>
Support for Corex Cardscan USB scanners. See <B><A HREF="sane-cardscan.5.html">sane-cardscan(5)</A></B> for
details.
Support for Corex Cardscan USB scanners. See <B><A HREF="sane-cardscan.5.html">sane-cardscan(5)</A></B> for de-
tails.
<B>coolscan</B> <B>coolscan2</B> <B>coolscan3</B>
Supports Nikon Coolscan film-scanners. See <B><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B>,
@ -203,12 +203,12 @@
<B>epson2</B>
Newer driver for Epson SCSI, parallel port, network and USB flatbed
scanners (try this before <B>epson</B> which is outdated). See
<B><A HREF="sane-epson2.5.html">sane-epson2(5)</A></B> for details.
scanners (try this before <B>epson</B> which is outdated). See <B>sane-ep-</B>
<B><A HREF="son2.5.html">son2(5)</A></B> for details.
<B>escl</B>
Supports scanners through the eSCL protocol. See <B><A HREF="sane-escl.5.html">sane-escl(5)</A></B> for
details.
Supports scanners through the eSCL protocol. See <B><A HREF="sane-escl.5.html">sane-escl(5)</A></B> for de-
tails.
<B>fujitsu</B>
Supports most Fujitsu SCSI and USB, flatbed and adf scanners. See
@ -259,19 +259,19 @@
for details.
<B>ibm</B>
Supports some IBM and Ricoh SCSI scanners. See <B><A HREF="sane-ibm.5.html">sane-ibm(5)</A></B> for
details.
Supports some IBM and Ricoh SCSI scanners. See <B><A HREF="sane-ibm.5.html">sane-ibm(5)</A></B> for de-
tails.
<B>kodak</B>
Supports some large Kodak scanners. See <B><A HREF="sane-kodak.5.html">sane-kodak(5)</A></B> for details.
<B>kodakaio</B>
Supports Kodak AiO printer/scanners. See <B><A HREF="sane-kodakaio.5.html">sane-kodakaio(5)</A></B> for
details.
Supports Kodak AiO printer/scanners. See <B><A HREF="sane-kodakaio.5.html">sane-kodakaio(5)</A></B> for de-
tails.
<B>kvs1025</B>
Supports Panasonic KV-S102xC scanners. See <B><A HREF="sane-kvs1025.5.html">sane-kvs1025(5)</A></B> for
details.
Supports Panasonic KV-S102xC scanners. See <B><A HREF="sane-kvs1025.5.html">sane-kvs1025(5)</A></B> for de-
tails.
<B>leo</B>
Supports the LEO S3 and the Across FS-1130, which is a re-badged LEO
@ -281,29 +281,33 @@
Supports the Lexmark X1100 series of USB scanners. See <B>sane-lex-</B>
<B><A HREF="mark.5.html">mark(5)</A></B> for details.
<B>lexmark_x2600</B>
Supports the Lexmark X2600 series of USB scanners. See <B>sane-lex-</B>
<B><A HREF="mark_x2600.5.html">mark_x2600(5)</A></B> for details.
<B>ma1509</B>
Supports the Mustek BearPaw 1200F USB flatbed scanner. See
Supports the Mustek BearPaw 1200F USB flatbed scanner. See
<B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B> for details.
<B>magicolor</B>
Supports the KONICA MINOLTA magicolor 1690MF multi-function
Supports the KONICA MINOLTA magicolor 1690MF multi-function
printer/scanner/fax. See <B><A HREF="sane-magicolor.5.html">sane-magicolor(5)</A></B> for details.
<B>matsushita</B>
Supports some Panasonic KVSS high speed scanners. See <B>sane-mat-</B>
Supports some Panasonic KVSS high speed scanners. See <B>sane-mat-</B>
<B><A HREF="sushita.5.html">sushita(5)</A></B> for details.
<B>microtek</B>
Supports "second generation" Microtek scanners with SCSI-1 command
Supports "second generation" Microtek scanners with SCSI-1 command
set. See <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B> for details.
<B>microtek2</B>
Supports some Microtek scanners with a SCSI-2 command set. See
Supports some Microtek scanners with a SCSI-2 command set. See
<B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B> for details.
<B>mustek</B>
Supports most Mustek SCSI flatbed scanners including the Paragon and
ScanExpress series and the 600 II N and 600 II EP (non-SCSI). Some
Supports most Mustek SCSI flatbed scanners including the Paragon and
ScanExpress series and the 600 II N and 600 II EP (non-SCSI). Some
Trust scanners are also supported. See <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B> for details.
<B>mustek_pp</B>
@ -311,16 +315,16 @@
for details.
<B>mustek_usb</B>
Supports some Mustek ScanExpress USB flatbed scanners. See
Supports 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>
Supports scanners using the SQ113 chipset like the Mustek BearPaw
Supports 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>
Supports the NEC PC-IN500/4C SCSI scanner. See <B><A HREF="sane-nec.5.html">sane-nec(5)</A></B> for
details.
Supports the NEC PC-IN500/4C SCSI scanner. See <B><A HREF="sane-nec.5.html">sane-nec(5)</A></B> for de-
tails.
<B>niash</B>
Supports the Agfa Snapscan Touch and the HP ScanJet 3300c, 3400c, and
@ -330,27 +334,27 @@
Supports the Primax PagePartner. See <B><A HREF="sane-p5.5.html">sane-p5(5)</A></B> for details.
<B>pie</B>
Supports Pacific Image Electronics (PIE) and Devcom SCSI flatbed
Supports Pacific Image Electronics (PIE) and Devcom SCSI flatbed
scanners. See <B><A HREF="sane-pie.5.html">sane-pie(5)</A></B> for details.
<B>pixma</B>
Supports Canon PIXMA MP series (multi-function devices), Canon image-
CLASS series (laser devices), Canon MAXIFY series and some Canon
CLASS series (laser devices), Canon MAXIFY series and some Canon
CanoScan series. See <B><A HREF="sane-pixma.5.html">sane-pixma(5)</A></B> for details.
<B>plustek</B>
Supports USB flatbed scanners that use the National Semiconductor
LM983[1/2/3] chipset aka Merlin. Scanners using this LM983x chips
include some models from Plustek, KYE/Genius, Hewlett-Packard,
Mustek, Umax, Epson, and Canon. See <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B> for details.
Supports USB flatbed scanners that use the National Semiconductor
LM983[1/2/3] chipset aka Merlin. Scanners using this LM983x chips in-
clude some models from Plustek, KYE/Genius, Hewlett-Packard, Mustek,
Umax, Epson, and Canon. See <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B> for details.
<B>plustek_pp</B>
Supports Plustek parallel port flatbed scanners using the Plustek
ASIC P96001, P96003, P98001 and P98003, which includes some models
Supports Plustek parallel port flatbed scanners using the Plustek
ASIC P96001, P96003, P98001 and P98003, which includes some models
from Plustek, KYE/Genius, Primax. See <B><A HREF="sane-plustek_pp.5.html">sane-plustek_pp(5)</A></B> for details.
<B>ricoh</B>
Supports the Ricoh flatbed scanners IS50 and IS60. See <B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B>
Supports the Ricoh flatbed scanners IS50 and IS60. See <B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B>
for details.
<B>ricoh2</B>
@ -358,18 +362,18 @@
SP-111SU. See <B><A HREF="sane-ricoh2.5.html">sane-ricoh2(5)</A></B> for details.
<B>s9036</B>
Supports Siemens 9036 flatbed scanners. See <B><A HREF="sane-s9036.5.html">sane-s9036(5)</A></B> for
details.
Supports Siemens 9036 flatbed scanners. See <B><A HREF="sane-s9036.5.html">sane-s9036(5)</A></B> for de-
tails.
<B>sceptre</B>
Supports the Sceptre S1200 flatbed scanner. See <B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B> for
Supports the Sceptre S1200 flatbed scanner. See <B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B> for
details.
<B>sharp</B>
Supports Sharp SCSI scanners. See <B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B> for details.
<B>sm3600</B>
Supports the Microtek ScanMaker 3600 USB scanner. See <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B>
Supports the Microtek ScanMaker 3600 USB scanner. See <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B>
for details.
<B>sm3840</B>
@ -377,11 +381,11 @@
for details.
<B>snapscan</B>
Supports AGFA SnapScan flatbed scanners including some which are
rebadged to other brands. See <B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B> for details.
Supports AGFA SnapScan flatbed scanners including some which are re-
badged to other brands. See <B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B> for details.
<B>sp15c</B>
Supports the Fujitsu FCPA ScanPartner 15C flatbed scanner. See
Supports the Fujitsu FCPA ScanPartner 15C flatbed scanner. See
<B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B> for details.
<B>st400</B>
@ -392,12 +396,12 @@
details.
<B>teco1</B> <B>teco2</B> <B>teco3</B>
Supports some TECO scanners, usually sold under the Relisys, Trust,
Primax, Piotech, Dextra names. See <B><A HREF="sane-teco1.5.html">sane-teco1(5)</A></B>, <B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B> and
Supports some TECO scanners, usually sold under the Relisys, Trust,
Primax, Piotech, Dextra names. See <B><A HREF="sane-teco1.5.html">sane-teco1(5)</A></B>, <B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B> and
<B><A HREF="sane-teco3.5.html">sane-teco3(5)</A></B> for details.
<B>u12</B>
Supports USB flatbed scanners based on Plustek's ASIC 98003 (paral-
Supports USB flatbed scanners based on Plustek's ASIC 98003 (paral-
lel-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.
@ -406,18 +410,18 @@
<B><A HREF="sane-umax.5.html">sane-umax(5)</A></B> for details.
<B>umax_pp</B>
Supports Umax parallel port flatbed scanners and the HP 3200C. See
Supports 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>
Supports the UMAX Astra 1220U (USB) flatbed scanner (and also the
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.
<B>xerox_mfp</B>
Supports multiple Samsung-based Samsung, Xerox, and Dell scanners.
Supports multiple Samsung-based Samsung, Xerox, and Dell scanners.
See <B><A HREF="sane-xerox_mfp.5.html">sane-xerox_mfp(5)</A></B> for details.
Also, have a look at the backend information page at
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/share/doc/sane-backends/PROJECTS</I>.
@ -437,11 +441,11 @@
Supports the Polaroid Digital Microscope Camera. See <B><A HREF="dmc.5.html">dmc(5)</A></B>.
<B>gphoto2</B>
Supports 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
Supports 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 be-
fore all of these cameras will be supported by <B>SANE</B> backend. See
<B><A HREF="gphoto2.5.html">gphoto2(5)</A></B>.
<B>qcam</B>
@ -450,7 +454,7 @@
<B>stv680</B>
Supports webcams with a stv680 chip. See <B><A HREF="stv680.5.html">stv680(5)</A></B> for details.
Also, have a look at the backend information page at
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/share/doc/sane-backends/PROJECTS</I>.
@ -462,17 +466,17 @@
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 <B><A HREF="saned.8.html">saned(8)</A></B> provides access to scanners located
on different computers in connection with the <B><A HREF="sane-net.5.html">sane-net(5)</A></B> backend.
The <B>SANE</B> network daemon <B><A HREF="saned.8.html">saned(8)</A></B> provides access to scanners located
on different computers in connection with the <B><A HREF="sane-net.5.html">sane-net(5)</A></B> backend.
See <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>
Supports 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
Supports 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>.
@ -481,48 +485,48 @@
and various test options. See <B><A HREF="sane-test.5.html">sane-test(5)</A></B>.
<B>v4l</B>
Provides generic access to video cameras and similar equipment using
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
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/share/doc/sane-backends/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> frontends 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> frontends 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.
The <B>SANE</B> standard defines the application programming interface (API)
that is used to communicate between frontends and backends. It can be
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>http://sane-project.gitlab.io/standard/</I> <I>.</I>
There is some more information for programmers in
<I>/usr/local/share/doc/sane-backends/backend-writing.txt</I>. Most of the
internal <B>SANE</B> routines (<B>sanei</B>) are documented using doxygen:
<I>http://www.sane-project.org/sanei/</I>. Before a new backend or frontend
project is started, have a look at <I>/usr/local/share/doc/sane-back-</I>
<I>ends/PROJECTS</I> for projects that are planned or not yet included into
the <B>SANE</B> distribution and at our bug-tracking system:
There is some more information for programmers in <I>/usr/lo-</I>
<I>cal/share/doc/sane-backends/backend-writing.txt</I>. Most of the internal
<B>SANE</B> routines (<B>sanei</B>) are documented using doxygen:
<I>http://www.sane-project.org/sanei/</I>. Before a new backend or frontend
project is started, have a look at <I>/usr/local/share/doc/sane-back-</I>
<I>ends/PROJECTS</I> for projects that are planned or not yet included into
the <B>SANE</B> distribution and at our bug-tracking system:
<I>http://www.http://www.sane-project.org/bugs.html</I>.
There are some links on how to find out about the protocol of a scan-
There are some links on how to find out about the protocol of a scan-
ner: <I>http://www.meier-geinitz.de/sane/misc/develop.html</I>.
If you start writing a backend or frontend or any other part of <B>SANE,</B>
please contact the sane-devel mailing list for coordination so that
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 that
work is not duplicated.
@ -535,7 +539,7 @@
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/share/doc/sane-backends/*</I>
@ -545,118 +549,119 @@
</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><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B> utility. It prints one line for
that it is detected by your operating system. For SCSI and USB scan-
ners, use the <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B> utility. It prints one line for
each scanner it has detected and some comments (#). If <B>sane-find-scan-</B>
<B><A HREF="ner.1.html">ner(1)</A></B> finds your scanner only as root but not as normal user, the per-
missions for the device files are not adjusted correctly. If the scan-
missions for the device files are not adjusted correctly. If the scan-
ner 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
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 backend's manual page for details on
how to set it up.
Is your scanner detected by the operating system but not by <B>SANE</B>? Try
<I>scanimage</I> <I>-L</I>. If the scanner is not found, check that the backend's
Is your scanner detected by the operating system but not by <B>SANE</B>? Try
<I>scanimage</I> <I>-L</I>. If the scanner is not found, check that the backend's
name is mentioned in <I>/usr/local/etc/sane.d/dll.conf</I>. Some backends are
commented out by default. Remove the comment sign for your backend in
this case. Also some backends aren't compiled at all if one of their
prerequisites are missing. Examples include dc210, dc240, canon_pp,
hpsj5s, gphoto2, pint, qcam, v4l, net, sm3600, snapscan, pnm. If you
need one of these backends and it isn't available, read the build
instructions in the <B>README</B> file and the individual manual pages of the
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 it isn't available, read the build in-
structions in the <B>README</B> file and the individual manual pages of the
backends.
Another reason for not being detected by <I>scanimage</I> <I>-L</I> may be a missing
or incorrect configuration in the backend's configuration file. While
<B>SANE</B> tries to automatically find most scanners, some can't be setup
correctly without the intervention of the administrator. Also on some
Another reason for not being detected by <I>scanimage</I> <I>-L</I> may be a missing
or incorrect configuration in the backend's configuration file. While
<B>SANE</B> tries to automatically find most scanners, some can't be setup
correctly without the intervention of the administrator. Also on some
operating systems auto-detection may not work. Check the backend's 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 <I>scanimage</I> <I>-L</I>. The
<B>SANE_DEBUG_DLL</B> messages tell if the <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B> backend was found
and loaded at all. The <B>SANE_DEBUG_MUSTEK</B> messages explain what the
backend is doing while the <B>SANE_DEBUG_SCSI</B> debugging shows the low
level handling. If you can't find out what's going on by checking the
messages carefully, contact the sane-devel mailing list for help (see
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 <I>scanimage</I> <I>-L</I>. The
<B>SANE_DEBUG_DLL</B> messages tell if the <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B> backend was found
and loaded at all. The <B>SANE_DEBUG_MUSTEK</B> messages explain what the
backend is doing while the <B>SANE_DEBUG_SCSI</B> debugging shows the low
level handling. If you can't find out what's going on by checking the
messages carefully, contact the sane-devel mailing list for help (see
REPORTING BUGS below).
Now that your scanner is found by <I>scanimage</I> <I>-L</I>, try to do a scan: <I>scan-</I>
<I>image</I> <I>&gt;image.pnm</I>. This command starts a scan for the default scanner
with default settings. All the available options are listed by running
<I>scanimage</I> <I>--help</I>. 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
<I>image</I> <I>&gt;image.pnm</I>. This command starts a scan for the default scanner
with default settings. All the available options are listed by running
<I>scanimage</I> <I>--help</I>. If scanning aborts with an error message, turn on
debugging as mentioned above. Maybe the configuration file needs some
tuning, e.g. to setup the path to a firmware that is needed by some
scanners. See the backend's manual page for details. If you can't find
out what's wrong, contact sane-devel.
To check that the <B>SANE</B> libraries are installed correctly you can use
the test backend, even if you don't have a scanner or other <B>SANE</B>
device:
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> de-
vice:
scanimage -d test -T
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> <B>(1)</B> works and you want to use one of the
graphical frontends like <B><A HREF="xsane.1.html">xsane(1)</A></B><B>,</B> <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B><B>,</B> <B>or</B> <B>quiteinsane</B> <B>(1)</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> con-
tains <I>/usr/local/lib</I> and does <B>not</B> contain <I>/usr/local/lib/sane</I>. See
also the documentation of the frontends.
graphical frontends like <B><A HREF="xsane.1.html">xsane(1)</A></B><B>,</B> <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B><B>,</B> <B>or</B> <B><A HREF="quiteinsane.1.html">quiteinsane(1)</A></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/lo-</I>
<I>cal/</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> li-
braries. For Linux, make sure that <I>/etc/ld.so.conf</I> contains <I>/usr/lo-</I>
<I>cal/lib</I> and does <B>not</B> contain <I>/usr/local/lib/sane</I>. See also the docu-
mentation 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/share/doc/sane-backends/AUTHORS</I> file or
the backend's manpage. For general discussion about SANE, please use
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/share/doc/sane-backends/AUTHORS</I> file or
the backend's manpage. For general discussion about SANE, please use
the <B>SANE</B> mailing list sane-devel (see <I>http://www.sane-project.org/mail-</I>
<I>ing-lists.html</I> for details).
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="saned.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_dr.5.html">sane-canon_dr(5)</A></B>, <B><A HREF="sane-canon_pp.5.html">sane-canon_pp(5)</A></B>,
<B><A HREF="sane-cardscan.5.html">sane-cardscan(5)</A></B>, <B><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B>, <B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B>,
<B><A HREF="sane-coolscan3.5.html">sane-coolscan3(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-epson2.5.html">sane-epson2(5)</A></B>, <B><A HREF="sane-escl.5.html">sane-escl(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><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-hp3500.5.html">sane-hp3500(5)</A></B>, <B><A HREF="sane-hp3900.5.html">sane-hp3900(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-hpljm1005.5.html">sane-hpljm1005(5)</A></B>, <B><A HREF="sane-ibm.5.html">sane-ibm(5)</A></B>,
<B><A HREF="sane-kodak.5.html">sane-kodak(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><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-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><A HREF="sane-ricoh2.5.html">sane-ricoh2(5)</A></B>, <B><A HREF="sane-s9036.5.html">sane-s9036(5)</A></B>, <B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B>,
<B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B>, <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B>, <B><A HREF="sane-sm3840.5.html">sane-sm3840(5)</A></B>, <B>sane-snap-</B>
<B><A HREF="scan.5.html">scan(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-stv680.5.html">sane-stv680(5)</A></B>, <B>sane-tama-</B>
<B><A HREF="rack.5.html">rack(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="sane-xerox_mfp.5.html">sane-xerox_mfp(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-ag-</B>
<B><A HREF="fafocus.5.html">fafocus(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_dr.5.html">sane-canon_dr(5)</A></B>, <B><A HREF="sane-canon_pp.5.html">sane-canon_pp(5)</A></B>, <B>sane-card-</B>
<B><A HREF="scan.5.html">scan(5)</A></B>, <B><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B>, <B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B>, <B><A HREF="sane-coolscan3.5.html">sane-coolscan3(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-epson2.5.html">sane-epson2(5)</A></B>, <B><A HREF="sane-escl.5.html">sane-escl(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><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-hp3500.5.html">sane-hp3500(5)</A></B>, <B><A HREF="sane-hp3900.5.html">sane-hp3900(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-hpljm1005.5.html">sane-hpljm1005(5)</A></B>, <B><A HREF="sane-ibm.5.html">sane-ibm(5)</A></B>, <B><A HREF="sane-kodak.5.html">sane-kodak(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-lexmark_x2600.5.html">sane-lexmark_x2600(5)</A></B>, <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>,
<B><A HREF="sane-matsushita.5.html">sane-matsushita(5)</A></B>, <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B>, <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B>,
<B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>, <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>,
<B><A HREF="sane-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><A HREF="sane-ricoh2.5.html">sane-ricoh2(5)</A></B>,
<B><A HREF="sane-s9036.5.html">sane-s9036(5)</A></B>, <B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B>,
<B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B>, <B><A HREF="sane-sm3840.5.html">sane-sm3840(5)</A></B>, <B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B>, <B><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-stv680.5.html">sane-stv680(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="sane-xerox_mfp.5.html">sane-xerox_mfp(5)</A></B>
</PRE>

284
man/saned.8.html
Wyświetl plik

@ -18,7 +18,7 @@
</PRE>
<H2>SYNOPSIS</H2><PRE>
<B>saned</B> <B>[</B> <B>-a</B> <I>[</I> <I>username</I> <I>]</I> <B>]</B> <B>[</B> <B>-u</B> <I>username</I> <B>]</B> <B>[</B> <B>-b</B> <I>address</I> <B>]</B> <B>[</B> <B>-p</B> <I>port</I> <B>]</B> <B>[</B>
<B>-l</B> <B>]</B> <B>[</B> <B>-D</B> <B>]</B> <B>[</B> <B>-o</B> <B>]</B> <B>[</B> <B>-d</B> <I>n</I> <B>]</B> <B>[</B> <B>-e</B> <B>]</B> <B>[</B> <B>-h</B> <B>]</B>
<B>-l</B> <B>]</B> <B>[</B> <B>-D</B> <B>]</B> <B>[</B> <B>-o</B> <B>]</B> <B>[</B> <B>-d</B> <I>n</I> <B>]</B> <B>[</B> <B>-e</B> <B>]</B> <B>[</B> <B>-h</B> <B>]</B> <B>[</B> <B>-B</B> <I>buffer-size</I> <B>]</B>
</PRE>
@ -51,8 +51,8 @@
<B>-l</B>, <B>--listen</B>
requests that <B>saned</B> run in standalone daemon mode. In this
mode, <B>saned</B> will listen for incoming client connections;
<B><A HREF="inetd.8.html">inetd(8)</A></B> is not required for <B>saned</B> operations in this mode.
mode, <B>saned</B> will listen for incoming client connections; <B>in-</B>
<B><A HREF="etd.8.html">etd(8)</A></B> is not required for <B>saned</B> operations in this mode.
<B>-D</B>, <B>--daemonize</B>
will request <B>saned</B> to detach from the console and run in the
@ -64,58 +64,52 @@
<B>-d</B> <I>n</I>, <B>--debug</B>=<I>n</I>
sets the level of <B>saned</B> debug output to <I>n</I>. When compiled with
debugging enabled, this flag may be followed by a number to
request more or less debug info. The larger the number, the
more verbose the debug output. E.g., <B>-d128</B> will request output
of all debug info. A level of 0 produces no output at all. The
debugging enabled, this flag may be followed by a number to re-
quest more or less debug info. The larger the number, the more
verbose the debug output. E.g., <B>-d128</B> will request output of
all debug info. A level of 0 produces no output at all. The
default value is 2.
<B>-e</B>, <B>--stderr</B>
will divert <B>saned</B> debug output to stderr instead of the syslog
default.
<B>-B</B>, <B>--buffer-size=</B><I>buffer-size</I>
specifies the size of the read buffer used for communication
with the backend in KB. Default value is 1MB.
<B>-h</B>, <B>--help</B>
displays a short help message.
If <B>saned</B> is run from other programs such as <B><A HREF="inetd.8.html">inetd(8)</A></B>, <B><A HREF="xinetd.8.html">xinetd(8)</A></B> and
<B><A HREF="systemd.1.html">systemd(1)</A></B>, check that program's documentation on how to pass command-
line options.
</PRE>
<H2>CONFIGURATION</H2><PRE>
First and foremost: <B>saned</B> is not intended to be exposed to the internet
or other non-trusted networks. Make sure that access is limited by tcp-
wrappers and/or a firewall setup. Don't depend only on <B>saned</B>'s own
authentication. Don't run <B>saned</B> as root if it's not necessary. And do
<B>not</B> install <B>saned</B> as setuid root.
The <I>saned.conf</I> configuration file contains both options for the daemon
The <I>saned.conf</I> configuration file contains both options for the daemon
and the access list.
<B>data_portrange</B> = <I>min</I><B>_</B><I>port</I> - <I>max</I><B>_</B><I>port</I>
Specify the port range to use for the data connection. Pick a
port range between 1024 and 65535; don't pick a too large port
range, as it may have performance issues. Use this option if
Specify the port range to use for the data connection. Pick a
port range between 1024 and 65535; don't pick a too large port
range, as it may have performance issues. Use this option if
your <B>saned</B> server is sitting behind a firewall. If that firewall
is a Linux machine, we strongly recommend using the Netfilter
is a Linux machine, we strongly recommend using the Netfilter
<I>nf</I><B>_</B><I>conntrack</I><B>_</B><I>sane</I> module instead.
<B>data_connect_timeout</B> = <I>timeout</I>
Specify the time in milliseconds that <B>saned</B> will wait for a data
connection. Without this option, if the data connection is not
done before the scanner reaches the end of scan, the scanner
will continue to scan past the end and may damage it depending
on the backend. Specify zero to have the old behavior. The
default is 4000ms.
connection. Without this option, if the data connection is not
done before the scanner reaches the end of scan, the scanner
will continue to scan past the end and may damage it depending
on the backend. Specify zero to have the old behavior. The de-
fault is 4000ms.
The access list is a list of host names, IP addresses or IP subnets
(CIDR notation) that are permitted to use local SANE devices. IPv6
addresses must be enclosed in brackets, and should always be specified
in their compressed form. Connections from localhost are always permit-
ted. Empty lines and lines starting with a hash mark (#) are ignored. A
line containing the single character ``+'' is interpreted to match any
hostname. This allows any remote machine to use your scanner and may
The access list is a list of host names, IP addresses or IP subnets
(CIDR notation) that are permitted to use local SANE devices. IPv6 ad-
dresses must be enclosed in brackets, and should always be specified in
their compressed form. Connections from localhost are always permitted.
Empty lines and lines starting with a hash mark (#) are ignored. A line
containing the single character ``+'' is interpreted to match any host-
name. This allows any remote machine to use your scanner and may
present a security risk, so this shouldn't be used unless you know what
you're doing.
@ -131,197 +125,19 @@
[::1]
[2001:db8:185e::42:12]/64
The case of the host names does not matter, so AHost.COM is considered
The case of the host names does not matter, so AHost.COM is considered
identical to ahost.com.
</PRE>
<H2>SERVER DAEMON CONFIGURATION</H2><PRE>
For <B>saned</B> to work properly in its default mode of operation, it is also
necessary to add the appropriate configuration for <B><A HREF="xinetd.8.html">xinetd(8)</A></B>, <B><A HREF="inetd.8.html">inetd(8)</A></B>
or <B><A HREF="systemd.1.html">systemd(1)</A></B> (see below). Note that your <B><A HREF="inetd.8.html">inetd(8)</A></B> must support IPv6
if you want to connect to <B>saned</B> over IPv6; <B><A HREF="xinetd.8.html">xinetd(8)</A></B>, <B><A HREF="openbsd-inetd.8.html">openbsd-inetd(8)</A></B>
and <B><A HREF="systemd.1.html">systemd(1)</A></B> are known to support IPv6, check the documentation for
your <B><A HREF="inetd.8.html">inetd(8)</A></B> daemon.
In the sections below the configuration for <B><A HREF="inetd.8.html">inetd(8)</A></B>, <B><A HREF="xinetd.8.html">xinetd(8)</A></B> and
<B><A HREF="systemd.1.html">systemd(1)</A></B> are described in more detail.
For the configurations below it is necessary to add a line of the fol-
lowing form to <I>/etc/services</I>:
sane-port 6566/tcp # SANE network scanner daemon
The official IANA short name for port 6566 is "sane-port". The older
name "sane" is now deprecated.
</PRE>
<H2>INETD CONFIGURATION</H2><PRE>
It is required to add a single line to the <B><A HREF="inetd.8.html">inetd(8)</A></B> configuration file
<I>(/etc/inetd.conf)</I>
The configuration line normally looks like this:
sane-port stream tcp nowait saned.saned /usr/local/sbin/saned
saned
However, if your system uses <B><A HREF="tcpd.8.html">tcpd(8)</A></B> for additional security screening,
you may want to disable <B>saned</B> access control by putting ``+'' in
<I>saned.conf</I> and use a line of the following form in <I>/etc/inetd.conf</I>
instead:
sane-port stream tcp nowait saned.saned /usr/sbin/tcpd
/usr/local/sbin/saned
Note that both examples assume that there is a <B>saned</B> group and a <B>saned</B>
user. If you follow this example, please make sure that the access
permissions on the special device are set such that <B>saned</B> can access
the scanner (the program generally needs read and write access to scan-
ner devices).
</PRE>
<H2>XINETD CONFIGURATION</H2><PRE>
If <B><A HREF="xinetd.8.html">xinetd(8)</A></B> is installed on your system instead of <B><A HREF="inetd.8.html">inetd(8)</A></B> the fol-
lowing example for <I>/etc/xinetd.conf</I> may be helpful:
# default: off
# description: The sane server accepts requests
# for network access to a local scanner via the
# network.
service sane-port
{
port = 6566
socket_type = stream
wait = no
user = saned
group = saned
server = /usr/local/sbin/saned
}
</PRE>
<H2>SYSTEMD CONFIGURATION</H2><PRE>
<B>saned</B> can be compiled with explicit <B><A HREF="systemd.1.html">systemd(1)</A></B> support. This will allow
logging debugging information to be forwarded to the <B><A HREF="systemd.1.html">systemd(1)</A></B> jour-
nal. The <B><A HREF="systemd.1.html">systemd(1)</A></B> support requires compilation with the systemd-devel
package installed on the system. This is the preferred option.
<B>saned</B> can be used with <B><A HREF="systemd.1.html">systemd(1)</A></B> without the <B><A HREF="systemd.1.html">systemd(1)</A></B> integration
compiled in, but then logging of debug information is not supported.
The <B><A HREF="systemd.1.html">systemd(1)</A></B> configuration is different for the 2 options, so both
are described below.
</PRE>
<H2>Systemd configuration for saned with systemd support compiled in</H2><PRE>
For <B><A HREF="systemd.1.html">systemd(1)</A></B> configuration we need to add 2 configuration files in
<I>/etc/systemd/system</I>.
The first file we need to add here is called <I>saned.socket.</I> It shall
have the following contents:
[Unit]
Description=saned incoming socket
[Socket]
ListenStream=6566
Accept=yes
MaxConnections=1
[Install]
WantedBy=sockets.target
The second file to be added is <I>saned@.service</I> with the following con-
tents:
[Unit]
Description=Scanner Service
Requires=saned.socket
[Service]
ExecStart=/usr/sbin/saned
User=saned
Group=saned
StandardInput=null
StandardOutput=syslog
StandardError=syslog
Environment=SANE_CONFIG_DIR=/usr/local/etc/sane.d
# If you need to debug your configuration uncomment the next line and
# change it as appropriate to set the desired debug options
# Environment=SANE_DEBUG_DLL=255 SANE_DEBUG_BJNP=5
[Install]
Also=saned.socket
You need to set an environment variable for <B>SANE_CONFIG_DIR</B> pointing to
the directory where <B>saned</B> can find its configuration files. You will
have to remove the # on the last line and set the variables for the
desired debugging information if required. Multiple variables can be
set by separating the assignments by spaces as shown in the example
above.
Unlike <B><A HREF="xinetd.8.html">xinetd(8)</A></B> and <B><A HREF="inetd.8.html">inetd(8)</A></B>, <B><A HREF="systemd.1.html">systemd(1)</A></B> allows debugging output from
backends set using <B>SANE_DEBUG_XXX</B> to be captured. See the man-page for
your backend to see what options are supported. With the service unit
as described above, the debugging output is forwarded to the system
log.
</PRE>
<H2>Systemd configuration when saned is compiled without systemd support</H2><PRE>
This configuration will also work when <B>saned</B> is compiled WITH <B>sys-</B>
<B><A HREF="temd.1.html">temd(1)</A></B> integration support, but it does not allow debugging informa-
tion to be logged.
For <B><A HREF="systemd.1.html">systemd(1)</A></B> configuration for <B>saned</B>, we need to add 2 configuration
files in <I>/etc/systemd/system</I>.
The first file we need to add here is called <I>saned.socket.</I> It is iden-
tical to the version for <B><A HREF="systemd.1.html">systemd(1)</A></B> with the support compiled in. It
shall have the following contents:
[Unit]
Description=saned incoming socket
[Socket]
ListenStream=6566
Accept=yes
MaxConnections=1
[Install]
WantedBy=sockets.target
The second file to be added is <I>saned@.service</I>. This one differs from
the version with <B><A HREF="systemd.1.html">systemd(1)</A></B> integration compiled in:
[Unit]
Description=Scanner Service
Requires=saned.socket
[Service]
ExecStart=/usr/sbin/saned
User=saned
Group=saned
StandardInput=socket
Environment=SANE_CONFIG_DIR=/etc/sane.d
[Install]
Also=saned.socket
</PRE>
<H2>FILES</H2><PRE>
<I>/etc/hosts.equiv</I>
The hosts listed in this file are permitted to access all local
SANE devices. Caveat: this file imposes serious security risks
The hosts listed in this file are permitted to access all local
SANE devices. Caveat: this file imposes serious security risks
and its use is not recommended.
<I>/usr/local/etc/sane.d/saned.conf</I>
Contains a list of hosts permitted to access local SANE devices
Contains a list of hosts permitted to access local SANE devices
(see also description of <B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/etc/sane.d/saned.users</I>
@ -329,8 +145,8 @@
user:password:backend
access to the listed backends is restricted. A backend may be
listed multiple times for different user/password combinations.
access to the listed backends is restricted. A backend may be
listed multiple times for different user/password combinations.
The server uses MD5 hashing if supported by the client.
@ -340,15 +156,29 @@
This environment variable specifies the list of directories that
may contain the configuration file. On *NIX systems, the direc-
tories are separated by a colon (`:'), under OS/2, they are sep-
arated 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
<I>/usr/local/etc/sane.d</I>. 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 <I>tmp/config</I>, <I>.</I>, and
<I>/usr/local/etc/sane.d</I> being searched (in this order).
arated 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 <I>/usr/lo-</I>
<I>cal/etc/sane.d</I>. If the value of the environment variable ends
with the directory separator character, then the default direc-
tories are searched after the explicitly specified directories.
For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories <I>tmp/config</I>, <I>.</I>, and <I>/usr/local/etc/sane.d</I> be-
ing searched (in this order).
</PRE>
<H2>NOTES</H2><PRE>
<B>saned</B> does <I>not</I> provide confidentiality when communicating with clients.
If <B>saned</B> is exposed directly on the network, other users may be able to
intercept scanned images, or learn passwords for connecting to <B>saned</B>,
with little effort. Client systems should connect to <B>saned</B> through a
secure tunnel to the server instead.
<B>saned</B> is not a trusted program and should not run with root privileges.
Refer to <I>/usr/local/share/doc/sane-backends/saned/saned.install.md</I> for
details on configuring <B>saned</B> as a service.
</PRE>

166
man/scanimage.1.html
Wyświetl plik

@ -17,24 +17,22 @@
</PRE>
<H2>SYNOPSIS</H2><PRE>
<B>scanimage</B> [<B>-d</B>|<B>--device-name</B> <I>dev</I>] [<B>--format</B> <I>format</I>] [<B>-i</B>|<B>--icc-profile</B>
<I>profile</I>] [<B>-L</B>|<B>--list-devices</B>] [<B>-f</B>|<B>--formatted-device-list</B> <I>format</I>]
[<B>-b</B>|<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>-p</B>|<B>--progress</B>] [<B>-o</B>|<B>--output-file</B> <I>path</I>] [<B>-n</B>|<B>--dont-scan</B>] [<B>-T</B>|<B>--test</B>]
[<B>-A</B>|<B>--all-options</B>] [<B>-h</B>|<B>--help</B>] [<B>-v</B>|<B>--verbose</B>] [<B>-B</B>|<B>--buffer-size</B>
[=<I>size</I>]] [<B>-V</B>|<B>--version</B>] [<I>device-specific-options</I>]
<B>scanimage</B> [<B>-d</B> <I>dev</I>] [<B>--format</B><I>=output-format</I>] [<B>-i</B> <I>profile</I>] [<B>-L</B>] [<B>-f</B> <I>de-</I>
<I>vice-format</I>] [<B>-b</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>-p]</B>
[<B>-o</B> <I>path</I>] [<B>-n</B>] [<B>-T</B>] [<B>-A</B>] [<B>-h</B>] [<B>-v</B>] [<B>-B</B> size<I>]</I> [<B>-V</B>] [<I>device-specific-op-</I>
<I>tions</I>]
</PRE>
<H2>DESCRIPTION</H2><PRE>
<B>scanimage</B> is a command-line interface to control image acquisition
devices such as flatbed scanners or cameras. The device is controlled
<B>scanimage</B> is a command-line interface to control image acquisition de-
vices such as flatbed scanners or cameras. The device is controlled
via command-line options. After command-line processing, <B>scanimage</B>
normally proceeds to acquire an image. The image data is written to
standard output in one of the PNM (portable aNyMaP) formats (PBM for
black-and-white images, PGM for grayscale images, and PPM for color
images), TIFF format (black-and-white, grayscale or color), PNG format,
black-and-white images, PGM for grayscale images, and PPM for color im-
ages), TIFF format (black-and-white, grayscale or color), PNG format,
or JPEG format (compression level 75). <B>scanimage</B> accesses image acqui-
sition devices through the <B>SANE</B> (Scanner Access Now Easy) interface and
can thus support any device for which there exists a <B>SANE</B> backend (try
@ -73,12 +71,13 @@
Often options that are similar in function may be implemented differ-
ently across backends. An example of this difference is <I>--mode</I> <I>Gray</I> and
<I>--mode</I> <I>Grayscale</I>. This may be due to differing backend author prefer-
ences. At other times, options are defined by the scanning device
itself and therefore out of the control of the backend code.
ences. At other times, options are defined by the scanning device it-
self and therefore out of the control of the backend code.
Parameters are separated by a blank from single-character options (e.g.
<B>-d</B> <I>epson</I><B>)</B> and by a "=" from multi-character options (e.g.
<B>--device-name</B>=<I>epson</I><B>).</B>
<B>-d</B> <I>epson</I>) and by a "=" from multi-character options (e.g. <B>--de-</B>
<B>vice-name</B>=<I>epson</I>).
<B>-d</B> <I>dev</I>, <B>--device-name</B>=<I>dev</I>
specifies the device to access and must be followed by a SANE
@ -89,11 +88,11 @@
ment variable <B>SANE_DEFAULT_DEVICE</B>. If this variable is not set,
<B>scanimage</B> will attempt to open the first available device.
<B>--format</B>=<I>format</I>
<B>--format</B>=<I>output-format</I>
selects how image data is written to standard output or the file
specified by the <B>--output-file</B> option. <I>format</I> can be <B>pnm</B>, <B>tiff</B>,
<B>png</B>, or <B>jpeg</B>. If <B>--format</B> is not specified, PNM is written by
default.
specified by the <B>--output-file</B> option. <I>output-format</I> can be
<B>pnm</B>, <B>tiff</B>, <B>png</B>, or <B>jpeg</B>. If <B>--format</B> is not specified, PNM is
written by default.
<B>-i</B> <I>profile</I>, <B>--icc-profile</B>=<I>profile</I>
is used to include an ICC profile into a TIFF file.
@ -109,8 +108,8 @@
to consult your system administrator to find out the names of
such devices.
<B>-f</B> <I>format</I>, <B>--formatted-device-list</B>=<I>format</I>
works similar to <B>--list-devices</B>, but requires a format string.
<B>-f</B> <I>format</I>, <B>--formatted-device-list</B>=<I>device-format</I>
works similarly to <B>--list-devices</B>, but requires a format string.
<B>scanimage</B> replaces the placeholders <B>%d</B> <B>%v</B> <B>%m</B> <B>%t</B> <B>%i</B> <B>%n</B> with the
device name, vendor name, model name, scanner type, an index
number and newline respectively. The command
@ -136,7 +135,6 @@
option. <I>format</I> is given as a printf style string with
one integer parameter.
<B>--batch-start</B>=<I>start</I>
selects the page number to start naming files with. If
this option is not given, the counter will start at 1.
@ -157,7 +155,7 @@
<B>--batch-double</B>
will automatically set the increment to 2. Equivalent to
<B>--batch-increment</B>=2
<B>--batch-increment</B>=2.
<B>--batch-prompt</B>
will ask for pressing RETURN before scanning a page. This
@ -201,118 +199,117 @@
dard output and no scan will be performed.
<B>-v</B>, <B>--verbose</B>
increases the verbosity of the output of <B>scanimage.</B> The option
increases the verbosity of the output of <B>scanimage</B>. The option
may be specified repeatedly, each time increasing the verbosity
level.
<B>-B</B> [<I>size</I>], <B>--buffer-size</B>=[<I>size</I>]
changes input buffer size from the default of 32KB to <I>size</I> KB.
If <I>size</I> is not specified then the buffer is set to 1 MB.
<B>-B</B> [<I>size</I>], <B>--buffer-size</B>=<I>size</I>
changes input buffer size from the default of 1MB to <I>size</I> KB.
<B>-V</B>, <B>--version</B>
requests that <B>scanimage</B> prints the program and package name, the
version number of the <B>SANE</B> distribution that it came with and
the version of the backend that it loads. If more information
about the version numbers of the backends are necessary, the
<B>DEBUG</B> variable for the dll layer can be used. Example:
<I>SANE</I><B>_</B><I>DEBUG</I><B>_</B><I>DLL=3</I> <I>scanimage</I> <I>-L</I> <I>.</I>
version number of the <B>SANE</B> distribution that it came with and
the version of the backend that it loads. If more information
about the version numbers of the backends are necessary, the <B>DE-</B>
<B>BUG</B> variable for the dll layer can be used. Example: <I>SANE</I><B>_</B><I>DE-</I>
<I>BUG</I><B>_</B><I>DLL=3</I> <I>scanimage</I> <I>-L</I>.
As you might imagine, much of the power of <B>scanimage</B> comes from the
As you might imagine, much of the power of <B>scanimage</B> comes from the
fact that it can control any <B>SANE</B> backend. Thus, the exact set of com-
mand-line options depends on the capabilities of the selected device.
To see the options for a device named <I>dev</I>, invoke <B>scanimage</B> via a com-
mand-line options depends on the capabilities of the selected device.
To see the options for a device named <I>dev</I>, invoke <B>scanimage</B> via a com-
mand-line of the form:
scanimage --help --device-name <I>dev</I>
The documentation for the device-specific options printed by <B>--help</B> is
The documentation for the device-specific options printed by <B>--help</B> is
best explained with a few examples:
<B>-l</B> <B>0..218mm</B> <B>[0]</B>
Top-left x position of scan area.
The description above shows that option <B>-l</B> expects an option
The description above shows that option <B>-l</B> expects an option
value in the range from 0 to 218 mm. The value in square brack-
ets indicates that the current option value is 0 mm. Most back-
ends provide similar geometry options for top-left y position
ets indicates that the current option value is 0 mm. Most back-
ends provide similar geometry options for top-left y position
(<B>-t</B>), width (<B>-x</B>) and height of scan-area (-y<B>).</B>
<B>--brightness</B> <B>-100..100%</B> <B>[0]</B>
Controls the brightness of the acquired image.
The description above shows that option <B>--brightness</B> expects an
option value in the range from -100 to 100 percent. The value
in square brackets indicates that the current option value is 0
The description above shows that option <B>--brightness</B> expects an
option value in the range from -100 to 100 percent. The value
in square brackets indicates that the current option value is 0
percent.
<B>--default-enhancements</B>
Set default values for enhancement controls.
The description above shows that option <B>--default-enhancements</B>
The description above shows that option <B>--default-enhancements</B>
has no option value. It should be thought of as having an imme-
diate effect at the point of the command-line at which it
appears. For example, since this option resets the <B>--brightness</B>
option, the option-pair <B>--brightness</B> <B>50</B> <B>--default-enhancements</B>
diate effect at the point of the command-line at which it ap-
pears. For example, since this option resets the <B>--brightness</B>
option, the option-pair <B>--brightness</B> <B>50</B> <B>--default-enhancements</B>
would effectively be a no-op.
<B>--mode</B> <B>Lineart|Gray|Color</B> <B>[Gray]</B>
Selects the scan mode (e.g., lineart or color).
The description above shows that option <B>--mode</B> accepts an argu-
ment that must be one of the strings <B>Lineart</B>, <B>Gray</B>, or <B>Color</B>.
The value in the square bracket indicates that the option is
The description above shows that option <B>--mode</B> accepts an argu-
ment that must be one of the strings <B>Lineart</B>, <B>Gray</B>, or <B>Color</B>.
The value in the square bracket indicates that the option is
currently set to <B>Gray</B>. For convenience, it is legal to abbrevi-
ate the string values as long as they remain unique. Also, the
case of the spelling doesn't matter. For example, option set-
ate the string values as long as they remain unique. Also, the
case of the spelling doesn't matter. For example, option set-
ting <B>--mode</B> <B>col</B> is identical to <B>--mode</B> <B>Color</B>.
<B>--custom-gamma[=(yes|no)]</B> <B>[inactive]</B>
Determines whether a builtin or a custom gamma-table should be
Determines whether a builtin or a custom gamma-table should be
used.
The description above shows that option <B>--custom-gamma</B> expects
The description above shows that option <B>--custom-gamma</B> expects
either no option value, a "yes" string, or a "no" string. Spec-
ifying the option with no value is equivalent to specifying
"yes". The value in square-brackets indicates that the option
is not currently active. That is, attempting to set the option
would result in an error message. The set of available options
typically depends on the settings of other options. For exam-
ple, the <B>--custom-gamma</B> table might be active only when a
ifying the option with no value is equivalent to specifying
"yes". The value in square-brackets indicates that the option
is not currently active. That is, attempting to set the option
would result in an error message. The set of available options
typically depends on the settings of other options. For exam-
ple, the <B>--custom-gamma</B> table might be active only when a
grayscale or color scan-mode has been requested.
Note that the <B>--help</B> option is processed only after all other
options have been processed. This makes it possible to see the
option settings for a particular mode by specifying the appro-
priate mode-options along with the <B>--help</B> option. For example,
Note that the <B>--help</B> option is processed only after all other
options have been processed. This makes it possible to see the
option settings for a particular mode by specifying the appro-
priate mode-options along with the <B>--help</B> option. For example,
the command-line:
<B>scanimage</B> <B>--help</B> <B>--mode</B> <I>color</I>
would print the option settings that are in effect when the
would print the option settings that are in effect when the
color-mode is selected.
<B>--gamma-table</B> <B>0..255,...</B>
Gamma-correction table. In color mode this option equally
affects the red, green, and blue channels simultaneously (i.e.,
it is an intensity gamma table).
Gamma-correction table. In color mode this option equally af-
fects the red, green, and blue channels simultaneously (i.e., it
is an intensity gamma table).
The description above shows that option <B>--gamma-table</B> expects
The description above shows that option <B>--gamma-table</B> expects
zero or more values in the range 0 to 255. For example, a legal
value for this option would be "3,4,5,6,7,8,9,10,11,12". Since
it's cumbersome to specify long vectors in this form, the same
can be expressed by the abbreviated form "[0]3-[9]12". What
this means is that the first vector element is set to 3, the
value for this option would be "3,4,5,6,7,8,9,10,11,12". Since
it's cumbersome to specify long vectors in this form, the same
can be expressed by the abbreviated form "[0]3-[9]12". What
this means is that the first vector element is set to 3, the
9-th element is set to 12 and the values in between are interpo-
lated linearly. Of course, it is possible to specify multiple
such linear segments. For example, "[0]3-[2]3-[6]7,[7]10-[9]6"
is equivalent to "3,3,3,4,5,6,7,10,8,6". The program
<B>gamma4scanimage</B> can be used to generate such gamma tables (see
lated linearly. Of course, it is possible to specify multiple
such linear segments. For example, "[0]3-[2]3-[6]7,[7]10-[9]6"
is equivalent to "3,3,3,4,5,6,7,10,8,6". The program
<B>gamma4scanimage</B> can be used to generate such gamma tables (see
<B><A HREF="gamma4scanimage.1.html">gamma4scanimage(1)</A></B> for details).
<B>--filename</B> <B>&lt;string&gt;</B> <B>[/tmp/input.ppm]</B>
The filename of the image to be loaded.
The description above is an example of an option that takes an
The description above is an example of an option that takes an
arbitrary string value (which happens to be a filename). Again,
the value in brackets show that the option is current set to the
filename <I>/tmp/input.ppm</I>.
@ -327,7 +324,7 @@
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d</I>
This directory holds various configuration files. For details,
This directory holds various configuration files. For details,
please refer to the manual pages listed below.
<I>~/.sane/pass</I>
@ -335,17 +332,16 @@
user:password:resource
<B>scanimage</B> uses this information to answer user authorization
requests automatically. The file must have 0600 permissions or
stricter. You should use this file in conjunction with the
<B>--accept-md5-only</B> option to avoid server-side attacks. The
resource may contain any character but is limited to 127 charac-
ters.
<B>scanimage</B> uses this information to answer user authorization re-
quests automatically. The file must have 0600 permissions or
stricter. You should use this file in conjunction with the <B>--ac-</B>
<B>cept-md5-only</B> option to avoid server-side attacks. The resource
may contain any character but is limited to 127 characters.
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="gamma4scanimage.1.html">gamma4scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, <B><A HREF="xcam.1.html">xcam(1)</A></B><B>,</B> <B><A HREF="xsane.1.html">xsane(1)</A></B><B>,</B>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="gamma4scanimage.1.html">gamma4scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, <B><A HREF="xcam.1.html">xcam(1)</A></B>, <B><A HREF="xsane.1.html">xsane(1)</A></B>,
<B><A HREF="scanadf.1.html">scanadf(1)</A></B>, <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>, <B><A HREF="sane-net.5.html">sane-net(5)</A></B>, <B>sane-"backendname"</B>(5)

21633
sane-backends-1.2.1.html 100644
Wyświetl plik

Plik diff jest za duży Load Diff

440
sane-backends.html
Wyświetl plik

@ -9,7 +9,7 @@
<h1>SANE: Backends (Drivers)</h1>
</div>
<hr>
The following table summarizes the backends/drivers distributed with sane-backends-1.2.1, and the hardware or software they support.
The following table summarizes the backends/drivers distributed with sane-backends-1.3.1, and the hardware or software they support.
<p>This is only a summary!
Please consult the manpages and the author-supplied webpages
for more detailed (and usually important) information
@ -41,14 +41,14 @@ isn't mentioned in this list at all.</p>
</tr>
<tr>
<td align=center><a href="#SCANNERS">Scanners</a></td>
<td align=center><font color="#000000">2725</font></td>
<td align=center><font color="#000000">1779</font></td>
<td align=center><font color="#007000">820</font></td>
<td align=center><font color="#90B000">805</font></td>
<td align=center><font color="#000000">2781</font></td>
<td align=center><font color="#000000">1804</font></td>
<td align=center><font color="#007000">825</font></td>
<td align=center><font color="#90B000">825</font></td>
<td align=center><font color="#FF9000">130</font></td>
<td align=center><font color="#B00000">24</font></td>
<td align=center><font color="#0000B0">469</font></td>
<td align=center><font color="#F00000">477</font></td>
<td align=center><font color="#0000B0">499</font></td>
<td align=center><font color="#F00000">478</font></td>
</tr>
<tr>
<td align=center><a href="#STILL">Still cameras</a></td>
@ -2348,7 +2348,7 @@ Kyocera
</tr>
</table>
<h3><a name="S-CANON-LIDE70">Backend: canon_lide70
(0, <font color="#F00000">NEW!</font>)
(0)
</a></h3>
<p>
<b>Link(s):</b>
@ -3323,7 +3323,7 @@ Sanford
<th align=center>Comment</th>
</tr>
<tr>
<td align=center rowspan=613>
<td align=center rowspan=614>
<a href="http://www.epson.com/">Epson</a>
<td align=center>AL-MX300DN Series</td>
<td align=center>USB</td>
@ -4620,6 +4620,13 @@ Sanford
<td>network interface supported via DFSG non-free iscan-network-nt package<br>all-in-one</td>
</tr>
<tr>
<td align=center>L360 Series</td>
<td align=center>USB</td>
<td align=center>0x04b8/0x08d1</td>
<td align=center><font color="#007000">Complete</font></td>
<td>&nbsp;</td>
</tr>
<tr>
<td align=center>L365 Series</td>
<td align=center>USB</td>
<td align=center>0x04b8/0x08d2</td>
@ -5442,7 +5449,7 @@ Sanford
<td align=center>Perfection 610</td>
<td align=center>USB</td>
<td align=center>0x04b8/0x0103</td>
<td align=center><font color="#FF9000">Basic</font></td>
<td align=center><font color="#007000">Complete</font></td>
<td>overseas version of the GT-6600U</td>
</tr>
<tr>
@ -7632,7 +7639,7 @@ Sanford
<th align=center>Comment</th>
</tr>
<tr>
<td align=center rowspan=69>
<td align=center rowspan=72>
<a href="http://www.epson.com/">Epson</a>
<td align=center>DS-5500</td>
<td align=center>USB</td>
@ -8116,6 +8123,27 @@ Sanford
<td align=center><font color="#007000">Complete</font></td>
<td>&nbsp;</td>
</tr>
<tr>
<td align=center>ES-C220</td>
<td align=center>USB</td>
<td align=center>0x04b8/0x0193</td>
<td align=center><font color="#007000">Complete</font></td>
<td>&nbsp;</td>
</tr>
<tr>
<td align=center>DS-C330</td>
<td align=center>USB</td>
<td align=center>0x04b8/0x018f</td>
<td align=center><font color="#007000">Complete</font></td>
<td>&nbsp;</td>
</tr>
<tr>
<td align=center>DS-C490</td>
<td align=center>USB</td>
<td align=center>0x04b8/0x0191</td>
<td align=center><font color="#007000">Complete</font></td>
<td>&nbsp;</td>
</tr>
</table>
<h3><a name="S-ESCL">Backend: escl
</a></h3>
@ -8491,11 +8519,11 @@ Sanford
</tr>
</table>
<h3><a name="S-FUJITSU">Backend: fujitsu
(139)
(140)
</a></h3>
<p>
<b>Manual page:</b> <a href="man/sane-fujitsu.5.html">sane-fujitsu</a><br>
<b>Comment:</b> Backend updated for SANE release 1.1.2, see sane-fujitsu manpage<br>
<b>Comment:</b> This backend supports most Fujitsu and Ricoh fi-series and similar scanners. See manpage for details.<br>
</p>
<table border=1>
<tr bgcolor=E0E0FF>
@ -9397,6 +9425,190 @@ Sanford
<td align=center><font color="#90B000">Good</font></td>
<td>&nbsp;</td>
</tr>
<tr>
<td align=center rowspan=26>
<a href="http://www.ricoh.com/">Ricoh</a>
<td align=center>fi-70F</td>
<td align=center>USB</td>
<td align=center>0x05ca/0x0308</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>&nbsp;</td>
</tr>
<tr>
<td align=center>fi-400F</td>
<td align=center>USB</td>
<td align=center>0x04c5/0x151e</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>&nbsp;</td>
</tr>
<tr>
<td align=center>fi-800R</td>
<td align=center>USB</td>
<td align=center>0x04c5/0x15fc</td>
<td align=center><font color="#90B000">Good</font></td>
<td>Both feed methods are supported.</td>
</tr>
<tr>
<td align=center>fi-7300NX</td>
<td align=center>USB</td>
<td align=center>0x04c5/0x1575</td>
<td align=center><font color="#90B000">Good</font></td>
<td>Ethernet and WiFi not supported.</td>
</tr>
<tr>
<td align=center>fi-7460</td>
<td align=center>USB</td>
<td align=center>0x04c5/0x14be</td>
<td align=center><font color="#90B000">Good</font></td>
<td>&nbsp;</td>
</tr>
<tr>
<td align=center>fi-7480</td>
<td align=center>USB</td>
<td align=center>0x04c5/0x14b8</td>
<td align=center><font color="#90B000">Good</font></td>
<td>&nbsp;</td>
</tr>
<tr>
<td align=center>fi-7600</td>
<td align=center>USB</td>
<td align=center>0x04c5/0x1521</td>
<td align=center><font color="#90B000">Good</font></td>
<td>&nbsp;</td>
</tr>
<tr>
<td align=center>fi-7700</td>
<td align=center>USB</td>
<td align=center>0x04c5/0x1520</td>
<td align=center><font color="#90B000">Good</font></td>
<td>&nbsp;</td>
</tr>
<tr>
<td align=center>fi-7700S</td>
<td align=center>USB</td>
<td align=center>0x04c5/0x1522</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>&nbsp;</td>
</tr>
<tr>
<td align=center>fi-7800</td>
<td align=center>USB</td>
<td align=center>0x04c5/0x160b</td>
<td align=center><font color="#90B000">Good</font></td>
<td>&nbsp;</td>
</tr>
<tr>
<td align=center>fi-7900</td>
<td align=center>USB</td>
<td align=center>0x04c5/0x160a</td>
<td align=center><font color="#90B000">Good</font></td>
<td>&nbsp;</td>
</tr>
<tr>
<td align=center>fi-8040</td>
<td align=center>USB</td>
<td align=center>0x05ca/0x0307</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>&nbsp;</td>
</tr>
<tr>
<td align=center>fi-8150</td>
<td align=center>USB</td>
<td align=center>0x04c5/0x1601</td>
<td align=center><font color="#90B000">Good</font></td>
<td>Ethernet not supported.</td>
</tr>
<tr>
<td align=center>fi-8150U</td>
<td align=center>USB</td>
<td align=center>0x04c5/0x162d</td>
<td align=center><font color="#90B000">Good</font></td>
<td>&nbsp;</td>
</tr>
<tr>
<td align=center>fi-8170</td>
<td align=center>USB</td>
<td align=center>0x04c5/0x15ff</td>
<td align=center><font color="#90B000">Good</font></td>
<td>Ethernet not supported.</td>
</tr>
<tr>
<td align=center>fi-8190</td>
<td align=center>USB</td>
<td align=center>0x04c5/0x15fd</td>
<td align=center><font color="#90B000">Good</font></td>
<td>Ethernet not supported.</td>
</tr>
<tr>
<td align=center>fi-8250</td>
<td align=center>USB</td>
<td align=center>0x04c5/0x1602</td>
<td align=center><font color="#90B000">Good</font></td>
<td>Ethernet not supported.</td>
</tr>
<tr>
<td align=center>fi-8250U</td>
<td align=center>USB</td>
<td align=center>0x04c5/0x162e</td>
<td align=center><font color="#90B000">Good</font></td>
<td>&nbsp;</td>
</tr>
<tr>
<td align=center>fi-8270</td>
<td align=center>USB</td>
<td align=center>0x04c5/0x1600</td>
<td align=center><font color="#90B000">Good</font></td>
<td>Ethernet not supported.</td>
</tr>
<tr>
<td align=center>fi-8290</td>
<td align=center>USB</td>
<td align=center>0x04c5/0x15fe</td>
<td align=center><font color="#90B000">Good</font></td>
<td>Ethernet not supported.</td>
</tr>
<tr>
<td align=center>N7100</td>
<td align=center>USB Ethernet</td>
<td align=center>0x04c5/0x146f</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>&nbsp;</td>
</tr>
<tr>
<td align=center>ScanSnap iX100</td>
<td align=center>USB WiFi</td>
<td align=center>0x04c5/0x13f4</td>
<td align=center><font color="#90B000">Good</font></td>
<td>WiFi not supported.</td>
</tr>
<tr>
<td align=center>ScanSnap iX1300</td>
<td align=center>USB WiFi</td>
<td align=center>0x04c5/0x162c</td>
<td align=center><font color="#90B000">Good</font></td>
<td>WiFi not supported.</td>
</tr>
<tr>
<td align=center>ScanSnap iX1400</td>
<td align=center>USB</td>
<td align=center>0x04c5/0x1630</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>&nbsp;</td>
</tr>
<tr>
<td align=center>ScanSnap iX1600</td>
<td align=center>USB WiFi</td>
<td align=center>0x04c5/0x1632</td>
<td align=center><font color="#90B000">Good</font></td>
<td>WiFi not supported.</td>
</tr>
<tr>
<td align=center>ScanSnap SV600</td>
<td align=center>USB</td>
<td align=center>0x04c5/0x128e</td>
<td align=center><font color="#F00000">Unsupported</font></td>
<td>Also has a second USB VID 0x13ba. Will require some gymnastics to support.</td>
</tr>
</table>
<h3><a name="S-GENESYS">Backend: genesys
(1.0-63)
@ -9691,7 +9903,7 @@ Sanford
<td>300, 600, 1200 dpi resolutions supported in flatbed scanning mode; 300, 600, 1200, 2400, 4800 dpi resolutions are supported in transparency and infrared transparency scanning modes</td>
</tr>
<tr>
<td align=center>CanoScan 700F</td>
<td align=center>CanoScan LiDE 700F</td>
<td align=center>USB</td>
<td align=center>0x04a9/0x1907</td>
<td align=center><font color="#FF9000">Basic</font></td>
@ -13238,7 +13450,7 @@ Adlib
<th align=center>Comment</th>
</tr>
<tr>
<td align=center rowspan=306>
<td align=center rowspan=330>
<a href="http://www.canon.com/">Canon</a>
<td align=center>PIXMA E400</td>
<td align=center>USB</td>
@ -13373,6 +13585,13 @@ Adlib
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>G2030 series</td>
<td align=center>USB</td>
<td align=center>0x04a9/0x1106</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>PIXMA G2060</td>
<td align=center>USB</td>
<td align=center>0x04a9/0x18c1</td>
@ -13380,6 +13599,13 @@ Adlib
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>G2070 series</td>
<td align=center>USB</td>
<td align=center>0x04a9/0x18f5</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>PIXMA G2100</td>
<td align=center>USB</td>
<td align=center>0x04a9/0x1795</td>
@ -13408,6 +13634,13 @@ Adlib
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>G3030 series</td>
<td align=center>USB</td>
<td align=center>0x04a9/0x1105</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>PIXMA G3060</td>
<td align=center>USB</td>
<td align=center>0x04a9/0x18c3</td>
@ -13415,6 +13648,13 @@ Adlib
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>G3070 series</td>
<td align=center>USB</td>
<td align=center>0x04a9/0x18f4</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>PIXMA G4000 Series</td>
<td align=center>USB WiFi</td>
<td align=center>0x04a9/0x181d</td>
@ -13429,6 +13669,13 @@ Adlib
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>G4070 series</td>
<td align=center>USB</td>
<td align=center>0x04a9/0x18f3</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>PIXMA G4511</td>
<td align=center>USB WiFi</td>
<td align=center>0x04a9/0x183d</td>
@ -13478,13 +13725,48 @@ Adlib
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>PIXMA GX1000 series</td>
<td align=center>USB WiFi</td>
<td align=center>0x04a9/0x110b</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>PIXMA GX2000 series</td>
<td align=center>USB WiFi</td>
<td align=center>0x04a9/0x110d</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>PIXMA GX3000 Series</td>
<td align=center>USB</td>
<td align=center>0x04a9/0x18f1</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>PIXMA GX4000</td>
<td align=center>USB</td>
<td align=center>0x04a9/0x18f2</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>PIXMA GX6000 Series</td>
<td align=center>USB Ethernet WiFi</td>
<td align=center>USB</td>
<td align=center>0x04a9/0x18a6</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>PIXMA GX6500 series</td>
<td align=center>USB WiFi</td>
<td align=center>0x04a9/0x1148</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>PIXMA GX7000</td>
<td align=center>USB</td>
<td align=center>0x04a9/0x18a8</td>
@ -14311,6 +14593,20 @@ Adlib
<td>Flatbed and ADF scan. All resolutions supported (up to 4800DPI)</td>
</tr>
<tr>
<td align=center>TC-20M</td>
<td align=center>USB</td>
<td align=center>0x04a9/0x18fc</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>TC-5200M</td>
<td align=center>USB</td>
<td align=center>0x04a9/0x18ff</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>PIXMA TR4500 Series</td>
<td align=center>USB WiFi</td>
<td align=center>0x04a9/0x1854</td>
@ -14360,6 +14656,13 @@ Adlib
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>PIXMA TR7800 series</td>
<td align=center>USB WiFi</td>
<td align=center>0x04a9/0x1151</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>PIXMA TR8500 Series</td>
<td align=center>USB Ethernet WiFi</td>
<td align=center>0x04a9/0x1823</td>
@ -14577,6 +14880,20 @@ Adlib
<td>All resolutions supported (up to 1200DPI). WiFi not tested by Pixma as yet.</td>
</tr>
<tr>
<td align=center>PIXMA TS6630 series</td>
<td align=center>USB WiFi</td>
<td align=center>0x04a9/0x114e</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>PIXMA TS6730 series</td>
<td align=center>USB WiFi</td>
<td align=center>0x04a9/0x1150</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>PIXMA TS7330 Series</td>
<td align=center>USB WiFi</td>
<td align=center>0x04a9/0x188f</td>
@ -14612,6 +14929,34 @@ Adlib
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>PIXMA TS7600i series</td>
<td align=center>USB WiFi</td>
<td align=center>0x04a9/0x114f</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>PIXMA TS7700 series</td>
<td align=center>USB WiFi</td>
<td align=center>0x04a9/0x110f</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>PIXMA TS7700A series</td>
<td align=center>USB WiFi</td>
<td align=center>0x04a9/0x1111</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>PIXMA TS7700i series</td>
<td align=center>USB WiFi</td>
<td align=center>0x04a9/0x1152</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>PIXMA TS8000 Series</td>
<td align=center>USB WiFi</td>
<td align=center>0x04a9/0x1800</td>
@ -14696,6 +15041,20 @@ Adlib
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>PIXMA TS8630 Series</td>
<td align=center>USB</td>
<td align=center>0x04a9/0x18f8</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>PIXMA TS8700 series</td>
<td align=center>USB WiFi</td>
<td align=center>0x04a9/0x1118</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>PIXMA TS9000 Series</td>
<td align=center>USB WiFi</td>
<td align=center>0x04a9/0x179f</td>
@ -14780,6 +15139,20 @@ Adlib
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>PIXUS XK110 Series</td>
<td align=center>USB WiFi</td>
<td align=center>0x04a9/0x18f9</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>PIXUS XK120 Series</td>
<td align=center>USB WiFi</td>
<td align=center>0x04a9/0x1119</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>PIXUS XK500 Series</td>
<td align=center>USB WiFi</td>
<td align=center>0x04a9/0x18df</td>
@ -14976,6 +15349,13 @@ Adlib
<td>Flatbed and ADF scan. All resolutions supported (up to 600DPI).</td>
</tr>
<tr>
<td align=center>i-SENSYS MF750 Series</td>
<td align=center>USB Ethernet WiFi</td>
<td align=center>0x04a9/0x2885</td>
<td align=center><font color="#0000B0">Untested</font></td>
<td>Testers needed!</td>
</tr>
<tr>
<td align=center>i-SENSYS MF810/820</td>
<td align=center>USB Ethernet</td>
<td align=center>0x04a9/0x27a6</td>
@ -15956,14 +16336,14 @@ BrightScan
<tr>
<td align=center rowspan=2>
<a href="http://www.ricoh.com/">Ricoh</a>
<td align=center>Ricoh IS50</td>
<td align=center>IS50</td>
<td align=center>SCSI</td>
<td align=center>&nbsp;</td>
<td align=center><font color="#FF9000">Basic</font></td>
<td>&nbsp;</td>
</tr>
<tr>
<td align=center>Ricoh IS60</td>
<td align=center>IS60</td>
<td align=center>SCSI</td>
<td align=center>&nbsp;</td>
<td align=center><font color="#FF9000">Basic</font></td>
@ -17170,7 +17550,7 @@ Trust
</tr>
</table>
<h3><a name="S-TEMPLATE">Backend: template
(0.42, <font color="#F00000">NEW!</font>)
(0.42)
</a></h3>
<p>
<b>Link(s):</b>
@ -20638,7 +21018,7 @@ Vantas
<th align=center>Comment</th>
</tr>
<tr>
<td align=center rowspan=7>
<td align=center rowspan=8>
<a href="http://www.office.xerox.com/">Xerox</a>
<td align=center><a href="http://www.office.xerox.com/multifunction-printer/multifunction-under-30ppm/phaser-3200mfp/spec-enus.html">Phaser 3200MFP</a></td>
<td align=center>USB</td>
@ -20689,7 +21069,14 @@ Vantas
<td>&nbsp;</td>
</tr>
<tr>
<td align=center rowspan=2>
<td align=center>WorkCentre 3335</td>
<td align=center>USB</td>
<td align=center>0x0924/0x42e2</td>
<td align=center><font color="#FF9000">Basic</font></td>
<td>When scanning from automatic feeder, only the first page is scanned</td>
</tr>
<tr>
<td align=center rowspan=3>
<a href="http://www.dell.com/">Dell</a>
<td align=center>Dell MFP Laser Printer 1815dn</td>
<td align=center>USB</td>
@ -20705,6 +21092,13 @@ Vantas
<td>&nbsp;</td>
</tr>
<tr>
<td align=center>Dell 1135n</td>
<td align=center>USB Ethernet</td>
<td align=center>0x413c/0x5318</td>
<td align=center><font color="#90B000">Good</font></td>
<td>&nbsp;</td>
</tr>
<tr>
<td align=center rowspan=76>
<a href="http://www.samsung.com">Samsung</a>
<td align=center>X4300 Series</td>
@ -21523,7 +21917,7 @@ Grandtek Scopecam
<b>Comment:</b> Used for debugging frontends. Obsolete, use test backend instead.<br>
</p>
<h3><a name="A-TEMPLATE">Backend: template
(0.42, <font color="#F00000">NEW!</font>)
(0.42)
</a></h3>
<p>
<b>Link(s):</b>
@ -21628,6 +22022,6 @@ Grandtek Scopecam
>Contact</a>
</address>
<font size=-1>
This page was created by sane-desc 3.6 from sane-backends 1.2.1
This page was created by sane-desc 3.6 from sane-backends 1.3.1
</font>
</body> </html>

899
sane-mfgs.html
Wyświetl plik

Plik diff jest za duży Load Diff

1
sane-supported-devices.html
Wyświetl plik

@ -91,6 +91,7 @@
</p>
<p>
SANE version:
<a href="sane-backends-1.2.1.html">1.2.1</a>,
<a href="sane-backends-1.1.1.html">1.1.1</a>,
<a href="sane-backends-1.0.32.html">1.0.32</a>,
<a href="sane-backends-1.0.31.html">1.0.31</a>,