kopia lustrzana https://gitlab.com/sane-project/website
Porównaj commity
8 Commity
2bb9b9ce4e
...
5c8d8c2861
Autor | SHA1 | Data |
---|---|---|
Povilas Kanapickas | 5c8d8c2861 | |
Povilas Kanapickas | 16839600fc | |
Povilas Kanapickas | 4e20920303 | |
Povilas Kanapickas | f6152c48a9 | |
Ralph Little | 70e5958002 | |
Povilas Kanapickas | 6d9961a6d1 | |
Povilas Kanapickas | 3c4d2ae201 | |
Povilas Kanapickas | 792efdacda |
|
@ -36,6 +36,9 @@
|
|||
<td valign=top bgcolor="#e0e0ff" width="50%">
|
||||
<h3>Latest News</h3>
|
||||
<h4>Backends</h4>
|
||||
<p>
|
||||
<strong>2022-01-19:</strong> <a href="https://gitlab.com/sane-project/backends/-/releases/1.1.1"><tt>sane-backends-1.1.1</tt></a> has been released.
|
||||
</p>
|
||||
<p>
|
||||
<strong>2021-02-14:</strong> <a href="https://gitlab.com/sane-project/backends/-/releases/1.0.32"><tt>sane-backends-1.0.32</tt></a> has been released.
|
||||
</p>
|
||||
|
@ -51,10 +54,6 @@ This is a security bug fix release.
|
|||
</p>
|
||||
<p>
|
||||
<strong>2019-07-31:</strong> <a href="https://gitlab.com/sane-project/backends/-/releases/1.0.28"><tt>sane-backends-1.0.28</tt></a> has been released.
|
||||
</p>
|
||||
<p>
|
||||
<strong>2017-05-22:</strong> <a href="https://gitlab.com/sane-project/backends/-/releases/RELEASE_1_0_27"><tt>sane-backends-1.0.27</tt></a> has been released.<br/>
|
||||
Please note that we skipped <tt>1.0.26</tt>.
|
||||
</p>
|
||||
<h4>Frontends</h4>
|
||||
<p>
|
||||
|
|
|
@ -82,11 +82,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -50,11 +50,11 @@
|
|||
|
||||
<I>special</I>
|
||||
|
||||
Where <I>special</I> is either the path-name for the special device that cor-
|
||||
responds to a SCSI scanner. For SCSI scanners, the special device name
|
||||
must be a generic SCSI device or a symlink to such a device. Under
|
||||
Linux, such a device name could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example.
|
||||
See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details.
|
||||
where <I>special</I> is the path-name for the special device that corresponds
|
||||
to a SCSI scanner. For SCSI scanners, the special device name must be a
|
||||
generic SCSI device or a symlink to such a device. Under Linux, such a
|
||||
device name could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example. See
|
||||
<B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
@ -87,11 +87,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -39,11 +39,11 @@
|
|||
|
||||
<I>special</I>
|
||||
|
||||
Where <I>special</I> is either the path-name for the special device that cor-
|
||||
responds to a SCSI scanner. For SCSI scanners, the special device name
|
||||
must be a generic SCSI device or a symlink to such a device. Under
|
||||
Linux, such a device name could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example.
|
||||
See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details.
|
||||
where <I>special</I> is the path-name for the special device that corresponds
|
||||
to a SCSI scanner. For SCSI scanners, the special device name must be a
|
||||
generic SCSI device or a symlink to such a device. Under Linux, such a
|
||||
device name could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example. See
|
||||
<B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
@ -86,8 +86,8 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable is list of directories where SANE
|
||||
looks for the configuration file. Under UNIX directory names
|
||||
are separated by a colon (`:'), under OS/2 by a semi-colon
|
||||
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/lo-</I>
|
||||
<I>cal/etc/sane.d</I>. If the value of $SANE_CONFIG_DIR ends with the
|
||||
|
|
|
@ -77,7 +77,7 @@
|
|||
</PRE>
|
||||
<H2>SCSI ADAPTER TIPS</H2><PRE>
|
||||
Some Artec scanners come with an included SCSI adapter. If your scan-
|
||||
ner came with a DTC ISA scsi cards, you can probably use it with recent
|
||||
ner came with a DTC ISA SCSI cards, you can probably use it with recent
|
||||
(>= 2.2.0) kernels using the generic NCR5380 support. You must pass
|
||||
the following boot argument to the kernel: "dtc3181e=0x2c0,0"
|
||||
I do not have any information on the PCI SCSI adapter included with
|
||||
|
@ -102,11 +102,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi- colon (`;'). If this variable is not set, the con-
|
||||
figuration file is searched in two default directories: first,
|
||||
the current working direc- tory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -21,7 +21,7 @@
|
|||
The <B>sane-artec_eplus48u</B> library implements a SANE (Scanner Access Now
|
||||
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) and an USB interface.
|
||||
contact image sensor (CIS).
|
||||
|
||||
A complete list of supported devices can be found on
|
||||
<I>http://www.sane-project.org/sane-supported-devices.html</I>.
|
||||
|
@ -68,9 +68,9 @@
|
|||
with a hash mark (#) are ignored. The scanners are autodetected by <I>usb</I>
|
||||
<I>vendor</I><B>_</B><I>id</I> <I>product</I><B>_</B><I>id</I> statements which are already included into
|
||||
<I>artec</I><B>_</B><I>eplus48u.conf</I> <I>.</I> "vendor_id" and "product_id" are hexadecimal
|
||||
numbers that identify the <B>scanner.</B>
|
||||
numbers that identify the scanner.
|
||||
|
||||
Every usb section can have additional options
|
||||
Every usb 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.
|
||||
|
@ -97,9 +97,9 @@
|
|||
<B>greenExposure</B> <B>0x116</B>
|
||||
|
||||
<B>blueExposure</B> <B>0xdc</B>
|
||||
These are the default values for offset and exposure time. You
|
||||
can e.g. change them to speed up calibration, if you don't want
|
||||
to save the calibration data to disk.
|
||||
These are the default values for offset and exposure time. You
|
||||
can change them (e.g. to speed up calibration) if you don't want
|
||||
to save the calibration data permanently.
|
||||
|
||||
<B>vendorString</B> <B>Artec</B>
|
||||
|
||||
|
@ -127,11 +127,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -12,32 +12,31 @@
|
|||
|
||||
</PRE>
|
||||
<H2>NAME</H2><PRE>
|
||||
sane-avision - SANE backend for original Avision and Avision OEM scan-
|
||||
ners (HP, Minolta, Mitsubishi, UMAX and possibly more) flatbed and film
|
||||
scanners.
|
||||
sane-avision - SANE backend for Avision branded and Avision OEM (HP,
|
||||
Minolta, Mitsubishi, UMAX and possibly more) flatbed and film scanners.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>DESCRIPTION</H2><PRE>
|
||||
The <B>sane-avision</B> library implements a SANE (Scanner Access Now Easy)
|
||||
backend that provides access to various Avision scanners and the Avi-
|
||||
The <B>sane-avision</B> library implements a SANE (Scanner Access Now Easy)
|
||||
backend that provides access to various Avision scanners and the Avi-
|
||||
sion OEM scanners labelled by HP, Minolta, Mitsubishi or Fujitsu.
|
||||
|
||||
It is fully big-endian aware and in everyday use on PowerPC and SPARC
|
||||
It is fully big-endian aware and in everyday use on PowerPC and SPARC
|
||||
systems.
|
||||
|
||||
<B>I</B> <B>suggest</B> <B>you</B> <B>hold</B> <B>one</B> <B>hand</B> <B>on</B> <B>the</B> <B>power-button</B> <B>of</B> <B>the</B> <B>scanner</B> <B>while</B>
|
||||
you try the first scans - especially with film-scanners!
|
||||
<B>I</B> <B>suggest</B> <B>you</B> <B>hold</B> <B>one</B> <B>hand</B> <B>on</B> <B>the</B> <B>power-button</B> <B>of</B> <B>the</B> <B>scanner</B> <B>while</B>
|
||||
<B>you</B> <B>try</B> <B>the</B> <B>first</B> <B>scans</B> <B>-</B> <B>especially</B> <B>with</B> <B>film-scanners!</B>
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONFIGURATION</H2><PRE>
|
||||
The configuration file for this backend resides in <I>/usr/lo-</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
|
||||
starting with a hash mark (#) are ignored. A sample configuration file
|
||||
Its contents is a list of device names that correspond to Avision and
|
||||
Avision compatible scanners and backend-options. Empty lines and lines
|
||||
starting with a hash mark (#) are ignored. A sample configuration file
|
||||
is shown below:
|
||||
|
||||
# this is a comment
|
||||
|
@ -53,38 +52,38 @@
|
|||
usb 0x03f0 0x0701
|
||||
|
||||
force-a4:
|
||||
Forces the backend to overwrite the scanable area returned by
|
||||
the scanner to ISO A4. Scanner that are known to return bogus
|
||||
Forces the backend to overwrite the scanable area returned by
|
||||
the scanner to ISO A4. Scanner that are known to return bogus
|
||||
data are marked in the backend so if you need this option please
|
||||
report this to the backend maintainer. USE WITH CARE!
|
||||
|
||||
force-a3:
|
||||
Forces the backend to overwrite the scanable area returned by
|
||||
the scanner to ISO A3. Scanner that are known to return bogus
|
||||
Forces the backend to overwrite the scanable area returned by
|
||||
the scanner to ISO A3. Scanner that are known to return bogus
|
||||
data are marked in the backend so if you need this option please
|
||||
report this to the backend maintainer. USE WITH CARE!
|
||||
|
||||
skip-adf:
|
||||
Forces the backend to ignore an inconsistent ADF status returned
|
||||
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 re-
|
||||
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 re-
|
||||
spond.
|
||||
|
||||
disable-gamma-table:
|
||||
Disables the usage of the scanner's gamma-table. You might try
|
||||
this if your scans hang or only produces random garbage.
|
||||
Disables the usage of the scanner's gamma-table. You might try
|
||||
this if your scans hang or only produce random garbage.
|
||||
|
||||
disable-calibration:
|
||||
Disables the scanner's color calibration. You might try this if
|
||||
your scans hang or only produces random garbage.
|
||||
Disables the scanner's color calibration. You might try this if
|
||||
your scans hang or only produce random garbage.
|
||||
|
||||
Note: Any option above modifies the default code-flow for your scan-
|
||||
Note: Any option above modifies the default code-flow for your scan-
|
||||
ner. The options should only be used when you encounter problems
|
||||
with the default be- haviour of the backend. Please report the
|
||||
need of options to the backend-author so the backend can be
|
||||
fixed as soon as possible.
|
||||
with the default behavior of the backend. Please report the need
|
||||
of options to the backend-author so the backend can be fixed as
|
||||
soon as possible.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
@ -96,23 +95,23 @@
|
|||
<I>usb</I> <I>usb-spec</I>
|
||||
|
||||
Where <I>scsi-spec</I> is the path-name to a special device or a device ID for
|
||||
the device that corresponds to a SCSI scanner. The special device name
|
||||
must be a generic SCSI device or a symlink to such a device, for exam-
|
||||
the device that corresponds to a SCSI scanner. The special device name
|
||||
must be a generic SCSI device or a symlink to such a device, for exam-
|
||||
ple on Linux <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 de-
|
||||
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
|
||||
Note: Since the backend now includes native USB access, it is no
|
||||
longer needed - even considered obsolete - to access USB scanner
|
||||
via the SCSI emulation (named hpusbscsi on Linux) for Avision
|
||||
USB devices such as the HP 53xx, HP 74xx or Minolta film-scan-
|
||||
via the SCSI emulation (named hpusbscsi on Linux) for Avision
|
||||
USB devices such as the HP 53xx, HP 74xx or Minolta film-scan-
|
||||
ners.
|
||||
|
||||
<I>usb-spec</I> is the USB device name, the vendor/product ID pair or the name
|
||||
used by libusb corresponding to the USB scanner. For example "0x03f0
|
||||
used by libusb corresponding to the USB scanner. For example "0x03f0
|
||||
0x0701" or "libusb:002:003". See <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B> for details.
|
||||
|
||||
The program <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B> helps to find out the correct scsi or
|
||||
The program <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B> helps to find out the correct scsi or
|
||||
usb device name.
|
||||
|
||||
A list with supported devices is built into the avision backend so nor-
|
||||
|
@ -122,7 +121,7 @@
|
|||
</PRE>
|
||||
<H2>FILES</H2><PRE>
|
||||
<I>/usr/local/etc/sane.d/avision.conf</I>
|
||||
The backend configuration file (see also description of
|
||||
The backend configuration file (see also description of
|
||||
<B>SANE_CONFIG_DIR</B> below).
|
||||
|
||||
<I>/usr/local/lib/sane/libsane-avision.a</I>
|
||||
|
@ -137,23 +136,23 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <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.
|
||||
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/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 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
|
||||
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.
|
||||
|
||||
Example: export SANE_DEBUG_AVISION=7
|
||||
|
|
|
@ -362,11 +362,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -71,7 +71,7 @@
|
|||
mode can be recommended if extensive adjustments have to be made to a
|
||||
picture (and if the frontend can handle 16-bit intensities).
|
||||
|
||||
Negatives are handled by simple color inversion and may require manual
|
||||
Negatives are handled by simple color inversion and will require manual
|
||||
removal of blue discoloration.
|
||||
|
||||
|
||||
|
|
|
@ -41,7 +41,7 @@
|
|||
|
||||
This product-specific scanner driver uses the lower-level kernel USB
|
||||
driver "scanner". Check for "Driver=usbscanner" under
|
||||
<I>/proc/bus/usb/devices.</I> If "Driver=(none)", try forcing it with <I>insmod</I>
|
||||
<I>/proc/bus/usb/devices</I>. If "Driver=(none)", try forcing it with <I>insmod</I>
|
||||
<I>scanner</I> <I>vendor=0x04a9</I> <I>product=0x2204</I>
|
||||
|
||||
|
||||
|
@ -58,8 +58,8 @@
|
|||
Some users have reported that this driver doesn't work at all. This
|
||||
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>DE-</I>
|
||||
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>DE-</I>
|
||||
<I>BUG</I><B>_</B><I>CANON630U=12</I> <I>scanimage</I> <I>></I> <I>/dev/null</I>
|
||||
|
||||
|
||||
|
@ -86,11 +86,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -20,8 +20,8 @@
|
|||
The <B>sane-canon_dr</B> library implements a SANE (Scanner Access Now Easy)
|
||||
backend which provides access to some Canon DR-series scanners.
|
||||
|
||||
This document describes backend version 57, which shipped with SANE
|
||||
1.0.28.
|
||||
This document describes backend version 60, which shipped with SANE
|
||||
1.0.32.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
@ -63,30 +63,31 @@
|
|||
|
||||
<B>--page-width,</B> <B>--page-height</B>
|
||||
Sets paper size. Used by scanner to determine centering of scan
|
||||
coordinates when using ADF and to detect double feed errors.
|
||||
coordinates when using the ADF (Automatic Document Feeder) and
|
||||
to detect double feed errors.
|
||||
|
||||
Other options will be available based on the capabilities of the scan-
|
||||
Other options will be available based on the capabilities of the scan-
|
||||
ner: enhancement, compression, buttons and sensors, etc.
|
||||
|
||||
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 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
|
||||
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 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
|
||||
Requests the driver to detect the extremities of the paper
|
||||
within the larger image, and crop the empty edges.
|
||||
|
||||
<B>--swdeskew</B>
|
||||
Requests the driver to detect the rotation of the paper within
|
||||
Requests the driver to detect the rotation of the paper within
|
||||
the larger image, and counter the rotation.
|
||||
|
||||
<B>--swdespeck</B> <B>X</B>
|
||||
Requests the driver to find and remove dots of X diameter or
|
||||
Requests the driver to find and remove dots of X diameter or
|
||||
smaller from the image, and fill the space with the average sur-
|
||||
rounding color.
|
||||
|
||||
|
@ -99,21 +100,21 @@
|
|||
<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)
|
||||
|
@ -122,41 +123,42 @@
|
|||
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>: 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.
|
||||
|
||||
|
||||
|
@ -207,8 +209,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
m. allan noah: <I><kitno455</I> <I>a</I> <I>t</I> <I>gmail</I> <I>d</I> <I>o</I> <I>t</I> <I>com></I>.
|
||||
|
||||
|
||||
31 Aug 2015 <B><A HREF="sane-canon_dr.5.html">sane-canon_dr(5)</A></B>
|
||||
13 Feb 2021 <B><A HREF="sane-canon_dr.5.html">sane-canon_dr(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
@ -110,10 +110,6 @@
|
|||
for prescans. The problem is worse on the LiDE 600(F), where the offset
|
||||
is five millimeters.
|
||||
|
||||
It is recommended that in <B><A HREF="xsane.1.html">xsane(1)</A></B> the gamma value be set to approxi-
|
||||
mately 1.7 to get more realistic colors. This also wipes out some arti-
|
||||
facts caused by the lack of real calibration.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
|
|
|
@ -120,11 +120,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -79,8 +79,8 @@
|
|||
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 <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><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><n></B>
|
||||
Here <n> can either be 8 or the maximum number of bits supported
|
||||
|
@ -106,17 +106,19 @@
|
|||
Multiply all exposure times with this value. This allows expo-
|
||||
sure correction without modifying white balance.
|
||||
|
||||
<B>--load</B> Load the next slide when using the slide loader.
|
||||
<B>--load</B> Load the next slide when using the slide loader (applies only to
|
||||
the SF-200 bulk feeder).
|
||||
|
||||
<B>--eject</B>
|
||||
Eject the film strip or mounted slide when using the slide
|
||||
Eject the film strip or mounted slide when using the slide
|
||||
loader.
|
||||
|
||||
<B>--reset</B>
|
||||
Reset scanner. The scanner will perform the same action as when
|
||||
power is turned on: it will eject the film strip and calibrate
|
||||
itself. Use this whenever the scanner refuses to load a film
|
||||
strip properly, as a result of which <B>--eject</B> does not work.
|
||||
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.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
@ -181,7 +183,7 @@
|
|||
<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 frame option will not appear at all. Also, restarting the
|
||||
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
|
||||
|
|
|
@ -79,8 +79,8 @@
|
|||
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 infor-
|
||||
mation.
|
||||
perform a batch scan with <B>--batch-count=2</B> to obtain the IR in-
|
||||
formation.
|
||||
|
||||
<B>--depth</B> <B><n></B>
|
||||
Here <n> can either be 8 or the maximum number of bits supported
|
||||
|
@ -106,17 +106,19 @@
|
|||
Multiply all exposure times with this value. This allows expo-
|
||||
sure correction without modifying white balance.
|
||||
|
||||
<B>--load</B> Load the next slide when using the slide loader.
|
||||
<B>--load</B> Load the next slide when using the slide loader (SF-200 bulk
|
||||
loader only).
|
||||
|
||||
<B>--eject</B>
|
||||
Eject the film strip or mounted slide when using the slide
|
||||
Eject the film strip or mounted slide when using the slide
|
||||
loader.
|
||||
|
||||
<B>--reset</B>
|
||||
Reset scanner. The scanner will perform the same action as when
|
||||
power is turned on: it will eject the film strip and calibrate
|
||||
itself. Use this whenever the scanner refuses to load a film
|
||||
strip properly, as a result of which <B>--eject</B> does not work.
|
||||
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.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
@ -136,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 know identifiers. This is the action
|
||||
taken 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><interface>:<device></I>
|
||||
Here <interface> can be one of "scsi" or "usb", and <device> is
|
||||
|
@ -171,7 +173,7 @@
|
|||
|
||||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B>xscanimage(1),</B> <B>xsane(1)</B>
|
||||
<B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, <B><A HREF="xsane.1.html">xsane(1)</A></B>
|
||||
|
||||
|
||||
</PRE>
|
||||
|
@ -181,7 +183,7 @@
|
|||
<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 frame option will not appear at all. Also, restarting the
|
||||
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
|
||||
|
|
|
@ -42,12 +42,12 @@
|
|||
The <B>dumpinquiry</B> line causes some information about the camera to be
|
||||
printed.
|
||||
|
||||
<B>cmdrespause</B> specifies how many usec (1,000,000ths of a) between writing
|
||||
the command and reading the result should be used. 125000 seems to be
|
||||
<B>cmdrespause</B> specifies how many usec (1,000,000ths of a second) to wait
|
||||
between writing the command and reading the result. 125000 seems to be
|
||||
the lowest I could go reliably.
|
||||
|
||||
<B>breakpause</B> is the time in 1,000,000ths of a usec between sending the
|
||||
"back to default" break sending commands.
|
||||
<B>breakpause</B> specifies how many usec (1,000,000ths of a second) between
|
||||
sending the "back to default" break and sending commands.
|
||||
|
||||
Empty lines and lines starting with a hash mark (#) are ignored. A
|
||||
sample configuration file is shown below:
|
||||
|
@ -78,11 +78,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -42,12 +42,12 @@
|
|||
The <B>dumpinquiry</B> line causes some information about the camera to be
|
||||
printed.
|
||||
|
||||
<B>cmdrespause</B> specifies how many usec (1,000,000ths of a) between writing
|
||||
the command and reading the result should be used. 125000 seems to be
|
||||
<B>cmdrespause</B> specifies how many usec (1,000,000ths of a second) to wait
|
||||
between writing the command and reading the result. 125000 seems to be
|
||||
the lowest I could go reliably.
|
||||
|
||||
<B>breakpause</B> is the time in 1,000,000ths of a usec between sending the
|
||||
"back to default" break sending commands.
|
||||
<B>breakpause</B> specifies how many usec (1,000,000ths of a second) between
|
||||
sending the "back to default" break and sending commands.
|
||||
|
||||
Empty lines and lines starting with a hash mark (#) are ignored. A
|
||||
sample configuration file is shown below:
|
||||
|
@ -78,11 +78,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
@ -106,24 +106,25 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
Peter S. Fales
|
||||
|
||||
This backend borrows heavily from the dc210 backend by Brian J. Murrell
|
||||
which is based somewhat on the dc25 backend by Peter Fales.
|
||||
This backend borrows heavily from the <B><A HREF="sane-dc210.5.html">sane-dc210(5)</A></B> backend by Brian J.
|
||||
Murrell which is based somewhat on the <B><A HREF="sane-dc25.5.html">sane-dc25(5)</A></B> backend by Peter
|
||||
Fales.
|
||||
|
||||
The manpage was largely copied from the dc210 manpage.
|
||||
The manpage was largely copied from the <B><A HREF="sane-dc210.5.html">sane-dc210(5)</A></B> manpage.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>BUGS</H2><PRE>
|
||||
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
|
||||
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.
|
||||
|
||||
More general comments, suggestions, and inquiries about frontends or
|
||||
SANE should go to the SANE Developers mailing list (see
|
||||
<I>http://www.sane-project.org/mailing-lists.html</I> for details). You must
|
||||
be subscribed to the list, otherwise your mail won't be sent to the
|
||||
More general comments, suggestions, and inquiries about frontends or
|
||||
SANE should go to the SANE Developers mailing list (see
|
||||
<I>http://www.sane-project.org/mailing-lists.html</I> for details). You must
|
||||
be subscribed to the list, otherwise your mail won't be sent to the
|
||||
subscribers.
|
||||
|
||||
11 Jul 2008 <B><A HREF="sane-dc240.5.html">sane-dc240(5)</A></B>
|
||||
|
|
|
@ -72,11 +72,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -115,11 +115,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -111,11 +111,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -105,7 +105,7 @@
|
|||
|
||||
</PRE>
|
||||
<H2>AUTHOR</H2><PRE>
|
||||
The package is written by Alessandro Zummo
|
||||
The backend is written by Alessandro Zummo.
|
||||
|
||||
29 Mar 2015 <B><A HREF="sane-epsonds.5.html">sane-epsonds(5)</A></B>
|
||||
</PRE>
|
||||
|
|
|
@ -23,15 +23,21 @@
|
|||
Currently, the following models work with this backend (This list is
|
||||
not exhaustive):
|
||||
|
||||
BROTHER DCP-L2530
|
||||
BROTHER DCP-J772DW, DCP-L2530DW
|
||||
BROTHER HL-L2590DW
|
||||
CANON IR C3520
|
||||
CANON PIXMA MG5765
|
||||
CANON PIXMA TS3100, TS3150, TS3300, TS3151, TS3350, TS3351,
|
||||
CANON PIXMA TS3352, TS5351, TS6150, TS8050, TS9100, TR4540,
|
||||
CANON PIXMA TR8500, TR8520
|
||||
EPSON ET3740, ET4750
|
||||
HP DESKJET 2710, DESKJET 2723, DESKJET 3760, LASERJET MFP M28W,
|
||||
CANON PIXMA G4511, G7050
|
||||
CANON PIXMA TR4520, TR4540, TR4550, TR4551, TR7500, TR8500,
|
||||
CANON PIXMA TR8520
|
||||
CANON PIXMA TS3100, TS3150, TS3151, TS3152, TS3300, TS3350,
|
||||
CANON PIXMA TS3351, TS3352, TS5350, TS5351, TS6150, TS8050,
|
||||
CANON PIXMA TS9100
|
||||
EPSON ET-2750, ET-3750, ET-4750
|
||||
EPSON XP-6100
|
||||
HP DESKJET 2710, DESKJET 2723, DESKJET 3760
|
||||
HP LASERJET ENTREPRISE FLOW MFP M578,
|
||||
HP LASERJET MFP M28W, LASERJET MFP M630
|
||||
HP OFFICEJET 4630, OFFICEJET PRO 8610
|
||||
RICOH SP3710S
|
||||
XEROX VERSALINK C7220
|
||||
|
|
|
@ -35,7 +35,7 @@
|
|||
device files even if it isn't supported by any SANE backend.
|
||||
|
||||
For <B>USB</B> scanners, first the USB kernel scanner device files (e.g.
|
||||
<I>/dev/usb/scanner0</I>), <I>/dev/usb/scanner</I>, and <I>/dev/usbscanner</I>) are tested.
|
||||
<I>/dev/usb/scanner0</I>, <I>/dev/usb/scanner</I>, and <I>/dev/usbscanner</I>) are tested.
|
||||
The files are opened and the vendor and device ids are determined, if
|
||||
the operating system supports this feature. Currently USB scanners are
|
||||
only found this way if they are supported by the Linux scanner module
|
||||
|
@ -50,7 +50,7 @@
|
|||
|
||||
<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 de-
|
||||
tected by <I>sane-find-scanner</I> <I>-p.</I> At the time of writing this will only
|
||||
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.
|
||||
|
||||
|
||||
|
|
|
@ -20,8 +20,8 @@
|
|||
The <B>sane-fujitsu</B> library implements a SANE (Scanner Access Now Easy)
|
||||
backend which provides access to most Fujitsu flatbed and ADF scanners.
|
||||
|
||||
This document describes backend version 136, which shipped with SANE
|
||||
1.0.30.
|
||||
This document describes backend version 137, which shipped with SANE
|
||||
1.0.32.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
@ -81,46 +81,60 @@
|
|||
|
||||
<B>page-width,</B> <B>page-height</B>
|
||||
Sets paper size. Used by scanner to determine centering of scan
|
||||
coordinates when using ADF and to detect double feed errors.
|
||||
coordinates when using the ADF (Automatic Document Feeder) and
|
||||
to detect double feed errors.
|
||||
|
||||
Other options will be available based on the capabilities of the scan-
|
||||
Other options will be available based on the capabilities of the scan-
|
||||
ner: machines with IPC or DTC will have additional enhancement options,
|
||||
those with CMP will have compression options, those with a printer will
|
||||
have a group of endorser options.
|
||||
|
||||
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 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
|
||||
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 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.
|
||||
|
||||
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 ad-
|
||||
swcrop
|
||||
Requests the driver to detect the extremities of the paper
|
||||
within the larger image, and crop the empty edges.
|
||||
|
||||
swdeskew
|
||||
Requests the driver to detect the rotation of the paper within
|
||||
the larger image, and counter the rotation.
|
||||
|
||||
swdespeck X
|
||||
Requests the driver to find and remove dots of X diameter or
|
||||
smaller from the image, and fill the space with the average sur-
|
||||
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 ad-
|
||||
vanced options may be hidden by some frontend programs.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONFIGURATION FILE</H2><PRE>
|
||||
The configuration file <I>fujitsu.conf</I> is used to tell the backend how to
|
||||
The configuration file <I>fujitsu.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
|
||||
a list of scanners, generally only when the frontend starts. If the
|
||||
configuration file is missing, the backend will be unable to locate any
|
||||
scanners.
|
||||
|
||||
Scanners can be specified in the configuration file in 4 ways:
|
||||
|
||||
"scsi FUJITSU"
|
||||
Requests backend to search all scsi buses in the system for a
|
||||
Requests backend to search all scsi buses in the system for a
|
||||
device which reports itself to be a scanner made by 'FUJITSU'.
|
||||
|
||||
"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 0x04c5 0x1042" (or other vendor/product ids)
|
||||
|
@ -129,28 +143,28 @@
|
|||
be queried to determine if it is a Fujitsu 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.
|
||||
|
||||
The only configuration option supported is "buffer-size=xxx", allowing
|
||||
you to set the number of bytes in the data buffer to something other
|
||||
The only configuration option supported is "buffer-size=xxx", allowing
|
||||
you to set the number of bytes in the data buffer to something other
|
||||
than the compiled-in default, 65536 (64K). Some users report that their
|
||||
scanner will "hang" mid-page, or fail to transmit the image if the buf-
|
||||
fer is not large enough.
|
||||
|
||||
Note: This option may appear multiple times in the configuration file.
|
||||
It only applies to scanners discovered by 'scsi/usb' lines that follow
|
||||
Note: This option may appear multiple times in the configuration file.
|
||||
It only applies to scanners discovered by 'scsi/usb' lines that follow
|
||||
this option.
|
||||
|
||||
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
|
||||
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.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>ENVIRONMENT</H2><PRE>
|
||||
The backend uses a single environment variable, <B>SANE_DEBUG_FUJITSU</B>,
|
||||
The backend uses a single environment variable, <B>SANE_DEBUG_FUJITSU</B>,
|
||||
which enables debugging output to stderr. Valid values are:
|
||||
|
||||
5 Errors
|
||||
|
@ -165,16 +179,16 @@
|
|||
|
||||
</PRE>
|
||||
<H2>KNOWN ISSUES</H2><PRE>
|
||||
Flatbed units may fail to scan at maximum area, particularly at high
|
||||
Flatbed units may fail to scan at maximum area, particularly at high
|
||||
resolution.
|
||||
|
||||
Any model that does not support VPD during inquiry will not function
|
||||
Any model that does not support VPD during inquiry will not function
|
||||
until an override is added to the backend.
|
||||
|
||||
CCITT Fax compression used by older scanners is not supported.
|
||||
|
||||
JPEG output is supported by the backend, but not by the SANE protocol,
|
||||
so is disabled in this release. It can be enabled if you rebuild from
|
||||
JPEG output is supported by the backend, but not by the SANE protocol,
|
||||
so is disabled in this release. It can be enabled if you rebuild from
|
||||
source.
|
||||
|
||||
|
||||
|
@ -203,7 +217,7 @@
|
|||
Automatic length detection support funded by:
|
||||
Martin G. Miller <I>mgmiller</I> <I>at</I> <I>optonline.net</I>
|
||||
|
||||
Hardware donated, software image enhancement and fi-6/7xxx support
|
||||
Hardware donated, software image enhancement and fi-6/7xxx support
|
||||
funded by:
|
||||
Fujitsu Computer Products of America, Inc. <I>www.fcpa.com</I>
|
||||
|
||||
|
@ -217,12 +231,11 @@
|
|||
<B><A HREF="sane-epjitsu.5.html">sane-epjitsu(5)</A></B>
|
||||
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>AUTHOR</H2><PRE>
|
||||
m. allan noah: <kitno455 a t gmail d o t com>
|
||||
|
||||
07 Feb 2020 <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>
|
||||
13 Feb 2021 <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
@ -198,11 +198,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -87,11 +87,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (<I>.</I>) and then in <I>/usr/lo-</I>
|
||||
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 (<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.
|
||||
|
@ -112,14 +112,14 @@
|
|||
|
||||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<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="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>
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>AUTHOR</H2><PRE>
|
||||
Peter S. Fales
|
||||
|
||||
The manpage was largely copied from the dc210 manpage.
|
||||
The manpage was largely copied from the <B><A HREF="sane-dc210.5.html">sane-dc210(5)</A></B> manpage.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
|
@ -45,7 +45,7 @@
|
|||
Please use libusb-0.1.8 or later. Without libusb or with older libusb
|
||||
versions all kinds of trouble can be expected. The scanner should be
|
||||
found by <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B> without further actions. For setting per-
|
||||
missions and general USB information looks at <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>.
|
||||
missions and general USB information, look at <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
@ -57,7 +57,7 @@
|
|||
with the installation program in an .exe file. For Mustek scanners, the
|
||||
file can be downloaded from the gt68xx backend homepage. For other
|
||||
scanners, check the CD for .usb files. If you only find *.cab files,
|
||||
try cabextract to unpack. If everything else fails, you must install
|
||||
try <B><A HREF="cabextract.1.html">cabextract(1)</A></B> to unpack. If everything else fails, you must install
|
||||
the Windows driver and get the firmware from there (usually in the <I>win-</I>
|
||||
<I>dows/system</I> or <I>system32</I> directories). Put that firmware file into
|
||||
<I>/usr/local/share/sane/gt68xx/</I>. Make sure that it's readable by every-
|
||||
|
@ -137,11 +137,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
@ -162,7 +162,8 @@
|
|||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B> <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>,
|
||||
<B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>, <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>
|
||||
<B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>, <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>,
|
||||
<B><A HREF="cabextract.1.html">cabextract(1)</A></B>
|
||||
<I>/usr/local/share/doc/sane-backends/gt68xx/gt68xx.CHANGES</I>
|
||||
<I>http://www.meier-geinitz.de/sane/gt68xx</I>
|
||||
|
||||
|
@ -170,8 +171,8 @@
|
|||
</PRE>
|
||||
<H2>AUTHOR</H2><PRE>
|
||||
Henning Meier-Geinitz <<I>henning@meier-geinitz.de</I>>
|
||||
The original gt68xx driver was written by Sergey Vlasov, Andreas
|
||||
Nowack, and David Stevenson. Thanks for sending patches and answering
|
||||
The original gt68xx driver was written by Sergey Vlasov, Andreas
|
||||
Nowack, and David Stevenson. Thanks for sending patches and answering
|
||||
questions to them and all the other contributors.
|
||||
|
||||
|
||||
|
@ -179,16 +180,16 @@
|
|||
<H2>BUGS</H2><PRE>
|
||||
The first few lines of the image are garbage for the 2400 TA Plus.
|
||||
|
||||
Interpolation should be used instead of just copying data, when the X-
|
||||
Interpolation should be used instead of just copying data, when the X-
|
||||
and Y-resolution differ.
|
||||
|
||||
Support for buttons is missing.
|
||||
|
||||
More detailed bug information is available at the gt68xx backend home-
|
||||
More detailed bug information is available at the gt68xx backend home-
|
||||
page <I>http://www.meier-geinitz.de/sane/gt68xx-backend/</I>.
|
||||
Please contact us if you find a bug or missing feature: <<I>sane-de-</I>
|
||||
Please contact us if you find a bug or missing feature: <<I>sane-de-</I>
|
||||
<I>vel@alioth-lists.debian.net</I>>.
|
||||
Please send a debug log if your scanner isn't detected correctly (see
|
||||
Please send a debug log if your scanner isn't detected correctly (see
|
||||
<B>SANE_DEBUG_GT68XX</B> above).
|
||||
|
||||
13 Jul 2008 <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>
|
||||
|
|
|
@ -159,11 +159,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (<I>.</I>) and then in <I>/usr/lo-</I>
|
||||
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 (<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.
|
||||
|
|
|
@ -33,7 +33,7 @@
|
|||
UMAX Astra 4900/4950 RTS8822L-01H *
|
||||
BenQ 5550 RTS8823L-01E *
|
||||
|
||||
More details can be found on the <B><A HREF="sane-hp3900.1.html">sane-hp3900(1)</A></B> backend homepage
|
||||
More details can be found on the <B><A HREF="sane-hp3900.5.html">sane-hp3900(5)</A></B> backend homepage
|
||||
<I>http://sourceforge.net/projects/hp3900-series/</I>.
|
||||
|
||||
This is ALPHA software. Keep your hand at the scanner's plug and unplug
|
||||
|
@ -78,11 +78,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (<I>.</I>) and then in <I>/usr/lo-</I>
|
||||
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 (<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.
|
||||
|
|
|
@ -70,11 +70,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (<I>.</I>) and then in <I>/usr/lo-</I>
|
||||
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 (<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.
|
||||
|
|
|
@ -71,11 +71,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (<I>.</I>) and then in <I>/usr/lo-</I>
|
||||
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 (<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.
|
||||
|
|
|
@ -28,7 +28,7 @@
|
|||
|
||||
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>li-</B>
|
||||
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
|
||||
|
@ -65,15 +65,16 @@
|
|||
</PRE>
|
||||
<H2>TIPS</H2><PRE>
|
||||
It seems that HP ScanJet 5S scanner uses software noise correction.
|
||||
This feature is not implemented for now. So does gamma correction and
|
||||
calibration. I'll handle it in future versions. Native resolution for
|
||||
this scanner is 300 DPI. Other modes could be jagged in some ways.
|
||||
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.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>FILES</H2><PRE>
|
||||
<I>/usr/local/etc/sane.d/hpsj5s.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-hpsj5s.a</I>
|
||||
|
@ -88,21 +89,21 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <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.
|
||||
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/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 en-
|
||||
vironment variable controls the debug level for this backend.
|
||||
vironment variable controls the debug level for this backend.
|
||||
Higher debug levels increase the verbosity of the output.
|
||||
|
||||
|
||||
|
|
|
@ -34,10 +34,10 @@
|
|||
|
||||
<I>special</I>
|
||||
|
||||
Where <I>special</I> is either the path-name for the special device that cor-
|
||||
responds to a SCSI scanner. 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/sga</I>, for example. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details.
|
||||
Where <I>special</I> is the path-name for the special device that corresponds
|
||||
to a SCSI scanner. 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/sga</I>, for example. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
@ -66,11 +66,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -34,10 +34,10 @@
|
|||
|
||||
<I>special</I>
|
||||
|
||||
Where <I>special</I> is either the path-name for the special device that cor-
|
||||
responds to a SCSI scanner. 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/sga</I>, for example. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details.
|
||||
Where <I>special</I> is the path-name for the special device that corresponds
|
||||
to a SCSI scanner. 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/sga</I>, for example. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
@ -66,11 +66,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -67,48 +67,49 @@
|
|||
|
||||
<B>--page-width</B>, <B>--page-height</B>
|
||||
Sets paper size. Used by scanner to determine centering of scan
|
||||
coordinates when using ADF and to detect double feed errors.
|
||||
coordinates when using the ADF (Automatic Document Feeder) and
|
||||
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 op-
|
||||
tions may be settable only when another option has been set, and that
|
||||
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 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>kodak.conf</I> is used to tell the backend how to
|
||||
The configuration file <I>kodak.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
|
||||
configuration file is missing, the backend will use a set of compiled
|
||||
a list of scanners, generally only when the frontend starts. If the
|
||||
configuration file is missing, the backend will use a set of compiled
|
||||
defaults, which are identical to the default configuration file shipped
|
||||
with SANE.
|
||||
|
||||
Scanners can be specified in the configuration file in 2 ways:
|
||||
|
||||
"scsi KODAK"
|
||||
Requests backend to search all scsi buses in the system for a
|
||||
Requests backend to search all scsi buses in the system for a
|
||||
device which reports itself to be a scanner made by 'KODAK'.
|
||||
|
||||
"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.
|
||||
|
||||
The only configuration option supported is "buffer-size=xxx", allowing
|
||||
you to set the number of bytes in the data buffer to something other
|
||||
The only configuration option supported is "buffer-size=xxx", allowing
|
||||
you to set the number of bytes in the data buffer to something other
|
||||
than the compiled-in default, 32768 (32K). Some users report that their
|
||||
scanner will "hang" mid-page, or fail to transmit the image if the buf-
|
||||
fer is not large enough.
|
||||
|
||||
Note: This option may appear multiple times in the configuration file.
|
||||
It only applies to scanners discovered by 'scsi/usb' lines that follow
|
||||
Note: This option may appear multiple times in the configuration file.
|
||||
It only applies to scanners discovered by 'scsi/usb' lines that follow
|
||||
this option.
|
||||
|
||||
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
|
||||
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.
|
||||
|
||||
|
@ -129,14 +130,14 @@
|
|||
|
||||
</PRE>
|
||||
<H2>KNOWN ISSUES</H2><PRE>
|
||||
Most hardware options are either not supported or not exposed for con-
|
||||
trol by the user, including: multifeed detection, image compression,
|
||||
autocropping, endorser, iThresholding, multi-stream, etc.
|
||||
Most hardware options are either not supported or not exposed for con-
|
||||
trol by the user, including: multifeed detection, image compression,
|
||||
autocropping, endorser, thresholding, multi-stream, etc.
|
||||
|
||||
|
||||
</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.
|
||||
Kodak provided access to hardware, documentation and personnel.
|
||||
|
||||
|
@ -150,6 +151,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
m. allan noah: <<I>kitno455</I> <I>a</I> <I>t</I> <I>gmail</I> <I>d</I> <I>o</I> <I>t</I> <I>com</I>>
|
||||
|
||||
|
||||
10 Feb 2010 <B><A HREF="sane-kodak.5.html">sane-kodak(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
|
|
|
@ -30,9 +30,10 @@
|
|||
This version should support models of the Kodak ESP and Hero series,
|
||||
and possibly some Advent AiO scanners. The ESP 5250 and Hero 9.1 were
|
||||
used to develop the backend, but other models may work. Please see the
|
||||
desc file.
|
||||
supported devices list at <I>http://www.sane-project.org/sane-back-</I>
|
||||
<I>ends.html#S-KODAKAIO</I>.
|
||||
|
||||
If you have a model not on that list, or reported as 'untested': the
|
||||
If you have a model not on that list, or reported as 'untested': the
|
||||
best way to determine level of support is to test the scanner directly.
|
||||
|
||||
|
||||
|
@ -48,14 +49,14 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_DEBUG_KODAKAIO</B>
|
||||
If the library was compiled with debug support enabled, this en-
|
||||
vironment variable controls the debug level for this backend.
|
||||
vironment variable controls the debug level for this backend.
|
||||
Higher debug levels increase the verbosity of the output.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>KNOWN ISSUES</H2><PRE>
|
||||
Most hardware options are either not supported or not exposed for con-
|
||||
trol by the user, including: multifeed detection, image compression
|
||||
Most hardware options are either not supported or not exposed for con-
|
||||
trol by the user, including: multifeed detection, image compression
|
||||
etc.
|
||||
|
||||
|
||||
|
|
|
@ -41,7 +41,7 @@
|
|||
|
||||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B><B>,</B> <B><A HREF="sane-usb.5.html">sane-usb(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>
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
|
@ -41,13 +41,14 @@
|
|||
|
||||
<B>Scan</B> <B>Mode</B>
|
||||
|
||||
<B>--mode</B> selects the basic mode of operation of the scanner valid choices
|
||||
are <I>Black</I> <I>&</I> <I>White</I> , <I>Grayscale</I> and <I>Color</I> The Black & White mode
|
||||
is black and white only (1 bit). Grayscale will produce 256 lev-
|
||||
els of gray (8 bits). Color will produce a 24 bits color image.
|
||||
<B>--mode</B> selects the basic mode of operation of the scanner. Valid
|
||||
choices are <I>Black</I> <I>&</I> <I>White</I>, <I>Grayscale</I> and <I>Color</I>. The <I>Black</I> <I>&</I>
|
||||
<I>White</I> mode is black and white only (1 bit). <I>Grayscale</I> mode will
|
||||
produce 256 levels of gray (8 bits). <I>Color</I> mode will produce a
|
||||
24 bit color image.
|
||||
|
||||
<B>--resolution</B>
|
||||
selects the resolution for a scan. The scanner can do all reso-
|
||||
selects the resolution for a scan. The scanner can do all reso-
|
||||
lutions between 1 and 300, in increments of 1.
|
||||
|
||||
<B>Geometry</B> <B>options</B>
|
||||
|
@ -55,35 +56,35 @@
|
|||
<B>-l</B> <B>-t</B> <B>-x</B> <B>-y</B>
|
||||
control the scan area: -l sets the top left x coordinate, -t the
|
||||
top left y coordinate, -x selects the width and -y the height of
|
||||
the scan area. All parameters are specified in millimeters by
|
||||
the scan area. All parameters are specified in millimeters by
|
||||
default.
|
||||
|
||||
<B>Enhancement</B> <B>options</B>
|
||||
|
||||
<B>--custom-gamma</B>
|
||||
(grayscale and color mode only) allows the user to specify a
|
||||
(grayscale and color mode only) allows the user to specify a
|
||||
gamma table (see the next 3 parameters).
|
||||
|
||||
<B>--red-gamma-table</B>
|
||||
(color mode only) can be used to download a user defined gamma
|
||||
(color mode only) can be used to download a user defined gamma
|
||||
table for the red channel. The table must be 256 bytes long.
|
||||
|
||||
<B>--green-gamma-table</B>
|
||||
(color mode only) can be used to download a user defined gamma
|
||||
(color mode only) can be used to download a user defined gamma
|
||||
table for the green channel. The table must be 256 bytes long.
|
||||
|
||||
<B>--blue-gamma-table</B>
|
||||
(color mode only) can be used to download a user defined gamma
|
||||
(color mode only) can be used to download a user defined gamma
|
||||
table for the blue channel. The table must be 256 bytes long.
|
||||
|
||||
<B>--halftone</B>
|
||||
(Black & White only) select the halftone mask to use. Possible
|
||||
values are <I>Diamond</I> , <I>8x8</I> <I>Coarse</I> <I>Fatting</I> , <I>8x8</I> <I>Fine</I> <I>Fatting</I> , <I>8x8</I>
|
||||
<I>Bayer</I> and <I>8x8</I> <I>Vertical</I> <I>Line</I>
|
||||
(Black & White only) select the halftone mask to use. Possible
|
||||
values are <I>Diamond</I>, <I>8x8</I> <I>Coarse</I> <I>Fatting</I>, <I>8x8</I> <I>Fine</I> <I>Fatting</I>, <I>8x8</I>
|
||||
<I>Bayer</I> and <I>8x8</I> <I>Vertical</I> <I>Line</I>.
|
||||
|
||||
<B>--preview</B>
|
||||
requests a preview scan. The resolution used for that scan is 28
|
||||
dpi and the scan area is the maximum allowed. The scan mode is
|
||||
dpi and the scan area is the maximum allowed. The scan mode is
|
||||
user selected. The default is "no".
|
||||
|
||||
|
||||
|
@ -107,18 +108,21 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_DEBUG_LEO</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 128 requests all debug output to be printed.
|
||||
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>
|
||||
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.
|
||||
|
||||
SH BUGS None known.
|
||||
|
||||
</PRE>
|
||||
<H2>BUGS</H2><PRE>
|
||||
None known.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
@ -126,7 +130,6 @@
|
|||
<B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, <B><A HREF="xsane.1.html">xsane(1)</A></B>, <B><A HREF="sane.7.html">sane(7)</A></B>
|
||||
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>AUTHOR</H2><PRE>
|
||||
The package is actively maintained by Frank Zago.
|
||||
|
|
|
@ -49,12 +49,12 @@
|
|||
|
||||
<B>Scan</B> <B>Mode</B> <B>Options</B>
|
||||
|
||||
<B>--mode</B> selects the basic mode of operation of the scanner valid choices
|
||||
are <I>Color</I>, <I>Gray</I> and <I>Lineart</I> The default mode is Color. The Lin-
|
||||
eart mode is black and white only (1 bit). Grayscale will pro-
|
||||
duce 256 levels of gray (8 bits). Color mode allows for over 16
|
||||
million different colors produced from 24 bits of color informa-
|
||||
tion.
|
||||
<B>--mode</B> selects the basic mode of operation of the scanner. Valid
|
||||
choices are <I>Color</I>, <I>Gray</I> and <I>Lineart</I>. The default mode is <I>Color</I>.
|
||||
The <I>Lineart</I> mode is black and white only (1 bit). <I>Gray</I> mode
|
||||
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.
|
||||
|
||||
<B>--resolution</B>
|
||||
selects the resolution for a scan. The horizontal and vertical
|
||||
|
|
|
@ -25,19 +25,18 @@
|
|||
This backend is ALPHA software. Be careful and remove the power plug
|
||||
immediately if your hear unusual noises.
|
||||
|
||||
More details can be found on the ma1509 backend homepage
|
||||
More details can be found on the <B>sane-ma1509</B> backend homepage
|
||||
<I>http://www.meier-geinitz.de/sane/ma1509-backend/</I>.
|
||||
|
||||
Other Mustek USB scanners are supported by the gt68xx, mustek_usb and
|
||||
the plustek backends. See <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> for details.
|
||||
Other Mustek USB scanners are supported by the <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> backends.
|
||||
|
||||
This backend can only work with scanners that are already detected by
|
||||
This backend can only work with scanners that are already detected by
|
||||
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
|
||||
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 ex-
|
||||
act model name and the USB vendor and device ids (e.g. from
|
||||
act model name and the USB vendor and device ids (e.g. from
|
||||
<I>/proc/bus/usb/devices</I> or syslog) to me.
|
||||
|
||||
|
||||
|
@ -48,32 +47,32 @@
|
|||
<I>special</I>
|
||||
|
||||
Where <I>special</I> is a path-name for the special device that corresponds to
|
||||
a USB scanner. With Linux, such a device name could be <I>/dev/usb/scan-</I>
|
||||
a USB scanner. With Linux, such a device name could be <I>/dev/usb/scan-</I>
|
||||
<I>ner0</I> or <I>libusb:001:002</I>, for example.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONFIGURATION</H2><PRE>
|
||||
The contents of the <I>ma1509.conf</I> file is a list of options and device
|
||||
names that correspond to Mustek BearPaw 1200F scanners. Empty lines
|
||||
The contents of the <I>ma1509.conf</I> file is a list of options and device
|
||||
names that correspond to Mustek BearPaw 1200F scanners. Empty lines
|
||||
and lines starting with a hash mark (#) are ignored.
|
||||
|
||||
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>ma1509.conf</I>. This is only supported with Linux 2.4.8 and higher and
|
||||
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>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 de-
|
||||
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 de-
|
||||
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 de-
|
||||
fault is 30 seconds.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>FILES</H2><PRE>
|
||||
<I>/usr/local/etc/sane.d/ma1509.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-ma1509.a</I>
|
||||
|
@ -88,27 +87,27 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <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.
|
||||
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/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 en-
|
||||
vironment variable controls the debug level for this backend.
|
||||
vironment variable controls the debug level for this backend.
|
||||
Higher debug levels increase the verbosity of the output.
|
||||
|
||||
|
||||
</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-gt68xx.5.html">sane-gt68xx(5)</A></B>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>,
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>,
|
||||
<B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>,
|
||||
<I>http://www.meier-geinitz.de/sane/ma1509-backend/</I>
|
||||
|
||||
|
|
|
@ -65,11 +65,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
@ -94,7 +94,7 @@
|
|||
</PRE>
|
||||
<H2>KNOWN BUGS AND RESTRICTIONS</H2><PRE>
|
||||
Large color scans may sometimes timeout due to unknown reasons (the
|
||||
scanner simply stops returning data)
|
||||
scanner simply stops returning data).
|
||||
|
||||
Cancelling large scans may lock up the scanner.
|
||||
|
||||
|
|
|
@ -109,11 +109,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -279,11 +279,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -347,11 +347,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -114,11 +114,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -22,7 +22,7 @@
|
|||
Service & Quality SQ113 chipset. At the moment, only the Mustek BearPaw
|
||||
2448 TA Pro is supported. It's planned to add support for other scan-
|
||||
ners that are based on the SQ113 and maybe SQ11 chip. For more details,
|
||||
see the mustek_usb2 backend homepage:
|
||||
see the <B>sane-mustek_usb2</B> backend homepage:
|
||||
<I>http://www.meier-geinitz.de/sane/mustek</I><B>_</B><I>usb2-backend/</I>.
|
||||
|
||||
This is BETA software. Especially if you test new or untested scanners,
|
||||
|
@ -42,7 +42,7 @@
|
|||
Please use libusb-0.1.8 or later. Without libusb or with older libusb
|
||||
versions all kinds of trouble can be expected. The scanner should be
|
||||
found by <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B> without further actions. For setting per-
|
||||
missions and general USB information looks at <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>.
|
||||
missions and general USB information, look at <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
|
@ -20,7 +20,7 @@
|
|||
The <B>sane-nec</B> library implements a SANE (Scanner Access Now Easy) back-
|
||||
end that provides access to NEC SCSI scanners. This backend should be
|
||||
considered <B>alpha-quality</B> software! In the current state it is known to
|
||||
work with PC-IN500/4C scanners. Another MultiReader scanner series is
|
||||
work with PC-IN500/4C scanners. Other MultiReader scanner series are
|
||||
not supported. PC-IN 500/4C and MultiReader scanner are only sold in
|
||||
Japan (except Multi Reader PetiScan).
|
||||
|
||||
|
|
|
@ -102,11 +102,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -78,11 +78,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -77,11 +77,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -29,7 +29,7 @@
|
|||
Currently, the following models work with this backend:
|
||||
|
||||
PIXMA E410, E510
|
||||
PIXMA G2000, G2010, G2100, G4000
|
||||
PIXMA G2000, G2010, G2100, G4000, G4511
|
||||
PIXMA MG2100, MG2200, MG2400, MG2500, MG2900, MG3000, MG3100
|
||||
PIXMA MG3200, MG3500, MG3600, MG4200, MG5100, MG5200, MG5300
|
||||
PIXMA MG5400, MG5500, MG5600, MG5700, MG6100, MG6200, MG6300
|
||||
|
@ -142,9 +142,9 @@
|
|||
|
||||
</PRE>
|
||||
<H2>OPTIONS</H2><PRE>
|
||||
Besides "well-known" options (e.g. resolution, mode etc.) backend also
|
||||
provides the following options, i.e. the options might change in the
|
||||
future.
|
||||
Besides "well-known" options (e.g. resolution, mode etc.) <B>sane-pixma</B>
|
||||
backend also provides the following options, i.e. the options might
|
||||
change in the future.
|
||||
The button status can be polled i.e. with <I>scanimage</I> <I>-A.</I>
|
||||
Button scan is disabled on MAC OS X due to darwin libusb not handling
|
||||
timeouts in usb interrupt reads, but may work when using the network
|
||||
|
@ -377,11 +377,11 @@
|
|||
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -288,11 +288,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
@ -311,7 +311,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-find-scanner.1.html">sane-find-scanner(1)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>,
|
||||
<B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>
|
||||
<I>/usr/local/share/doc/sane-backends/plustek/Plustek-USB.changes</I>
|
||||
|
||||
|
||||
|
|
|
@ -322,11 +322,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -69,11 +69,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -56,11 +56,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -42,10 +42,10 @@
|
|||
|
||||
<B>Scan</B> <B>Mode</B> <B>Options</B>
|
||||
|
||||
<B>--mode</B> selects the basic mode of operation of the scanner valid choices
|
||||
are <I>R</I> <I>Color</I>, <I>Gray</I> and <I>Lineart</I> The default mode is Color. The
|
||||
Lineart mode is black and white only (1 bit). Grayscale will
|
||||
produce 256 levels of gray (8 bits). Color mode allows for over
|
||||
<B>--mode</B> selects the basic mode of operation of the scanner. Valid
|
||||
choices are <I>Color</I>, <I>Gray</I> and <I>Lineart</I>. The default mode is <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 in-
|
||||
formation.
|
||||
|
||||
|
|
|
@ -53,11 +53,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -99,7 +99,7 @@
|
|||
$ chmod 660 /dev/sg0
|
||||
|
||||
When your system uses the device filesystem (devfs), you have to edit
|
||||
There you should search the line
|
||||
<I>/etc/devfs/perms.</I> There you should search the line
|
||||
|
||||
REGISTER ^sg[^/]* PERMISSIONS root.root 0600
|
||||
|
||||
|
@ -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 directory. The scanner should then be accessi-
|
||||
ble 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>
|
||||
|
|
|
@ -49,11 +49,11 @@
|
|||
|
||||
<I>special</I>
|
||||
|
||||
Where <I>special</I> is either the path-name for the special device that cor-
|
||||
responds 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.
|
||||
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 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>
|
||||
|
|
|
@ -43,11 +43,9 @@
|
|||
supported by the scanner dependent on the scanning-mode and other op-
|
||||
tions. Unsupported options are disabled.
|
||||
|
||||
The following options are supported by the Microtek2-driver:
|
||||
|
||||
Color, grayscale, halftone and lineart scans.
|
||||
|
||||
contrast, brightness, control, gamma correction.
|
||||
The following options are supported by the <B>sane-sm3600</B> backend: Color,
|
||||
grayscale, halftone and lineart scans. Also contrast, brightness, and
|
||||
gamma correction.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
@ -83,6 +81,7 @@
|
|||
export SANE_DEBUG_SM3600=5
|
||||
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B><B>,</B> <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B>, <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B>
|
||||
|
|
|
@ -75,11 +75,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -44,7 +44,7 @@
|
|||
|
||||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B><B>,</B> <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B><B>,</B> <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>
|
||||
Fujitsu ScanPartner 15C OEM Manual, Doc. No. 250-0081-0
|
||||
Fujitsu M3096G OEM Manual, part number 50FH5028E-05
|
||||
Fujitsu M3096GX/M3093GX/M3093DG OEM Manual, part number C150-E015...03
|
||||
|
|
|
@ -42,11 +42,11 @@
|
|||
|
||||
<I>special</I>
|
||||
|
||||
Where <I>special</I> is either the path-name for the special device that cor-
|
||||
responds to a SCSI scanner. For SCSI scanners, the special device name
|
||||
must be a generic SCSI device or a symlink to such a device. Under
|
||||
Linux, such a device name could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example.
|
||||
See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details.
|
||||
Where <I>special</I> is the path-name for the special device that corresponds
|
||||
to a SCSI scanner. For SCSI scanners, the special device name must be a
|
||||
generic SCSI device or a symlink to such a device. Under Linux, such a
|
||||
device name could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example. See
|
||||
<B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
@ -91,11 +91,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -149,7 +149,7 @@
|
|||
|
||||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<B>sane(7),</B> <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="xcam.1.html">xcam(1)</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="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="xcam.1.html">xcam(1)</A></B>
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
|
@ -58,11 +58,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -69,10 +69,12 @@
|
|||
<B>Scan</B> <B>Mode</B>
|
||||
|
||||
<B>--mode</B> <B>Black</B> <B>&</B> <B>White|Grayscale|Color</B>
|
||||
Selects the basic mode of operation of the scanner valid choices
|
||||
are The <I>Black</I> <I>&</I> <I>White</I> mode is black and white only (1 bit).
|
||||
Selects the basic mode of operation of the scanner. Valid
|
||||
choices are <I>Black</I> <I>&</I> <I>White</I>, <I>Grayscale</I> and <I>Color</I>.
|
||||
|
||||
The <I>Black</I> <I>&</I> <I>White</I> mode is for black and white only (1 bit).
|
||||
<I>Grayscale</I> will produce 256 levels of gray (8 bits). <I>Color</I> will
|
||||
produce a 24 bits color image.
|
||||
produce a 24 bit color image.
|
||||
|
||||
<B>--resolution</B> <B>1..600</B>
|
||||
Selects the resolution for a scan. The scanner can do all reso-
|
||||
|
|
|
@ -82,7 +82,7 @@
|
|||
|
||||
<B>Note:</B> All values with ydpi > 300 (300 x 600) or 600 (600 x 1200)
|
||||
result in a wrong proportion for the scan. The proportion can be
|
||||
adjusted with the following imagemagick command:
|
||||
adjusted with the following <B><A HREF="convert.1.html">convert(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 ad-
|
||||
just with: convert -geometry 200%x100%
|
||||
|
@ -137,7 +137,7 @@
|
|||
|
||||
<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 i value
|
||||
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>
|
||||
|
@ -222,7 +222,7 @@
|
|||
|
||||
Michael Hoeller for testing the support for the VM356A.
|
||||
|
||||
Christoph.Hoeffner for testing the support for the VM3564 (Relisys AVEC
|
||||
Christoph Hoeffner for testing the support for the VM3564 (Relisys AVEC
|
||||
II S3 firmware 1.09).
|
||||
|
||||
14 Jul 2008 <B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B>
|
||||
|
|
|
@ -52,7 +52,7 @@
|
|||
enables a fixed width of 11 cm.
|
||||
|
||||
Setting option <B>three-pass</B> simulates a three-pass scanner. Older color
|
||||
scanners needed to scan the image once per color (reg/green/blue) to
|
||||
scanners needed to scan the image once per color (red/green/blue) to
|
||||
get the full image. Therefore, in this mode three single frames are
|
||||
transmitted in color mode.
|
||||
|
||||
|
@ -247,11 +247,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -104,11 +104,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -17,15 +17,15 @@
|
|||
|
||||
</PRE>
|
||||
<H2>ABOUT THIS FILE</H2><PRE>
|
||||
This file only is a short description of the <B>sane-umax</B> backend for
|
||||
sane! For detailed information take a look at sane-umax-doc.html (it is
|
||||
This file is only a brief description of the <B>sane-umax</B> backend for
|
||||
SANE! For detailed information take a look at sane-umax-doc.html (it is
|
||||
included in the sane source directory and in the <B><A HREF="xsane.1.html">xsane(1)</A></B> online help)!
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>DESCRIPTION</H2><PRE>
|
||||
The <B>sane-umax</B> library implements a SANE backend that provides access to
|
||||
several UMAX-SCSI-scanners and some Linotye Hell SCSI-scanners, paral-
|
||||
several UMAX-SCSI-scanners and some Linotype Hell SCSI-scanners, paral-
|
||||
lel- and USB-scanners are not (and probably will never be) supported!
|
||||
|
||||
<B>I</B> <B>suggest</B> <B>you</B> <B>hold</B> <B>one</B> <B>hand</B> <B>on</B> <B>the</B> <B>power-button</B> <B>of</B> <B>the</B> <B>scanner</B> <B>while</B>
|
||||
|
@ -72,9 +72,9 @@
|
|||
execute-request-sense:
|
||||
values: 0 = disabled, 1 = enabled
|
||||
default = 0
|
||||
If set to 1 umax_do_request_sense is called in umax_do_calibra-
|
||||
tion. This can hang the system (but has been enabled until this
|
||||
version)
|
||||
If set to 1, <B>umax_do_request_sense</B>() is called in <B>umax_do_cali-</B>
|
||||
<B>bration</B>(). This can hang the system, but has been enabled until
|
||||
this version.
|
||||
|
||||
scsi-buffer-size-min, scsi-buffer-size-max:
|
||||
values: 4096-1048576
|
||||
|
@ -101,9 +101,10 @@
|
|||
slow-speed, care-about-smearing:
|
||||
values: -1 = auto, 0 = disabled, 1 = enabled
|
||||
default = -1
|
||||
dangerous options, needed for some scanners do not changed these
|
||||
options until you really know what you do, you may destroy your
|
||||
scanner when you define wrong values for this options
|
||||
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-
|
||||
ues.
|
||||
|
||||
calibration-full-ccd:
|
||||
values: -1 = auto, 0 = disabled, 1 = enabled
|
||||
|
@ -112,7 +113,7 @@
|
|||
|
||||
calibration-width-offset:
|
||||
values: -99999 = auto, > -99999 set value
|
||||
add an offset width to the calculated with for image/ccd
|
||||
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
|
||||
|
@ -149,7 +150,7 @@
|
|||
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 mprove anything when
|
||||
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.
|
||||
|
||||
|
@ -161,9 +162,9 @@
|
|||
|
||||
</PRE>
|
||||
<H2>SCSI ADAPTER TIPS</H2><PRE>
|
||||
The ISA-SCSI-adapters that are shipped with some Umax-scanners are not
|
||||
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
|
||||
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
|
||||
|
@ -175,7 +176,7 @@
|
|||
(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>
|
||||
|
@ -200,7 +201,7 @@
|
|||
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.
|
||||
Smaller levels reduce verbosity. <B>SANE_DEBUG_UMAX</B> values:
|
||||
|
||||
Number Remark
|
||||
0 print important errors (printed each time)
|
||||
|
|
|
@ -162,11 +162,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -67,11 +67,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
|
|
@ -20,7 +20,7 @@
|
|||
The <B>sane-xerox_mfp</B> library implements a SANE (Scanner Access Now Easy)
|
||||
backend that provides access to several Samsung-based Samsung, Xerox,
|
||||
and Dell scanners. Please see full list of supported devices at
|
||||
http://www.sane-project.org/sane-supported-devices.html
|
||||
<I>http://www.sane-project.org/sane-supported-devices.html</I>.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
@ -64,7 +64,7 @@
|
|||
</PRE>
|
||||
<H2>LIMITATIONS</H2><PRE>
|
||||
Multicast autoconfiguration for LAN scanners is not implemented yet.
|
||||
IPv6 addressing never been tested.
|
||||
IPv6 addressing has never been tested.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
130
man/sane.7.html
130
man/sane.7.html
|
@ -46,7 +46,7 @@
|
|||
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>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
|
||||
<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.
|
||||
|
||||
|
@ -87,7 +87,7 @@
|
|||
|
||||
<B>SANE</B> <B>IRC</B> <B>channel</B>
|
||||
The IRC (Internet Relay Chat) channel #sane can be found on the
|
||||
Freenode network (irc.freenode.net). It's for discussing <B>SANE</B> prob-
|
||||
Freenode network (irc.libera.chat). It's for discussing <B>SANE</B> prob-
|
||||
lems, talking about development and general <B>SANE</B> related chatting.
|
||||
Before asking for help, please read the other documentation mentioned
|
||||
in this manual page. The channel's topic is also used for announce-
|
||||
|
@ -178,8 +178,8 @@
|
|||
<B><A HREF="sane-canon_dr.5.html">sane-canon_dr(5)</A></B> for details.
|
||||
|
||||
<B>canon_lide70</B>
|
||||
Supports the CanoScan LiDE 70 USB scanner. See <B><A HREF="sane-canon_lide70.5.html">sane-canon_lide70(5)</A></B>
|
||||
for details.
|
||||
Supports the CanoScan LiDE 70 and 600 USB scanners. See
|
||||
<B><A HREF="sane-canon_lide70.5.html">sane-canon_lide70(5)</A></B> for details.
|
||||
|
||||
<B>canon_pp</B>
|
||||
Supports the CanoScan FB330P, FB630P, N340P and N640P parallel port
|
||||
|
@ -198,8 +198,13 @@
|
|||
details.
|
||||
|
||||
<B>epson</B>
|
||||
Supports Epson SCSI, parallel port and USB flatbed scanners. See
|
||||
<B><A HREF="sane-epson.5.html">sane-epson(5)</A></B> for details.
|
||||
Old driver for Epson SCSI, parallel port and USB flatbed scanners.
|
||||
See <B><A HREF="sane-epson.5.html">sane-epson(5)</A></B> for details but try <B>epson2</B> first.
|
||||
|
||||
<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>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 de-
|
||||
|
@ -212,14 +217,14 @@
|
|||
<B>genesys</B>
|
||||
Supports several scanners based on the Genesys Logic GL646, GL841,
|
||||
GL843, GL847 and GL124 chips like the Medion 6471 and Hewlett-Packard
|
||||
2300c.
|
||||
See <B><A HREF="sane-genesys.5.html">sane-genesys(5)</A></B> for details.
|
||||
2300c. See <B><A HREF="sane-genesys.5.html">sane-genesys(5)</A></B> for details.
|
||||
|
||||
<B>gt68xx</B>
|
||||
Supports scanners based on the Grandtech GT-6801 and GT-6816 chips
|
||||
like the Artec Ultima 2000 and several Mustek BearPaw CU and TA mod-
|
||||
els. Some Genius, Lexmark, Medion, Packard Bell, Plustek, and Trust
|
||||
scanners are also supported. See <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B> for details.
|
||||
els.
|
||||
Some Genius, Lexmark, Medion, Packard Bell, Plustek, and Trust scan-
|
||||
ners are also supported. See <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B> for details.
|
||||
|
||||
<B>hp</B>
|
||||
Supports Hewlett-Packard ScanJet scanners which utilize SCL (Scanner
|
||||
|
@ -247,7 +252,7 @@
|
|||
|
||||
<B>hpljm1005</B>
|
||||
Supports the Hewlett-Packard LaserJet M1005 scanner. See
|
||||
<B>sane-hpljm1005(5)</B> for details.
|
||||
<B><A HREF="sane-hpljm1005.5.html">sane-hpljm1005(5)</A></B> for details.
|
||||
|
||||
<B>hs2p</B>
|
||||
Supports the Ricoh IS450 family of SCSI scanners. See <B><A HREF="sane-hs2p.5.html">sane-hs2p(5)</A></B>
|
||||
|
@ -458,8 +463,8 @@
|
|||
|
||||
<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 net backend. See
|
||||
<B><A HREF="sane-net.5.html">sane-net(5)</A></B> and <B><A HREF="saned.8.html">saned(8)</A></B>.
|
||||
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-
|
||||
|
@ -574,80 +579,81 @@
|
|||
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 de-
|
||||
bug messages for the dll backend tell if the mustek backend was found
|
||||
and loaded at all. The mustek messages explain what the mustek backend
|
||||
is doing while the SCSI debugging shows the low level handling. If you
|
||||
can't find out what's going on by checking the messages carefully, con-
|
||||
tact the sane-devel mailing list for help (see REPORTING BUGS below).
|
||||
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>>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>>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> de-
|
||||
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(1)</B> works and you want to use one of the
|
||||
graphical frontends like <B>xsane(1)</B>, <B>xscanimage(1)</B>, or <B>quiteinsane(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/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.
|
||||
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 in-
|
||||
stalled by your distribution in <I>/usr</I> and one you installed from source
|
||||
in <I>/usr/local/</I>. Make sure that only one version is installed. Another
|
||||
possible reason is, that your system's dynamic loader can't find the
|
||||
<B>SANE</B> libraries. For Linux, make sure that <I>/etc/ld.so.conf</I> contains
|
||||
<I>/usr/local/lib</I> and does <B>not</B> contain <I>/usr/local/lib/sane</I>. See also the
|
||||
documentation of the frontends.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>HOW CAN YOU HELP SANE</H2><PRE>
|
||||
We appreciate any help we can get. Please have a look at our web page
|
||||
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>sane-ag-</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-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-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>sane-lex-</B>
|
||||
<B><A HREF="mark.5.html">mark(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>sane-plus-</B>
|
||||
<B><A HREF="tek_pp.5.html">tek_pp(5)</A></B>, <B><A HREF="sane-pnm.5.html">sane-pnm(5)</A></B>, <B><A HREF="sane-qcam.5.html">sane-qcam(5)</A></B>, <B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B>, <B><A HREF="sane-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="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-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>sane-plus-</B>
|
||||
<B><A HREF="tek_pp.5.html">tek_pp(5)</A></B>, <B><A HREF="sane-pnm.5.html">sane-pnm(5)</A></B>, <B><A HREF="sane-qcam.5.html">sane-qcam(5)</A></B>, <B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B>, <B><A HREF="sane-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>
|
||||
|
@ -656,8 +662,8 @@
|
|||
</PRE>
|
||||
<H2>AUTHOR</H2><PRE>
|
||||
David Mosberger-Tang and many many more (see <I>/usr/local/share/doc/sane-</I>
|
||||
<I>backends/AUTHORS</I> for details). This man page was written by Henning
|
||||
Meier-Geinitz. Quite a lot of text was taken from the <B>SANE</B> standard,
|
||||
<I>backends/AUTHORS</I> for details). This man page was written by Henning
|
||||
Meier-Geinitz. Quite a lot of text was taken from the <B>SANE</B> standard,
|
||||
several man pages, and README files.
|
||||
|
||||
03 Jan 2020 <B><A HREF="sane.7.html">sane(7)</A></B>
|
||||
|
|
|
@ -30,30 +30,52 @@
|
|||
|
||||
</PRE>
|
||||
<H2>OPTIONS</H2><PRE>
|
||||
The <B>-l</B> flag 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. The <B>-b</B> flag tells <B>saned</B>
|
||||
to bind to the <I>address</I> given. The <B>-p</B> flags tells <B>saned</B> to listen on
|
||||
the port given. A value of 0 tells <B>saned</B> to pick an unused port. The
|
||||
default is the <B>sane-port</B> <B>(6566).</B> The <B>-u</B> flag requests that <B>saned</B> drop
|
||||
root privileges and run as the user (and group) associated with <I>user-</I>
|
||||
<I>name</I> after binding. The <B>-D</B> flag will request <B>saned</B> to detach from the
|
||||
console and run in the background. The flag <B>-a</B> is equivalent to the
|
||||
combination of <B>-l</B> <B>-B</B> <B>-u</B> <I>username</I> options.
|
||||
<B>saned</B> recognises the following options:
|
||||
|
||||
The <B>-d</B> flag sets the level of <B>saned</B> debug output. 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 default value is 2.
|
||||
<B>-a</B> <I>[username]</I>, <B>--alone</B>[=<I>username]</I>
|
||||
is equivalent to the combination of <B>-l</B> <B>-D</B> <B>-u</B> <I>username</I> options.
|
||||
However, <I>username</I> is optional and running user will only be set
|
||||
when specified.
|
||||
|
||||
The <B>-e</B> flag will divert <B>saned</B> debug output to stderr instead of the
|
||||
syslog default.
|
||||
<B>-u</B> <I>username</I>, <B>--user</B>=<I>username</I>
|
||||
requests that <B>saned</B> drop root privileges and run as the user
|
||||
(and group) associated with <I>username</I> after binding.
|
||||
|
||||
The <B>-o</B> flag requests that <B>saned</B> exits after the first client discon-
|
||||
nects. This is useful for debugging.
|
||||
<B>-b</B> <I>address</I>, <B>--bind</B>=<I>address</I>
|
||||
tells <B>saned</B> to bind to the <I>address</I> given.
|
||||
|
||||
The <B>-h</B> flag displays a short help message.
|
||||
<B>-p</B> <I>port</I>, <B>--port=</B><I>port</I>
|
||||
tells <B>saned</B> to listen on the <I>port</I> given. A value of 0 tells
|
||||
<B>saned</B> to pick an unused port. The default is the <B>sane-port</B>
|
||||
<B>(6566).</B>
|
||||
|
||||
<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>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
|
||||
background.
|
||||
|
||||
<B>-o</B>, <B>--once</B>
|
||||
requests that <B>saned</B> exits after the first client disconnects.
|
||||
This is useful for debugging.
|
||||
|
||||
<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 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>-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-
|
||||
|
@ -181,10 +203,10 @@
|
|||
|
||||
</PRE>
|
||||
<H2>SYSTEMD CONFIGURATION</H2><PRE>
|
||||
<B>saned</B> can be compiled with explicit <B><A HREF="systemd.1.html">systemd(1)</A></B><B>support.</B>This will allow
|
||||
<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.
|
||||
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.
|
||||
|
@ -196,7 +218,7 @@
|
|||
</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>
|
||||
<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:
|
||||
|
@ -235,7 +257,7 @@
|
|||
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
|
||||
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 de-
|
||||
sired debugging information if required. Multiple variables can be set
|
||||
by separating the assignments by spaces as shown in the example above.
|
||||
|
@ -250,11 +272,11 @@
|
|||
</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><B>integration</B>support,<B>but</B>it<B>does</B>not<B>allow</B>debugging information to be
|
||||
logged.
|
||||
<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>
|
||||
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
|
||||
|
@ -271,8 +293,8 @@
|
|||
[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:
|
||||
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
|
||||
|
@ -315,11 +337,11 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in <I>/usr/lo-</I>
|
||||
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/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.
|
||||
|
@ -331,7 +353,7 @@
|
|||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<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="xcam.1.html">xcam(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), <B><A HREF="inetd.8.html">inetd(8)</A></B>, <B><A HREF="xinetd.8.html">xinetd(8)</A></B>, <B><A HREF="systemd.1.html">systemd(1)</A></B>,
|
||||
<B><A HREF="sane-net.5.html">sane-net(5)</A></B>, <B>sane-"backendname"</B>(5), <B><A HREF="inetd.8.html">inetd(8)</A></B>, <B><A HREF="xinetd.8.html">xinetd(8)</A></B>, <B><A HREF="systemd.1.html">systemd(1)</A></B>
|
||||
<I>http://www.penguin-breeder.org/?page=sane-net</I>
|
||||
|
||||
|
||||
|
|
|
@ -19,9 +19,9 @@
|
|||
<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>-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>] [<B>-n</B>|<B>--dont-scan</B>] [<B>-T</B>|<B>--test</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>]
|
||||
|
||||
|
@ -63,211 +63,256 @@
|
|||
|
||||
</PRE>
|
||||
<H2>OPTIONS</H2><PRE>
|
||||
There are two sets of options available when running <B>scanimage</B>.
|
||||
|
||||
The options that are provided by <B>scanimage</B> itself are listed below. In
|
||||
addition, each backend offers its own set of options and these can also
|
||||
be specified. Note that the options available from the backend may vary
|
||||
depending on the scanning device that is selected.
|
||||
|
||||
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 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> <B>epson</B>) and by a "=" from multi-character options (e.g. <B>--de-</B>
|
||||
<B>vice-name=epson</B>).
|
||||
<B>-d</B> <I>epson</I><B>)</B> and by a "=" from multi-character options (e.g. <B>--de-</B>
|
||||
<B>vice-name</B>=<I>epson</I><B>).</B>
|
||||
|
||||
The <B>-d</B> or <B>--device-name</B> options must be followed by a SANE device-name
|
||||
like `<I>epson:/dev/sg0</I>' or `<I>hp:/dev/usbscanner0</I>'. A (partial) list of
|
||||
available devices can be obtained with the <B>--list-devices</B> option (see
|
||||
below). If no device-name is specified explicitly, <B>scanimage</B> reads a
|
||||
device-name from the environment variable <B>SANE_DEFAULT_DEVICE</B>. If this
|
||||
variable is not set, <B>scanimage</B> will attempt to open the first available
|
||||
device.
|
||||
<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
|
||||
device-name like `<I>epson:/dev/sg0</I>' or `<I>hp:/dev/usbscanner0</I>'. A
|
||||
(partial) list of available devices can be obtained with the
|
||||
<B>--list-devices</B> option (see below). If no device-name is speci-
|
||||
fied explicitly, <B>scanimage</B> reads a device-name from the environ-
|
||||
ment variable <B>SANE_DEFAULT_DEVICE</B>. If this variable is not set,
|
||||
<B>scanimage</B> will attempt to open the first available device.
|
||||
|
||||
The <B>--format</B> <I>format</I> option selects how image data is written to stan-
|
||||
dard 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.
|
||||
<B>--format</B>=<I>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.
|
||||
|
||||
The <B>-i</B> or <B>--icc-profile</B> option is used to include an ICC profile into a
|
||||
TIFF file.
|
||||
<B>-i</B> <I>profile</I>, <B>--icc-profile</B>=<I>profile</I>
|
||||
is used to include an ICC profile into a TIFF file.
|
||||
|
||||
The <B>-L</B> or <B>--list-devices</B> option requests a (partial) list of devices
|
||||
that are available. The list is not complete since some devices may be
|
||||
available, but are not listed in any of the configuration files (which
|
||||
are typically stored in directory <I>/usr/local/etc/sane.d</I>). This is par-
|
||||
ticularly the case when accessing scanners through the network. If a
|
||||
device is not listed in a configuration file, the only way to access it
|
||||
is by its full device name. You may need to consult your system admin-
|
||||
istrator to find out the names of such devices.
|
||||
<B>-L</B>, <B>--list-devices</B>
|
||||
requests a (partial) list of devices that are available. The
|
||||
list may not be complete since some devices may be available,
|
||||
but are not listed in any of the configuration files (which are
|
||||
typically stored in directory <I>/usr/local/etc/sane.d</I>). This is
|
||||
particularly the case when accessing scanners through the net-
|
||||
work. If a device is not listed in a configuration file, the
|
||||
only way to access it is by its full device name. You may need
|
||||
to consult your system administrator to find out the names of
|
||||
such devices.
|
||||
|
||||
The <B>-f</B> or <B>--formatted-device-list</B> option works similar to <B>--list-de-</B>
|
||||
<B>vices</B>, but requires a format string. <B>scanimage</B> replaces the placehold-
|
||||
ers <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
|
||||
<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>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
|
||||
|
||||
<B>scanimage</B> <B>-f</B> <I>"</I> <I>scanner</I> <I>number</I> <I>%i</I> <I>device</I> <I>%d</I> <I>is</I> <I>a</I> <I>%t,</I> <I>model</I> <I>%m,</I>
|
||||
<B>scanimage</B> <B>-f</B> <I>"</I> <I>scanner</I> <I>number</I> <I>%i</I> <I>device</I> <I>%d</I> <I>is</I> <I>a</I> <I>%t,</I> <I>model</I> <I>%m,</I>
|
||||
<I>produced</I> <I>by</I> <I>%v</I> <I>"</I>
|
||||
|
||||
will produce something like:
|
||||
will produce something like:
|
||||
|
||||
scanner number 0 device sharp:/dev/sg1 is a flatbed scanner,
|
||||
model JX250 SCSI, produced by SHARP
|
||||
scanner number 0 device sharp:/dev/sg1 is a flatbed
|
||||
scanner, model JX250 SCSI, produced by SHARP
|
||||
|
||||
The <B>--batch*</B> options provide the features for scanning documents using
|
||||
document feeders. <B>--batch</B> [<I>format</I>] is used to specify the format of
|
||||
the filename that each page will be written to. Each page is written
|
||||
out to a single file. If <I>format</I> is not specified, the default of
|
||||
<I>out%d.pnm</I> (or <I>out%d.tif</I> for <B>--format</B> <B>tiff</B>, <I>out%d.png</I> for <B>--format</B> <B>png</B>
|
||||
or <I>out%d.jpg</I> for <B>--format</B> <B>jpeg</B>) will be used. This option is incompat-
|
||||
ible with the <B>--output-path</B> 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. <B>--batch-count</B> <I>count</I> specifies the number
|
||||
of pages to attempt to scan. If not given, scanimage will continue
|
||||
scanning until the scanner returns a state other than OK. Not all
|
||||
scanners with document feeders signal when the ADF is empty, use this
|
||||
command to work around them. With <B>--batch-increment</B> <I>increment</I> you can
|
||||
change the amount that the number in the filename is incremented by.
|
||||
Generally this is used when you are scanning double-sided documents on
|
||||
a single-sided document feeder. A specific command is provided to aid
|
||||
this: <B>--batch-double</B> will automatically set the increment to 2.
|
||||
<B>--batch-prompt</B> will ask for pressing RETURN before scanning a page.
|
||||
This can be used for scanning multiple pages without an automatic docu-
|
||||
ment feeder.
|
||||
The <B>--batch*</B> options provide features for scanning documents using doc-
|
||||
ument feeders.
|
||||
|
||||
The <B>--accept-md5-only</B> option only accepts user authorization requests
|
||||
that support MD5 security. The <B>SANE</B> network daemon (<B>saned</B>) is capable
|
||||
of doing such requests. See <B><A HREF="saned.8.html">saned(8)</A></B>.
|
||||
<B>-b</B> [<I>format</I>], <B>--batch</B>=[<I>format</I>]
|
||||
is used to specify the format of the filename that each
|
||||
page will be written to. Each page is written out to a
|
||||
single file. If <I>format</I> is not specified, the default of
|
||||
<I>out%d.pnm</I> (or <I>out%d.tif</I> for <B>--format</B> <B>tiff</B>, <I>out%d.png</I> for
|
||||
<B>--format</B> <B>png</B> or <I>out%d.jpg</I> for <B>--format</B> <B>jpeg</B>) will be
|
||||
used. This option is incompatible with the <B>--output-path</B>
|
||||
option. <I>format</I> is given as a printf style string with
|
||||
one integer parameter.
|
||||
|
||||
The <B>-p</B> or <B>--progress</B> option requests that <B>scanimage</B> prints a progress
|
||||
counter. It shows how much image data of the current image has already
|
||||
been received by <B>scanimage</B> (in percent).
|
||||
|
||||
The <B>-o</B> or <B>--output-file</B> option requests that <B>scanimage</B> saves the scan-
|
||||
ning output to the given path. This option is incompatible with the
|
||||
--batch option. The program will try to guess <B>--format</B> from the file
|
||||
name. If that is not possible, it will print an error message and exit.
|
||||
<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.
|
||||
|
||||
The <B>-n</B> or <B>--dont-scan</B> option requests that <B>scanimage</B> only sets the op-
|
||||
tions provided by the user but doesn't actually perform a scan. This
|
||||
option can be used to e.g. turn off the scanner's lamp (if supported by
|
||||
the backend).
|
||||
<B>--batch-count</B>=<I>count</I>
|
||||
specifies the number of pages to attempt to scan. If not
|
||||
given, <B>scanimage</B> will continue scanning until the scanner
|
||||
returns a state other than OK. Not all scanners with
|
||||
document feeders signal when the ADF is empty. Use this
|
||||
option to work around them.
|
||||
|
||||
The <B>-T</B> or <B>--test</B> option requests that <B>scanimage</B> performs a few simple
|
||||
sanity tests to make sure the backend works as defined by the <B>SANE</B> API
|
||||
(in particular the <B>sane_read</B>() function is exercised by this test).
|
||||
<B>--batch-increment</B>=<I>increment</I>
|
||||
sets the amount that the number in the filename is incre-
|
||||
mented by. Generally this is used when you are scanning
|
||||
double-sided documents on a single-sided document feeder.
|
||||
<B>--batch-double</B> is a specific command provided to aid
|
||||
this.
|
||||
|
||||
The <B>-A</B> or <B>--all-options</B> option requests that <B>scanimage</B> lists all avail-
|
||||
able options exposed the backend, including button options. The infor-
|
||||
mation is printed on standard output and no scan will be done.
|
||||
<B>--batch-double</B>
|
||||
will automatically set the increment to 2. Equivalent to
|
||||
<B>--batch-increment</B>=2
|
||||
|
||||
The <B>-h</B> or <B>--help</B> options request help information. The information is
|
||||
printed on standard output and in this case, no attempt will be made to
|
||||
acquire an image.
|
||||
<B>--batch-prompt</B>
|
||||
will ask for pressing RETURN before scanning a page. This
|
||||
can be used for scanning multiple pages without an auto-
|
||||
matic document feeder.
|
||||
|
||||
The <B>-v</B> or <B>--verbose</B> options increase the verbosity of the operation of
|
||||
<B>scanimage.</B> The option may be specified repeatedly, each time increas-
|
||||
ing the verbosity level.
|
||||
<B>--accept-md5-only</B>
|
||||
only accepts user authorization requests that support MD5 secu-
|
||||
rity. The <B>SANE</B> network daemon <B><A HREF="saned.8.html">saned(8)</A></B> is capable of doing such
|
||||
requests.
|
||||
|
||||
The <B>-B</B> option without argument changes the input buffer size from the
|
||||
default 32KB to 1MB. For finer grained control, use <B>--buffer-size=</B>
|
||||
followed by the number of KB.
|
||||
<B>-p</B>, <B>--progress</B>
|
||||
requests that <B>scanimage</B> prints a progress counter. It shows how
|
||||
much image data of the current image has already been received
|
||||
(in percent).
|
||||
|
||||
The <B>-V</B> or <B>--version</B> option 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. Usually that's
|
||||
the dll backend. If more information about the version numbers of the
|
||||
backends are necessary, the <B>DEBUG</B> variable for the dll backend 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>
|
||||
<B>-o</B> <I>path</I>, <B>--output-file</B>=<I>path</I>
|
||||
requests that <B>scanimage</B> saves the scanning output to the given
|
||||
<I>path</I>. This option is incompatible with the <B>--batch</B> option. The
|
||||
program will try to guess <B>--format</B> from the file name. If that
|
||||
is not possible, it will print an error message and exit.
|
||||
|
||||
As you might imagine, much of the power of <B>scanimage</B> comes from the
|
||||
<B>-n</B>, <B>--dont-scan</B>
|
||||
requests that <B>scanimage</B> only sets the options provided by the
|
||||
user but doesn't actually perform a scan. This option can be
|
||||
used to e.g. turn off the scanner's lamp (if supported by the
|
||||
backend).
|
||||
|
||||
<B>-T</B>, <B>--test</B>
|
||||
requests that <B>scanimage</B> performs a few simple sanity tests to
|
||||
make sure the backend works as defined by the <B>SANE</B> API. In par-
|
||||
ticular the <B>sane_read</B>() function is exercised by this test.
|
||||
|
||||
<B>-A</B>, <B>--all-options</B>
|
||||
requests that <B>scanimage</B> lists all available options exposed by
|
||||
the backend, including button options. The information is
|
||||
printed on standard output and no scan will be performed.
|
||||
|
||||
<B>-h</B>, <B>--help</B>
|
||||
requests help information. The information is printed on stan-
|
||||
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
|
||||
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>-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>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> <I>.</I>
|
||||
|
||||
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.
|
||||
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
|
||||
(-t), width (-x) and height of scan-area (-y).
|
||||
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.
|
||||
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.
|
||||
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 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>
|
||||
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).
|
||||
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
|
||||
used.
|
||||
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><string></B> <B>[/tmp/input.ppm]</B>
|
||||
The filename of the image to be loaded.
|
||||
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>.
|
||||
|
@ -282,7 +327,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>
|
||||
|
@ -291,28 +336,28 @@
|
|||
user:password:resource
|
||||
|
||||
<B>scanimage</B> uses this information to answer user authorization re-
|
||||
quests automatically. The file must have 0600 permissions or
|
||||
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
|
||||
<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>xcam(1)</B>, <B>xsane(1)</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>,</B> <B><A HREF="xsane.1.html">xsane(1)</A></B><B>,</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)
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>AUTHOR</H2><PRE>
|
||||
David Mosberger, Andreas Beck, Gordon Matzigkeit, Caskey Dickson, and
|
||||
many others. For questions and comments contact the sane-devel mail-
|
||||
David Mosberger, Andreas Beck, Gordon Matzigkeit, Caskey Dickson, and
|
||||
many others. For questions and comments contact the sane-devel mail-
|
||||
inglist (see <I>http://www.sane-project.org/mailing-lists.html</I>).
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>BUGS</H2><PRE>
|
||||
For vector options, the help output currently has no indication as to
|
||||
For vector options, the help output currently has no indication as to
|
||||
how many elements a vector-value should have.
|
||||
|
||||
10 Jul 2008 <B><A HREF="scanimage.1.html">scanimage(1)</A></B>
|
||||
|
|
Plik diff jest za duży
Load Diff
Plik diff jest za duży
Load Diff
2965
sane-mfgs.html
2965
sane-mfgs.html
Plik diff jest za duży
Load Diff
|
@ -92,7 +92,8 @@
|
|||
</p>
|
||||
<p>
|
||||
SANE version:
|
||||
<a href="sane-backends-1.0.31.html">1.0.30</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>,
|
||||
<a href="sane-backends-1.0.30.html">1.0.30</a>,
|
||||
<a href="sane-backends-1.0.29.html">1.0.29</a>,
|
||||
<a href="sane-backends-1.0.28.html">1.0.28</a>,
|
||||
|
|
Ładowanie…
Reference in New Issue