kopia lustrzana https://gitlab.com/sane-project/website
Updated scanner lists and man pages from sane-backends 1.0.18.
Henning Geinitz
rodzic
7ef0780753
commit
ad12152962
|
|
@ -71,7 +71,7 @@
|
|||
<H2>EMAIL-CONTACT</H2><PRE>
|
||||
Oliver.Rauch@Rauch-Domain.DE
|
||||
|
||||
sane-backends 1.0.17 11 Sep 2002 <B><A HREF="gamma4scanimage.1.html">gamma4scanimage(1)</A></B>
|
||||
sane-backends 1.0.18 11 Sep 2002 <B><A HREF="gamma4scanimage.1.html">gamma4scanimage(1)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -142,7 +142,7 @@
|
|||
The sane-abaton backend was partially written by David Huggins-Daines,
|
||||
based on the sane-apple backend by Milon Firikis.
|
||||
|
||||
sane-backends 1.0.17 19 Nov 1998 <B><A HREF="sane-abaton.5.html">sane-abaton(5)</A></B>
|
||||
sane-backends 1.0.18 19 Nov 1998 <B><A HREF="sane-abaton.5.html">sane-abaton(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -178,7 +178,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
Ingo Schneider and Karl Anders Øygard.
|
||||
|
||||
sane-backends 1.0.17 17 Oct 1998 <B><A HREF="sane-agfafocus.5.html">sane-agfafocus(5)</A></B>
|
||||
sane-backends 1.0.18 17 Oct 1998 <B><A HREF="sane-agfafocus.5.html">sane-agfafocus(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -48,13 +48,13 @@
|
|||
|
||||
</PRE>
|
||||
<H2>CONFIGURATION</H2><PRE>
|
||||
The contents of the <I>apple.conf</I> file is a list of options and device
|
||||
names that correspond to Apple scanners. Empty lines and lines start-
|
||||
ing with a hash mark (#) are ignored. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> on details of
|
||||
what constitutes a valid device name.
|
||||
The <I>apple.conf</I> file is a list of options and device names that corre-
|
||||
spond to Apple scanners. Empty lines and lines starting with a hash
|
||||
mark (#) are ignored. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> on details of what constitutes
|
||||
a valid device name.
|
||||
|
||||
Options come in two flavors: global and positional ones. Global
|
||||
options apply to all devices managed by the backend whereas positional
|
||||
options apply to all devices managed by the backend, whereas positional
|
||||
options apply just to the most recently mentioned device. Note that
|
||||
this means that the order in which the options appear matters!
|
||||
|
||||
|
|
@ -63,9 +63,9 @@
|
|||
<H2>SCSI ADAPTER TIPS</H2><PRE>
|
||||
SCSI scanners are typically delivered with an ISA SCSI adapter. Unfor-
|
||||
tunately, that adapter is not worth much since it is not interrupt
|
||||
driven. It is (sometimes) possible to get the supplied card to work,
|
||||
but without interrupt line, scanning will put so much load on the sys-
|
||||
tem, that it becomes almost unusable for other tasks.
|
||||
driven. It is sometimes possible to get the supplied card to work, but
|
||||
without an interrupt line, scanning will put so much load on the system
|
||||
that it becomes almost unusable for other tasks.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -85,128 +85,125 @@
|
|||
</PRE>
|
||||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in
|
||||
/usr/local/etc/sane.d. If the value of the environment variable
|
||||
ends with the directory separator character, then the default
|
||||
directories are searched after the explicitly specified directo-
|
||||
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
|
||||
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
|
||||
(`;'). If SANE_CONFIG_DIR is not set, SANE defaults to search-
|
||||
ing the current working directory (".") and then /etc/sane.d.
|
||||
If the value of $SANE_CONFIG_DIR ends with the separator charac-
|
||||
ter, the default directories are searched after the directory
|
||||
list. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
|
||||
would result in directories "tmp/config", ".", and
|
||||
"/usr/local/etc/sane.d" being searched (in this order).
|
||||
"/usr/local/etc/sane.d" being searched (in that order).
|
||||
|
||||
<B>SANE_DEBUG_APPLE</B>
|
||||
If the library was compiled with debug support enabled, this
|
||||
environment variable controls the debug level for this backend.
|
||||
E.g., a value of 255 requests all debug output to be printed.
|
||||
Smaller levels reduce verbosity.
|
||||
Controls the debug level. A value of 255 prints all debug out-
|
||||
put. Smaller values reduce verbosity. Requires a library com-
|
||||
piled with debug support.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CURRENT STATUS</H2><PRE>
|
||||
The apple backend is now in version 0.3 (Tue Jul 21 1998). Since I only
|
||||
have the AppleScanner and not the other models (OneScanner, ColorOneS-
|
||||
have the AppleScanner and not the other models (OneScanner, ColorOneS-
|
||||
canner) I can only develop/test for the AppleScanner effectively. How-
|
||||
ever with this release I almost complete the gui part of all scanners.
|
||||
Most of the functionality is there. At least OneScanner should scan at
|
||||
the AppleScanner's compatible modes (LineArt, HalfTone, Gray16). My
|
||||
ever with this release I almost completed the gui part of all scanners.
|
||||
Most of the functionality is there. At least OneScanner should scan at
|
||||
the AppleScanner's compatible modes (LineArt, HalfTone, Gray16). My
|
||||
personal belief is that with a slight touch of debugging the OneScanner
|
||||
could be actually usable. The ColorOneScanner needs more work. AppleS-
|
||||
could be actually usable. The ColorOneScanner needs more work. AppleS-
|
||||
canner is of course almost fully supported.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>MISSING FUNCTIONALITY</H2><PRE>
|
||||
Currently all 3 models are lacking upload/dowload support.
|
||||
Currently all three models lack upload/download support.
|
||||
|
||||
<B>AppleScanner</B>
|
||||
Cannot up/download a halftone pattern.
|
||||
|
||||
<B>OneScanner</B>
|
||||
Cannot up/download halftone pattern and calibration vector.
|
||||
Cannot up/download halftone patterns or calibration vectors.
|
||||
|
||||
<B>ColorOneScanner</B>
|
||||
Cannot up/download halftone pattern, calibration vectors, custom
|
||||
Color Correction Table (CCT) and of course custom gamma tables.
|
||||
Cannot up/download halftone patterns, calibration vectors, cus-
|
||||
tom Color Correction Tables (CCT) and of course custom gamma
|
||||
tables.
|
||||
|
||||
<B>Park/UnPark</B> <B>(OneScanner,</B> <B>ColorOneScanner)</B>
|
||||
|
||||
The above functionalities are not only missing because I don't actually
|
||||
have the hardware to experiment on it. Another reason is the lack of
|
||||
understanding of how SANE API could provide enaugh means to me to actu-
|
||||
ally describe other array types than the gamma one.
|
||||
The above functionalities are missing because I don't have the hardware
|
||||
to experiment on. Another reason is my lack of understanding as to how
|
||||
or if the SANE API provide means to describe any array type besides
|
||||
gamma.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>UNSUPPORTED FEATURES</H2><PRE>
|
||||
The following "features" will never be supported. At least as I am
|
||||
maintaining the sane-apple backend.
|
||||
The following "features" will never be supported, at least while I
|
||||
maintain the sane-apple backend.
|
||||
|
||||
<B>NoHome</B> <B>(AppleScanner)</B>
|
||||
The scanner lamp stays on and the carriage assembly remains
|
||||
The scanner lamp stays on and the carriage assembly remains
|
||||
where it stops at the end of the scan. After two minutes, if the
|
||||
scanner does not receive another SCAN command the lamp goes off
|
||||
scanner does not receive another SCAN command, the lamp goes off
|
||||
and the carriage returns to the home position.
|
||||
|
||||
<B>Compression</B> <B>(AppleScanner)</B>
|
||||
The Scanner can compress data with CCITT Group III, one dimen-
|
||||
sional algorithm (fax), and the Skip White Line algorithm.
|
||||
The Scanner can compress data with CCITT Group III one dimen-
|
||||
sional algorithm (fax) and the Skip White Line algorithm.
|
||||
|
||||
<B>Multiple</B> <B>Windows</B> <B>(AppleScanner)</B>
|
||||
AppleScanner may support multiple windows. It would be a cool
|
||||
feature and a challenge for me to code it if you could intermix
|
||||
different options for different windows (scan areas). This way
|
||||
you could scan a document in LineArt mode but the figures in it
|
||||
on Gray and in a different resolution. Unfortunately this is
|
||||
AppleScanner may support multiple windows. It would be a cool
|
||||
feature and a challenge for me to code if it could intermix dif-
|
||||
ferent options for different windows (scan areas). This way it
|
||||
could scan a document in LineArt mode but the figures in it in
|
||||
Gray and at a different resolution. Unfortunately this is
|
||||
impossible.
|
||||
|
||||
<B>Scan</B> <B>Direction</B> <B>(OneScanner)</B>
|
||||
It controls the scan direction. (?)
|
||||
|
||||
<B>Status/Reset</B> <B>Button</B> <B>(OneScanner)</B>
|
||||
This option controls the status of the button in OneScanner
|
||||
This option controls the status of the button on the OneScanner
|
||||
model. You can also reset the button status by software.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>BUGS</H2><PRE>
|
||||
The bugs in a sane backend are divided in two classes. We have <B>GUI</B> bugs
|
||||
and <B>scanner</B> <B>specific</B> bugs.
|
||||
SANE backend bugs are divided in two classes. We have <B>GUI</B> bugs and
|
||||
<B>scanner</B> <B>specific</B> bugs.
|
||||
|
||||
We know we have a GUI bug when a parameter is not showing up itself
|
||||
when it should (active) or vice versa. To find out which parameters are
|
||||
active accross various Apple modes and models from the documentation
|
||||
We know we have a GUI bug when a parameter is not showing up when it
|
||||
should (active) or vice versa. Finding out which parameters are active
|
||||
across various Apple modes and models from the documentation
|
||||
<B>ftp://ftpdev.info.apple.com/devworld/Technical_Documentation/Peripher-</B>
|
||||
<B>als_Documentation/</B> is an interesting exercise. I may missed some depen-
|
||||
dancies. For example for the threshold parameter the Apple Scanners
|
||||
Programming guide says nothing. I had to assume that is valid only in
|
||||
<B>als_Documentation/</B> is an interesting exercise. I may have missed some
|
||||
dependencies. For example of the threshold parameter the Apple Scanners
|
||||
Programming Guide says nothing. I had to assume it is valid only in
|
||||
LineArt mode.
|
||||
|
||||
Scanner specific bugs are mostly due to mandatory round offs in order
|
||||
to scan. In the documentation in some place states that the width of
|
||||
the scan area should be a byte multiple. In an other place says that
|
||||
the width of the scan area should be an even byte multiple. Go fig-
|
||||
ure...
|
||||
Scanner specific bugs are mostly due to mandatory round-offs in order
|
||||
to scan. In the documentation in one place states that the width of the
|
||||
scan area should be a byte multiple. In another place it says that the
|
||||
width of the scan area should be an even byte multiple. Go figure...
|
||||
|
||||
Other source of bugs are due to scsi communcation, scsi connects and
|
||||
Other sources of bugs are due to scsi communication, scsi connects and
|
||||
disconnects. However the classical bugs are still there. So you may
|
||||
encouter buffer overruns, null pointers, memory corruption and <B>SANE</B> API
|
||||
violations.
|
||||
encounter buffer overruns, null pointers, memory corruption and <B>SANE</B>
|
||||
API violations.
|
||||
|
||||
<B>SIGSEGV</B> <B>on</B> <B>SliceBars</B>
|
||||
When you try to modify the scan area from the slice bar you have
|
||||
a nice little cute core dump. I don't know why. If you select
|
||||
the scan are from the preview window, or by hand typing the num-
|
||||
the scan area from the preview window or by hand typing the num-
|
||||
bers everything is fine. The SIGSEGV happens deep in gtk library
|
||||
(gdk). I really cannot debug it.
|
||||
|
||||
<B>Options</B> <B>too</B> <B>much</B>
|
||||
It is possible, especially for the ColorOneScanner, that the
|
||||
backend's options panel to exceed from your screen. It happens
|
||||
with mine and I am running at 1024x768 my X Server. What can I
|
||||
It is possible, especially for the ColorOneScanner, for the
|
||||
backend's options panel to extend beyond your screen. It happens
|
||||
with mine and I am running my X Server at 1024x768. What can I
|
||||
say? Try smaller fonts in the X server, or virtual screens.
|
||||
|
||||
<B>Weird</B> <B>SCSI</B> <B>behaviour</B>
|
||||
|
|
@ -226,35 +223,34 @@
|
|||
|
||||
</PRE>
|
||||
<H2>DEBUG</H2><PRE>
|
||||
If you encounter a GUI bug please set the environment variable
|
||||
SANE_DEBUG_APPLE to 255 and rerun the excact sequence of keystrokes and
|
||||
If you encounter a GUI bug please set the environmental variable
|
||||
SANE_DEBUG_APPLE to 255 and rerun the exact sequence of keystrokes and
|
||||
menu selections to reproduce it. Then send me a report with the log
|
||||
attached.
|
||||
|
||||
It would be very helpfull if you have handy an Apple machine (I am not
|
||||
sure how Mackintoshs are spelled) with the AppleScanners driver
|
||||
installed and check what option are grayed out (inactive) in what modes
|
||||
and report back to me.
|
||||
If you have an Apple Macintosh with the AppleScanners driver installed,
|
||||
reporting to me which options are grayed out (inactive) in what modes
|
||||
would be very helpful.
|
||||
|
||||
If you want to offer some help but you don't have a scanner or you
|
||||
don't have the model you would like to offer some help, or you are a
|
||||
sane developer and you just want to take a look at how the apple back-
|
||||
end looks like. Goto to apple.h and #define the NEUTRALIZE_BACKEND
|
||||
macro. You can select the scanner model through the APPLE_MODEL_SELECT
|
||||
macro. Available options are APPLESCANNER, ONESCANNER, COLORONESCANNER.
|
||||
If you want to offer some help but you don't have a scanner, or you
|
||||
don't have the model you would like to help with, or you are a SANE
|
||||
developer and you just want to take a look at how the apple backend
|
||||
looks like, goto to apple.h and #define the NEUTRALIZE_BACKEND macro.
|
||||
You can select the scanner model through the APPLE_MODEL_SELECT macro.
|
||||
Available options are APPLESCANNER, ONESCANNER, COLORONESCANNER.
|
||||
|
||||
If you encounter a SCSI bus error or trimmed and/or displaced images
|
||||
please also set the environment variable SANE_DEBUG_SANEI_SCSI to 255
|
||||
before sendme the report.
|
||||
please set the environment variable SANE_DEBUG_SANEI_SCSI to 255 before
|
||||
sending me the report.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>TODO</H2><PRE>
|
||||
<B>Non</B> <B>Blocking</B> <B>Support</B>
|
||||
Make sane-apple a non blocking backend. Properly support for
|
||||
Make sane-apple a non blocking backend. Properly support
|
||||
<B>sane_set_io_mode</B> and <B>sane_get_select_fd</B>
|
||||
|
||||
<B>Scan</B> Make scan possible for all models in all supported modes.
|
||||
<B>Scan</B> Make scanning possible for all models in all supported modes.
|
||||
|
||||
<B>Missing</B> <B>Functionality</B>
|
||||
|
||||
|
|
@ -270,7 +266,7 @@
|
|||
Firikis. It is mostly based on the mustek backend from David Mosberger
|
||||
and Andreas Czechanowski
|
||||
|
||||
sane-backends 1.0.17 13 May 1998 <B><A HREF="sane-apple.5.html">sane-apple(5)</A></B>
|
||||
sane-backends 1.0.18 13 May 1998 <B><A HREF="sane-apple.5.html">sane-apple(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -170,7 +170,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
Chris Pinkham (cpinkham@corp.infi.net)
|
||||
|
||||
sane-backends 1.0.17 24 Jan 2000 <B><A HREF="sane-artec.5.html">sane-artec(5)</A></B>
|
||||
sane-backends 1.0.18 24 Jan 2000 <B><A HREF="sane-artec.5.html">sane-artec(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -19,66 +19,55 @@
|
|||
</PRE>
|
||||
<H2>DESCRIPTION</H2><PRE>
|
||||
The <B>sane-artec_eplus48u</B> library implements a SANE (Scanner Access Now
|
||||
Easy) backend that at present provides access to the USB flatbed scan-
|
||||
ners
|
||||
Easy) backend that provides access to several USB flatbed scanners
|
||||
using the GT6816 chipset like the Artec E+ 48U. These scanners have a
|
||||
contact image sensor (CIS) and an USB interface.
|
||||
|
||||
Artec E+ 48U,
|
||||
Tevion MD 9693,
|
||||
Medion MD 9693,
|
||||
Medion MD 9705 and
|
||||
Trust Easy Webscan 19200.
|
||||
A complete list of supported devices can be found on <I>http://www.sane-</I>
|
||||
<I>project.org/sane-supported-devices.html</I>.
|
||||
|
||||
These scanners have a contact image sensor (CIS) and an USB interface.
|
||||
|
||||
VendorID: 0x05d8
|
||||
ProductID: 0x4003
|
||||
|
||||
The Trust Easy Webscan 19200 is an exception. It's ProductID is 0x4006.
|
||||
|
||||
More details can be found on <I>http://www.angelfire.com/linux/crapsite/</I>.
|
||||
|
||||
This is ALPHA software. Especially if you test new or untested scan-
|
||||
ners, keep your hand at the scanner's plug and unplug it, if the head
|
||||
This is ALPHA software. Especially if you test new or untested scan-
|
||||
ners, keep your hand at the scanner's plug and unplug it, if the head
|
||||
bumps at the end of the scan area.
|
||||
|
||||
If you own a scanner other than the ones listed above that works with
|
||||
this backend, please let me know this by sending the scanner's exact
|
||||
model name and the USB vendor and product ids (e.g. from
|
||||
/proc/bus/usb/devices, sane-find-scanner or syslog) to me. Even if the
|
||||
scanner's name is only slightly different from the models mentioned
|
||||
If you own a scanner other than the ones mentioned on the list that
|
||||
works with this backend, please let us know this by sending the scan-
|
||||
ner's exact model name and the USB vendor and product ids (e.g. from
|
||||
/proc/bus/usb/devices, sane-find-scanner or syslog) to me. Even if the
|
||||
scanner's name is only slightly different from the models mentioned
|
||||
above, please let me know.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>KERNEL ISSUES</H2><PRE>
|
||||
If libusb-0.1.6 or later is installed, this section can be skipped. The
|
||||
scanner should be found by sane-find-scanner without further actions.
|
||||
For setting permissions and general USB information look at sane-
|
||||
scanner should be found by sane-find-scanner without further actions.
|
||||
For setting permissions and general USB information look at sane-
|
||||
<B><A HREF="usb.5.html">usb(5)</A></B>.
|
||||
|
||||
When you are using the scanner module, a Linux kernel 2.4.12 or newer
|
||||
When you are using the scanner module, a Linux kernel 2.4.12 or newer
|
||||
is required.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>FIRMWARE FILE</H2><PRE>
|
||||
You need a firmware file for your scanner. That's a small file contain-
|
||||
ing software that will be uploaded to the scanner's memory. For the
|
||||
scanners mentioned above, it's usually named Artec48.usb. You can find
|
||||
it on the installation CD that was provided by the manufacturer, nor-
|
||||
mally in the directory Win98, WinMe or similar. If the Windows-driver
|
||||
is installed on your computer, then you can also find the firmware file
|
||||
under c:\windows\system32\drivers.
|
||||
ing software that will be uploaded to the scanner's memory. For the
|
||||
scanners mentioned above, it's usually named Artec48.usb or 1200.usb.
|
||||
You can find it on the installation CD that was provided by the manu-
|
||||
facturer, normally in the directory Win98, WinMe or similar. If the
|
||||
Windows-driver is installed on your computer, then you can also find
|
||||
the firmware file under c:\windows\system32\drivers.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONFIGURATION</H2><PRE>
|
||||
The contents of the <I>artec</I><B>_</B><I>eplus48u.conf</I> file is a list of usb lines
|
||||
containing vendor and product ids that correspond to USB scanners. The
|
||||
file can also contain option lines. Empty lines and lines starting
|
||||
The contents of the <I>artec</I><B>_</B><I>eplus48u.conf</I> file is a list of usb lines
|
||||
containing vendor and product ids that correspond to USB scanners. The
|
||||
file can also contain option lines. Empty lines and lines starting
|
||||
with a hash mark (#) are ignored. The scanners are autodetected by <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
|
||||
<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>
|
||||
|
||||
Every usb section can have additional options
|
||||
|
|
@ -93,8 +82,8 @@
|
|||
<B>blueGamma</B> <B>1.0</B>
|
||||
|
||||
<B>masterGamma</B> <B>1.9</B>
|
||||
These are the default gamma values. If you set the "Defaults"
|
||||
option with a frontend, then the gamma options are reset to the
|
||||
These are the default gamma values. If you set the "Defaults"
|
||||
option with a frontend, then the gamma options are reset to the
|
||||
values specified here.
|
||||
|
||||
<B>redOffset</B> <B>0x28</B>
|
||||
|
|
@ -108,22 +97,22 @@
|
|||
<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
|
||||
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.
|
||||
|
||||
<B>vendorString</B> <B>Artec</B>
|
||||
|
||||
<B>modelString</B> <B>E+</B> <B>48U</B>
|
||||
By default, the scanner is reported as "Artec E+ 48U". If you
|
||||
don't like this, e.g. because you have an Tevion MD 9693, then
|
||||
By default, the scanner is reported as "Artec E+ 48U". If you
|
||||
don't like this, e.g. because you have an Tevion MD 9693, then
|
||||
change the options accordingly.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>FILES</H2><PRE>
|
||||
<I>/usr/local/etc/sane.d/artec</I><B>_</B><I>eplus48u.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-artec</I><B>_</B><I>eplus48u.a</I>
|
||||
|
|
@ -139,20 +128,20 @@
|
|||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in
|
||||
/usr/local/etc/sane.d. If the value of the environment variable
|
||||
ends with the directory separator character, then the default
|
||||
ends with the directory separator character, then the default
|
||||
directories are searched after the explicitly specified directo-
|
||||
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
|
||||
would result in directories "tmp/config", ".", and
|
||||
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
|
||||
would result in directories "tmp/config", ".", and
|
||||
"/usr/local/etc/sane.d" being searched (in this order).
|
||||
|
||||
<B>SANE_DEBUG_ARTEC_EPLUS48U</B>
|
||||
If the library was compiled with debug support enabled, this
|
||||
environment variable controls the debug level for this backend.
|
||||
If the library was compiled with debug support enabled, this
|
||||
environment variable controls the debug level for this backend.
|
||||
Higher debug levels increase the verbosity of the output.
|
||||
|
||||
Example: export SANE_DEBUG_ARTEC_EPLUS48U=3
|
||||
|
|
@ -165,28 +154,27 @@
|
|||
|
||||
</PRE>
|
||||
<H2>AUTHOR</H2><PRE>
|
||||
Michael Herder <crapsite@gmx.net>
|
||||
This backend is based on the gt68xx test-program written by Sergey
|
||||
Vlasov, Andreas Nowack, and David Stevenson. Thanks to everyone who
|
||||
Michael Herder
|
||||
This backend is based on the gt68xx test-program written by Sergey
|
||||
Vlasov, Andreas Nowack, and David Stevenson. Thanks to everyone who
|
||||
tested the backend or reported bugs.
|
||||
This man page is based on man sane-gt68xx, written by Henning Meier-
|
||||
This man page is based on man sane-gt68xx, written by Henning Meier-
|
||||
Geinitz.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>BUGS</H2><PRE>
|
||||
This backend has been tested on Linux only. If you are using it on a
|
||||
different platform, please contact me.
|
||||
This backend has been tested on Linux only. If you are using it on a
|
||||
different platform, please contact us.
|
||||
|
||||
Interpolation with 1200 dpi is weak.
|
||||
|
||||
Support for buttons is missing due to missing support in SANE.
|
||||
|
||||
More detailed bug information is available at
|
||||
<I>http://www.angelfire.com/linux/crapsite</I>. Please contact me if you find
|
||||
a bug or missing feature: <crapsite@gmx.net>
|
||||
Please contact us if you find a bug: <I>http://www.sane-</I>
|
||||
<I>project.org/bugs.html</I>.
|
||||
|
||||
sane-backends 1.0.17 19 Nov 2002 <B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B>
|
||||
sane-backends 1.0.18 15 Jan 2006 <B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -50,7 +50,7 @@
|
|||
<H2>EMAIL-CONTACT</H2><PRE>
|
||||
yossarian@users.sourceforge.net
|
||||
|
||||
sane-backends 1.0.17 Dec 14th, 2003 <B><A HREF="sane-as6e.5.html">sane-as6e(5)</A></B>
|
||||
sane-backends 1.0.18 Dec 14th, 2003 <B><A HREF="sane-as6e.5.html">sane-as6e(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -168,7 +168,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
René Rebe and Meino Christian Cramer
|
||||
|
||||
sane-backends 1.0.17 04 Mar 2003 <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B>
|
||||
sane-backends 1.0.18 04 Mar 2003 <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -232,7 +232,7 @@
|
|||
for the frontend to pass this knowledge to the backend. If
|
||||
batch mode is enabled and the --end-count terminates a scanadf
|
||||
session, an extra page will be pulled through the scanner, but
|
||||
is niether read nor delivered to the frontend. The issue can be
|
||||
is neither read nor delivered to the frontend. The issue can be
|
||||
avoided by specifying --batch=no when scanning a fixed number of
|
||||
pages.
|
||||
|
||||
|
|
@ -332,7 +332,7 @@
|
|||
TION command. Note that this feature requires RSC firmware
|
||||
level 1.5 or higher and dip switch 4 must be in the on position.
|
||||
NOTE: This option has not been tested extensively and may pro-
|
||||
duce undesireable results.
|
||||
duce undesirable results.
|
||||
|
||||
<B>Enhancement:</B>
|
||||
|
||||
|
|
@ -502,7 +502,7 @@
|
|||
Reifschneider of tummy.com ltd. Some 8000 enhancements added by Mark
|
||||
Temple.
|
||||
|
||||
sane-backends 1.0.17 15 Sep 1999 <B><A HREF="sane-bh.5.html">sane-bh(5)</A></B>
|
||||
sane-backends 1.0.18 15 Sep 1999 <B><A HREF="sane-bh.5.html">sane-bh(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -108,7 +108,7 @@
|
|||
support by Mitsuru Okaniwa; FS2710S support by Ulrich Deiters
|
||||
Man page by Henning Meier-Geinitz (mostly based on canon.README)
|
||||
|
||||
sane-backends 1.0.17 03 May 2001 <B><A HREF="sane-canon.5.html">sane-canon(5)</A></B>
|
||||
sane-backends 1.0.18 03 May 2001 <B><A HREF="sane-canon.5.html">sane-canon(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -117,7 +117,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
Nathan Rutman
|
||||
|
||||
sane-backends 1.0.17 06 Apr 2002 <B><A HREF="sane-canon630u.5.html">sane-canon630u(5)</A></B>
|
||||
sane-backends 1.0.18 06 Apr 2002 <B><A HREF="sane-canon630u.5.html">sane-canon630u(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -222,7 +222,7 @@
|
|||
Many thanks to Kevin Easton for his comments and help, and Kent A. Sig-
|
||||
norini for his help with the N340P.
|
||||
|
||||
sane-backends 1.0.17 1 October 2002 <B><A HREF="sane-canon_pp.5.html">sane-canon_pp(5)</A></B>
|
||||
sane-backends 1.0.18 1 October 2002 <B><A HREF="sane-canon_pp.5.html">sane-canon_pp(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -69,7 +69,7 @@
|
|||
This manual page was written by Julien BLACHE <jblache@debian.org>, for
|
||||
the Debian GNU/Linux system (but may be used by others).
|
||||
|
||||
sane-backends 1.0.17 8 Jan 2004 <B><A HREF="sane-config.1.html">sane-config(1)</A></B>
|
||||
sane-backends 1.0.18 8 Jan 2004 <B><A HREF="sane-config.1.html">sane-config(1)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@
|
|||
|
||||
</PRE>
|
||||
<H2>ABOUT THIS FILE</H2><PRE>
|
||||
This file is a short descripton of the coolscan-backend for sane!
|
||||
This file is a short description of the coolscan-backend for sane!
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -29,7 +29,7 @@
|
|||
<B>Even</B> <B>though</B> <B>the</B> <B>backend</B> <B>has</B> <B>worked</B> <B>for</B> <B>a</B> <B>number</B> <B>of</B> <B>people,</B> <B>there</B> <B>are</B>
|
||||
<B>still</B> <B>some</B> <B>problems,</B> <B>especially</B> <B>in</B> <B>combination</B> <B>with</B> <B>some</B> <B>SCSI</B>
|
||||
<B>card/drivers</B> <B>(AHA-1505/aha152x.o)</B> <B>and</B> <B>the</B> <B>autofocus</B> <B>command.</B> <B>You</B> <B>should</B>
|
||||
<B>consider</B> <B>this</B> <B>backend</B> <B>'alpha'</B> <B>and</B> <B>be</B> <B>carefull</B> <B>when</B> <B>using</B> <B>it</B> <B>the</B> <B>first</B>
|
||||
<B>consider</B> <B>this</B> <B>backend</B> <B>'alpha'</B> <B>and</B> <B>be</B> <B>careful</B> <B>when</B> <B>using</B> <B>it</B> <B>the</B> <B>first</B>
|
||||
<B>time.</B>
|
||||
|
||||
|
||||
|
|
@ -131,7 +131,7 @@
|
|||
<H2>EMAIL-CONTACT</H2><PRE>
|
||||
andreas.rick@free.fr
|
||||
|
||||
sane-backends 1.0.17 4 July 2000 <B><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B>
|
||||
sane-backends 1.0.18 4 July 2000 <B><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -193,7 +193,7 @@
|
|||
The backend is written and maintained by András Major
|
||||
(andras@users.sourceforge.net).
|
||||
|
||||
sane-backends 1.0.17 22/08/2002 <B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B>
|
||||
sane-backends 1.0.18 22/08/2002 <B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -123,7 +123,7 @@
|
|||
be subscribed to the list, otherwise your mail won't be sent to the
|
||||
subscribers.
|
||||
|
||||
sane-backends 1.0.17 15 July 2000 <B><A HREF="sane-dc210.5.html">sane-dc210(5)</A></B>
|
||||
sane-backends 1.0.18 15 July 2000 <B><A HREF="sane-dc210.5.html">sane-dc210(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -109,7 +109,7 @@
|
|||
This backend borrows heavily from the dc210 backend by Brian J. Murrell
|
||||
which is based somewhat on the dc25 backend by Peter Fales.
|
||||
|
||||
The manpage was largeley copied from the dc210 manpage.
|
||||
The manpage was largely copied from the dc210 manpage.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -126,7 +126,7 @@
|
|||
be subscribed to the list, otherwise your mail won't be sent to the
|
||||
subscribers.
|
||||
|
||||
sane-backends 1.0.17 23 March 2001 <B><A HREF="sane-dc240.5.html">sane-dc240(5)</A></B>
|
||||
sane-backends 1.0.18 23 March 2001 <B><A HREF="sane-dc240.5.html">sane-dc240(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -116,7 +116,7 @@
|
|||
be subscribed to the list, otherwise your mail won't be sent to the
|
||||
subscribers.
|
||||
|
||||
sane-backends 1.0.17 12 April 1999 <B><A HREF="sane-dc25.5.html">sane-dc25(5)</A></B>
|
||||
sane-backends 1.0.18 12 April 1999 <B><A HREF="sane-dc25.5.html">sane-dc25(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -148,7 +148,7 @@
|
|||
David Mosberger
|
||||
|
||||
|
||||
sane-backends 1.0.17 4 Dec 2002 <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>
|
||||
sane-backends 1.0.18 4 Dec 2002 <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -159,7 +159,7 @@
|
|||
|
||||
The backend is derived from <B>sane-hp</B> by David Mosberger
|
||||
|
||||
sane-backends 1.0.17 13 May 1998 <B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B>
|
||||
sane-backends 1.0.18 13 May 1998 <B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -107,7 +107,7 @@
|
|||
The <I>--sharpness</I> switch sets the sharpness of the image data.
|
||||
Valid options are integer values from -2 to 2, with -2 meaning
|
||||
"Defocus", -1 "Defocus slightly", 0 "Normal", 1 "Sharpen
|
||||
slighly" and 2 "Sharpen".
|
||||
slightly" and 2 "Sharpen".
|
||||
|
||||
The <I>--gamma-correction</I> switch controls the scanner's internal
|
||||
gamma correction. Valid options are "Default", "User defined",
|
||||
|
|
@ -120,13 +120,13 @@
|
|||
and "CRT monitors". The default is "CRT monitors".
|
||||
|
||||
The <I>--resolution</I> switch selects the resolution for a scan. Some
|
||||
EPSON scanners will scan in any resulution between the lowest
|
||||
EPSON scanners will scan in any resolution between the lowest
|
||||
and highest possible value. The list reported by the scanner can
|
||||
be displayed using the "--help -d epson" parameters to scanim-
|
||||
age.
|
||||
|
||||
The <I>--mirror</I> option controls the way the image is scanned. By
|
||||
reading the image data from right to left the image is mirored.
|
||||
reading the image data from right to left the image is mirrored.
|
||||
Valid options are "yes" and "no". The default is "no".
|
||||
|
||||
The <I>--speed</I> option can improve the scan speed in monochrome
|
||||
|
|
@ -136,7 +136,7 @@
|
|||
The <I>--auto-area-segmentation</I> switch activates the automatic area
|
||||
segmentation for monochrome scans. The scanner will try to
|
||||
determine which areas are text and which contain images. The
|
||||
image areas will be halftoned, and the text will be impoved.
|
||||
image areas will be halftoned, and the text will be improved.
|
||||
Valid options are "yes" and "no". The default is "yes".
|
||||
|
||||
The <I>--gamma-table</I> parameter can be used to download a user
|
||||
|
|
@ -171,8 +171,8 @@
|
|||
|
||||
The geometry options <I>-l</I> <I>-t</I> <I>-x</I> <I>-y</I> 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 aea. All parame-
|
||||
ters are specified in milimeters.
|
||||
selects the width and -y the height of the scan area. All param-
|
||||
eters are specified in millimeters.
|
||||
|
||||
The <I>--quick-format</I> option lets the user select a scan area with
|
||||
predefined sizes. Valid parameters are "CD", "A5 portrait", "A5
|
||||
|
|
@ -289,7 +289,7 @@
|
|||
The package is actively maintained by Karl Heinz Kremer (khk@khk.net).
|
||||
The software is based on work by Christian Bucher and Kazuhiro Sasayama
|
||||
|
||||
sane-backends 1.0.17 27-Dec-2000 <B><A HREF="sane-epson.5.html">sane-epson(5)</A></B>
|
||||
sane-backends 1.0.18 27-Dec-2000 <B><A HREF="sane-epson.5.html">sane-epson(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -120,7 +120,7 @@
|
|||
No support for most parallel port scanners yet.
|
||||
Detection of USB chipsets is limited to a few chipsets.
|
||||
|
||||
sane-backends 1.0.17 4 Oct 2004 <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>
|
||||
sane-backends 1.0.18 4 Oct 2004 <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -18,146 +18,220 @@
|
|||
</PRE>
|
||||
<H2>DESCRIPTION</H2><PRE>
|
||||
The <B>sane-fujitsu</B> library implements a SANE (Scanner Access Now Easy)
|
||||
backend which provides access to Fujitsu flatbed and ADF scanners. At
|
||||
present, the following scanners are known to work with this backend:
|
||||
backend which provides access to most Fujitsu flatbed and ADF scanners.
|
||||
|
||||
Vendor: Model: Rev:
|
||||
-------- ---------------- -----
|
||||
FUJITSU M3096Gm 02
|
||||
FUJITSU M3093GX
|
||||
FUJITSU M3093GD
|
||||
FUJITSU M4097
|
||||
FUJITSU fi-4220C
|
||||
FUJITSU fi-4340C
|
||||
FUJITSU M3091DCd BF21
|
||||
FUJITSU M3092DCd
|
||||
This document describes the rewritten backend versions 1.0.21 and
|
||||
greater.
|
||||
|
||||
The driver supports lineart, halftone, grayscale, and color (3091 and
|
||||
3092) scanning depending on hardware capabiliites.
|
||||
|
||||
The "Fujitsu" driver is a first attempt at integrating support for all
|
||||
Fujitsu scanners - previously available as different single drivers -
|
||||
in one driver. At present, the M3091DCd is working (lineart, halftone,
|
||||
8-bit grayscale and 24-bit color, simplex and duplex), and the driver
|
||||
should also support the M3096 as the M3096g driver code has been incor-
|
||||
porated. This driver supersedes the old "m3091"/"fujitsu" drivers and
|
||||
the old "m3096g" driver.
|
||||
|
||||
Other scanners in these families may work. The ScanPartner 15C seems
|
||||
to be a repackaging of the ScanPartner 600C, but I don't know if it
|
||||
works. Look at the sp15c backend for this scanner. Perusal of the
|
||||
M3096GX/M3093GX/M3093DG manual suggests the M3096G driver offers access
|
||||
to a subset of the new scanners. People are encouraged to try these
|
||||
driver with the other scanners and to contact the author with test
|
||||
results.
|
||||
The backend supports lineart, halftone, grayscale, and color scanning
|
||||
for most USB and SCSI scanners, depending on hardware capabilities.
|
||||
Most simple scanning related features are exposed. This version fea-
|
||||
tures at least basic support for many more models. See KNOWN ISSUES.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>DUPLEX MODE</H2><PRE>
|
||||
The M3091 driver supports duplex scanning. To the front-end, a duplex
|
||||
scan looks very much like scanning two separate pages from the document
|
||||
feeder, i.e. the SANE front-end receives two images instead of one.
|
||||
Front-ends which are not capable of dealing with that - e.g. the com-
|
||||
mand-line tool scanimage - cannot be used for duplex scanning. If you
|
||||
want to do duplex scans from the command line, get Tom Martone's
|
||||
scanadf program from http://www.martoneconsulting.com/sane-
|
||||
scanadf.html.
|
||||
<H2>HARDWARE SUPPORT</H2><PRE>
|
||||
The following scanners are thought to have at least basic scanning
|
||||
capability, either because they have been tested with a prior version,
|
||||
or because documentation indicates they are compatible with a tested
|
||||
model.
|
||||
|
||||
WORKGROUP SIZED SCANNERS:
|
||||
--------------------------------------
|
||||
SCSI: SCSI/USB: USB:
|
||||
------------ ------------ ------------
|
||||
M3091DC fi-4120C fi-5110C
|
||||
M3092DC fi-4220C fi-5110EOX
|
||||
SP-93GX fi-4120C2
|
||||
fi-4220C2
|
||||
fi-5120C
|
||||
fi-5220C
|
||||
|
||||
DEPARTMENTAL SIZED SCANNERS:
|
||||
--------------------------------------
|
||||
SCSI: SCSI/USB:
|
||||
------------ ------------
|
||||
M3093GX/DG fi-4340C
|
||||
M3096G/GX fi-4530C
|
||||
M3097G+/DG fi-5530C
|
||||
fi-4640S
|
||||
fi-4750C
|
||||
|
||||
PRODUCTION SIZED SCANNERS:
|
||||
--------------------------------------
|
||||
SCSI: SCSI/USB:
|
||||
------------ ------------
|
||||
M3099G/GH/GX fi-5650C
|
||||
M4097D fi-5750C
|
||||
fi-4750L fi-5900C
|
||||
fi-4860C
|
||||
M4099D
|
||||
|
||||
The following scanners are known NOT to work with this backend, either
|
||||
because they have a non-fujitsu chipset, or an unsupported interface
|
||||
type. Some of these scanners may be supported by another backend.
|
||||
|
||||
UNSUPPORTED SCANNERS:
|
||||
--------------------------------------
|
||||
SCSI: SERIAL: USB:
|
||||
------------ ------------ ------------
|
||||
ScanStation M3093E/DE/EX fi-4110EOX2
|
||||
ScanPartner M3096EX fi-4010CU
|
||||
SP-Jr M3097E+/DE
|
||||
SP-10/10C M3099A/EH/EX
|
||||
SP-15C/300C
|
||||
SP-600C/620C
|
||||
|
||||
This backend may support scanners not listed here. The best way to
|
||||
determine level of support is to test the scanner directly. Fujitsu
|
||||
equipment has historically been good enough to not be damaged by incor-
|
||||
rect commands if the scanner is incompatible. Please contact the
|
||||
author with test results, positive or negative.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONFIGURATION</H2><PRE>
|
||||
A modest effort has been made to expose the standard options to the
|
||||
API. This allows frontends such as xscanimage to set scanning region,
|
||||
resolution, bit-depth (and color), and enable the automatic document
|
||||
feeder.
|
||||
The "Fujitsu" driver supports the following options:
|
||||
<H2>OPTIONS</H2><PRE>
|
||||
A modest effort has been made to expose the standard options to the
|
||||
API. This allows a frontend to set scanning region, resolution, bit-
|
||||
depth, color mode, and enable the automatic document feeder. The
|
||||
fujitsu backend supports the following basic options for most scanners:
|
||||
|
||||
source s
|
||||
Selects the source for the scan. Options may include "Flatbed",
|
||||
"ADF Front", "ADF Back", "ADF Duplex".
|
||||
|
||||
mode m
|
||||
<I>m</I> may be one of "Color", "Lineart", "Halftone", or "Gray",
|
||||
dependent on the scanner model. It is advisable to specify this
|
||||
option first when using command line tools, as the validity of
|
||||
some of the other options depends on the mode setting.
|
||||
|
||||
x, y
|
||||
Scan width and height
|
||||
|
||||
pagewidth, pageheight
|
||||
Page size; when using the ADF, the driver will assume that a
|
||||
page of the given width is centered
|
||||
Selects the mode for the scan. Options may include "Lineart",
|
||||
"Halftone", "Gray", and "Color".
|
||||
|
||||
resolution, y-resolution
|
||||
Controls scan resolution. Permissible values dependent on model
|
||||
and scan mode; setting --resolution also sets --y-resolution but
|
||||
not vice versa. This makes it possible to set the 3091's maximum
|
||||
resolution of 300x600dpi.
|
||||
Controls scan resolution. Setting --resolution also sets --y-
|
||||
resolution but not vice versa. This behavior is overridden by
|
||||
some frontends.
|
||||
|
||||
brightness b
|
||||
Only supported for M3096
|
||||
tlx, tly, brx, bry
|
||||
Sets scan area upper left and lower right coordinates. Often
|
||||
converted to t, l, x, y by frontend code.
|
||||
|
||||
threshold t
|
||||
Only supported for M3096
|
||||
pagewidth, pageheight
|
||||
Sets paper size. Used by scanner to determine centering of scan
|
||||
coordinates when using ADF.
|
||||
|
||||
duplex d
|
||||
<I>d</I> may be "front", "back", or "both" and denotes which sides of
|
||||
the page are to be scanned (duplex scanner only for example
|
||||
3091, 3093Gd).
|
||||
Other options will be available based on the capabilities of the scan-
|
||||
ner. Use 'scanimage --help' to get a list. Be aware that some options
|
||||
may appear only when another option has been set.
|
||||
|
||||
lampcolor c
|
||||
<I>c</I> may be "red", "green", "blue", or "default" - the lamp color
|
||||
to be used when doing graysacale or b/w scans on the M3091.
|
||||
|
||||
blueoffset, greenoffset
|
||||
Color justification options for the M3091; anything other than
|
||||
+1/-1 will probably distort the image. Should be left alone
|
||||
unless your scanner is buggy.
|
||||
</PRE>
|
||||
<H2>CONFIGURATION FILE</H2><PRE>
|
||||
The configuration file "fujitsu.conf" 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
|
||||
defaults, which are identical to the default configuration file shipped
|
||||
with SANE.
|
||||
|
||||
swapfile
|
||||
boolean option for the M3091. Only affects duplex scans. If set,
|
||||
a swap file will be used for storing the rear side of a document
|
||||
as it is scanned; otherwise the whole page will be kept in mem-
|
||||
ory.
|
||||
Scanners can be specified in the configuration file in 4 ways:
|
||||
|
||||
You may specify the line "forceModel=xxx" in the configuration file to
|
||||
make the driver treat your scanner as an "xxx" scanner (currently sup-
|
||||
ported: 3096, 3091). Use this if you have another scanner that is not
|
||||
automatically detected as being compatible.
|
||||
"scsi FUJITSU"
|
||||
Requests backend to search all scsi busses in the system for a
|
||||
device which reports itself to be a scanner made by 'FUJITSU'.
|
||||
|
||||
The only other configuration option supported is "scsi-buf-size=xxx",
|
||||
allowing you to set the SCSI buffer size to something other than the
|
||||
compiled-in default. Especially with the M3091 scanner, some users had
|
||||
the problem that the scanner would "hang" mid-page, and this can often
|
||||
be alleviated by using "scsi-buf-size=32768".
|
||||
"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
|
||||
other "scsi" line above.
|
||||
|
||||
"usb 0x04c5 0x1042" (or other vendor/product ids)
|
||||
Requests backend to search all usb busses in the system for a
|
||||
device which uses that vendor and product id. The device will
|
||||
then be queried to determine if it is a Fujitsu scanner.
|
||||
|
||||
"usb /dev/usb/scanner0" (or other device file)
|
||||
Some systems use a kernel driver to access usb scanners. This
|
||||
method is untested.
|
||||
|
||||
The only configuration option supported is "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
|
||||
buffer 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
|
||||
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
|
||||
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, SANE_DEBUG_FUJITSU,
|
||||
which enables debugging output to stderr. Valid values are:
|
||||
|
||||
5 Errors
|
||||
10 Function trace
|
||||
15 Function detail
|
||||
20 Option commands
|
||||
25 SCSI/USB trace
|
||||
30 SCSI/USB detail
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>OLDER VERSIONS</H2><PRE>
|
||||
Backend versions prior to this were numbered with a two part version,
|
||||
or with no version number at all. At the time this version was written,
|
||||
all older versions were retroactively renumbered, 1.0.2 - 1.0.20.
|
||||
|
||||
The current backend may have lost support for some feature you were
|
||||
using. The last of the "old" backends, 1.0.20, is still available as
|
||||
source from:
|
||||
|
||||
http://www2.pfeiffer.edu/~anoah/fujitsu/
|
||||
|
||||
If you find that you need to use the older version, please contact the
|
||||
author, to try and get those features restored to a later version.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>KNOWN ISSUES</H2><PRE>
|
||||
All IPC, imprinter, and compression options are disabled.
|
||||
Most scanner specific 'quirks' are not accounted for, making it
|
||||
possible to set some options in ways that the scanner does not
|
||||
support.
|
||||
Some flatbed options are affected by adf settings.
|
||||
Any model that does not support VPD during inquiry will not
|
||||
function.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>HISTORY</H2><PRE>
|
||||
m3091 backend: Frederik Ramm <frederik a t remote d o t org>
|
||||
m3096g backend: Randolph Bentson <bentson a t holmsjoen d o t com>
|
||||
(with credit to the unnamed author of the coolscan driver)
|
||||
fujitsu backend, 3093, fi-4340C, ipc, cmp, long-time maintainer:
|
||||
Oliver Schirrmeister <oschirr a t abm d o t de>
|
||||
3092: Mario Goppold <mgoppold a t tbzpariv d o t tcc-chemnitz d o t de>
|
||||
fi-4220C and basic USB support: Ron Cemer <ron a t roncemer d o t com>
|
||||
fi-4120, fi-series color support, backend re-write, current maintainer:
|
||||
M. Allan Noah: <anoah a t pfeiffer d o t edu>
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B> <B><A HREF="sane-usb.5.html">sane-usb(5)</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
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B>, <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B>
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>AUTHOR</H2><PRE>
|
||||
3096/SP15 drivers: Randolph Bentson <bentson@holmsjoen.com>, with
|
||||
credit to the unnamed author of the coolscan driver
|
||||
3091 driver: Frederik Ramm <frederik@remote.org> 3093GD,fi-4340C, ipc
|
||||
and cmp options: Oliver Schirrmeister <oschirr@abm.de> 3092 patch:
|
||||
Mario Goppold <mgoppold@tbzpariv.tcc-chemnitz.de> fi-4220C patch and
|
||||
USB support: Ronald B. Cemer <ron@roncemer.com>
|
||||
M. Allan Noah: <anoah a t pfeiffer d o t edu>
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>LIMITATIONS</H2><PRE>
|
||||
Only tested with Linux 2.4
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>BUGS</H2><PRE>
|
||||
I'm sure there are plenty, and not too well hidden, but I haven't seen
|
||||
them yet. I don't know if the ScanPartner 15C still works, because I'm
|
||||
not able to test it. 3091/3092 don't support halftone
|
||||
|
||||
sane-backends 1.0.17 17 Apr 2002 <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>
|
||||
sane-backends 1.0.18 2006-06-06 <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -59,7 +59,7 @@
|
|||
also contain option lines. Empty lines and lines starting with a hash
|
||||
mark (#) are ignored. The scanners are autodetected by <B>usb</B> <B>vendor_id</B>
|
||||
<B>product_id</B> statements which are already included into <I>genesys.conf</I>.
|
||||
"vendor_id" and "product_id" are hexadecimal numbers that identfy the
|
||||
"vendor_id" and "product_id" are hexadecimal numbers that identify the
|
||||
scanner.
|
||||
|
||||
|
||||
|
|
@ -132,7 +132,7 @@
|
|||
<H2>BUGS</H2><PRE>
|
||||
Support for buttons is missing.
|
||||
|
||||
sane-backends 1.0.17 20 Nov 2005 <B><A HREF="sane-genesys.5.html">sane-genesys(5)</A></B>
|
||||
sane-backends 1.0.18 20 Nov 2005 <B><A HREF="sane-genesys.5.html">sane-genesys(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -52,7 +52,7 @@
|
|||
The "topfolder" line specifies the "fixed" part of the file path. For
|
||||
example, on the Kodak DC-240, files are stored in the directory
|
||||
/DCIM/100DC240. The /DCIM portion is constant, but 100DC240 will
|
||||
change and must be read from the camers. In this case, the line would
|
||||
change and must be read from the camera. In this case, the line would
|
||||
read "topfolder=/DCIM"
|
||||
|
||||
Some cameras don't implement a file structure and store all pictures in
|
||||
|
|
@ -118,7 +118,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
Peter S. Fales
|
||||
|
||||
The manpage was largeley copied from the dc210 manpage.
|
||||
The manpage was largely copied from the dc210 manpage.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -131,7 +131,7 @@
|
|||
be subscribed to the list, otherwise your mail won't be sent to the
|
||||
subscribers.
|
||||
|
||||
sane-backends 1.0.17 04 September 2001 <B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>
|
||||
sane-backends 1.0.18 04 September 2001 <B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -55,10 +55,10 @@
|
|||
ally named *.usb, e.g. <I>PS1fw.usb</I>. It comes on the installation CD
|
||||
that was provided by the manufacturer, but it may be packaged together
|
||||
with the installation program in an .exe file. For Mustek scanners, the
|
||||
file can be dowloaded from the gt68xx backend homepage. For other scan-
|
||||
ners, check the CD for .usb files. If you only find *.cab files, try
|
||||
cabextract to unpack. If everything else fails, you must install the
|
||||
Windows driver and get the firmware from there (usually in the <I>win-</I>
|
||||
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
|
||||
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-
|
||||
one.
|
||||
|
|
@ -71,7 +71,7 @@
|
|||
also contain option lines. Empty lines and lines starting with a hash
|
||||
mark (#) are ignored. The scanners are autodetected by <B>usb</B> <B>vendor_id</B>
|
||||
<B>product_id</B> statements which are already included into <I>gt68xx.conf</I>.
|
||||
"vendor_id" and "product_id" are hexadecimal numbers that identfy the
|
||||
"vendor_id" and "product_id" are hexadecimal numbers that identify the
|
||||
scanner.
|
||||
|
||||
The <B>override</B>, <B>firmware</B>, <B>vendor</B>, <B>model</B>, and <B>afe</B> options must be placed
|
||||
|
|
@ -163,7 +163,7 @@
|
|||
<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>sane-</B>
|
||||
<B><A HREF="ma1509.5.html">ma1509(5)</A></B>, <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>
|
||||
<I>/usr/local/doc/sane-1.0.17/gt68xx/gt68xx.CHANGES</I>
|
||||
<I>/usr/local/doc/sane-1.0.18/gt68xx/gt68xx.CHANGES</I>
|
||||
<I>http://www.meier-geinitz.de/sane/gt68xx</I>
|
||||
|
||||
|
||||
|
|
@ -190,7 +190,7 @@
|
|||
Please send a debug log if your scanner isn't detected correctly (see
|
||||
SANE_DEBUG_GT68XX above).
|
||||
|
||||
sane-backends 1.0.17 29 September 2005 <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>
|
||||
sane-backends 1.0.18 29 September 2005 <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -60,7 +60,7 @@
|
|||
SCL (beside the OfficeJets), the above list of supported scanners is
|
||||
complete. Other HP scanners are not supported by the "hp" backend, but
|
||||
might be supported by another one. See <I>http://www.sane-project.org/</I>.
|
||||
You can also watch the sane-devel mailinglist at <I>http://www.sane-</I>
|
||||
You can also watch the sane-devel mailing list at <I>http://www.sane-</I>
|
||||
<I>project.org/mailing-lists.html</I>.
|
||||
|
||||
More details about the hp backend can be found on its homepage
|
||||
|
|
@ -120,8 +120,8 @@
|
|||
moving scanner lamp.
|
||||
|
||||
Option <B>dumb-read</B> can be used to work around problems with "Error during
|
||||
device I/O". These problems may occur with certain SCSI-to-USB conver-
|
||||
tors or Buslogic SCSI cards. The option should not be used for SCSI
|
||||
device I/O". These problems may occur with certain SCSI-to-USB convert-
|
||||
ers or Buslogic SCSI cards. The option should not be used for SCSI
|
||||
devices which are working correctly. Otherwise startup of frontends
|
||||
and changing parameters might be slower.
|
||||
|
||||
|
|
@ -255,7 +255,7 @@
|
|||
The sane-hp backend was written by Geoffrey T. Dairiki. HP PhotoSmart
|
||||
PhotoScanner support by Peter Kirchgessner.
|
||||
|
||||
sane-backends 1.0.17 27 Mar 2004 <B><A HREF="sane-hp.5.html">sane-hp(5)</A></B>
|
||||
sane-backends 1.0.18 27 Mar 2004 <B><A HREF="sane-hp.5.html">sane-hp(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -68,7 +68,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
Troy Rollo <sane@troy.rollo.name>
|
||||
|
||||
sane-backends 1.0.17-cvs 27 Nov 2005 <B><A HREF="sane-hp3500.5.html">sane-hp3500(5)</A></B>
|
||||
sane-backends 1.0.18 27 Nov 2005 <B><A HREF="sane-hp3500.5.html">sane-hp3500(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -114,7 +114,7 @@
|
|||
Send bug reports to the sane-devel mailing list: sane-
|
||||
devel@lists.alioth.debian.org.
|
||||
|
||||
sane-backends 1.0.17 14 August 2005 <B><A HREF="sane-hp4200.5.html">sane-hp4200(5)</A></B>
|
||||
sane-backends 1.0.18 14 August 2005 <B><A HREF="sane-hp4200.5.html">sane-hp4200(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -110,7 +110,7 @@
|
|||
other operating systems and especially on big-endian platforms. The
|
||||
scanner may get wrong data.
|
||||
|
||||
sane-backends 1.0.17 17 Apr 2003 <B><A HREF="sane-hp5400.5.html">sane-hp5400(5)</A></B>
|
||||
sane-backends 1.0.18 17 Apr 2003 <B><A HREF="sane-hp5400.5.html">sane-hp5400(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -12,30 +12,30 @@
|
|||
|
||||
</PRE>
|
||||
<H2>NAME</H2><PRE>
|
||||
sane-hpsj5s - SANE backend for HP ScanJet 5S sheetfed scanner
|
||||
sane-hpsj5s - SANE backend for HP ScanJet 5S sheet-fed scanner
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>DESCRIPTION</H2><PRE>
|
||||
The <B>sane-hpsj5s</B> library implements a SANE (Scanner Access Now Easy)
|
||||
backend that provides access to parallel port Hewlett-Packard ScanJet
|
||||
5S scaner.
|
||||
backend that provides access to a parallel port Hewlett-Packard ScanJet
|
||||
5S scanner.
|
||||
|
||||
IMPORTANT: this is alpha code. Don't expect this to work correctly.
|
||||
Many functions are missing, others contain errors. In some cases, your
|
||||
computer might even hang. It cannot be excluded (although I consider it
|
||||
extremely unprobable) that your scanner will be damaged.
|
||||
extremely improbable) that your scanner will be damaged.
|
||||
|
||||
LIMITATIONS: For now this backend works only at Linux platform.This
|
||||
limitation is due dependance on libieee1284 library. If your system
|
||||
supports libieee1284 too, this backend should work. If you ported
|
||||
libieee1284 for you platform, please let me know.Your system should
|
||||
support <B>EPP</B> (or <B>EPP+ECP</B> ) mode to operate this scaner. Future versions
|
||||
LIMITATIONS: For now this backend works only on Linux. This limitation
|
||||
is due to dependence on the libieee1284 library. If your system sup-
|
||||
ports libieee1284 too, this backend should work. If you ported
|
||||
libieee1284 for your platform, please let me know. Your system should
|
||||
support <B>EPP</B> (or <B>EPP+ECP</B> ) mode to operate this scanner. Future versions
|
||||
will support ECP and SPP (Nibble and Byte) modes also. It's planned to
|
||||
support for scaners not only at 0 daisy-chain position, but at any one.
|
||||
Support for multiple scaners could be implemented too.
|
||||
support scanners not only at daisy-chain position 0, but anywhere. Sup-
|
||||
port for multiple scanners could be implemented too.
|
||||
|
||||
Current version implements only gray scale scaning. True Color and B/W
|
||||
Current version implements only gray scale scanning. True Color and B/W
|
||||
modes are not supported for now.
|
||||
|
||||
That said, TESTERS ARE WELCOME. Send your bug reports and comments to
|
||||
|
|
@ -64,10 +64,10 @@
|
|||
|
||||
</PRE>
|
||||
<H2>TIPS</H2><PRE>
|
||||
It seems that HP ScanJet 5S scaner uses software noise correction. This
|
||||
feature is not implemented for now. So does gamma correction and cali-
|
||||
bration. I'll handle it in future versions. Native resolution for
|
||||
this scaner is 300 DPI. Other modes could be jagged in some ways.
|
||||
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.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -111,7 +111,7 @@
|
|||
Max Vorobiev
|
||||
Man page mostly based on canon.man
|
||||
|
||||
sane-backends 1.0.17 24 Feb 2002 <B><A HREF="sane-hpsj5s.5.html">sane-hpsj5s(5)</A></B>
|
||||
sane-backends 1.0.18 24 Feb 2002 <B><A HREF="sane-hpsj5s.5.html">sane-hpsj5s(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -94,7 +94,7 @@
|
|||
mf <massifr@tiscalinet.it>
|
||||
Maintained by Henning Meier-Geinitz <henning@meier-geinitz.de>
|
||||
|
||||
sane-backends 1.0.17 15 Apr 2003 <B><A HREF="sane-ibm.5.html">sane-ibm(5)</A></B>
|
||||
sane-backends 1.0.18 15 Apr 2003 <B><A HREF="sane-ibm.5.html">sane-ibm(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -134,7 +134,7 @@
|
|||
The package is actively maintained by Frank Zago.
|
||||
<I>http://www.zago.net/sane/#leo</I>
|
||||
|
||||
sane-backends 1.0.17 16 April 2002 <B><A HREF="sane-leo.5.html">sane-leo(5)</A></B>
|
||||
sane-backends 1.0.18 16 April 2002 <B><A HREF="sane-leo.5.html">sane-leo(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -132,7 +132,7 @@
|
|||
The package is actively maintained by Fred Odendaal.
|
||||
<I>http://ca.geocities.com/freshshelf@rogers.com/</I>
|
||||
|
||||
sane-backends 1.0.17 02 September 2005 <B><A HREF="sane-lexmark.5.html">sane-lexmark(5)</A></B>
|
||||
sane-backends 1.0.18 02 September 2005 <B><A HREF="sane-lexmark.5.html">sane-lexmark(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -62,7 +62,7 @@
|
|||
<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 hex-
|
||||
adecimal numbers that identfy the scanner. If this doesn't work, a
|
||||
adecimal numbers that identify the scanner. If this doesn't work, a
|
||||
device 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
|
||||
|
|
@ -127,7 +127,7 @@
|
|||
More detailed bug information is available at the MA-1509 backend home-
|
||||
page <I>http://www.meier-geinitz.de/sane/ma1509-backend/</I>.
|
||||
|
||||
sane-backends 1.0.17 24 Feb 2003 <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>
|
||||
sane-backends 1.0.18 24 Feb 2003 <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -184,7 +184,7 @@
|
|||
The package is actively maintained by Frank Zago.
|
||||
<I>http://www.zago.net/sane/#matsushita</I>
|
||||
|
||||
sane-backends 1.0.17 February 11th, 2004 <B><A HREF="sane-matsushita.5.html">sane-matsushita(5)</A></B>
|
||||
sane-backends 1.0.18 February 11th, 2004 <B><A HREF="sane-matsushita.5.html">sane-matsushita(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -29,7 +29,7 @@
|
|||
Agfa StudioScan
|
||||
Agfa StudioScan II, StudioScan IIsi
|
||||
Agfa Arcus II (but not the "Arcus")
|
||||
Agfa DuoScan (premliminary)
|
||||
Agfa DuoScan (preliminary)
|
||||
Vobis "Highscreen Realscan"
|
||||
Microtek Color PageWiz (preliminary)
|
||||
|
||||
|
|
@ -166,7 +166,7 @@
|
|||
ers mailing list. Have a look at http://www.sane-project.org/mailing-
|
||||
lists.html concerning subscription to sane-devel.
|
||||
|
||||
sane-backends 1.0.17 February 8, 2000 <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B>
|
||||
sane-backends 1.0.18 February 8, 2000 <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -66,9 +66,9 @@
|
|||
|
||||
If you try your scanner for the first time keep an eye on it. If it
|
||||
gets commands that it doesn't understand the scanhead may go beyond the
|
||||
scan area. The scanner then makes strange noises. In this case imme-
|
||||
dieately switch off the scanner or disconnect its power cable to pre-
|
||||
vent damages!
|
||||
scan area. The scanner then makes strange noises. In this case immedi-
|
||||
ately switch off the scanner or disconnect its power cable to prevent
|
||||
damages!
|
||||
|
||||
If your scanner is a different one than the models mentioned above and
|
||||
it is working please tell the author about it. It would be nice if you
|
||||
|
|
@ -272,7 +272,7 @@
|
|||
Bernd Schroeder (not active anymore)
|
||||
Karsten Festag karsten.festag@gmx.de
|
||||
|
||||
sane-backends 1.0.17 28 Jan 2002 <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B>
|
||||
sane-backends 1.0.18 28 Jan 2002 <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -55,7 +55,7 @@
|
|||
only non-SCSI scanners that have some support at this point is the 600
|
||||
II N and 600 II EP scanners. The former one comes with its own parallel
|
||||
port adapter (i.e., it does <I>not</I> attach to the printer port). Both scan-
|
||||
ners use the SCSI protocoll internally, too. More info on how to use
|
||||
ners use the SCSI protocol internally, too. More info on how to use
|
||||
these parallel port scanners can be found below in section <B>PARALLEL</B>
|
||||
<B>PORT</B> <B>SCANNERS</B>. Other parallel port scanners are not supported by this
|
||||
backend but you may be successful using the Mustek parallel port back-
|
||||
|
|
@ -70,7 +70,7 @@
|
|||
noises and the scan mechanism may be damaged. Thus, if you hear such a
|
||||
noise, IMMEDIATELY turn off the scanner. This shouldn't happen if your
|
||||
scanner is in the list of known scanners. There is more information in
|
||||
the <I>/usr/local/doc/sane-1.0.17/PROBLEMS</I> file.
|
||||
the <I>/usr/local/doc/sane-1.0.18/PROBLEMS</I> file.
|
||||
|
||||
If you own a Mustek (or Trust) scanner other than the ones listed above
|
||||
that works with this backend, please let us know by sending the scan-
|
||||
|
|
@ -248,7 +248,7 @@
|
|||
reasons) or, alternatively, access this backend through the network
|
||||
daemon <B><A HREF="saned.8.html">saned(8)</A></B>.
|
||||
|
||||
If the Mustek backend blocks while sending the inqiury command to the
|
||||
If the Mustek backend blocks while sending the inquiry command to the
|
||||
scanner, add the option <B>force-wait</B> to <I>mustek.conf</I>.
|
||||
|
||||
Also note that after a while of no activity, some scanners themselves
|
||||
|
|
@ -311,7 +311,7 @@
|
|||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B>sane-</B>
|
||||
<B><A HREF="gt68xx.5.html">gt68xx(5)</A></B>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>
|
||||
<I>/usr/local/doc/sane-1.0.17/mustek/mustek.CHANGES</I>
|
||||
<I>/usr/local/doc/sane-1.0.18/mustek/mustek.CHANGES</I>
|
||||
<I>http://www.meier-geinitz.de/sane/mustek-backend/</I>
|
||||
|
||||
|
||||
|
|
@ -324,7 +324,7 @@
|
|||
</PRE>
|
||||
<H2>BUGS</H2><PRE>
|
||||
Scanning with the SCSI adapters supplied by Mustek is very slow at high
|
||||
resolutions and wide scanareas.
|
||||
resolutions and wide scan areas.
|
||||
|
||||
Some scanners (e.g. Paragon 1200 A3 + Pro, SE A3) need more testing.
|
||||
|
||||
|
|
@ -334,7 +334,7 @@
|
|||
More detailed bug information is available at the Mustek backend home-
|
||||
page: <I>http://www.meier-geinitz.de/sane/mustek-backend/</I>.
|
||||
|
||||
sane-backends 1.0.17 18 Sep 2005 <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>
|
||||
sane-backends 1.0.18 18 Sep 2005 <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -182,7 +182,7 @@
|
|||
<I>option</I> <I><name></I> <I>[<value>]</I>
|
||||
|
||||
Depending on the nature of the option, a value may or may not be
|
||||
present. Options always apply to the scanner definition that preceeds
|
||||
present. Options always apply to the scanner definition that precedes
|
||||
them. There are no global options. Options are also driver-specific:
|
||||
not all drivers support all possible options.
|
||||
|
||||
|
|
@ -241,7 +241,7 @@
|
|||
sufficient. The maximum delay is 100 ms.
|
||||
Note that every additional ms of delay can add up to 14 sec-
|
||||
onds to the total scanning time (highest resolution), so an
|
||||
as small as possible value is prefered.
|
||||
as small as possible value is preferred.
|
||||
Default value: 0
|
||||
Minimum: 0
|
||||
Maximum: 100
|
||||
|
|
@ -310,7 +310,7 @@
|
|||
</PRE>
|
||||
<H2>GLOBAL OPTIONS</H2><PRE>
|
||||
You can control the overall behaviour of the mustek_pp backend by
|
||||
global options which preceed any scanner definition in the
|
||||
global options which precede any scanner definition in the
|
||||
mustek_pp.conf file.
|
||||
Currently, there is only one global option:
|
||||
|
||||
|
|
@ -400,7 +400,7 @@
|
|||
</PRE>
|
||||
<H2>AUTHORS</H2><PRE>
|
||||
Jochen Eisinger <jochen.eisinger@gmx.net>
|
||||
Eddy De Greef <eddy_de_greef at tiscali dot be>
|
||||
Eddy De Greef <eddy_de_greef at scarlet dot be>
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
|
|||
|
|
@ -73,7 +73,7 @@
|
|||
<B>usb</B> <B>vendor_id</B> <B>product_id</B> statements which are already included into
|
||||
<I>mustek</I><B>_</B><I>usb.conf</I>. This is only supported with Linux 2.4.8 and higher
|
||||
and all systems that support libsub. "vendor_id" and "product_id" are
|
||||
hexadecimal numbers that identfy the scanner. If this doesn't work, a
|
||||
hexadecimal numbers that identify the scanner. If this doesn't work, a
|
||||
device name and the option specifying the scanner type must be placed
|
||||
in <I>mustek</I><B>_</B><I>usb.conf</I> as described above.
|
||||
|
||||
|
|
@ -131,7 +131,7 @@
|
|||
environment variable controls the debug level for this backend.
|
||||
Higher debug levels increase the verbosity of the output.
|
||||
|
||||
Value Descsription
|
||||
Value Description
|
||||
0 no output
|
||||
1 print fatal errors
|
||||
2 print important messages
|
||||
|
|
@ -148,8 +148,8 @@
|
|||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>, <B>sane-plus-</B>
|
||||
<B><A HREF="tek.5.html">tek(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>, <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>
|
||||
<I>/usr/local/doc/sane-1.0.17/mustek</I><B>_</B><I>usb/mustek</I><B>_</B><I>usb.CHANGES</I>,
|
||||
<I>/usr/local/doc/sane-1.0.17/mustek</I><B>_</B><I>usb/mustek</I><B>_</B><I>usb.TODO</I>
|
||||
<I>/usr/local/doc/sane-1.0.18/mustek</I><B>_</B><I>usb/mustek</I><B>_</B><I>usb.CHANGES</I>,
|
||||
<I>/usr/local/doc/sane-1.0.18/mustek</I><B>_</B><I>usb/mustek</I><B>_</B><I>usb.TODO</I>
|
||||
<I>http://www.meier-geinitz.de/sane/mustek</I><B>_</B><I>usb-backend/</I>
|
||||
|
||||
|
||||
|
|
@ -166,16 +166,16 @@
|
|||
can't be reset (toggle = DATA0). That means, any operation that tries
|
||||
to reset the device will result in running into timeouts.
|
||||
|
||||
In earlier versions this backend failed when it is loaded the second
|
||||
In earlier versions this backend failed when it was loaded the second
|
||||
time in some configurations. The only choice was to replug the scanner
|
||||
in this case. The backend uses a workaround for that bug now but it's
|
||||
only tested on Linux. Reports for other operating systems are apprici-
|
||||
only tested on Linux. Reports for other operating systems are appreci-
|
||||
ated.
|
||||
|
||||
More detailed bug information is available at the Mustek backend home-
|
||||
page <I>http://www.meier-geinitz.de/sane/mustek</I><B>_</B><I>usb-backend/</I>.
|
||||
|
||||
sane-backends 1.0.17 3 Mar 2004 <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>
|
||||
sane-backends 1.0.18 3 Mar 2004 <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -47,10 +47,6 @@
|
|||
|
||||
</PRE>
|
||||
<H2>FILES</H2><PRE>
|
||||
<I>/usr/local/etc/sane.d/mustek</I><B>_</B><I>usb2.conf</I>
|
||||
The backend configuration file (see also description of
|
||||
<B>SANE_CONFIG_DIR</B> below).
|
||||
|
||||
<I>/usr/local/lib/sane/libsane-mustek</I><B>_</B><I>usb2.a</I>
|
||||
The static library implementing this backend.
|
||||
|
||||
|
|
@ -61,20 +57,6 @@
|
|||
|
||||
</PRE>
|
||||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in
|
||||
/usr/local/etc/sane.d. If the value of the environment variable
|
||||
ends with the directory separator character, then the default
|
||||
directories are searched after the explicitly specified directo-
|
||||
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
|
||||
would result in directories "tmp/config", ".", and
|
||||
"/usr/local/etc/sane.d" being searched (in this order).
|
||||
|
||||
<B>SANE_DEBUG_MUSTEK_USB2</B>
|
||||
If the library was compiled with debug support enabled, this
|
||||
environment variable controls the debug level for this backend.
|
||||
|
|
@ -87,7 +69,7 @@
|
|||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>, <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>, <B>sane-</B>
|
||||
<B><A HREF="mustek_usb.5.html">mustek_usb(5)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>
|
||||
<I>/usr/local/doc/sane-1.0.17/mustek</I><B>_</B><I>usb2/mustek</I><B>_</B><I>usb2.CHANGES</I>
|
||||
<I>/usr/local/doc/sane-1.0.18/mustek</I><B>_</B><I>usb2/mustek</I><B>_</B><I>usb2.CHANGES</I>
|
||||
<I>http://www.meier-geinitz.de/sane/mustek</I><B>_</B><I>usb2-backend/</I>
|
||||
|
||||
|
||||
|
|
@ -103,7 +85,7 @@
|
|||
geinitz.de>. Please send a debug log if your scanner isn't detected
|
||||
correctly (see SANE_DEBUG_MUSTEK_USB2 above).
|
||||
|
||||
sane-backends 1.0.17 29 Sep 2005 <B><A HREF="sane-mustek_usb2.5.html">sane-mustek_usb2(5)</A></B>
|
||||
sane-backends 1.0.18 15 Apr 2006 <B><A HREF="sane-mustek_usb2.5.html">sane-mustek_usb2(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@
|
|||
<H2>AUTHORS</H2><PRE>
|
||||
Kazuya Fukuda
|
||||
|
||||
sane-backends 1.0.17 17 Feb 2000 <B><A HREF="sane-nec.5.html">sane-nec(5)</A></B>
|
||||
sane-backends 1.0.18 17 Feb 2000 <B><A HREF="sane-nec.5.html">sane-nec(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -131,7 +131,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
David Mosberger and Andreas Beck
|
||||
|
||||
sane-backends 1.0.17 8 Oct 2002 <B><A HREF="sane-net.5.html">sane-net(5)</A></B>
|
||||
sane-backends 1.0.18 8 Oct 2002 <B><A HREF="sane-net.5.html">sane-net(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -22,11 +22,13 @@
|
|||
to support the following models:
|
||||
|
||||
MANUFACTURER: MODEL: USB ID:
|
||||
--------------- -------------- ---------
|
||||
Agfa Snapscan Touch 06BD-0100 (1)(a)
|
||||
Hewlett-Packard Scanjet 3300c 03F0-0205 (1)(a)(b)
|
||||
Hewlett-Packard Scanjet 3400c 03F0-0405 (2)(b)
|
||||
Hewlett-Packard Scanjet 4300c 03F0-0305 (2)(a)
|
||||
--------------- ---------------- ---------
|
||||
Agfa Snapscan Touch 06BD-0100 (1)(a)
|
||||
Trust Office Scan 19200 047B-1000 (1)(a)
|
||||
Hewlett-Packard Scanjet 3300c 03F0-0205 (1)(a)(b)
|
||||
Hewlett-Packard Scanjet 3400c 03F0-0405 (2)(b)
|
||||
Hewlett-Packard Scanjet 4300c 03F0-0305 (2)(a)
|
||||
Silitek ScanJet 4300c 047B-1002 (2)(b)
|
||||
|
||||
ASIC: (1) - NIASH00012/00013/00014 / (2) - NIASH00019
|
||||
ANALOG FRONT-END: (a) - ESIC ES8100QA / (b) - WM8143-12
|
||||
|
|
@ -78,7 +80,8 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
Bertrik Sikken <bertrik@zonnet.nl>
|
||||
|
||||
sane-backends 1.0.17 29 July 2004 <B><A HREF="sane-niash.5.html">sane-niash(5)</A></B>
|
||||
|
||||
sane-backends 1.0.18 29 July 2004 <B><A HREF="sane-niash.5.html">sane-niash(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -66,7 +66,7 @@
|
|||
Please send any information and bug-reports to:
|
||||
<B>Simon</B> <B>Munton</B> <B><simon@munton.demon.co.uk></B>
|
||||
|
||||
sane-backends 1.0.17 7 Sept 2000 <B><A HREF="sane-pie.5.html">sane-pie(5)</A></B>
|
||||
sane-backends 1.0.18 7 Sept 2000 <B><A HREF="sane-pie.5.html">sane-pie(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -134,7 +134,7 @@
|
|||
No testing has been done on three-pass or handheld scanners, or with
|
||||
Automatic Document Feeder support.
|
||||
|
||||
sane-backends 1.0.17 13 May 1998 <B><A HREF="sane-pint.5.html">sane-pint(5)</A></B>
|
||||
sane-backends 1.0.18 13 May 1998 <B><A HREF="sane-pint.5.html">sane-pint(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -0,0 +1,126 @@
|
|||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>sane-pixma.5</TITLE>
|
||||
</HEAD>
|
||||
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="/images/sane.png" HEIGHT=117 WIDTH=346></H1>
|
||||
<H1>sane-pixma.5</H1>
|
||||
<HR>
|
||||
<PRE>
|
||||
<!-- Manpage converted by man2html 3.0.1 -->
|
||||
<B><A HREF="sane-pixma.5.html">sane-pixma(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-pixma.5.html">sane-pixma(5)</A></B>
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>NAME</H2><PRE>
|
||||
sane-pixma - SANE backend for Canon PIXMA MP series
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>DESCRIPTION</H2><PRE>
|
||||
The <B>sane-pixma</B> library implements a SANE (Scanner Access Now Easy)
|
||||
backend that provides access to Canon PIXMA multi-function devices
|
||||
(All-in-one printers). Currently, the following models work with this
|
||||
backend:
|
||||
|
||||
PIXMA MP150, PIXMA MP170, PIXMA MP450, PIXMA MP500
|
||||
PIXMA MP800, PIXMA MP830,
|
||||
MultiPASS MP700 (no grayscale), PIXMA MP750 (no grayscale)
|
||||
|
||||
The following model are marked as experimental because they are not
|
||||
well tested and/or the scanner sometimes hangs and must be switched off
|
||||
and on. Therefore they are disabled by default. (See PIXMA_EXPERIMENT
|
||||
below)
|
||||
|
||||
MultiPASS MP730, PIXMA MP760, PIXMA MP780
|
||||
|
||||
The backend supports
|
||||
* resolutions at 75,150,300,600,1200 and 2400 DPI,
|
||||
* color and grayscale mode,
|
||||
* a custom gamma table with 4096 entries and
|
||||
* automatic document feeder.
|
||||
|
||||
The device name is in the form pixma:xxxxyyyy_zzzzz where x, y and z
|
||||
are vendor ID, product ID and serial number respectively. Example:
|
||||
pixma:04A91709_123456 is a MP150.
|
||||
|
||||
This backend is in <B>alpha</B> stage and will stay in this stage until we get
|
||||
the programming manual for the hardware. Although we have tested it as
|
||||
good as we could, it will not work in every situations. You will find
|
||||
an up-to-date status at the project homepage. (See below)
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>OPTIONS</H2><PRE>
|
||||
Besides "well-known" options (e.g. resolution, mode etc.) pixma backend
|
||||
also provides the following <B>experimental</B> options for button handling,
|
||||
i.e. the options might change in the future.
|
||||
|
||||
<I>button-controlled</I>
|
||||
This option can be used in combination with <B><A HREF="scanadf.1.html">scanadf(1)</A></B> and <B>scan-</B>
|
||||
<B><A HREF="image.1.html">image(1)</A></B> in batch mode, for example when you want to scan many
|
||||
photos or multiple-page documents. If it is enabled (i.e. is set
|
||||
to true or yes), the backend waits before every scan until the
|
||||
user presses the "SCAN" button (for MP150) or the color-scan
|
||||
button (for other models). Just put the first page in the scan-
|
||||
ner, press the button, then the next page, press the button and
|
||||
so on. When you finished, press the gray-scan button. (For MP150
|
||||
you have to stop the frontend by pressing Ctrl-C for example.)
|
||||
|
||||
<I>button-update</I> <I>button-1</I> <I>button-2</I>
|
||||
These options are interesting for developers. To check button
|
||||
status: (1) set <I>button-1</I> and <I>button-2</I> to zero, (2) set <I>button-</I>
|
||||
<I>update</I> (Its type is SANE_TYPE_BUTTON.), (3) get <I>button-1</I> and
|
||||
<I>button-2</I>. If the result is not zero, the corresponding button
|
||||
was pressed.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>FILES</H2><PRE>
|
||||
<I>/usr/local/lib/sane/libsane-pixma.a</I>
|
||||
The static library implementing this backend.
|
||||
|
||||
<I>/usr/local/lib/sane/libsane-pixma.so</I>
|
||||
The shared library implementing this backend (present on systems
|
||||
that support dynamic loading).
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_DEBUG_PIXMA</B>
|
||||
If the library was compiled with debug support enabled, this
|
||||
environment variable controls the debug level for this backend.
|
||||
Higher value increases the verbosity.
|
||||
|
||||
0 print nothing
|
||||
1 print error and warning messages (recommended)
|
||||
2 print informational messages
|
||||
3 print debug-level messages
|
||||
10 dump USB traffics
|
||||
|
||||
<B>PIXMA_EXPERIMENT</B>
|
||||
Setting to a non-zero value will enable the support for experi-
|
||||
mental models. You should also set SANE_DEBUG_PIXMA to 10.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>, <I>http://home.arcor.de/wittawat/pixma/</I>
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>AUTHOR</H2><PRE>
|
||||
Wittawat Yamwong
|
||||
|
||||
I would like to thank all testers and helpers. Without them I would not
|
||||
be able to write subdrivers for models I don't have. See also the
|
||||
project homepage.
|
||||
|
||||
sane-backends 1.0.18 1 July 2006 <B><A HREF="sane-pixma.5.html">sane-pixma(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
Man(1) output converted with
|
||||
<a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a>
|
||||
</ADDRESS>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
|
@ -105,6 +105,12 @@
|
|||
CanoScan LIDE25 LM9833 1200x2400dpi 48bit 512Kb 0x2220
|
||||
CanoScan LIDE30 LM9833 1200x2400dpi 48bit 512Kb 0x220E
|
||||
|
||||
Vendor Syscan - ID: 0x0A82
|
||||
----------------------------------------------------------
|
||||
USB Model: ASIC: Properties: Prod-ID
|
||||
----------------------------------------------------------
|
||||
Travelscan 662 LM9833 600x1200dpi 48bit 512Kb 0x6620
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>OTHER PLUSTEK SCANNERS</H2><PRE>
|
||||
|
|
@ -141,7 +147,7 @@
|
|||
its own. If device is set to <I>auto</I> then the next matching device is
|
||||
used.
|
||||
The following options can be used for a default setup of your device.
|
||||
Most of them are also availaby through the frontend.
|
||||
Most of them are also available through the frontend.
|
||||
|
||||
<B>The</B> <B>Options:</B>
|
||||
|
||||
|
|
@ -170,8 +176,8 @@
|
|||
invert picture
|
||||
|
||||
option cacheCalData b
|
||||
<I>b</I> 0 --> do not save coarse calibration results, 1 --> save
|
||||
results of coarse calibration in ~/.sane/ directory
|
||||
<I>b</I> 0 --> do not save calibration results, 1 --> save results of
|
||||
calibration in ~/.sane/ directory
|
||||
|
||||
option altCalibration b
|
||||
<I>b</I> 0 --> use standard calibration routines, 1 --> use alternate
|
||||
|
|
@ -281,7 +287,7 @@
|
|||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-u12.5.html">sane-u12(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>,
|
||||
<I>/usr/local/doc/sane-1.0.17/plustek/Plustek-USB.changes</I>
|
||||
<I>/usr/local/doc/sane-1.0.18/plustek/Plustek-USB.changes</I>
|
||||
<I>http://www.gjaeger.de/scanner/plustek/</I>
|
||||
|
||||
|
||||
|
|
@ -312,20 +318,20 @@
|
|||
<H2>KNOWN BUGS & RESTRICTIONS</H2><PRE>
|
||||
* The driver does not support these manic scalings up to 16 times the
|
||||
physical resolution. The only scaling is done on resolutions between
|
||||
the physical resolution of the CDD-sensor and the stepper motor i.e.
|
||||
you have a 600x1200 dpi scanner and you are scanning using 800dpi, so
|
||||
scaling is necesary, because the sensor only delivers 600dpi but the
|
||||
motor is capable to perform 1200dpi steps.
|
||||
the physical resolution of the CCD-/CIS-sensor and the stepper motor
|
||||
i.e. you have a 600x1200 dpi scanner and you are scanning using 800dpi,
|
||||
so scaling is necessary, because the sensor only delivers 600dpi but
|
||||
the motor is capable to perform 1200dpi steps.
|
||||
|
||||
* Plusteks' model policy is somewhat inconsistent. This means, they
|
||||
sell technical different devices under the same product name. Therefore
|
||||
it is possible that some devices like the UT12 or U12 won't work -
|
||||
please check the model list above and compare the product-id to the one
|
||||
your device has.
|
||||
* Plusteks' model policy is somewhat inconsistent. They sell techni-
|
||||
cally different devices under the same product name. Therefore it is
|
||||
possible that some devices like the UT12 or U12 won't work - please
|
||||
check the model list above and compare the product-id to the one your
|
||||
device has.
|
||||
|
||||
* Negative/Slide scanning quality is poor.
|
||||
|
||||
sane-backends 1.0.17 08 August 2005 <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
|
||||
sane-backends 1.0.18 09 April 2006 <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -118,7 +118,7 @@
|
|||
|
||||
</PRE>
|
||||
<H2>CONFIGURATION</H2><PRE>
|
||||
This section decribes the backends' configuration file entries. The
|
||||
This section describes the backends' configuration file entries. The
|
||||
file is located at: <I>/usr/local/etc/sane.d/plustek</I><B>_</B><I>pp.conf</I>
|
||||
|
||||
For a proper setup, you will need at least two entries:
|
||||
|
|
@ -161,12 +161,12 @@
|
|||
detected) swaps red/green color
|
||||
|
||||
<I>m</I> = 3 OpticPro 9636 override (works if OP9636 has been
|
||||
detected) disables backends transparency/negativ capabil-
|
||||
ities
|
||||
detected) disables backends transparency/negative capa-
|
||||
bilities
|
||||
|
||||
<I>m</I> = 4 OpticPro 9636P override (works if OP9636 has been
|
||||
detected) disables backends transparency/negativ capabil-
|
||||
ities
|
||||
detected) disables backends transparency/negative capa-
|
||||
bilities
|
||||
|
||||
<I>m</I> = 5 OpticPro A3I override (works if OP12000 has been
|
||||
detected) enables A3 scanning
|
||||
|
|
@ -217,7 +217,8 @@
|
|||
|
||||
port=ppp
|
||||
<I>ppp</I> specifies the port base address, where the scanner is con-
|
||||
nected to. The default value is 0x378 which normaly is standard.
|
||||
nected to. The default value is 0x378, which normaly is stan-
|
||||
dard.
|
||||
|
||||
warmup=www
|
||||
<I>www</I> specifies the time in seconds, how long a lamp has to be on,
|
||||
|
|
@ -246,12 +247,12 @@
|
|||
detected) swaps red/green color
|
||||
|
||||
<I>m</I> = 3 OpticPro 9636 override (works if OP9636 has been
|
||||
detected) disables backends transparency/negativ capabil-
|
||||
ities
|
||||
detected) disables backends transparency/negative capa-
|
||||
bilities
|
||||
|
||||
<I>m</I> = 4 OpticPro 9636P override (works if OP9636 has been
|
||||
detected) disables backends transparency/negativ capabil-
|
||||
ities
|
||||
detected) disables backends transparency/negative capa-
|
||||
bilities
|
||||
|
||||
<I>m</I> = 5 OpticPro A3I override (works if OP12000 has been
|
||||
detected) enables A3 scanning
|
||||
|
|
@ -338,11 +339,10 @@
|
|||
Example: export SANE_DEBUG_PLUSTEK_PP=10
|
||||
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>,
|
||||
<I>/usr/local/doc/sane-1.0.17/plustek/Plustek-PARPORT.changes</I>
|
||||
<I>/usr/local/doc/sane-1.0.18/plustek/Plustek-PARPORT.changes</I>
|
||||
<I>http://www.gjaeger.de/scanner/plustek</I><B>_</B><I>pp/</I>
|
||||
|
||||
|
||||
|
|
@ -376,19 +376,19 @@
|
|||
|
||||
* The driver does not support these manic scalings up to 16 times the
|
||||
physical resolution. The only scaling is done on resolutions between
|
||||
the physical resolution of the CDD-sensor and the stepper motor i.e.
|
||||
the physical resolution of the CCD-sensor and the stepper motor i.e.
|
||||
you have a 600x1200 dpi scanner and you are scanning using 800dpi, so
|
||||
scaling is necesary, because the sensor only delivers 600dpi but the
|
||||
scaling is necessary, because the sensor only delivers 600dpi but the
|
||||
motor is capable to perform 800dpi steps.
|
||||
|
||||
* On some devices, the pictures seems to be bluished
|
||||
* On some devices, the pictures seems bluish
|
||||
|
||||
<I>ASIC</I> <I>98001</I> <I>based</I> <I>models:</I>
|
||||
|
||||
* The 300dpi transparency and negative mode does not work correctly.
|
||||
|
||||
* There is currently no way to distinguish a model with and without
|
||||
transpareny unit.
|
||||
transparency unit.
|
||||
|
||||
* The scanned images seem to be too dark (P9636T)
|
||||
|
||||
|
|
@ -396,15 +396,16 @@
|
|||
|
||||
* 30bit mode is currently not supported.
|
||||
|
||||
* On low-end systems and under heavy system load, the driver will loose
|
||||
data, this might causes the sensor to hit the scan-bed and/or the pic-
|
||||
ture is corrupted.
|
||||
* On low end systems under heavy system load the driver may lose data,
|
||||
which can result in picture corruption or cause the sensor to hit the
|
||||
scan bed.
|
||||
|
||||
* The scanspeed on 600x1200 dpi models is slow.
|
||||
* The scanning speed on 600x1200 dpi models is slow.
|
||||
|
||||
* The scanquality of the A3I is poor
|
||||
* The scanning quality of the A3I is poor
|
||||
|
||||
sane-backends 1.0.17 18 June 2004 <B><A HREF="sane-plustek_pp.5.html">sane-plustek_pp(5)</A></B>
|
||||
|
||||
sane-backends 1.0.18 18 June 2004 <B><A HREF="sane-plustek_pp.5.html">sane-plustek_pp(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -74,7 +74,7 @@
|
|||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>
|
||||
|
||||
sane-backends 1.0.17 22 April 2001 <B><A HREF="sane-pnm.5.html">sane-pnm(5)</A></B>
|
||||
sane-backends 1.0.18 22 April 2001 <B><A HREF="sane-pnm.5.html">sane-pnm(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -101,7 +101,7 @@
|
|||
work fine, but others result in shifted images (sounds like a problem
|
||||
due to byte-padding).
|
||||
|
||||
The program needs root-priviledges since it needs to be able to access
|
||||
The program needs root-privileges since it needs to be able to access
|
||||
the camera's I/O ports.
|
||||
|
||||
|
||||
|
|
@ -109,7 +109,7 @@
|
|||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>
|
||||
|
||||
sane-backends 1.0.17 25 October 1997 <B><A HREF="sane-qcam.5.html">sane-qcam(5)</A></B>
|
||||
sane-backends 1.0.18 25 October 1997 <B><A HREF="sane-qcam.5.html">sane-qcam(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -85,7 +85,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
Feico W. Dillema
|
||||
|
||||
sane-backends 1.0.17 24 Jun 2000 <B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B>
|
||||
sane-backends 1.0.18 24 Jun 2000 <B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -83,7 +83,7 @@
|
|||
Ingo Schneider
|
||||
|
||||
|
||||
sane-backends 1.0.17 24 Jun 2000 <B><A HREF="sane-s9036.5.html">sane-s9036(5)</A></B>
|
||||
sane-backends 1.0.18 24 Jun 2000 <B><A HREF="sane-s9036.5.html">sane-s9036(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -44,10 +44,10 @@
|
|||
<B>Scan</B> <B>Mode</B>
|
||||
|
||||
<B>--mode</B> selects the basic mode of operation of the scanner valid choices
|
||||
are <I>Lineart,</I> <I>Halftone,</I> <I>Gray</I> <I>and</I> <I>Color.</I> The Lineart and Haltone
|
||||
are <I>Lineart,</I> <I>Halftone,</I> <I>Gray</I> <I>and</I> <I>Color.</I> The Lineart and Halftone
|
||||
mode are black and white only (1 bit). Gray will produce 256
|
||||
levels of gray (8 bits). Color will produce a 24 bits color
|
||||
image. The scanner suports 30 bits internally but it only
|
||||
image. The scanner supports 30 bits internally but it only
|
||||
exports 24.
|
||||
|
||||
<B>--resolution</B>
|
||||
|
|
@ -93,7 +93,7 @@
|
|||
<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 milimeters by
|
||||
the scan area. All parameters are specified in millimeters by
|
||||
default.
|
||||
|
||||
|
||||
|
|
@ -147,7 +147,7 @@
|
|||
The package is actively maintained by Frank Zago.
|
||||
<I>http://www.zago.net/sane/#sceptre</I>
|
||||
|
||||
sane-backends 1.0.17 April 21st, 2002 <B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B>
|
||||
sane-backends 1.0.18 April 21st, 2002 <B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -124,8 +124,8 @@
|
|||
Adaptec 1522
|
||||
The scanner probes ok but any attempt to access it <I>hangs</I>
|
||||
the entire system. It looks like something is disabling
|
||||
interrupts and then not reenabling them, so it looks like
|
||||
a bug in the FreeBSD <B>aic</B> driver.
|
||||
interrupts and then not re-enabling them, so it looks
|
||||
like a bug in the FreeBSD <B>aic</B> driver.
|
||||
|
||||
Adaptec 1505
|
||||
Works on FreeBSD 2.2.5R and 3.0 using the <B>aic</B> driver,
|
||||
|
|
@ -235,7 +235,7 @@
|
|||
umentation is in this file and NCR5380.c.
|
||||
|
||||
NCR/Symbios 810
|
||||
For some scanners it may be necssary to disable discon-
|
||||
For some scanners it may be necessary to disable discon-
|
||||
nect/reconnect. To achieve this use the option
|
||||
ncr53c8xx="disc:n". Some people reported that their scan-
|
||||
ner only worked with the 53c7,8xx driver, not the
|
||||
|
|
@ -303,7 +303,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
David Mosberger
|
||||
|
||||
sane-backends 1.0.17 28 Oct 2003 <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>
|
||||
sane-backends 1.0.18 28 Oct 2003 <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -102,7 +102,7 @@
|
|||
.. 255 (i.e., gamma == 1). This table is only used for gray scale
|
||||
scans.
|
||||
|
||||
<B>Red</B> <B>Gamma</B> <B>Table</B> (paramter <B>--red-gamma-table</B> for scanimage). Allowed
|
||||
<B>Red</B> <B>Gamma</B> <B>Table</B> (parameter <B>--red-gamma-table</B> for scanimage). Allowed
|
||||
values: 0..255; 256 numbers must be defined. The default values are 0,
|
||||
1, 2, .. 255 (i.e., gamma == 1).
|
||||
|
||||
|
|
@ -191,7 +191,7 @@
|
|||
|
||||
</PRE>
|
||||
<H2>ADF USAGE</H2><PRE>
|
||||
If a paper jam occured, the maintenance cover <I>must</I> be opened and
|
||||
If a paper jam occurred, the maintenance cover <I>must</I> be opened and
|
||||
closed, even if the jammed paper can be removed without opening the
|
||||
maintenance cover. Otherwise, the error condition cannot be cleared.
|
||||
|
||||
|
|
@ -236,7 +236,7 @@
|
|||
|
||||
|
||||
</PRE>
|
||||
<H2>Performance Considarations</H2><PRE>
|
||||
<H2>Performance Considerations</H2><PRE>
|
||||
This section focuses on the problem of stops of the scanner's carriage
|
||||
during a scan. Carriage stops happen mainly with the JX-250. This scan-
|
||||
ner has obviously only a small internal buffer compared to its speed.
|
||||
|
|
@ -255,7 +255,7 @@
|
|||
|
||||
- too much "traffic" on the SCSI bus
|
||||
- slow responses by the backend to the scanner,
|
||||
- a program which processes the data aquired by the backend too
|
||||
- a program which processes the data acquired by the backend too
|
||||
slow.
|
||||
|
||||
Too much "traffic" on the SCSI bus: This happens for example, if hard
|
||||
|
|
@ -280,7 +280,7 @@
|
|||
mended, because it supports, in combination with the SCSI library of
|
||||
Sane version 1.0.2, command queueing within the kernel. This queueing
|
||||
implementation, combined with a buffer size of at least 128 kB, should
|
||||
avoid most carirage stops.
|
||||
avoid most carriage stops.
|
||||
|
||||
Slow processing of the scan data: An example for this situation is the
|
||||
access to the scanner via a 10 MBit Ethernet, which is definitely too
|
||||
|
|
@ -366,7 +366,7 @@
|
|||
Parts of this man page are a plain copy of <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B> by David Mos-
|
||||
berger-Tang, Andreas Czechanowski and Andreas Bolsch
|
||||
|
||||
sane-backends 1.0.17 21 Nov 2000 <B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B>
|
||||
sane-backends 1.0.18 21 Nov 2000 <B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -93,7 +93,7 @@
|
|||
Marian Eichholz (eichholz@computer.org)
|
||||
Glenn Ramsey (glenn@componic.com)
|
||||
|
||||
sane-backends 1.0.17 16 August 2005 <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B>
|
||||
sane-backends 1.0.18 16 August 2005 <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -98,7 +98,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
Earle F. Philhower III (earle@ziplabel.com)
|
||||
|
||||
sane-backends 1.0.17 Mar 15, 2005 <B><A HREF="sane-sm3840.5.html">sane-sm3840(5)</A></B>
|
||||
sane-backends 1.0.18 Mar 15, 2005 <B><A HREF="sane-sm3840.5.html">sane-sm3840(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -114,7 +114,7 @@
|
|||
Man page by Henning Meier-Geinitz (mostly based on the web pages and
|
||||
source code).
|
||||
|
||||
sane-backends 1.0.17 26 May 2001 <B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B>
|
||||
sane-backends 1.0.18 26 May 2001 <B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -78,7 +78,7 @@
|
|||
working first driver. Watch this space for changes.
|
||||
|
||||
|
||||
sane-backends 1.0.17 17 Apr 2002 <B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B>
|
||||
sane-backends 1.0.18 17 Apr 2002 <B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -153,7 +153,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
Ingo Wilken <Ingo.Wilken@informatik.uni-oldenburg.de>
|
||||
|
||||
sane-backends 1.0.17 08 Mar 1999 <B><A HREF="sane-st400.5.html">sane-st400(5)</A></B>
|
||||
sane-backends 1.0.18 08 Mar 1999 <B><A HREF="sane-st400.5.html">sane-st400(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -0,0 +1,173 @@
|
|||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>sane-stv680.5</TITLE>
|
||||
</HEAD>
|
||||
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="/images/sane.png" HEIGHT=117 WIDTH=346></H1>
|
||||
<H1>sane-stv680.5</H1>
|
||||
<HR>
|
||||
<PRE>
|
||||
<!-- Manpage converted by man2html 3.0.1 -->
|
||||
<B><A HREF="sane-stv680.5.html">sane-stv680(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-stv680.5.html">sane-stv680(5)</A></B>
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>NAME</H2><PRE>
|
||||
sane-stv680 - SANE backend for STV680 camera's
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>DESCRIPTION</H2><PRE>
|
||||
The <B>sane-stv680</B> library implements a SANE (Scanner Access Now Easy)
|
||||
backend that provides access to some STV680 cameras. This backend
|
||||
should be considered <B>beta-quality</B> software! STV680 cameras are sold
|
||||
under various brands like Aiptek. This backend may or may not support
|
||||
yours.
|
||||
|
||||
The cameras that should work with this backend are:
|
||||
|
||||
Vendor Model USB vendor id USB product id status
|
||||
------------------------ ------------- -------------- --------
|
||||
AIPTEK stv680 0x0553 0x0202 basic
|
||||
Konica e-mini 0x04c8 0x0722 untested
|
||||
DigitalDream l'espion XS 0x1183 0x0001 untested
|
||||
Creative WebCam Go mini 0x041e 0x4007 untested
|
||||
|
||||
For all these cameras, see the backend home page (under AUTHOR) for the
|
||||
exact status of each camera.
|
||||
|
||||
For startup of this backend check that if present the stv680 kernel
|
||||
module is removed or disabled.
|
||||
Also before using, enable the backend by editing the
|
||||
/etc/sane.d/dll.conf file, change #stv680 to stv680.
|
||||
|
||||
For problems with the untested cameras, you should contact the author
|
||||
for that.
|
||||
|
||||
The options the backend supports can either be selected through command
|
||||
line options to programs like scanimage or through GUI elements in
|
||||
xcam. For both programs use the -B option needed for size buffer.
|
||||
|
||||
Some frontends examples:
|
||||
xcam
|
||||
xcam -B
|
||||
|
||||
scanimage: for writing in batch mode to a file or to a new file each
|
||||
time.
|
||||
scanimage -B -d stv680:libusb:001:002 --batch=out.ppm --batch-
|
||||
count 5 --mode "Color RGB"
|
||||
scanimage -B -d stv680:libusb:001:002 --batch=out%d.ppm --batch-
|
||||
count 5 --mode "Color RGB"
|
||||
|
||||
If you have any success with a camera not listed here, or if you have
|
||||
any strange behavior, please report to the backend maintainer or to the
|
||||
SANE mailing list.
|
||||
|
||||
Valid command line options and their syntax can be listed by using
|
||||
scanimage --help -d stv680
|
||||
|
||||
<B>Scan</B> <B>Mode</B>
|
||||
|
||||
<B>--mode</B> selects the basic mode of operation of the webcams valid
|
||||
choices.
|
||||
|
||||
The read resolution mode is 8 bits, output resolution is 24
|
||||
bits. Selects the resolution for a scan. The camera can do
|
||||
only the resolutions listed.
|
||||
|
||||
<B>--Raw</B> In this mode raw data is displayed
|
||||
|
||||
<B>--Color</B>
|
||||
In this mode the bayer unshuffle is done but no color correction
|
||||
|
||||
<B>--Color_RGB</B>
|
||||
Bayer unshuffle, color correction
|
||||
|
||||
<B>--Color_RGB_TXT</B>
|
||||
Bayer unshuffle, color correction, textline with date and time
|
||||
is added
|
||||
|
||||
<B>Enhancement</B> <B>options</B>
|
||||
|
||||
<B>--white-level-r</B>
|
||||
Selects what red radiance level should be considered "white",
|
||||
when scanning some sheets by changing the calibration value
|
||||
loaded into the scanner. Scale -32 .. 0 .. +32 in steps of 1.
|
||||
|
||||
<B>--white-level-g</B>
|
||||
Selects what green radiance level should be considered "white",
|
||||
when scanning some sheets by changing the calibration i value
|
||||
loaded into the scanner. Scale -32 .. 0 .. +32 in steps of 1.
|
||||
|
||||
<B>--white-level-b</B>
|
||||
Selects what blue radiance level should be considered "white",
|
||||
when scanning some sheets by changing the calibration value
|
||||
loaded into the scanner. Scale -32 .. 0 .. +32 in steps of 1.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONFIGURATION FILE</H2><PRE>
|
||||
The configuration file /usr/local/etc/sane.d/stv680.conf supports only
|
||||
one information: the device name to use (eg usb 0x.... 0x....).
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>FILES</H2><PRE>
|
||||
<I>/usr/local/lib/sane/libsane-stv680.a</I>
|
||||
The static library implementing this backend.
|
||||
|
||||
<I>/usr/local/lib/sane/libsane-stv680.so</I>
|
||||
The shared library implementing this backend (present on systems
|
||||
that support dynamic loading).
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_DEBUG_STV680</B>
|
||||
If the library was compiled with debug support enabled, this
|
||||
environment variable controls the debug level for this backend.
|
||||
E.g., a value of 128 requests all debug output to be printed.
|
||||
Smaller levels reduce verbosity.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>LIMITATIONS</H2><PRE>
|
||||
The windows TWAIN driver has many more options than this SANE backend.
|
||||
However they are only software adjustments. This backend only imple-
|
||||
ments what the webcam can support.
|
||||
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>BUGS</H2><PRE>
|
||||
Plenty. Parts of this backend are still under development.
|
||||
1. Some untested cameras.
|
||||
2. Video streaming slow and stops sometimes (scanimage).
|
||||
3. Sometimes 1/3 of image is NOK (xcam).
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<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>
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>AUTHORS</H2><PRE>
|
||||
Gerard Klaver http://gkall.hobby.nl/stv680-aiptek.html
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CREDITS</H2><PRE>
|
||||
Thanks to developers of the other stv680 programs:
|
||||
STV680 kernel module
|
||||
pencam2 program
|
||||
libghoto2 program (camlib stv0680)
|
||||
|
||||
sane-backends 1.0.18 09 June 2006 <B><A HREF="sane-stv680.5.html">sane-stv680(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
Man(1) output converted with
|
||||
<a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a>
|
||||
</ADDRESS>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
|
@ -87,7 +87,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
Roger Wolff
|
||||
|
||||
sane-backends 1.0.17 24 Jun 2000 <B><A HREF="sane-tamarack.5.html">sane-tamarack(5)</A></B>
|
||||
sane-backends 1.0.18 24 Jun 2000 <B><A HREF="sane-tamarack.5.html">sane-tamarack(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -166,7 +166,7 @@
|
|||
Thanks to Gerard Delafond for the VM4542 support. Thanks to Jean-Yves
|
||||
Simon for the VM3510 support.
|
||||
|
||||
sane-backends 1.0.17 August 30th, 2002 <B><A HREF="sane-teco1.5.html">sane-teco1(5)</A></B>
|
||||
sane-backends 1.0.18 August 30th, 2002 <B><A HREF="sane-teco1.5.html">sane-teco1(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -214,7 +214,7 @@
|
|||
Christoph.Hoeffner for testing the support for the VM3564 (Relisys AVEC
|
||||
II S3 firmware 1.09).
|
||||
|
||||
sane-backends 1.0.17 29 July 2005 <B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B>
|
||||
sane-backends 1.0.18 29 July 2005 <B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -139,7 +139,7 @@
|
|||
The package is actively maintained by Frank Zago.
|
||||
<I>http://www.zago.net/sane/#teco3</I>
|
||||
|
||||
sane-backends 1.0.17 25 July 2002 <B><A HREF="sane-teco3.5.html">sane-teco3(5)</A></B>
|
||||
sane-backends 1.0.18 25 July 2002 <B><A HREF="sane-teco3.5.html">sane-teco3(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -25,11 +25,11 @@
|
|||
|
||||
The idea is not only to find bugs in frontends but also to show all
|
||||
capabilities of SANE. Therefore <B>sane-test</B> implements functions and
|
||||
options that are not (or seldomly) found in other backends.
|
||||
options that are not (or seldom) found in other backends.
|
||||
|
||||
The backend is commented out in /usr/local/etc/sane.d/dll.conf, so
|
||||
either the comment character must be removed or the backend must be
|
||||
called explicitely. E.g. `scanimage -d test' or `xscanimage test'.
|
||||
called explicitly. E.g. `scanimage -d test' or `xscanimage test'.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -62,59 +62,62 @@
|
|||
|
||||
Option <B>resolution</B> sets the resolution of the image in dots per inch.
|
||||
|
||||
Option <B>source</B> can be used to simulate an Automatic Document Feeder
|
||||
(ADF). After 10 scans, the ADF will be "empty".
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>SPECIAL OPTIONS</H2><PRE>
|
||||
Option <B>test-picture</B> allows to set the image that's returned to the
|
||||
Option <B>test-picture</B> allows to set the image that's returned to the
|
||||
frontend. While "Solid white" and "Solid black" are quite obvious, the
|
||||
other options need some more explanation. Color patterns are used to
|
||||
determine if all modes and their colors are reprented correctly by the
|
||||
frontend. The grid should look like the same in every mode and resolu-
|
||||
tion. A table of all the test pictures can be found at:
|
||||
other options need some more explanation. Color patterns are used to
|
||||
determine if all modes and their colors are represented correctly by
|
||||
the frontend. The grid should look like the same in every mode and
|
||||
resolution. A table of all the test pictures can be found at:
|
||||
http://www.meier-geinitz.de/sane/test-backend/test-pictures.html.
|
||||
|
||||
If option <B>invert-endianess</B> is set, the upper and lower bytes of image
|
||||
data in 16 bit modes are exchanged. This option can be used to test
|
||||
the 16 bit modes of frontends, e.g. if the frontend uses the correct
|
||||
If option <B>invert-endianess</B> is set, the upper and lower bytes of image
|
||||
data in 16 bit modes are exchanged. This option can be used to test
|
||||
the 16 bit modes of frontends, e.g. if the frontend uses the correct
|
||||
endianess.
|
||||
|
||||
If option <B>read-limit</B> is set, the maximum amount of data tranferred with
|
||||
each call to sane_read() is limited.
|
||||
If option <B>read-limit</B> is set, the maximum amount of data transferred
|
||||
with each call to sane_read() is limited.
|
||||
|
||||
Option <B>read-limit-size</B> sets the limit for option read-limit. A low
|
||||
Option <B>read-limit-size</B> sets the limit for option read-limit. A low
|
||||
limit slows down scanning. It can be used to detect errors in frontend
|
||||
that occur because of wrong assumptions on the size of the buffer or
|
||||
that occur because of wrong assumptions on the size of the buffer or
|
||||
timing problems.
|
||||
|
||||
Option <B>read-delay</B> enables delaying data to the frontend.
|
||||
|
||||
Option <B>read-delay-duration</B> selects the number of microseconds the back-
|
||||
ends waits after each transfer of a buffer. This option is useful to
|
||||
ends waits after each transfer of a buffer. This option is useful to
|
||||
find timing-related bugs, especially if used over the network.
|
||||
|
||||
If option <B>read-return-value</B> is different from "Default", the selected
|
||||
status will be returned by every call to sane_read(). This is useful
|
||||
If option <B>read-return-value</B> is different from "Default", the selected
|
||||
status will be returned by every call to sane_read(). This is useful
|
||||
to test the frontend's handling of the SANE statii.
|
||||
|
||||
If option <B>ppl-loss</B> is different from 0, it determines the number of
|
||||
pixels that are "lost" at the end of each line. That means, lines are
|
||||
If option <B>ppl-loss</B> is different from 0, it determines the number of
|
||||
pixels that are "lost" at the end of each line. That means, lines are
|
||||
padded with unused data.
|
||||
|
||||
Option <B>fuzzy-parameters</B> selects that fuzzy (inexact) parameters are
|
||||
returned as long as the scan hasn't been started. This option can be
|
||||
used to test if the frontend uses the parameters it got before the
|
||||
Option <B>fuzzy-parameters</B> selects that fuzzy (inexact) parameters are
|
||||
returned as long as the scan hasn't been started. This option can be
|
||||
used to test if the frontend uses the parameters it got before the
|
||||
start of the scan (which it shouldn't).
|
||||
|
||||
Option <B>non-blocking</B> determines if non-blocking IO for sane_read()
|
||||
Option <B>non-blocking</B> determines if non-blocking IO for sane_read()
|
||||
should be used if supported by the frontend.
|
||||
|
||||
If option <B>select-fd</B> is set, the backend offers a select filedescriptor
|
||||
If option <B>select-fd</B> is set, the backend offers a select filedescriptor
|
||||
for detecting if sane_read() will return data.
|
||||
|
||||
If option <B>enable-test-options</B> is set, a fairly big list of options for
|
||||
If option <B>enable-test-options</B> is set, a fairly big list of options for
|
||||
testing the various SANE option types is enabled.
|
||||
|
||||
Option <B>print-options</B> can be used to print a list of all options to
|
||||
Option <B>print-options</B> can be used to print a list of all options to
|
||||
standard error.
|
||||
|
||||
|
||||
|
|
@ -131,35 +134,35 @@
|
|||
|
||||
</PRE>
|
||||
<H2>BOOL TEST OPTIONS</H2><PRE>
|
||||
There are 6 bool test options in total. Each option is numbered.
|
||||
(3/6) means: this is option 3 of 6. The numbering scheme is inetended
|
||||
for easier detection of options not displayed by the frontend (bevause
|
||||
There are 6 bool test options in total. Each option is numbered.
|
||||
(3/6) means: this is option 3 of 6. The numbering scheme is intended
|
||||
for easier detection of options not displayed by the frontend (because
|
||||
of missing support or bugs).
|
||||
|
||||
Option <B>bool-soft-select-soft-detect</B> (1/6) is a bool test option that
|
||||
has soft select and soft detect (and advanced) capabilities. That's
|
||||
Option <B>bool-soft-select-soft-detect</B> (1/6) is a bool test option that
|
||||
has soft select and soft detect (and advanced) capabilities. That's
|
||||
just a normal bool option.
|
||||
|
||||
Option <B>bool-hard-select-soft-detect</B> (2/6) is a bool test option that
|
||||
has hard select and soft detect (and advanced) capabilities. That
|
||||
means the option can't be set by the frontend but by the user (e.g. by
|
||||
Option <B>bool-hard-select-soft-detect</B> (2/6) is a bool test option that
|
||||
has hard select and soft detect (and advanced) capabilities. That
|
||||
means the option can't be set by the frontend but by the user (e.g. by
|
||||
pressing a button at the device).
|
||||
|
||||
Option <B>bool-hard-select</B> (3/6) is a bool test option that has hard
|
||||
Option <B>bool-hard-select</B> (3/6) is a bool test option that has hard
|
||||
select (and advanced) capabilities. That means the option can't be set
|
||||
by the frontend but by the user (e.g. by pressing a button at the
|
||||
by the frontend but by the user (e.g. by pressing a button at the
|
||||
device) and can't be read by the frontend.
|
||||
|
||||
Option <B>bool-soft-detect</B> (4/6) is a bool test option that has soft
|
||||
detect (and advanced) capabilities. That means the option is read-
|
||||
Option <B>bool-soft-detect</B> (4/6) is a bool test option that has soft
|
||||
detect (and advanced) capabilities. That means the option is read-
|
||||
only.
|
||||
|
||||
Option <B>bool-soft-select-soft-detect-emulated</B> (5/6) is a Bool test
|
||||
option that has soft select, soft detect, and emulated (and advanced)
|
||||
option that has soft select, soft detect, and emulated (and advanced)
|
||||
capabilities.
|
||||
|
||||
Option <B>bool-soft-select-soft-detect-auto</B> (6/6) is a Bool test option
|
||||
that has soft select, soft detect, and automatic (and advanced) capa-
|
||||
Option <B>bool-soft-select-soft-detect-auto</B> (6/6) is a Bool test option
|
||||
that has soft select, soft detect, and automatic (and advanced) capa-
|
||||
bilities. This option can be automatically set by the backend.
|
||||
|
||||
|
||||
|
|
@ -167,23 +170,23 @@
|
|||
<H2>INT TEST OPTIONS</H2><PRE>
|
||||
There are 6 int test options in total.
|
||||
|
||||
Option <B>int</B> (1/6) is an int test option with no unit and no constraint
|
||||
Option <B>int</B> (1/6) is an int test option with no unit and no constraint
|
||||
set.
|
||||
|
||||
Option <B>int-constraint-range</B> (2/6) is an int test option with unit pixel
|
||||
and constraint range set. Minimum is 4, maximum 192, and quant is 2.
|
||||
|
||||
Option <B>int-constraint-word-list</B> (3/6) is an int test option with unit
|
||||
Option <B>int-constraint-word-list</B> (3/6) is an int test option with unit
|
||||
bits and constraint word list set.
|
||||
|
||||
Option <B>int-constraint-array</B> (4/6) is an int test option with unit mm
|
||||
Option <B>int-constraint-array</B> (4/6) is an int test option with unit mm
|
||||
and using an array without constraints.
|
||||
|
||||
Option <B>int-constraint-array-constraint-range</B> (5/6) is an int test
|
||||
option with unit mm and using an array with a range constraint. Mini-
|
||||
option with unit mm and using an array with a range constraint. Mini-
|
||||
mum is 4, maximum 192, and quant is 2.
|
||||
|
||||
Option <B>int-constraint-array-constraint-word-list</B> (6/6) is an int test
|
||||
Option <B>int-constraint-array-constraint-word-list</B> (6/6) is an int test
|
||||
option with unit percent and using an array a word list constraint.
|
||||
|
||||
|
||||
|
|
@ -191,14 +194,14 @@
|
|||
<H2>FIXED TEST OPTIONS</H2><PRE>
|
||||
There are 3 fixed test options in total.
|
||||
|
||||
Option <B>fixed</B> (1/3) is a fixed test option with no unit and no con-
|
||||
Option <B>fixed</B> (1/3) is a fixed test option with no unit and no con-
|
||||
straint set.
|
||||
|
||||
Option <B>fixed-constraint-range</B> (2/3) is a fixed test option with unit
|
||||
microsecond and constraint range set. Minimum is -42.17, maximum
|
||||
Option <B>fixed-constraint-range</B> (2/3) is a fixed test option with unit
|
||||
microsecond and constraint range set. Minimum is -42.17, maximum
|
||||
32767.9999, and quant is 2.0.
|
||||
|
||||
Option <B>fixed-constraint-word-list</B> (3/3) is a Fixed test option with no
|
||||
Option <B>fixed-constraint-word-list</B> (3/3) is a Fixed test option with no
|
||||
unit and constraint word list set.
|
||||
|
||||
|
||||
|
|
@ -223,14 +226,14 @@
|
|||
</PRE>
|
||||
<H2>FILES</H2><PRE>
|
||||
<I>/usr/local/etc/sane.d/test.conf</I>
|
||||
The backend configuration file (see also description of
|
||||
<B>SANE_CONFIG_DIR</B> below). The initial values of most of the basic
|
||||
The backend configuration file (see also description of
|
||||
<B>SANE_CONFIG_DIR</B> below). The initial values of most of the basic
|
||||
SANE options can be configured in this file. A template contain-
|
||||
ing all the default values is provided together with this back-
|
||||
end. One of the more interesting values may be <B>num-</B>
|
||||
<B>ber_of_devices</B>. It can be used to check the frontend's ability
|
||||
to show a long list of devices. The config values concerning
|
||||
resolution and geometry can be useful to test the handling of
|
||||
ing all the default values is provided together with this back-
|
||||
end. One of the more interesting values may be <B>num-</B>
|
||||
<B>ber_of_devices</B>. It can be used to check the frontend's ability
|
||||
to show a long list of devices. The config values concerning
|
||||
resolution and geometry can be useful to test the handling of
|
||||
big file sizes.
|
||||
|
||||
<I>/usr/local/lib/sane/libsane-test.a</I>
|
||||
|
|
@ -246,20 +249,20 @@
|
|||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in
|
||||
/usr/local/etc/sane.d. If the value of the environment variable
|
||||
ends with the directory separator character, then the default
|
||||
ends with the directory separator character, then the default
|
||||
directories are searched after the explicitly specified directo-
|
||||
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
|
||||
would result in directories "tmp/config", ".", and
|
||||
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
|
||||
would result in directories "tmp/config", ".", and
|
||||
"/usr/local/etc/sane.d" being searched (in this order).
|
||||
|
||||
<B>SANE_DEBUG_TEST</B>
|
||||
If the library was compiled with debug support enabled, this
|
||||
environment variable controls the debug level for this backend.
|
||||
If the library was compiled with debug support enabled, this
|
||||
environment variable controls the debug level for this backend.
|
||||
Higher debug levels increase the verbosity of the output.
|
||||
|
||||
Example: export SANE_DEBUG_TEST=4
|
||||
|
|
@ -279,7 +282,7 @@
|
|||
<H2>BUGS</H2><PRE>
|
||||
- config file values aren't tested for correctness
|
||||
|
||||
sane-backends 1.0.17 24 Jul 2002 <B><A HREF="sane-test.5.html">sane-test(5)</A></B>
|
||||
sane-backends 1.0.18 2 Jan 2006 <B><A HREF="sane-test.5.html">sane-test(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -128,7 +128,7 @@
|
|||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>,
|
||||
<I>/usr/local/doc/sane-1.0.17/u12/U12.changes</I>
|
||||
<I>/usr/local/doc/sane-1.0.18/u12/U12.changes</I>
|
||||
<I>http://www.gjaeger.de/scanner/u12/</I>
|
||||
|
||||
|
||||
|
|
@ -159,7 +159,7 @@
|
|||
* When using libusb, it might be, that the backend hangs. In that
|
||||
case, reconnect the scanner.
|
||||
|
||||
sane-backends 1.0.17 18 June 2004 <B><A HREF="sane-u12.5.html">sane-u12(5)</A></B>
|
||||
sane-backends 1.0.18 18 June 2004 <B><A HREF="sane-u12.5.html">sane-u12(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -244,7 +244,7 @@
|
|||
<H2>EMAIL-CONTACT</H2><PRE>
|
||||
Oliver.Rauch@Rauch-Domain.DE
|
||||
|
||||
sane-backends 1.0.17 29 november 2002 <B><A HREF="sane-umax.5.html">sane-umax(5)</A></B>
|
||||
sane-backends 1.0.18 29 november 2002 <B><A HREF="sane-umax.5.html">sane-umax(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -12,41 +12,35 @@
|
|||
|
||||
</PRE>
|
||||
<H2>NAME</H2><PRE>
|
||||
sane-umax1220u - SANE backend for the UMAX Astra 1220U scanner
|
||||
sane-umax1220u - SANE backend for the UMAX Astra 1220U and similar
|
||||
scanners
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>DESCRIPTION</H2><PRE>
|
||||
The <B>sane-umax1220</B> library implements a SANE (Scanner Access Now Easy)
|
||||
backend for the the UMAX Astra 1220U scanner.
|
||||
The <B>sane-umax1220</B> library implements a SANE (Scanner Access Now Easy)
|
||||
backend for the the UMAX Astra 1220U and similar scanners.
|
||||
|
||||
For the latest information on this backend, please visit
|
||||
<I>http://umax1220u-sane.sourceforge.net/</I>.
|
||||
For more information on this backend, please visit <I>http://umax1220u-</I>
|
||||
<I>sane.sourceforge.net/</I>.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>UMAX ASTRA 2000U EXPERIMENTAL SUPPORT</H2><PRE>
|
||||
This backend may also be able to drive the UMAX Astra 2000U. Some peo-
|
||||
ple are successful with it, others report that the colors come out ter-
|
||||
rible. Your milage may vary.
|
||||
|
||||
From Stephane (the author of sane-umax_pp), I learned that there are
|
||||
differences in the way the color calibration is performed on the 1220U
|
||||
and the 2000U and it may account for the problem. Stephane's backend
|
||||
support the 2000P, the parallel port sibling to the 2000U. It may be
|
||||
possible to use ideas and code from Stephane's backend to add complete
|
||||
support for the 2000U to this backend. Since I do not have access to an
|
||||
Astra 2000U, I do not plan to work on this - any volunteers?
|
||||
<H2>UMAX ASTRA 1600U/2000U/2100U SUPPORT</H2><PRE>
|
||||
This backend is also able to drive the UMAX Astra 1600U/2000U/2100U.
|
||||
The 2100U is confirmed to work. For the other scanners no reports have
|
||||
been received yet. Please contact us and tell us if your scanner works
|
||||
(sane-devel@lists.alioth.debian.org).
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONFIGURATION</H2><PRE>
|
||||
The configuration file for this backend resides in
|
||||
<I>/usr/local/etc/sane.d/umax1220u.conf</I>.
|
||||
Usually, no manual configuration is necessary. The configuration file
|
||||
for this backend resides in <I>/usr/local/etc/sane.d/umax1220u.conf</I>.
|
||||
|
||||
Its contents is a list of device names that correspond to UMAX Astra
|
||||
1220U scanners. Empty lines and lines starting with a hash mark (#)
|
||||
are ignored. A sample configuration file is shown below:
|
||||
scanners. Empty lines and lines starting with a hash mark (#) are
|
||||
ignored. A sample configuration file is shown below:
|
||||
|
||||
#usb vendor product
|
||||
usb 0x1606 0x0010
|
||||
|
|
@ -54,9 +48,8 @@
|
|||
/dev/scanner
|
||||
/dev/usb/scanner0
|
||||
|
||||
When driving a Astra 2000U, use the product number 0x0030. See sane-
|
||||
<B><A HREF="usb.5.html">usb(5)</A></B> for information on how to set the access permissions on the usb
|
||||
device files.
|
||||
See <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B> for information on how to set the access permissions on
|
||||
the usb device files.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -68,16 +61,16 @@
|
|||
<I>/usr/local/lib/sane/libsane-umax1220u.a</I>
|
||||
|
||||
The shared library implementing this backend:
|
||||
<I>/usr/local/lib/sane/libsane-umax1220u.so</I> (present on systems
|
||||
<I>/usr/local/lib/sane/libsane-umax1220u.so</I> (present on systems
|
||||
that support dynamic loading)
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_DEBUG_UMAX1220U</B>
|
||||
If the library was compiled with debug support enabled, this
|
||||
environment variable controls the debug level for this backend.
|
||||
E.g., a value of 128 requests all debug output to be printed.
|
||||
If the library was compiled with debug support enabled, this
|
||||
environment variable controls the debug level for this backend.
|
||||
E.g., a value of 128 requests all debug output to be printed.
|
||||
Smaller levels reduce verbosity:
|
||||
|
||||
SANE_DEBUG_UMAX1220U values
|
||||
|
|
@ -101,14 +94,14 @@
|
|||
<H2>KNOWN BUGS</H2><PRE>
|
||||
600 dpi scanning may fail for large image sizes.
|
||||
|
||||
If you keep getting I/O errors, try cycling the power on your scanner
|
||||
If you keep getting I/O errors, try cycling the power on your scanner
|
||||
to reset it.
|
||||
|
||||
There is no way to cancel a scan, since the driver ignores sane_can-
|
||||
There is no way to cancel a scan, since the driver ignores sane_can-
|
||||
cel().
|
||||
|
||||
If you try scanning an image which is too small, you will get I/O
|
||||
errors. Be sure to adjust the scan area before doing a scan, since by
|
||||
If you try scanning an image which is too small, you will get I/O
|
||||
errors. Be sure to adjust the scan area before doing a scan, since by
|
||||
default, the scan area is zero.
|
||||
|
||||
|
||||
|
|
@ -116,7 +109,7 @@
|
|||
<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>
|
||||
|
||||
For latest bug fixes and information see
|
||||
(Old) homepage:
|
||||
<I>http://umax1220u-sane.sourceforge.net/</I>
|
||||
|
||||
|
||||
|
|
@ -127,15 +120,17 @@
|
|||
|
||||
</PRE>
|
||||
<H2>EMAIL-CONTACT</H2><PRE>
|
||||
umax1220u-sane-devel@lists.sourceforge.net
|
||||
sane-devel@lists.alioth.debian.org
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>REPORTING BUGS</H2><PRE>
|
||||
When reporting bugs, please run the backend with SANE_DEBUG_UMAX1220U
|
||||
set to 10 and attach a copy of the log messages.
|
||||
This backend isn't actively maintained. Nevertheless, bug reports and
|
||||
comments should be sent to the sane-devel mailing list. When reporting
|
||||
bugs, please run the backend with SANE_DEBUG_UMAX1220U set to 10 and
|
||||
attach a copy of the log messages.
|
||||
|
||||
sane-backends 1.0.17 6 Jan 2002 <B><A HREF="sane-umax1220u.5.html">sane-umax1220u(5)</A></B>
|
||||
sane-backends 1.0.18 17 Apr 2006 <B><A HREF="sane-umax1220u.5.html">sane-umax1220u(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -247,7 +247,7 @@
|
|||
better), or you think I should know something, please include
|
||||
it.
|
||||
|
||||
sane-backends 1.0.17 23 August 2004 <B><A HREF="sane-umax_pp.5.html">sane-umax_pp(5)</A></B>
|
||||
sane-backends 1.0.18 23 August 2004 <B><A HREF="sane-umax_pp.5.html">sane-umax_pp(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -38,7 +38,7 @@
|
|||
how to go on.
|
||||
|
||||
Sane-find-scanner doesn't list your scanner? Does it work as root? If
|
||||
yes, there is a permission issue. See the <B>LIBSUB</B> section for details.
|
||||
yes, there is a permission issue. See the <B>LIBUSB</B> section for details.
|
||||
|
||||
Nothing is found even as root? Check that your kernel supports USB and
|
||||
that libusb is installed (see section <B>LIBUSB</B>).
|
||||
|
|
@ -73,17 +73,19 @@
|
|||
|
||||
The permissions for the device files used by libusb must be adjusted
|
||||
for user access. Otherwise only root can use SANE devices. For <I>Linux</I>,
|
||||
the devices are located in /proc/bus/usb/. There are directories named
|
||||
e.g. "001" (the bus name) containing files "001", "002" etc. (the
|
||||
device files). The right device files can be found out by running scan-
|
||||
image -L as root. Setting permissions with "chmod" is not permanent,
|
||||
however. They will be reset after reboot or replugging the scanner.
|
||||
the devices are located in /proc/bus/usb/ or in /dev/bus/usb, if you
|
||||
use udev. There are directories named e.g. "001" (the bus name) con-
|
||||
taining files "001", "002" etc. (the device files). The right device
|
||||
files can be found out by running scanimage -L as root. Setting permis-
|
||||
sions with "chmod" is not permanent, however. They will be reset after
|
||||
reboot or replugging the scanner.
|
||||
|
||||
Usually the the hotplug utilities (<I>http://linux-hotplug.source-</I>
|
||||
<I>forge.net/</I>) are used, which support dynamic setting of access permis-
|
||||
sions. SANE comes with hotplug scripts in the directory tools/hotplug.
|
||||
They can be used for setting permissions. Precompiled SANE packages
|
||||
may have already installed such hotplug scrips in /etc/hotplug/.
|
||||
Usually udev or for older distributions the hotplug utilities are used,
|
||||
which support dynamic setting of access permissions. SANE comes with
|
||||
udev and hotplug scripts in the directory tools/udev and tools/hotplug.
|
||||
They can be used for setting permissions, see
|
||||
/usr/local/doc/sane-1.0.18/README.linux, tools/README and the README in
|
||||
the tools/hotplug directory for more details.
|
||||
|
||||
For the <B>BSDs</B>, the device files used by libusb are named <I>/dev/ugen*</I>.
|
||||
Use chmod to apply appropriate permissions.
|
||||
|
|
@ -110,7 +112,7 @@
|
|||
hexadecimal format. The correct values for these fields can be found by
|
||||
running sane-find-scanner, looking into the syslog (e.g., /var/log/mes-
|
||||
sages) or under Linux by issuing the command "cat
|
||||
/proc/bus/usb/devices/". This is an example of a config file line:
|
||||
/proc/bus/usb/devices". This is an example of a config file line:
|
||||
|
||||
usb 0x055f 0x0006
|
||||
|
||||
|
|
@ -149,7 +151,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
Henning Meier-Geinitz <henning@meier-geinitz.de>
|
||||
|
||||
sane-backends 1.0.17 16 August 2005 <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>
|
||||
sane-backends 1.0.18 19 Jun 2006 <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -105,7 +105,7 @@
|
|||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="xcam.1.html">xcam(1)</A></B>.
|
||||
|
||||
sane-backends 1.0.17 28 Aug 2002 <B><A HREF="sane-v4l.5.html">sane-v4l(5)</A></B>
|
||||
sane-backends 1.0.18 28 Aug 2002 <B><A HREF="sane-v4l.5.html">sane-v4l(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
167
man/sane.7.html
167
man/sane.7.html
|
|
@ -58,9 +58,9 @@
|
|||
information about several aspects of <B>SANE.</B> A name with a number in
|
||||
parenthesis (e.g. `<B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>') points to a manual page. In this case
|
||||
`<B>man</B> <B>5</B> <B>sane-dll</B>' will display the page. Entries like
|
||||
`<I>/usr/local/doc/sane-1.0.17/sane.tex</I>' are references to text files that
|
||||
`<I>/usr/local/doc/sane-1.0.18/sane.tex</I>' are references to text files that
|
||||
were copied to the <B>SANE</B> documentation directory
|
||||
(<I>/usr/local/doc/sane-1.0.17/</I>) during installation. Everything else is a
|
||||
(<I>/usr/local/doc/sane-1.0.18/</I>) during installation. Everything else is a
|
||||
URL to a resource on the web.
|
||||
|
||||
<B>SANE</B> <B>homepage</B>
|
||||
|
|
@ -75,7 +75,7 @@
|
|||
CAN YOU HELP SANE for details. There are lists for specific releases
|
||||
of SANE, for the current development version and a search engine:
|
||||
<I>http://www.sane-project.org/sane-supported-devices.html</I>. The lists
|
||||
are also installed on your system at /usr/local/doc/sane-1.0.17/.
|
||||
are also installed on your system at /usr/local/doc/sane-1.0.18/.
|
||||
|
||||
<B>SANE</B> <B>mailing</B> <B>list</B>
|
||||
There is a mailing list for the purpose of discussing the SANE stan-
|
||||
|
|
@ -95,7 +95,7 @@
|
|||
server, etc.).
|
||||
|
||||
<B>Compiling</B> <B>and</B> <B>installing</B> <B>SANE</B>
|
||||
Look at <I>/usr/local/doc/sane-1.0.17/README</I> and the os-dependent README
|
||||
Look at <I>/usr/local/doc/sane-1.0.18/README</I> and the os-dependent README
|
||||
files for information about compiling and installing <B>SANE.</B>
|
||||
|
||||
<B>SCSI</B> <B>configuration</B>
|
||||
|
|
@ -189,8 +189,8 @@
|
|||
and USB flatbed scanners. See <B><A HREF="sane-epson.5.html">sane-epson(5)</A></B> for details.
|
||||
|
||||
<B>fujitsu</B>
|
||||
The fujitsu backend provides support for Fujitsu 3091, 3093, 3096 and
|
||||
fi-4340 SCSI scanners. See <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B> for details.
|
||||
The fujitsu backend provides support for most Fujitsu SCSI and USB,
|
||||
flatbed and adf scanners. See <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B> for details.
|
||||
|
||||
<B>genesys</B>
|
||||
The genesys backend provides support for scanners based on the
|
||||
|
|
@ -214,47 +214,51 @@
|
|||
The SANE backend for the Hewlett-Packard ScanJet 5S scanner. See
|
||||
<B><A HREF="sane-hpsj5s.5.html">sane-hpsj5s(5)</A></B> for details.
|
||||
|
||||
<B>hp3500</B>
|
||||
The SANE backend for the Hewlett-Packard ScanJet 3500 series. See
|
||||
<B><A HREF="sane-hp3500.5.html">sane-hp3500(5)</A></B> for details.
|
||||
|
||||
<B>hp4200</B>
|
||||
The SANE backend for the Hewlett-Packard ScanJet 4200 series. See
|
||||
The SANE backend for the Hewlett-Packard ScanJet 4200 series. See
|
||||
<B><A HREF="sane-hp4200.5.html">sane-hp4200(5)</A></B> for details.
|
||||
|
||||
<B>hp5400</B>
|
||||
The SANE backend for the Hewlett-Packard ScanJet 54XXC series. See
|
||||
The SANE backend for the Hewlett-Packard ScanJet 54XXC series. See
|
||||
<B><A HREF="sane-hp5400.5.html">sane-hp5400(5)</A></B> for details.
|
||||
|
||||
<B>ibm</B>
|
||||
The SANE backend for some IBM and Ricoh SCSI scanners. See <B>sane-</B>
|
||||
The SANE backend for some IBM and Ricoh SCSI scanners. See <B>sane-</B>
|
||||
<B><A HREF="ibm.5.html">ibm(5)</A></B> for details.
|
||||
|
||||
<B>leo</B>
|
||||
This backend supports the Leo S3 and the Across FS-1130, which is a
|
||||
This backend supports the Leo S3 and the Across FS-1130, which is a
|
||||
re-badged LEO FS-1130 scanner. See <B><A HREF="sane-leo.5.html">sane-leo(5)</A></B> for details.
|
||||
|
||||
<B>lexmark</B>
|
||||
This backend supports the Lexmark X1100 series of USB scanners. See
|
||||
This backend supports the Lexmark X1100 series of USB scanners. See
|
||||
<B><A HREF="sane-lexmark.5.html">sane-lexmark(5)</A></B> for details.
|
||||
|
||||
<B>ma1509</B>
|
||||
The ma1509 backend supports the Mustek BearPaw 1200F USB flatbed
|
||||
The ma1509 backend supports the Mustek BearPaw 1200F USB flatbed
|
||||
scanner. See <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B> for details.
|
||||
|
||||
<B>matsushita</B>
|
||||
This backend supports some Panasonic KVSS high speed scanners. See
|
||||
This backend supports some Panasonic KVSS high speed scanners. See
|
||||
<B><A HREF="sane-matsushita.5.html">sane-matsushita(5)</A></B> for details.
|
||||
|
||||
<B>microtek</B>
|
||||
The microtek backend provides access to the "second generation"
|
||||
Microtek scanners with SCSI-1 command set. See <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B> for
|
||||
The microtek backend provides access to the "second generation"
|
||||
Microtek scanners with SCSI-1 command set. See <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B> for
|
||||
details.
|
||||
|
||||
<B>microtek2</B>
|
||||
The microtek2 backend provides access to some Microtek scanners with
|
||||
The microtek2 backend provides access to some Microtek scanners with
|
||||
a SCSI-2 command set. See <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B> for details.
|
||||
|
||||
<B>mustek</B>
|
||||
The SANE mustek backend supports most Mustek SCSI flatbed scanners
|
||||
The SANE mustek backend supports most Mustek SCSI flatbed scanners
|
||||
including the Paragon and ScanExpress series and the 600 II N and 600
|
||||
II EP (non-SCSI). Some Trust scanners are also supported. See <B>sane-</B>
|
||||
II EP (non-SCSI). Some Trust scanners are also supported. See <B>sane-</B>
|
||||
<B><A HREF="mustek.5.html">mustek(5)</A></B> for details.
|
||||
|
||||
<B>mustek_pp</B>
|
||||
|
|
@ -266,103 +270,108 @@
|
|||
flatbed scanners. See <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B> for details.
|
||||
|
||||
<B>mustek_usb2</B>
|
||||
The mustek_usb2 backend provides access to scanners using the SQ113
|
||||
chipset like the Mustek BearPaw 2448 TA Pro USB flatbed scanner. See
|
||||
The mustek_usb2 backend provides access to scanners using the SQ113
|
||||
chipset like the Mustek BearPaw 2448 TA Pro USB flatbed scanner. See
|
||||
<B><A HREF="sane-mustek_usb2.5.html">sane-mustek_usb2(5)</A></B> for details.
|
||||
|
||||
<B>nec</B>
|
||||
The SANE nec backend supports the NEC PC-IN500/4C SCSI scanner. See
|
||||
The SANE nec backend supports the NEC PC-IN500/4C SCSI scanner. See
|
||||
<B><A HREF="sane-nec.5.html">sane-nec(5)</A></B> for details.
|
||||
|
||||
<B>niash</B>
|
||||
The niash backend supports the Agfa Snapscan Touch and the HP ScanJet
|
||||
3300c, 3400c, and 4300c USB flatbed scanners. See <B><A HREF="sane-niash.5.html">sane-niash(5)</A></B> for
|
||||
3300c, 3400c, and 4300c USB flatbed scanners. See <B><A HREF="sane-niash.5.html">sane-niash(5)</A></B> for
|
||||
details.
|
||||
|
||||
<B>pie</B>
|
||||
The pie backend provides access to Pacific Image Electronics (PIE)
|
||||
The pie backend provides access to Pacific Image Electronics (PIE)
|
||||
and Devcom SCSI flatbed scanners. See <B><A HREF="sane-pie.5.html">sane-pie(5)</A></B> for details.
|
||||
|
||||
<B>pixma</B>
|
||||
The pixma backend supports Canon PIXMA MP series (multi-function
|
||||
devices). See <B><A HREF="sane-pixma.5.html">sane-pixma(5)</A></B> or <I>http://home.arcor.de/wittawat/pixma/</I>
|
||||
for details.
|
||||
|
||||
<B>plustek</B>
|
||||
The SANE plustek backend supports USB flatbed scanners that use the
|
||||
The SANE plustek backend supports USB flatbed scanners that use the
|
||||
National Semiconductor LM983[1/2/3]-chipset aka Merlin. Scanners
|
||||
using this LM983x chips include some models from Plustek, KYE/Genius,
|
||||
Hewlett-Packard, Mustek, Umax, Epson, and Canon. See <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
|
||||
Hewlett-Packard, Mustek, Umax, Epson, and Canon. See <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
|
||||
for details.
|
||||
|
||||
<B>plustek_pp</B>
|
||||
The SANE plustek_pp backend supports Plustek parallel port flatbed
|
||||
The SANE plustek_pp backend supports Plustek parallel port flatbed
|
||||
scanners. Scanners using the Plustek ASIC P96001, P96003, P98001 and
|
||||
P98003 include some models from Plustek, KYE/Genius, Primax. See
|
||||
P98003 include some models from Plustek, KYE/Genius, Primax. See
|
||||
<B><A HREF="sane-plustek_pp.5.html">sane-plustek_pp(5)</A></B> for details.
|
||||
|
||||
<B>ricoh</B>
|
||||
The ricoh backend provides access to the following Ricoh flatbed
|
||||
The ricoh backend provides access to the following Ricoh flatbed
|
||||
scanners: IS50 and IS60. See <B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B> for details.
|
||||
|
||||
<B>s9036</B>
|
||||
The s9036 backend provides access to Siemens 9036 flatbed scanners.
|
||||
The s9036 backend provides access to Siemens 9036 flatbed scanners.
|
||||
See <B><A HREF="sane-s9036.5.html">sane-s9036(5)</A></B> for details.
|
||||
|
||||
<B>sceptre</B>
|
||||
The sceptre backend provides access to the Sceptre S1200 flatbed
|
||||
The sceptre backend provides access to the Sceptre S1200 flatbed
|
||||
scanner. See <B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B> for details.
|
||||
|
||||
<B>sharp</B>
|
||||
The SANE sharp backend supports Sharp SCSI scanners. See <B>sane-</B>
|
||||
The SANE sharp backend supports Sharp SCSI scanners. See <B>sane-</B>
|
||||
<B><A HREF="sharp.5.html">sharp(5)</A></B> for details.
|
||||
|
||||
<B>sm3600</B>
|
||||
The SANE sm3600 backend supports the Microtek ScanMaker 3600 USB
|
||||
The SANE sm3600 backend supports the Microtek ScanMaker 3600 USB
|
||||
scanner. See <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B> for details.
|
||||
|
||||
<B>sm3840</B>
|
||||
The SANE sm3840 backend suppoert the Microtek ScanMaker 3840 USB
|
||||
The SANE sm3840 backend supports the Microtek ScanMaker 3840 USB
|
||||
scanner. See <B><A HREF="sane-sm3840.5.html">sane-sm3840(5)</A></B> for details.
|
||||
|
||||
<B>snapscan</B>
|
||||
The snapscan backend supports AGFA SnapScan flatbed scanners. See
|
||||
The snapscan backend supports AGFA SnapScan flatbed scanners. See
|
||||
<B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B> for details.
|
||||
|
||||
<B>sp15c</B>
|
||||
This backend supports the Fujitsu FCPA ScanPartner 15C flatbed scan-
|
||||
This backend supports the Fujitsu FCPA ScanPartner 15C flatbed scan-
|
||||
ner. See <B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B> for details.
|
||||
|
||||
<B>st400</B>
|
||||
The sane-st400 backend provides access to Siemens ST400 and ST800.
|
||||
The sane-st400 backend provides access to Siemens ST400 and ST800.
|
||||
See <B><A HREF="sane-st400.5.html">sane-st400(5)</A></B> for details.
|
||||
|
||||
<B>tamarack</B>
|
||||
The SANE tamarack backend supports Tamarack Artiscan flatbed scan-
|
||||
The SANE tamarack backend supports Tamarack Artiscan flatbed scan-
|
||||
ners. See <B><A HREF="sane-tamarack.5.html">sane-tamarack(5)</A></B> for details.
|
||||
|
||||
<B>teco1</B> <B>teco2</B> <B>teco3</B>
|
||||
The SANE teco1, teco2 and teco3 backends support some TECO scanners,
|
||||
The SANE teco1, teco2 and teco3 backends support some TECO scanners,
|
||||
usually sold under the Relisys, Trust, Primax, Piotech, Dextra names.
|
||||
See <B><A HREF="sane-teco1.5.html">sane-teco1(5)</A></B>, <B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B> and <B><A HREF="sane-teco3.5.html">sane-teco3(5)</A></B> for details.
|
||||
|
||||
<B>u12</B>
|
||||
The sane-u12 backend provides USB flatbed scanners based on Plustek's
|
||||
ASIC 98003 (parallel-port ASIC) and a GeneSys Logics' USB-parport
|
||||
bridge chip like the Plustek OpticPro U(T)12. See <B><A HREF="sane-u12.5.html">sane-u12(5)</A></B> for
|
||||
ASIC 98003 (parallel-port ASIC) and a GeneSys Logics' USB-parport
|
||||
bridge chip like the Plustek OpticPro U(T)12. See <B><A HREF="sane-u12.5.html">sane-u12(5)</A></B> for
|
||||
details.
|
||||
|
||||
<B>umax</B>
|
||||
The sane-umax backend provides access to several UMAX-SCSI-scanners
|
||||
The sane-umax backend provides access to several UMAX-SCSI-scanners
|
||||
and some Linotype Hell SCSI-scanners. See <B><A HREF="sane-umax.5.html">sane-umax(5)</A></B> for details.
|
||||
|
||||
<B>umax_pp</B>
|
||||
The sane-umax_pp backend provides access to Umax parallel port
|
||||
The sane-umax_pp backend provides access to Umax parallel port
|
||||
flatbed scanners and the HP 3200C. See <B><A HREF="sane-umax_pp.5.html">sane-umax_pp(5)</A></B> for details.
|
||||
|
||||
<B>umax1200u</B>
|
||||
The sane-umax1220u backend supports the UMAX Astra 1220U (USB)
|
||||
flatbed scanner (and also the UMAX Astra 2000U, sort of). See <B>sane-</B>
|
||||
The sane-umax1220u backend supports the UMAX Astra 1220U (USB)
|
||||
flatbed scanner (and also the UMAX Astra 2000U, sort of). See <B>sane-</B>
|
||||
<B><A HREF="umax1220u.5.html">umax1220u(5)</A></B> for details.
|
||||
|
||||
Also, have a look at the backend information page at <I>http://www.sane-</I>
|
||||
<I>project.org/sane-supported-devices.html</I> and the list of projects in
|
||||
<I>/usr/local/doc/sane-1.0.17/PROJECTS</I>.
|
||||
Also, have a look at the backend information page at <I>http://www.sane-</I>
|
||||
<I>project.org/sane-supported-devices.html</I> and the list of projects in
|
||||
<I>/usr/local/doc/sane-1.0.18/PROJECTS</I>.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -377,22 +386,26 @@
|
|||
Backend for Kodak DC20/DC25 Digital Cameras. See <B><A HREF="sane-dc25.5.html">sane-dc25(5)</A></B>.
|
||||
|
||||
<B>dmc</B>
|
||||
Backend for the Polaroid Digital Microscope Camera. See <B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B>.
|
||||
Backend for the Polaroid Digital Microscope Camera. See <B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B>.
|
||||
|
||||
<B>gphoto2</B>
|
||||
Backend for digital cameras supported by the gphoto2 library package.
|
||||
(See <I>http://www.gphoto.org</I> for more information and a list of sup-
|
||||
ported cameras.) Gphoto2 supports over 140 different camera models.
|
||||
However, please note that more development and testing is needed
|
||||
before all of these cameras will be supported by <B>SANE</B> backend. See
|
||||
(See <I>http://www.gphoto.org</I> for more information and a list of sup-
|
||||
ported cameras.) Gphoto2 supports over 140 different camera models.
|
||||
However, please note that more development and testing is needed
|
||||
before all of these cameras will be supported by <B>SANE</B> backend. See
|
||||
<B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>.
|
||||
|
||||
<B>qcam</B>
|
||||
Backend for Connectix QuickCam cameras. See <B><A HREF="sane-qcam.5.html">sane-qcam(5)</A></B>.
|
||||
|
||||
<B>stv680</B>
|
||||
The sane-st680 backend provides access to webcams with a stv680 chip.
|
||||
See <B><A HREF="sane-st680.5.html">sane-st680(5)</A></B> for details.
|
||||
|
||||
Also, have a look at the backend information page at <I>http://www.sane-</I>
|
||||
<I>project.org/sane-supported-devices.html</I> and the list of projects in
|
||||
<I>/usr/local/doc/sane-1.0.17/PROJECTS</I>.
|
||||
<I>/usr/local/doc/sane-1.0.18/PROJECTS</I>.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -414,8 +427,8 @@
|
|||
<B>pint</B>
|
||||
Backend for scanners that use the <B>PINT</B> (Pint Is Not Twain) device
|
||||
driver. The <B>PINT</B> driver is being actively developed on the OpenBSD
|
||||
platform, and has been ported to a few other *nix-like operating
|
||||
systems. See <B><A HREF="sane-pint.5.html">sane-pint(5)</A></B>.
|
||||
platform, and has been ported to a few other *nix-like operating sys-
|
||||
tems. See <B><A HREF="sane-pint.5.html">sane-pint(5)</A></B>.
|
||||
|
||||
<B>test</B>
|
||||
The <B>SANE</B> test backend is for testing frontends and the <B>SANE</B> installa-
|
||||
|
|
@ -429,7 +442,7 @@
|
|||
|
||||
Also, have a look at the backend information page at <I>http://www.sane-</I>
|
||||
<I>project.org/sane-supported-devices.html</I> and the list of projects in
|
||||
<I>/usr/local/doc/sane-1.0.17/PROJECTS</I>.
|
||||
<I>/usr/local/doc/sane-1.0.18/PROJECTS</I>.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -450,15 +463,15 @@
|
|||
|
||||
The <B>SANE</B> standard defines the application programming interface (API)
|
||||
that is used to communicate between frontends and backends. It can be
|
||||
found at <I>/usr/local/doc/sane-1.0.17/sane.ps</I> (if latex is installed on
|
||||
found at <I>/usr/local/doc/sane-1.0.18/sane.ps</I> (if latex is installed on
|
||||
your system) and on the <B>SANE</B> website: <I>http://www.sane-project.org/html/</I>
|
||||
(HTML), or <I>http://www.sane-project.org/sane.ps</I> (Postscript).
|
||||
|
||||
There is some more information for programmers in
|
||||
<I>/usr/local/doc/sane-1.0.17/backend-writing.txt</I>. Most of the internal
|
||||
<I>/usr/local/doc/sane-1.0.18/backend-writing.txt</I>. Most of the internal
|
||||
<B>SANE</B> routines (<B>sanei</B>) are documented using doxygen: <I>http://www.sane-</I>
|
||||
<I>project.org/sanei/</I>. Before a new backend or frontend project is
|
||||
started, have a look at <I>/usr/local/doc/sane-1.0.17/PROJECTS</I> for
|
||||
started, have a look at <I>/usr/local/doc/sane-1.0.18/PROJECTS</I> for
|
||||
projects that are planned or not yet included into the <B>SANE</B> distribu-
|
||||
tion and at our bug-tracking system: <I>http://www.http://www.sane-</I>
|
||||
<I>project.org/bugs.html</I>.
|
||||
|
|
@ -483,7 +496,7 @@
|
|||
The shared libraries implementing the backends (present on sys-
|
||||
tems that support dynamic loading).
|
||||
|
||||
<I>/usr/local/doc/sane-1.0.17/*</I>
|
||||
<I>/usr/local/doc/sane-1.0.18/*</I>
|
||||
<B>SANE</B> documentation: The standard, READMEs, text files for back-
|
||||
ends etc.
|
||||
|
||||
|
|
@ -573,7 +586,7 @@
|
|||
For reporting bugs or requesting new features, please use our bug-
|
||||
tracking system: <I>http://www.sane-project.org/bugs.html</I>. You can also
|
||||
contact the author of your backend directly. Usually the email address
|
||||
can be found in the <I>/usr/local/doc/sane-1.0.17/AUTHORS</I> file or the
|
||||
can be found in the <I>/usr/local/doc/sane-1.0.18/AUTHORS</I> file or the
|
||||
backend's manpage. For general discussion about SANE, please use the
|
||||
<B>SANE</B> mailing list sane-devel (see <I>http://www.sane-project.org/mailing-</I>
|
||||
<I>lists.html</I> for details).
|
||||
|
|
@ -587,28 +600,28 @@
|
|||
<B><A HREF="canon630u.5.html">canon630u(5)</A></B>, <B><A HREF="sane-canon_pp.5.html">sane-canon_pp(5)</A></B>, <B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B>, <B><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B>,
|
||||
<B><A HREF="sane-dc210.5.html">sane-dc210(5)</A></B>, <B><A HREF="sane-dc240.5.html">sane-dc240(5)</A></B>, <B><A HREF="sane-dc25.5.html">sane-dc25(5)</A></B>, <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>, <B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B>,
|
||||
<B><A HREF="sane-epson.5.html">sane-epson(5)</A></B>, <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>, <B><A HREF="sane-genesys.5.html">sane-genesys(5)</A></B>, <B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>, <B>sane-</B>
|
||||
<B><A HREF="gt68xx.5.html">gt68xx(5)</A></B>, <B><A HREF="sane-hp.5.html">sane-hp(5)</A></B>, <B><A HREF="sane-hpsj5s.5.html">sane-hpsj5s(5)</A></B>, <B><A HREF="sane-hp4200.5.html">sane-hp4200(5)</A></B>, <B><A HREF="sane-hp5400.5.html">sane-hp5400(5)</A></B>,
|
||||
<B><A HREF="sane-ibm.5.html">sane-ibm(5)</A></B>, <B><A HREF="sane-leo.5.html">sane-leo(5)</A></B>, <B><A HREF="sane-lexmark.5.html">sane-lexmark(5)</A></B>, <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>, <B>sane-mat-</B>
|
||||
<B><A HREF="sushita.5.html">sushita(5)</A></B>, <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B>, <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B>sane-</B>
|
||||
<B><A HREF="mustek_pp.5.html">mustek_pp(5)</A></B>, <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B><A HREF="sane-mustek_usb2.5.html">sane-mustek_usb2(5)</A></B>, <B><A HREF="sane-nec.5.html">sane-nec(5)</A></B>,
|
||||
<B><A HREF="sane-net.5.html">sane-net(5)</A></B>, <B><A HREF="sane-niash.5.html">sane-niash(5)</A></B>, <B><A HREF="sane-pie.5.html">sane-pie(5)</A></B>, <B><A HREF="sane-pint.5.html">sane-pint(5)</A></B>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>,
|
||||
<B><A HREF="sane-plustek_pp.5.html">sane-plustek_pp(5)</A></B>, <B><A HREF="sane-pnm.5.html">sane-pnm(5)</A></B>, <B><A HREF="sane-qcam.5.html">sane-qcam(5)</A></B>, <B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B>, <B>sane-</B>
|
||||
<B><A HREF="s9036.5.html">s9036(5)</A></B>, <B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B>, <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B>,
|
||||
<B><A HREF="sane-sm3840.5.html">sane-sm3840(5)</A></B>, <B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B>, <B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B>, <B><A HREF="sane-st400.5.html">sane-st400(5)</A></B>, <B>sane-</B>
|
||||
<B><A HREF="tamarack.5.html">tamarack(5)</A></B>, <B><A HREF="sane-teco1.5.html">sane-teco1(5)</A></B>, <B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B>, <B><A HREF="sane-teco3.5.html">sane-teco3(5)</A></B>, <B><A HREF="sane-test.5.html">sane-test(5)</A></B>,
|
||||
<B><A HREF="sane-u12.5.html">sane-u12(5)</A></B>, <B><A HREF="sane-umax1220u.5.html">sane-umax1220u(5)</A></B>, <B><A HREF="sane-umax.5.html">sane-umax(5)</A></B>, <B><A HREF="sane-umax_pp.5.html">sane-umax_pp(5)</A></B>, <B>sane-</B>
|
||||
<B><A HREF="usb.5.html">usb(5)</A></B>, <B><A HREF="sane-v4l.5.html">sane-v4l(5)</A></B>
|
||||
<B><A HREF="gt68xx.5.html">gt68xx(5)</A></B>, <B><A HREF="sane-hp.5.html">sane-hp(5)</A></B>, <B><A HREF="sane-hpsj5s.5.html">sane-hpsj5s(5)</A></B>, <B><A HREF="sane-hp3500.5.html">sane-hp3500(5)</A></B>, <B><A HREF="sane-hp4200.5.html">sane-hp4200(5)</A></B>,
|
||||
<B><A HREF="sane-hp5400.5.html">sane-hp5400(5)</A></B>, <B><A HREF="sane-ibm.5.html">sane-ibm(5)</A></B>, <B><A HREF="sane-leo.5.html">sane-leo(5)</A></B>, <B><A HREF="sane-lexmark.5.html">sane-lexmark(5)</A></B>, <B>sane-</B>
|
||||
<B><A HREF="ma1509.5.html">ma1509(5)</A></B>, <B><A HREF="sane-matsushita.5.html">sane-matsushita(5)</A></B>, <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B>, <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B>,
|
||||
<B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>, <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B>sane-</B>
|
||||
<B><A HREF="mustek_usb2.5.html">mustek_usb2(5)</A></B>, <B><A HREF="sane-nec.5.html">sane-nec(5)</A></B>, <B><A HREF="sane-net.5.html">sane-net(5)</A></B>, <B><A HREF="sane-niash.5.html">sane-niash(5)</A></B>, <B><A HREF="sane-pie.5.html">sane-pie(5)</A></B>,
|
||||
<B><A HREF="sane-pint.5.html">sane-pint(5)</A></B>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>, <B><A HREF="sane-plustek_pp.5.html">sane-plustek_pp(5)</A></B>, <B><A HREF="sane-pnm.5.html">sane-pnm(5)</A></B>, <B>sane-</B>
|
||||
<B><A HREF="qcam.5.html">qcam(5)</A></B>, <B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B>, <B><A HREF="sane-s9036.5.html">sane-s9036(5)</A></B>, <B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>,
|
||||
<B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B>, <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B>, <B><A HREF="sane-sm3840.5.html">sane-sm3840(5)</A></B>, <B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B>, <B>sane-</B>
|
||||
<B><A HREF="sp15c.5.html">sp15c(5)</A></B>, <B><A HREF="sane-st400.5.html">sane-st400(5)</A></B>, <B><A HREF="sane-stv680.5.html">sane-stv680(5)</A></B>, <B><A HREF="sane-tamarack.5.html">sane-tamarack(5)</A></B>, <B>sane-</B>
|
||||
<B><A HREF="teco1.5.html">teco1(5)</A></B>, <B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B>, <B><A HREF="sane-teco3.5.html">sane-teco3(5)</A></B>, <B><A HREF="sane-test.5.html">sane-test(5)</A></B>, <B><A HREF="sane-u12.5.html">sane-u12(5)</A></B>,
|
||||
<B><A HREF="sane-umax1220u.5.html">sane-umax1220u(5)</A></B>, <B><A HREF="sane-umax.5.html">sane-umax(5)</A></B>, <B><A HREF="sane-umax_pp.5.html">sane-umax_pp(5)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B>sane-</B>
|
||||
<B><A HREF="v4l.5.html">v4l(5)</A></B>
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>AUTHOR</H2><PRE>
|
||||
David Mosberger-Tang and many many more (see
|
||||
<I>/usr/local/doc/sane-1.0.17/AUTHORS</I> for details). This man page was
|
||||
written by Henning Meier-Geinitz. Quite a lot of text was taken from
|
||||
David Mosberger-Tang and many many more (see
|
||||
<I>/usr/local/doc/sane-1.0.18/AUTHORS</I> for details). This man page was
|
||||
written by Henning Meier-Geinitz. Quite a lot of text was taken from
|
||||
the <B>SANE</B> standard, several man pages, and README files.
|
||||
|
||||
|
||||
sane-backends 1.0.17 16 October 2005 <B><A HREF="sane.7.html">sane(7)</A></B>
|
||||
sane-backends 1.0.18 16 October 2005 <B><A HREF="sane.7.html">sane(7)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -179,7 +179,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
David Mosberger
|
||||
|
||||
sane-backends 1.0.17 30 May 2004 <B><A HREF="saned.8.html">saned(8)</A></B>
|
||||
sane-backends 1.0.18 30 May 2004 <B><A HREF="saned.8.html">saned(8)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -283,7 +283,7 @@
|
|||
For vector options, the help output currently has no indication as to
|
||||
how many elements a vector-value should have.
|
||||
|
||||
sane-backends 1.0.17 23 Sep 2005 <B><A HREF="scanimage.1.html">scanimage(1)</A></B>
|
||||
sane-backends 1.0.18 23 Sep 2005 <B><A HREF="scanimage.1.html">scanimage(1)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
Plik diff jest za duży
Load Diff
4934
sane-backends.html
4934
sane-backends.html
Plik diff jest za duży
Load Diff
6583
sane-mfgs.html
6583
sane-mfgs.html
Plik diff jest za duży
Load Diff
Ładowanie…
Reference in New Issue