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

Added HTML versions of the SANE manual pages from CVS.

merge-requests/1/head
Henning Geinitz 2003-09-23 15:30:05 +00:00
rodzic eeb2e3b991
commit dde3b8e0a3
70 zmienionych plików z 13413 dodań i 0 usunięć
Pokaż statystyki Ściągnij plik aktualizacji Ściągnij plik porównania Expand all files Collapse all files

82
man/gamma4scanimage.1.html 100644
Wyświetl plik

@ -0,0 +1,82 @@
<HTML>
<HEAD>
<TITLE>gamma4scanimage.1</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>gamma4scanimage.1</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="gamma4scanimage.1.html">gamma4scanimage(1)</A></B> SANE Scanner Access Now Easy <B><A HREF="gamma4scanimage.1.html">gamma4scanimage(1)</A></B>
</PRE>
<H2>NAME</H2><PRE>
gamma4scanimage - create a gamma table for scanimage
</PRE>
<H2>SYNOPSIS</H2><PRE>
<B>gamma4scanimage</B> <I>gamma</I> [<I>shadow</I> [<I>highlight</I> [<I>maxin</I> [<I>maxout</I>]]]]
</PRE>
<H2>DESCRIPTION</H2><PRE>
The tool <B>gamma4scanimage</B> creates a gamma table in the format expected
by scanimage. You can define a <B>gamma,</B> a <B>shadow</B> and a <B>highlight</B> value.
You also can specify the size (<B>maxin</B>) and maximum output value (<B>maxout</B>)
of the gamma table.
<B>gamma</B> is a floating point value, neutral value is 1.0, if the value is
larger than 1.0 then the image gets brighter.
<B>shadow</B> defines the minmum input value that is necessary to create an
output value larger than zero. shadow has to be in the range
[0..maxin]. Its default value is 0.
<B>highlight</B> defines the maximum input value that produces an output value
smaller than maxout. highlight has to be in the range [0..maxin],
highlight has to be larger than shadow. Its default value is the same
as maxin (16383 if not set).
<B>maxin</B> defines the size of the gamma table. The size depends on the
scanner/backend. If the scanner uses 8 bits gamma input then maxin has
to be set to 255, for 10 bits 1023, for 12 bits 4095, for 14 bits
16383. The default is 16383. To find out what value maxin has to be
call scanimage with a very large gamma table [0]0-[99999]255 then scan-
image prints an error message with the needed size of the gamma table.
<B>maxout</B> defines the maximum output value. Take a look at the output of
scanimage -h to find out what maxout has to be. The default value is
255.
</PRE>
<H2>EXAMPLE</H2><PRE>
<B>scanimage</B> <B>--custom-gamma=yes</B> <B>--gamma-table</B> <I>`gamma4scanimage</I> <I>1.8</I> <I>0</I> <I>11500</I>
<I>16383</I> <I>255`</I> &gt;image.pnm
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="scanimage.7.html">scanimage(7)</A></B>
</PRE>
<H2>AUTHOR</H2><PRE>
Oliver Rauch
</PRE>
<H2>EMAIL-CONTACT</H2><PRE>
Oliver.Rauch@Rauch-Domain.DE
sane-backends 1.0.12-cvs 11 Sep 2002 <B><A HREF="gamma4scanimage.1.html">gamma4scanimage(1)</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>

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

@ -0,0 +1,153 @@
<HTML>
<HEAD>
<TITLE>sane-abaton.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-abaton.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-abaton.5.html">sane-abaton(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-abaton.5.html">sane-abaton(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-abaton - SANE backend for Abaton flatbed scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-abaton</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to Abaton flatbed scanners. At present,
only the Scan 300/GS (8bit, 256 levels of gray) is fully supported, due
to the absence of programming information. The Scan 300/S (black and
white) is recognized, but support for it is untested.
If you own a Abaton scanner other than the ones listed above that works
with this backend, or if you own an Abaton scanner that does not work
with this backend, please contact <I>sane-devel@mostang.com</I> with the model
number, so that arrangements can be made to include support for it.
Have a look at http://www.mostang.com/sane/mail.html concerning sub-
scription to sane-devel.
Abaton is out of business, and these scanners are not supported by
Everex (the parent company of Abaton), nor is there any programming
information to be found. This driver is therefore based on information
obtained by running Abaton's scanning desk accessory under MacsBug and
tracing the MacOS SCSI Manager calls it made during image acquisition.
However, the protocol is very similar to, though not compatible with,
the one used by the Apple scanners, therefore, if this backend is ever
extended to support the other Abaton models (they also made a color
flatbed scanner), it may be possible to fill in some "missing pieces"
from the (quite detailed) Apple scanner documentation.
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form:
<I>special</I>
Where <I>special</I> is the path-name for the special device that corresponds
to a SCSI scanner. For SCSI scanners, the special device name must be a
generic SCSI device or a symlink to such a device. Under Linux, such a
device name takes a format such as <I>/dev/sga</I> or <I>/dev/sg0</I>, for example.
See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>abaton.conf</I> file is a list of device names that
correspond to Abaton 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 consti-
tutes a valid device name.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/abaton.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-abaton.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-abaton.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_ABATON</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.
</PRE>
<H2>BUGS</H2><PRE>
There are a few known ones, and definitely some unknown ones.
<B>Scan</B> <B>area</B> <B>miscalculations</B>
For the sake of programmer efficiency, this backend handles all
measurements in millimetres, and floors (rather than rounds)
values to avoid possible damage to the scanner mechanism.
Therefore, it may not be possible to scan to the extreme right
or bottom edges of the page.
<B>Cancelling</B> <B>the</B> <B>scan</B>
This might not work correctly, or it might abort the frontend.
The former is more likely than the latter.
If you have found something that you think is a bug, please attempt to
recreate it with the SANE_DEBUG_ABATON environment variable set to 255,
and send a report detailing the conditions surrounding the bug to
<I>sane-devel@mostang.com</I>.
</PRE>
<H2>TODO</H2><PRE>
<B>Implement</B> <B>non-blocking</B> <B>support</B>
<B>Finish</B> <B>reverse-engineering</B> <B>the</B> <B>MacOS</B> <B>driver</B>
This will allow me to add support for other models with reason-
able confidence that it will work, as well as to fully exploit
the information returned by the INQUIRY command.
</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="scanimage.1.html">scanimage(1)</A></B>
</PRE>
<H2>AUTHOR</H2><PRE>
The sane-abaton backend was partially written by David Huggins-Daines,
based on the sane-apple backend by Milon Firikis.
sane-backends 1.0.12-cvs 19 Nov 1998 <B><A HREF="sane-abaton.5.html">sane-abaton(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>

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

@ -0,0 +1,189 @@
<HTML>
<HEAD>
<TITLE>sane-agfafocus.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-agfafocus.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-agfafocus.5.html">sane-agfafocus(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-agfafocus.5.html">sane-agfafocus(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-agfafocus - SANE backend for AGFA Focus flatbed scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-agfafocus</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to AGFA Focus flatbed scanners. At
present, the following scanners are supported from this backend:
AGFA Focus GS Scanner (6 bit gray scale) (untested)
AGFA Focus Lineart Scanner (lineart) (untested)
AGFA Focus II (8 bit gray scale) (untested)
AGFA Focus Color (24 bit color 3-pass)
AGFA Focus Color Plus (24 bit color 3-pass)
Siemens S9036 (8 bit gray scale) (untested)
The driver supports line art, 6bpp and 8bpp gray, 18bpp and 24bpp color
scans.
If you own a scanner other than the ones listed above that works with
this backend, please let us know by sending the scanner's model name,
SCSI id, and firmware revision to <I>sane-devel@mostang.com</I>. Have a look
at http://www.mostang.com/sane/mail.html concerning subscription to
sane-devel.
All of these scanners are pre-SCSI-2, and do not even report properly
to SCSI Inquiry. This is typically evident in SCSI bus scans, where
the scanner will come up with only garbage as vendor and models
strings.
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form:
<I>special</I>
Where <I>special</I> is either the path-name for the special device that cor-
responds to a SCSI scanner. For SCSI scanners, the special device name
must be a generic SCSI device or a symlink to such a device. Under
Linux, such a device name could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example.
See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>agfafocus.conf</I> file is a list of device names that
correspond to AGFA Focus scanners. Empty lines and lines starting with
a hash mark (#) are ignored. A sample configuration file is shown
below:
/dev/scanner
# this is a comment
/dev/sge
</PRE>
<H2>FILES</H2><PRE>
<I>/etc/sane.d/agfafocus.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/lib/libsane-agfafocus.a</I>
The static library implementing this backend.
<I>/usr/lib/libsane-agfafocus.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in /etc/sane.d. If the
value of the environment variable ends with the directory sepa-
rator character, then the default directories are searched after
the explicitly specified directories. For example, setting
<B>SANE_CONFIG_DIR</B> to "/tmp/config:" would result in directories
"tmp/config", ".", and "/etc/sane.d" being searched (in this
order).
<B>SANE_DEBUG_AGFAFOCUS</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
E.g., a value of 128 requests all debug output to be printed.
Smaller levels reduce verbosity. SANE_DEBUG_AGFAFOCUS values:
Number Remark
0 print important errors (printed each time)
1 print errors
2 print sense
3 print warnings
4 print scanner-inquiry
5 print informations
6 print less important informations
7 print called procedures
8 print reader_process messages
10 print called sane-init-routines
11 print called sane-procedures
12 print sane infos
13 print sane option-control messages
</PRE>
<H2>MISSING FUNCTIONALITY</H2><PRE>
Uploading of dither matrices and tonecurves has been implemented, but
so far has not proven to be useful for anything. For this reason these
options have been disabled.
</PRE>
<H2>BUGS</H2><PRE>
The scanners that do not support disconnect have problems with SCSI
timeouts if the SCSI bus gets loaded, eg. if you do a kernel build at
the same time as scanning. To see if your scanner supports disconnect,
run "SANE_DEBUG_AGFAFOCUS=128 scanimage -L" in sh and look for the
"disconnect:" line)
</PRE>
<H2>DEBUG</H2><PRE>
If you have problems with SANE not detecting your scanner, make sure
the Artec backend is disabled. Somehow, this backend causes at least
my scanner not to respond correctly to SCSI inquiry commands.
If you encounter a bug please set the environment variable
SANE_DEBUG_AGFAFOCUS to 128 and try to regenerate the problem. Then
send me a report with the log attached.
If you encounter a SCSI bus error or trimmed and/or displaced images
please also set the environment variable SANE_DEBUG_SANEI_SCSI to 128
before sending me the report.
</PRE>
<H2>TODO</H2><PRE>
<B>More</B> <B>scanners?</B>
The AGFA ACS and ARCUS scanners are similar to the FOCUS scan-
ners. The driver could probably be extended to support these
scanners without too many changes. I do not have access to such
scanners, and cannot add support for it. However, if you are in
possession of such a scanner, I could be helpful in adding sup-
port for these scanners.
The AGFA HORIZON scanners are SCSI-2 scanners, and it would
probably be easier to support these scanners in a SCSI-2 compli-
ant backend.
</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>
</PRE>
<H2>AUTHOR</H2><PRE>
Ingo Schneider and Karl Anders ?ygard.
sane-backends 1.0.12-cvs 17 Oct 1998 <B><A HREF="sane-agfafocus.5.html">sane-agfafocus(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>

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

@ -0,0 +1,293 @@
<HTML>
<HEAD>
<TITLE>sane-apple.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-apple.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-apple.5.html">sane-apple(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-apple.5.html">sane-apple(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-apple - SANE backend for Apple flatbed scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-apple</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to Apple flatbed scanners. At present, the
following scanners are supported from this backend:
--------------- ----- ------------------ ------
AppleScanner 4bit 16 Shades of Gray
OneScanner 8bit 256 Shades of Gray
ColorOneScanner 24bit RGB color 3-pass
If you own a Apple scanner other than the ones listed above that works
with this backend, please let us know by sending the scanner's model
name, SCSI id, and firmware revision to <I>sane-devel@mostang.com</I>. See
http://www.mostang.com/sane/mail.html for details on how to subscribe
to sane-devel.
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form:
<I>special</I>
Where <I>special</I> is either the path-name for the special device that cor-
responds to a SCSI scanner. For SCSI scanners, the special device name
must be a generic SCSI device or a symlink to such a device. Under
Linux, such a device name could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example.
See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details.
</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.
Options come in two flavors: global and positional ones. Global
options apply to all devices managed by the backend whereas positional
options apply just to the most recently mentioned device. Note that
this means that the order in which the options appear matters!
</PRE>
<H2>SCSI ADAPTER TIPS</H2><PRE>
SCSI scanners are typically delivered with an ISA SCSI adapter. Unfor-
tunately, that adapter is not worth much since it is not interrupt
driven. It is (sometimes) possible to get the supplied card to work,
but without interrupt line, scanning will put so much load on the sys-
tem, that it becomes almost unusable for other tasks.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/apple.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-apple.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-apple.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_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.
</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-
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
personal belief is that with a slight touch of debugging the OneScanner
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.
<B>AppleScanner</B>
Cannot up/download a halftone pattern.
<B>OneScanner</B>
Cannot up/download halftone pattern and calibration vector.
<B>ColorOneScanner</B>
Cannot up/download halftone pattern, calibration vectors, custom
Color Correction Table (CCT) and of course custom gamma tables.
<B>Park/UnPark</B> <B>(OneScanner,</B> <B>ColorOneScanner)</B>
The above functionalities are not only missing because I don't actually
have the hardware to experiment on it. Another reason is the lack of
understanding of how SANE API could provide enaugh means to me to actu-
ally describe other array types than the gamma one.
</PRE>
<H2>UNSUPPORTED FEATURES.</H2><PRE>
The following "features" will never be supported. At least as I am
maintaining the sane-apple backend.
<B>NoHome</B> <B>(AppleScanner)</B>
The scanner lamp stays on and the carriage assembly remains
where it stops at the end of the scan. After two minutes, if the
scanner does not receive another SCAN command the lamp goes off
and the carriage returns to the home position.
<B>Compression</B> <B>(AppleScanner)</B>
The Scanner can compress data with CCITT Group III, one dimen-
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
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
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.
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
<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
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...
Other source of bugs are due to scsi communcation, scsi connects and
disconnects. However the classical bugs are still there. So you may
encouter buffer overruns, null pointers, memory corruption and <B>SANE</B> API
violations.
<B>SIGSEGV</B> <B>on</B> <B>SliceBars</B>
When you try to modify the scan area from the slice bar you have
a nice little cute core dump. I don't know why. If you select
the scan are from the preview window, or by hand typing the num-
bers everything is fine. The SIGSEGV happens deep in gtk library
(gdk). I really cannot debug it.
<B>Options</B> <B>too</B> <B>much</B>
It is possible, especially for the ColorOneScanner, that the
backend's options panel to exceed from your screen. It happens
with mine and I am running at 1024x768 my X Server. What can I
say? Try smaller fonts in the X server, or virtual screens.
<B>Weird</B> <B>SCSI</B> <B>behaviour.</B>
I am quoting David Myers Here...
&gt;&gt; OS: FreeBSD 2.2.6
&gt;&gt; CC: egcs-1.02
&gt;Just wanted to follow up on this... I recently changed my SCSI
card from
&gt;the Adaptec 2940UW to a dual-channel Symbios 786 chipset. When
I started up
&gt;SANE with your driver, I managed to scan line art drawings
okay, but Gray16
&gt;scans led to a stream of SCSI error messages on the console,
ultimately
&gt;hanging with a message saying the scanner wasn't releasing the
SCSI bus.
&gt;This may be that the Symbios is simply less tolerant of ancient
&gt;hardware, or may be bugs in your driver or in SANE itself...
</PRE>
<H2>DEBUG</H2><PRE>
If you encounter a GUI bug please set the environment variable
SANE_DEBUG_APPLE to 255 and rerun the excact 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 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 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.
</PRE>
<H2>TODO</H2><PRE>
<B>Non</B> <B>Blocking</B> <B>Support</B>
Make sane-apple a non blocking backend. Properly support for
<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>Missing</B> <B>Functionality.</B>
</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>
</PRE>
<H2>AUTHOR</H2><PRE>
The sane-apple backend was written not entirely from scratch by Milon
Firikis. It is mostly based on the mustek backend from David Mosberger
and Andreas Czechanowski
sane-backends 1.0.12-cvs 13 May 1998 <B><A HREF="sane-apple.5.html">sane-apple(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>

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

@ -0,0 +1,183 @@
<HTML>
<HEAD>
<TITLE>sane-artec.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-artec.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-artec.5.html">sane-artec(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-artec.5.html">sane-artec(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-artec - SANE backend for Artec flatbed scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-artec</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to Artec/Ultima SCSI flatbed scanners. At
present, the following scanners are known to work at least partially
with this backend:
Artec A6000C
Artec A6000C PLUS
Artec ViewStation AT3
BlackWidow BW4800SP (rebadged Artec AT3)
Artec ViewStation AT6
Artec ViewStation AT12
Artec AM12S
Plustek 19200S (rebadged Artec AM12S)
Although this manual page is generally updated with each release, up-
to-date information on new releases and extraneous helpful hints are
available from the backend homepage:
<B>http://www4.infi.net/~cpinkham/sane/</B>
</PRE>
<H2>DOCUMENTATION</H2><PRE>
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>artec.conf</I> file are a list of device names that
correspond to Artec scanners. Empty lines and lines starting with a
hash mark (#) are ignored. See <I>sane-scsi(5)</I> on details of what consti-
tutes a valid device name.
Sample file:
# artec.conf
#
# this is a comment.
#
# this line says search for any SCSI devices which are scanners and
have
# a vendor string of 'ULTIMA'
scsi ULTIMA
#
# the next line forces the backend to assume the next scanner found has
# the specified vendor string (useful for testing rebadged models).
vendor ULTIMA
#
# the next line forces the backend to assume the next scanner found has
# the specified model string (useful for testing rebadged models).
model AT3
#
# now a line that actually specifies a device. The backend is going to
# assume this is an Artec/Ultima AT3 because we forced the vendor
and
# model above.
/dev/scanner
#
# once we hit a scanner device line, the forced vendor and model
# string are
# 'forgotten', so the vendor and model for this next device will be
# determined from the result of a SCSI inquiry.
/dev/sge
#
</PRE>
<H2>SCSI ADAPTER TIPS</H2><PRE>
Some Artec scanners come with an included SCSI adapter. If your scan-
ner came with a DTC ISA scsi cards, you can probably use it with recent
(&gt;= 2.2.0) kernels using the generic NCR5380 support. You must pass
the following boot argument to the kernel: "dtc3181e=0x2c0,0"
I do not have any information on the PCI SCSI adapter included with
some newer Artec scanners.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/artec.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-artec.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-artec.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi- colon (`;'). If this variable is not set, the con-
figuration file is searched in two default directories: first,
the current working direc- tory (".") 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_ARTEC</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: SANE_DEBUG_ARTEC values
Number Remark
0 print important errors
1 print errors
2 print sense
3 print warnings
4 print scanner-inquiry
5 print informations
6 print less important informations
7 print major called procedures
8 print all called procedures
9 print procedure info/data messages
10 print called sane-init-routines
11 print called sane-procedures
12 print sane infos
13 print sane option-control messages
50 print verbose data/debug messages
== 100 print software RGB calibration data
== 101 print raw data from scanner to artec.data.raw file
== 128 print out all messages
Example:
export SANE_DEBUG_ARTEC=13
</PRE>
<H2>BUGS</H2><PRE>
Known bugs in this release: A6000C+ users with firmware v1.92 or ear-
lier have problems with the backend, the cause has not been determined.
Sometimes the backend is not particularly robust, you can possibly lock
up the SCSI bus (and/or machine) by not having patience enough when
scanning. 3-channel gamma correction is not implemented and single-
channel gamma correction is not totally working on models other than
the AT3.
</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>
</PRE>
<H2>AUTHOR</H2><PRE>
Chris Pinkham (cpinkham@infi.net) (does not exist anymore?)
sane-backends 1.0.12-cvs 24 Jan 2000 <B><A HREF="sane-artec.5.html">sane-artec(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>

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

@ -0,0 +1,198 @@
<HTML>
<HEAD>
<TITLE>sane-artec_eplus48u.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-artec_eplus48u.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B> SANE <B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-artec_eplus48u - SANE backend for the scanner Artec E+ 48U and re-
badged models
</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
Artec E+ 48U,
Tevion MD 9693,
Medion MD 9693,
Medion MD 9705 and
Trust Easy Webscan 19200.
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
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
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-
<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
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.
</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
with a hash mark (#) are ignored. The scanners are autodetected by <I>usb</I>
<I>vendor</I><B>_</B><I>id</I> <I>product</I><B>_</B><I>id</I> statements which are already included into
<I>artec</I><B>_</B><I>eplus48u.conf</I> <I>.</I> "vendor_id" and "product_id" are hexadecimal
numbers that identify the <B>scanner.</B>
Every usb section can have additional options
<B>artecFirmwareFile</B> <B>&lt;path&gt;/Artec48.usb</B>
The path to the firmware file. This option is required.
<B>redGamma</B> <B>1.0</B>
<B>greenGamma</B> <B>1.0</B>
<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
values specified here.
<B>redOffset</B> <B>0x28</B>
<B>greenOffset</B> <B>0x2f</B>
<B>blueOffset</B> <B>0x2f</B>
<B>redExposure</B> <B>0xa7</B>
<B>greenExposure</B> <B>0x116</B>
<B>blueExposure</B> <B>0xdc</B>
These are the default values for offset and exposure time. You
can e.g. change them to speed up calibration, if you don't want
to save the calibration data to disk.
<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
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
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-artec</I><B>_</B><I>eplus48u.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-artec</I><B>_</B><I>eplus48u.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_ARTEC_EPLUS48U</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_ARTEC_EPLUS48U=3
</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>
</PRE>
<H2>AUTHOR</H2><PRE>
Michael Herder &lt;crapsite@gmx.net&gt;
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-
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.
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: &lt;crapsite@gmx.net&gt;
sane-backends 1.0.12-cvs 19 Nov 2002 <B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(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>

61
man/sane-as6e.5.html 100644
Wyświetl plik

@ -0,0 +1,61 @@
<HTML>
<HEAD>
<TITLE>sane-as6e.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-as6e.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-as6e.5.html">sane-as6e(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-as6e.5.html">sane-as6e(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-as6e - SANE backend for using the Artec AS6E parallel port inter-
face scanner.
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-as6e</B> library implements a SANE (Scanner Access Now Easy) back-
end that provides access to Artec AS6E flatbed scanner. <B>It</B> <B>requires</B>
<B>the</B> <B>as6edriver</B> <B>program</B> <B>in</B> <B>order</B> <B>to</B> <B>operate.</B> The as6edriver program is
<B>not</B> included with the SANE package. It can be found at
<B>http://as6edriver.sourceforge.net</B>. See the as6edriver documentation
for technical information.
The <I>as6edriver</I> program must be in the path for executables ($PATH).
Especially if you run <I>saned</I> (the SANE network scanning daemon), take
care to setup the path for <I>inetd</I> or <I>xinetd</I> correctly or place the pro-
gram in a directory that is in the path.
</PRE>
<H2>FILES</H2><PRE>
<B>as6edriver</B> - driver program that controls the scanner.
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="as6edriver.5.html">as6edriver(5)</A></B>, <B><A HREF="saned.1.html">saned(1)</A></B>, <B>http://as6edriver.sourceforge.net</B>
</PRE>
<H2>AUTHOR</H2><PRE>
Eugene S. Weiss
</PRE>
<H2>EMAIL-CONTACT</H2><PRE>
yossarian@users.sourceforge.net
sane-backends 1.0.12-cvs Apr 2nd, 2003 <B><A HREF="sane-as6e.5.html">sane-as6e(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>

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

@ -0,0 +1,176 @@
<HTML>
<HEAD>
<TITLE>sane-avision.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-avision.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-avision.5.html">sane-avision(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-avision - SANE backend for original Avision and Avision OEM scan-
ners (HP, Minolta, Mitsubishi, UMAX and possibly more) flatbed scanners
</PRE>
<H2>ABOUT THIS FILE</H2><PRE>
This file only is a short descripton of the avision-backend for sane!
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-avision</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to various Avision scanners and the Avi-
sion OEM scanners labelled by HP, Minolta, Mitsubishi or Fujitsu.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The configuration file for this backend resides in
/usr/local/etc/sane.d/avision.conf.
Its contents is a list of device names that correspond to Avision and
Avision compatible scanners and backend-options. Empty lines and lines
starting with a hash mark (#) are ignored. A sample configuration file
is shown below:
<B>I</B> <B>suggest</B> <B>you</B> <B>hold</B> <B>one</B> <B>hand</B> <B>on</B> <B>the</B> <B>power-button</B> <B>of</B> <B>the</B> <B>scanner</B> <B>while</B>
<B>you</B> <B>try</B> the first scans!
# this is a comment
option force-a4
option disable-gamma-table
option disable-calibration
option one-calib-only
option old-calibration
#scsi Vendor Model Type Bus Channel ID LUN
scsi AVISION
scsi HP
scsi /dev/scanner
usb 0x03f0 0x0701
- force-a4:
Forces the backend to overwrite the scanable area
returned by the scanner. This might be needed for
the AV 630 which returns no area - or newer scanners
which retun the area in a unkown format our backend
doesn't recongize yet.
- disable-gamma-table:
Disables the usage of the scanner's gamma-table. You
might try this if your scans hang or only produces
random garbage.
- disable-calibration:
Disables the scanner's color calibration. You
might try this if your scans hang or only produces
random garbage.
- one-calib-only:
When this option is enabled, the backend will only
perform a calibration when the backend is initialized
and not before each scan. This might extend the life
of the CCD, but does not work reliable with the newer
USB scanners (they hang sometimes or return garbage
image data). So this option should be used with care.
- old-calibration:
This enables the use of the old calibration code for
testing purposes.
Note: Any option above modifies the default code-flow
for your scanner. The options should only be used
when you encounter problems with the default be-
haviour of the backend. Please report the need of
options to the backend-author so the backend can
be fixed as soon as possible.
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form:
<I>scsi</I> <I>special</I> <I>usb</I> <I>special</I>
Where <I>special</I> is the path-name for the device that corresponds to a
SCSI scanner or the USB vendor/product ID pair corresponding to the USB
scanner. The special device name must be a generic SCSI device or a
symlink to such a device. The program <I>sane-find-scanner</I> helps to find
out the correct device. Under Linux, such a device name could be
<I>/dev/sg0</I> or <I>/dev/sga</I>, for example. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details.
Note: Since the backend now includes native USB access,
it is no longer needed - even considered obsolete -
to access the scanner via the SCSI emulation (named
hpusbscsi on Linux) for Avision USB devices such as
the HP 53xx, HP 74xx or Minolta film-scanners.
A list with supported devices is built into the avision backend so
normally specifying an ID should not be necessary.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/avision.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-avision.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-avision.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_AVISION</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output. The
debug level 7 is the author's prefered value to debug backend
problems.
Example: export SANE_DEBUG_AVISION=7
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>
http://drocklinux.dyndns.org/rene/avision/index.html
</PRE>
<H2>AUTHOR</H2><PRE>
Ren? Rebe and Meino Christian Cramer
sane-backends 1.0.12-cvs 04 Mar 2003 <B><A HREF="sane-avision.5.html">sane-avision(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>

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

@ -0,0 +1,513 @@
<HTML>
<HEAD>
<TITLE>sane-bh.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-bh.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-bh.5.html">sane-bh(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-bh.5.html">sane-bh(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-bh - SANE backend for Bell+Howell Copiscan II series document
scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-bh</B> library implements a SANE (Scanner Access Now Easy) backend
that provides access to Bell+Howell Copiscan II series document scan-
ners. The Copiscan II 6338 has been the primary scanner model used
during development and testing, but since the programming interface for
the entire series is consistent the backend should work for the follow-
ing scanner models.
COPISCAN II 6338 Duplex Scanner with ACE
COPISCAN II 2135 Simplex Scanner
COPISCAN II 2137(A) Simplex Scanner (with ACE)
COPISCAN II 2138A Simplex Scanner with ACE
COPISCAN II 3238 Simplex Scanner
COPISCAN II 3338(A) Simplex Scanner (with ACE)
If you have a Bell+Howell scanner and are able to test it with this
backend, please contact <I>sane-devel@mostang.com</I> with the model number
and testing results. Have a look at
http://www.mostang.com/sane/mail.html concerning subscription to sane-
devel. Additionally, the author is curious as to the likelihood of
using this backend with the newer 4000 and 8000 series scanners. If
you have such a beast, please let me know.
The Bell+Howell Copiscan II series document scanners are high volume,
high throughput scanners designed for document scanning applications.
As such, they are lineart/grayscale scanners supporting a fixed number
of fairly low resolutions (e.g. 200/240/300dpi). However, they do have
a number of interesting and useful features suited to needs of document
imaging applications. This backend attempts to support as many of
these features as possible.
The main technical reference used in writing this backend is the <B>Bell</B>
<B>and</B> <B>Howell</B> <B>Copiscan</B> <B>II</B> <B>Remote</B> <B>SCSI</B> <B>Controller</B> <B>(RSC)</B> <B>OEM</B> <B>Technical</B> <B>Man-</B>
<B>ual</B> <B>Version</B> <B>1.5.</B> The Linux SCSI programming HOWTO, the SANE API docu-
mentation, and SANE source code were also extremely valuable resources.
The latest backend release, additional information and helpful hints
are available from the backend homepage:
<B>http://www.martoneconsulting.com/sane-bh.html</B>
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form:
<I>special</I>
Where <I>special</I> is the path-name for the special device that corresponds
to a SCSI scanner. For SCSI scanners, the special device name must be a
generic SCSI device or a symlink to such a device. Under Linux, such a
device name takes a format such as <I>/dev/sga</I> or <I>/dev/sg0</I>, for example.
See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>bh.conf</I> file is a list of device names that corre-
spond to Bell+Howell scanners. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> on details of what
constitutes a valid device name. Additionally, options can be speci-
fied; these lines begin with the word "option". Each option is
described in detail below. Empty lines and lines starting with a hash
mark (#) are ignored.
</PRE>
<H2>OPTIONS</H2><PRE>
The following options can be specified in the <I>bh.conf</I> file.
<B>disable-optional-frames</B>
This option prevents the backend from sending any optional
frames. This option may be useful when dealing with frontends
which do not support these optional frames. When this option is
in effect, the data is sent in a SANE_FRAME_GRAY frame. The
optional frames sent by this backend are: SANE_FRAME_G31D,
SANE_FRAME_G32D, SANE_FRAME_G42D and SANE_FRAME_TEXT. These
frames are generated based on the compression and barcode
options. These frames are never sent in preview mode.
<B>fake-inquiry</B>
This option is used for debugging purposes and its use is not
encouraged. Essentially, it allows the backend to initialize in
the absence of a scanner. This is useful for development and
not much else. This option must be specified earlier in the
configuration file than the devices which are to be "faked".
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/bh.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-bh.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-bh.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_BH</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.
</PRE>
<H2>SUPPORTED FEATURES</H2><PRE>
<B>ADF</B> <B>support</B>
With document scanners, automatic document feeder (ADF) support
is a key feature. The backend supports the ADF by default and
returns <B>SANE_STATUS_NO_DOCS</B> when the out-of-paper condition is
detected. The SANE frontend <B>scanadf</B> is a command line frontend
that supports multi-page scans. It has been used successfully
with this backend. The SANE frontend <B>xsane</B> is an improved GUI
frontend by Oliver Rauch. Support for multi-page scans is
included in xsane version 0.35 and above.
<B>Duplex</B> <B>scanning</B>
Some models, such as the COPISCAN II 6338, support duplex scan-
ning. That is, they scan both sides of the document during a
single pass through the scanner (the scanner has two cameras).
This backend supports duplex scanning (with the <B>--duplex</B>
option). The front and back page images are delivered consecu-
tively as if they were separately scanned pages.
<B>Hardware</B> <B>compression</B>
The scanner is capable of compressing the data into several
industry standard formats (CCITT G3, CCITT G3-2D, CCITT G4).
This results in increased performance as less data is passed
from the scanner to the host over the SCSI bus. The backend
supports these compression formats via the <B>--g31d,</B> <B>--g32d,</B>
<B>--g42d</B> options, respectively. Many SANE frontends are not
equipped to deal with these formats, however. The SANE frontend
<B>scanadf</B> supports these optional frame formats. The compressed
image data is written directly to a file and can then be pro-
cessed by a scan-script using the <B>--scan-script</B> option. Exam-
ples of this are given on the scanadf homepage.
<B>Automatic</B> <B>Border</B> <B>Detection</B>
The scanner can automatically detect the paper size and adjust
the scanning window geometry appropriately. The backend sup-
ports this useful feature with the <B>--autoborder</B> option. It is
enabled by default.
<B>Batch</B> <B>Mode</B> <B>Scanning</B>
The batch scan mode allows for maximum throughput. The Set Win-
dow parameters must remain constant during the entire batch.
<B>Icon</B> <B>Generation</B>
The Icon function generates a thumbnail of the full page image,
that can be transferred as if it were a separate page. This
allows the host to quickly display a thumbnail representation
during the scanning operation. Perhaps this would be a great
way of implementing a preview scan, but since a normal scan is
so quick, it might not be worth the trouble.
<B>Multiple</B> <B>Sections</B>
Multiple sections (scanning sub-windows) can be defined for the
front and back pages. Each section can have different charac-
teristics (e.g. geometry, compression). The sections are
returned as if they were separately scanned images. Addition-
ally sections can be used to greatly enhance the accuracy and
efficiency of the barcode/patchcode decoding process by limiting
the search area to a small subset of the page. Most Copiscan II
series scanners support up to 8 user-defined sections.
<B>Support</B> <B>Barcode/Patchcode</B> <B>Decoding</B>
The RSC unit can recognize Bar and Patch Codes of various types
embedded in the scanned image. The codes are decoded and the
data is returned to the frontend as a text frame. The text is
encoded in xml and contains a great deal of information about
the decoded data such as the location where it was found, its
orientation, and the time it took to find. Further information
on the content of this text frame as well as some barcode decod-
ing examples can be found on the backend homepage.
</PRE>
<H2>LIMITATIONS</H2><PRE>
<B>Decoding</B> <B>a</B> <B>single</B> <B>barcode</B> <B>type</B> <B>per</B> <B>scan</B>
The RSC unit can search for up to six different barcode types at
a time. While the code generally supports this as well, the
<B>--barcode-search-bar</B> option only allows the user to specify a
single barcode type. Perhaps another option which allows a
comma separated list of barcode type codes could be added to
address this.
<B>Scanning</B> <B>a</B> <B>fixed</B> <B>number</B> <B>of</B> <B>pages</B> <B>in</B> <B>batch</B> <B>mode</B>
The separation of front and back end functionality in SANE
presents a problem in supporting the 'cancel batch' functional-
ity in the scanner. In batch mode, the scanner is always a page
ahead of the host. The host, knowing ahead of time which page
will be the last, can cancel batch mode prior to initiating the
last scan command. Currently, there is no mechanism available
for the frontend to pass this knowledge to the backend. If
batch mode is enabled and the --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
avoided by specifying --batch=no when scanning a fixed number of
pages.
<B>Revision</B> <B>1.2</B> <B>Patch</B> <B>detector</B>
There is an enhanced patchcode detection algorithm available in
the RSC with revision 1.2 or higher that is faster and more
reliable than the standard Bar/Patch code decoder. This is not
currently supported.
</PRE>
<H2>OPTIONS</H2><PRE>
<B>Scan</B> <B>Mode</B> <B>Options:</B>
<B>--preview[=(yes|no)]</B> <B>[no]</B>
Request a preview-quality scan. When preview is set to yes
image compression is disabled and the image is delivered in a
SANE_FRAME_GRAY frame.
<B>--mode</B> <B>lineart|halftone</B> <B>[lineart]</B>
Selects the scan mode (e.g., lineart,monochrome, or color).
<B>--resolution</B> <B>200|240|300dpi</B> <B>[200]</B>
Sets the resolution of the scanned image. Each scanner model
supports a list of standard resolutions; only these resolutions
can be used.
<B>--compression</B> <B>none|g31d|g32d|g42d</B> <B>[none]</B>
Sets the compression mode of the scanner. Determines the type
of data returned from the scanner. Values are:
<B>none</B> - uncompressed data - delivered in a SANE_FRAME_GRAY frame
<B>g31d</B> - CCITT G3 1 dimension (MH) - delivered in a
SANE_FRAME_G31D frame
<B>g32d</B> - CCITT G3 2 dimensions (MR, K=4) - delivered in a
SANE_FRAME_G32D frame
<B>g42d</B> - CCITT G4 (MMR) - delivered in a SANE_FRAME_G42D frame
NOTE: The use of g31d, g32d, and g42d compression values causes
the backend to generate optional frame formats which may not be
supported by all SANE frontends.
<B>Geometry</B> <B>Options:</B>
<B>--autoborder[=(yes|no)]</B> <B>[yes]</B>
Enable/Disable automatic image border detection. When enabled,
the RSC unit automatically detects the image area and sets the
window geometry to match.
<B>--paper-size</B> <B>Custom|Letter|Legal|A3|A4|A5|A6|B4|B5</B> <B>[Custom]</B>
Specify the scan window geometry by specifying the paper size of
the documents to be scanned.
<B>--tl-x</B> <B>0..297.18mm</B> <B>[0]</B>
Top-left x position of scan area.
<B>--tl-y</B> <B>0..431.8mm</B> <B>[0]</B>
Top-left y position of scan area.
<B>--br-x</B> <B>0..297.18mm</B> <B>[297.18]</B>
Bottom-right x position of scan area.
<B>--br-y</B> <B>0..431.8mm</B> <B>[431.8]</B>
Bottom-right y position of scan area.
<B>Feeder</B> <B>Options:</B>
<B>--source</B> <B>Automatic</B> <B>Document</B> <B>Feeder|Manual</B> <B>Feed</B> <B>Tray</B> <B>[Automatic</B> <B>Document</B>
<B>Feeder]</B>
Selects the scan source (such as a document feeder). This
option is provided to allow multiple image scans with xsane; it
has no other purpose.
<B>--batch[=(yes|no)]</B> <B>[no]</B>
Enable/disable batch mode scanning. Batch mode allows scanning
at maximum throughput by buffering within the RSC unit. This
option is recommended when performing multiple pages scans until
the feeder is emptied.
<B>--duplex[=(yes|no)]</B> <B>[no]</B>
Enable duplex (dual-sided) scanning. The scanner takes an image
of each side of the document during a single pass through the
scanner. The front page is delivered followed by the back page.
Most options, such as compression, affect both the front and
back pages.
<B>--timeout-adf</B> <B>0..255</B> <B>[0]</B>
Sets the timeout in seconds for the automatic document feeder
(ADF). The value 0 specifies the hardware default value which
varies based on the scanner model.
<B>--timeout-manual</B> <B>0..255</B> <B>[0]</B>
Sets the timeout in seconds for semi-automatic feeder. The
value 0 specifies the hardware default value which varies based
on the scanner model.
<B>--check-adf[=(yes|no)]</B> <B>[no]</B>
Check ADF Status prior to starting scan using the OBJECT POSI-
TION command. Note that this feature requires RSC firmware
level 1.5 or higher and dip switch 4 must be in the on position.
NOTE: This option has not been tested extensively and may pro-
duce undesireable results.
<B>Enhancement:</B>
<B>--control-panel[=(yes|no)]</B> <B>[yes]</B>
Enables the scanner's control panel for selecting image enhance-
ment parameters. When the option is set to no the following
options are used to control image enhancement. See the
Bell+Howell scanner users' guide for complete information on ACE
functionality.
<B>--ace-function</B> <B>-4..4</B> <B>[3]</B>
Specify the Automatic Contrast Enhancement (ACE) Function.
<B>--ace-sensitivity</B> <B>0..9</B> <B>[5]</B>
Specify the Automatic Contrast Enhancement (ACE) Sensitivity.
<B>--brightness</B> <B>0..255</B> <B>[0]</B>
Controls the brightness of the acquired image. Ignored for ACE
capable scanners.
<B>--threshold</B> <B>0..255</B> <B>[0]</B>
Select minimum-brightness to get a white point. Ignored for ACE
capable scanners.
<B>--contrast</B> <B>0..255</B> <B>[inactive]</B>
Controls the contrast of the acquired image. This option is not
currently used by the scanner (and perhaps never will be).
<B>--negative[=(yes|no)]</B> <B>[no]</B>
Swap black and white, yielding a reverse-video image.
<B>Icon:</B>
<B>--icon-width</B> <B>0..3600pel</B> <B>(in</B> <B>steps</B> <B>of</B> <B>8)</B> <B>[0]</B>
Width of icon (thumbnail) image in pixels.
<B>--icon-length</B> <B>0..3600pel</B> <B>(in</B> <B>steps</B> <B>of</B> <B>8)</B> <B>[0]</B>
Length of icon (thumbnail) image in pixels.
<B>Barcode</B> <B>Options:</B>
<B>--barcode-search-bar</B> <B>&lt;see</B> <B>list&gt;</B> <B>[none]</B>
Specifies the barcode type to search for. If this option is not
specified, or specified with a value of none, then the barcode
decoding feature is completely disabled. The valid barcode type
are:
<B>none</B>
<B>ean-8</B>
<B>ean-13</B>
<B>reserved-ean-add</B>
<B>code39</B>
<B>code2-5-interleaved</B>
<B>code2-5-3lines-matrix</B>
<B>code2-5-3lines-datalogic</B>
<B>code2-5-5lines-industrial</B>
<B>patchcode</B>
<B>codabar</B>
<B>codabar-with-start-stop</B>
<B>code39ascii</B>
<B>code128</B>
<B>code2-5-5lines-iata</B>
<B>--barcode-search-count</B> <B>1..7</B> <B>[3]</B>
Number of times that the RSC performs the decoding algorithm.
Specify the smallest number possible to increase performance.
If you are having trouble recognizing barcodes, it is suggested
that you increase this option to its maximum value (7).
<B>--barcode-search-mode</B> <B>&lt;see</B> <B>list&gt;</B> <B>[horiz-vert]</B>
Chooses the orientation of barcodes to be searched. The valid
orientations are:
<B>horiz-vert</B>
<B>horizontal</B>
<B>vertical</B>
<B>vert-horiz</B>
<B>--barcode-hmin</B> <B>0..1660mm</B> <B>[5]</B>
Sets the barcode minimum height in millimeters (larger values
increase recognition speed). Of course the actual barcodes in
the document must be of sufficient size.
<B>--barcode-search-timeout</B> <B>20..65535us</B> <B>[10000]</B>
Sets the timeout for barcode searching in milliseconds. When
the timeout expires, the decoder will stop trying to decode bar-
codes.
<B>--section</B> <B>&lt;string&gt;</B> <B>[]</B>
Specifies a series of image sections. A section can be used to
gather a subset image or to provide a small area for barcode
decoding. Each section is specified in the following format
(units are in millimeters):
<B>&lt;width&gt;x&lt;height&gt;+&lt;top-left-x&gt;+&lt;top-left-y&gt;[:functioncode...]</B>
Multiple sections can be specified by separating them with commas.
For example <B>76.2x25.4+50.8+0:frontbar</B> identifies an area 3 inches wide
and 1 inch high with a top left corner at the top of the page two
inches from the left hand edge of the page. This section will be used
for barcode decoding on the front page only.
For example <B>50.8x25.4+25.4+0:frontbar:front:g42d</B> identifies an area 2
inches wide and 1 inch high with a top left corner at the top of the
page one inch from the left hand edge of the page. This section will
be used for barcode decoding on the front page as well as generating an
image compressed in g42d format.
Ordinarily barcodes are searched in the entire image. However, when
you specify sections all barcode searching is done within the specific
sections identified. This can significantly speed up the decoding pro-
cess.
The following functioncodes are available:
<B>front</B> - generate an image for the front page section
<B>back</B> - generate an image for the back page section
<B>frontbar</B> - perform barcode search in front page section
<B>backbar</B> - perform barcode search in back page section
<B>frontpatch</B> - perform patchcode search in front page section
<B>backpatch</B> - perform patchcode search in back page section
<B>none</B> - use no image compression
<B>g31d</B> - use Group 3 1 dimension image compression
<B>g32d</B> - use Group 3 2 dimensions image compression
<B>g42d</B> - use Group 4 2 dimensions image compression
If you omit a compression functioncode, the full page compression set-
ting is used. If you specify multiple compression functioncodes, only
the last one is used.
<B>--barcode-relmax</B> <B>0..255</B> <B>[0]</B>
Specifies the maximum relation from the widest to the smallest
bar.
<B>--barcode-barmin</B> <B>0..255</B> <B>[0]</B>
Specifies the minimum number of bars in Bar/Patch code.
<B>--barcode-barmax</B> <B>0..255</B> <B>[0]</B>
Specifies the maximum number of bars in a Bar/Patch code.
<B>--barcode-contrast</B> <B>0..6</B> <B>[3]</B>
Specifies the image contrast used in decoding. Use higher val-
ues when there are more white pixels in the code.
<B>--barcode-patchmode</B> <B>0..1</B> <B>[0]</B>
Controls Patch Code detection.
</PRE>
<H2>BUGS</H2><PRE>
This is a new backend; detailed bug reports are welcome -- and expected
;)
If you have found something that you think is a bug, please attempt to
recreate it with the SANE_DEBUG_BH environment variable set to 255, and
send a report detailing the conditions surrounding the bug to
<I>sane-devel@mostang.com</I>.
</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="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="scanadf.1.html">scanadf(1)</A></B>
</PRE>
<H2>AUTHOR</H2><PRE>
The sane-bh backend was written by Tom Martone, based on the sane-ricoh
backend by Feico W. Dillema and the bnhscan program by Sean
Reifschneider of tummy.com ltd. Some 8000 enhancements added by Mark
Temple.
sane-backends 1.0.12-cvs 15 Sep 1999 <B><A HREF="sane-bh.5.html">sane-bh(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>

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

@ -0,0 +1,119 @@
<HTML>
<HEAD>
<TITLE>sane-canon.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-canon.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-canon.5.html">sane-canon(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-canon.5.html">sane-canon(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-canon - SANE backend for Canon SCSI scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-canon</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to the following Canon flatbed and film
scanners:
CanoScan 300
CanoScan 600
CanoScan FB620S
CanoScan FB1200S
CanoScan FS2700F
CanoScan FS2710S
Parallel port and USB scanners are not supported by this backend; see
the manual pages for sane-canon_pp and sane-canon630u for further
information.
IMPORTANT: This is beta code. We tested the code on the scanners listed
above, using the computers and operating systems available to us, but
we cannot guarantee that the backend will work smoothly with future
operating systems, SCSI adapters, SANE frontend programs, or Canon
scanners not contained in the list above. In some cases your computer
might even hang. It cannot be excluded (although we consider it
extremely unlikely) that your scanner will be damaged.
That said, TESTERS ARE WELCOME. Send your bug reports and comments to
Manuel Panea &lt;mpd@rzg.mpg.de&gt;; for questions concerning the FB620 and
FB1200S contact Mitsuru Okaniwa &lt;m-okaniwa@bea.hi-ho.ne.jp&gt;, for the
FS2710S Ulrich Deiters &lt;ukd@xenon.pc.uni-koeln.de&gt;.
</PRE>
<H2>TIPS (FS2700F)</H2><PRE>
Scanning either slides or negatives has been found to require rather
large gamma corrections of about 2.2 to 2.4 (same value for red, green,
and blue). It is recommended to use the automatic exposure controls of
the frontend xsane for best results.
The "Auto Focus" function triggers a special pass to determine the
focus value. After that, the real scanning pass takes place.
Even with "Auto Focus" turned on, the scanned image is often a bit too
blurred. Using the GIMP to do a "Filter-&gt;Enhance-&gt;Sharpen" at about 40
to 60 improves the image considerably.
</PRE>
<H2>TIPS (FS2710S)</H2><PRE>
Gamma corrections are done not by the scanner, but by the backend. The
scanner is always run in 12-bit mode. In "color" mode the image data
are corrected for gamma, shadow point, etc., and then truncated to
8-bit intensities; the default gamma value is 2.0. In "raw" mode the
image data are exported without corrections as 16-bit intensities; this
mode can be recommended if extensive adjustments have to be made to a
picture (and if the frontend can handle 16-bit intensities).
Negatives are handled by simple color inversion and may require manual
removal of blue discoloration.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/lib/sane/libsane-canon.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-canon.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_CANON</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_CANON=4
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>
http://www.rzg.mpg.de/~mpd/sane/
doc/canon.install2700F.txt (installation of a CanoScan 2700F
</PRE>
<H2>AUTHOR</H2><PRE>
Helmut Koeberle, Manuel Panea, and Markus Mertinat; FB620S and FB1200S
support by Mitsuru Okaniwa; FS2710S support by Ulrich Deiters
Man page by Henning Meier-Geinitz (mostly based on canon.README)
sane-backends 1.0.12-cvs 03 May 2001 <B><A HREF="sane-canon.5.html">sane-canon(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>

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

@ -0,0 +1,135 @@
<HTML>
<HEAD>
<TITLE>sane-canon630u.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-canon630u.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-canon630u.5.html">sane-canon630u(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-canon630u.5.html">sane-canon630u(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-canon630u - SANE backend for the Canon 630u USB flatbed scanner
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-canon</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to the following Canon flatbed scanners:
CanoScan 630u
CanoScan 636u (hopefully)
IMPORTANT: this is alpha code. Although there are no known bugs at
this time, this code uses the Linux USB kernel drivers, which are cur-
rently in active development. So it may not work, your computer might
even hang, and it cannot be excluded (although I consider it extremely
unprobable) that your scanner will be damaged.
That said, TESTERS ARE WELCOME. Send your bug reports and comments to
Nathan Rutman &lt;nathan@gordian.com&gt;
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form:
<I>special</I>
Where <I>special</I> is the path-name for the special device that corresponds
to a USB scanner or a symlink to such a device. The program <I>sane-find-</I>
<I>scanner</I> helps to find out the correct device. Under Linux, such a
device name could be <I>/dev/usb/scanner0</I> for example. See <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>
for details.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>canon630u.conf</I> file is a list of device names that
correspond to Canon USB scanners. Empty lines and lines starting with
a hash mark (#) are ignored. Only one device name can be listed in
<I>canon630u.conf</I>.
</PRE>
<H2>NOTES</H2><PRE>
Due to Canon's unwillingness to provide scanner documentation, this
software was developed by analyzing the USB traffic of the Windows 2000
driver. So things like the calibration procedure I kind of made up; it
seems to work for my scanner. If you have complaints, let me know.
This driver requires the ability to send USB Control Messages, avail-
able in kernel 2.4.12 or later.
This scanner may not be recognized (yet) by the USB kernel driver.
Check for "Driver=usbscanner" under /proc/bus/usb/devices. If
"Driver=(none)", try forcing it with "modprobe scanner vendor=0x04a9
product=0x2204"
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/canon630u.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-canon630u.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-canon630u.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
<I>/tmp/canon.cal</I>
The calibration file used to normalize pixel brightness. This
is calculated every time the scanner is first used after it has
lost power. It can be forced to recalibrate by simply deleting
this file.
</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_CANON630U</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: SANE_DEBUG_CANON630U=12 scanimage &gt; /dev/null
</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-find-scanner.1.html">sane-find-scanner(1)</A></B>
http://canon-fb630u.sourceforge.net/
</PRE>
<H2>AUTHOR</H2><PRE>
Nathan Rutman
sane-backends 1.0.12-cvs 06 Apr 2002 <B><A HREF="sane-canon630u.5.html">sane-canon630u(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>

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

@ -0,0 +1,233 @@
<HTML>
<HEAD>
<TITLE>sane-canon_pp.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-canon_pp.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-canon_pp.5.html">sane-canon_pp(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-canon_pp.5.html">sane-canon_pp(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-canon_pp - SANE backend for Canon CanoScan Parallel Port flatbed
scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-canon_pp</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to the following Canon flatbed scanners:
CanoScan FB320P
CanoScan FB620P
CanoScan FB330P
CanoScan FB630P
CanoScan N340P
CanoScan N640P
CanoScan N640P ex
No USB scanners are supported and there are no plans to support them in
the future. Other projects are working on support for USB scanners.
See the <B>PROJECTS</B> file for more detail. The FB310P and FB610P are re-
badged Avision scanners which use a different command set, so are
unlikely to be supported by this backend in the future.
IMPORTANT: this is alpha code. While we have made every effort to make
it as reliable as possible, it will not always work as expected. Feed-
back is still appreciated. Please send any bug reports to the main-
tainers as listed on the web page (listed in <B>SEE</B> <B>ALSO</B> below).
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form presented by libieee1284.
These names are highly dependent on operating system and version.
On Linux 2.4 kernels this will be of the form <I>parport0</I> or older (2.2
and before) kernels may produce names like <I>0x378</I> (the base address of
your port) or simply <I>0</I> depending on your module configuration. Check
the contents of <I>/proc/parport</I> if it exists. If you don't want to spec-
ify a default port (or don't know its name), the backend should be able
to detect which port your scanner is on.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>canon</I><B>_</B><I>pp.conf</I> file is a list of options for the
driver to use. Empty lines and lines starting with a hash mark (#) are
ignored.
The supported options are currently <B>ieee1284</B>, <B>calibrate</B>, <B>init_mode</B>, and
<B>force_nibble</B>
Option <B>ieee1284</B> <I>port-name</I> defines which port to use. The format of
port-name is OS dependent, based on the names presented by libieee1284.
Please only have one of these lines, or all but one will be ignored.
Option <B>calibrate</B> <I>cal-file</I> <I>[port-name]</I> defines which calibration file to
use on a per-port basis. If you only have one parport, the port-name
argument may be omitted - but be careful as this will cause problems on
multi-scanner systems. You may have as many of these lines as you
like, as long as each has a unique port name. The tilde (`~') charac-
ter is acceptable and will be expanded to the value of the HOME envi-
ronment.
Option <B>init_mode</B> <I>&lt;AUTO|FB620P|FB630P&gt;</I> <I>[portname]</I> defines which
initialisation (wake-up) mode to use on a per-port basis. If you only
have one parport, the portname argument may be omitted - but be careful
as this may cause problems on multi-scanner systems. You may have as
many of these lines as you like, as long as each has a unique port
name. The valid initialisation modes are FB620P (which strobes
10101010 and 01010101 on the data pins), FB630P (which strobes 11001100
and 00110011 on the data pins) and AUTO, which will try FB630P mode
first then FB620P mode second. The FB620P mode is also used by the
FB320P. The FB630P mode is used by the FB330P, N340P, and N640P.
Option <B>force_nibble</B> forces the driver to use nibble mode even if ECP
mode is reported to work by libieee1284. This works-around the rare
issue of ECP mode being reported to work by the library, then not work-
ing.
</PRE>
<H2>TIPS</H2><PRE>
Hit the "Calibrate" button before scanning. It vastly improves the
quality of scans.
To enable automatic detection of your scanner, uncomment the "canon_pp"
line from <I>/usr/local/etc/sane.d/dll.conf</I>
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/canon</I><B>_</B><I>pp.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-canon</I><B>_</B><I>pp.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-canon</I><B>_</B><I>pp.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_CANON_PP</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_CANON_PP=4
</PRE>
<H2>NOTES</H2><PRE>
<B>Features</B> <B>available</B> <B>in</B> <B>the</B> <B>Windows</B> <B>interface</B>
<B>Brightness</B> <B>and</B> <B>Contrast</B>
These are not implemented, and probably never will be. These
appear to be implemented entirely in software. Use GIMP or a
similar program if you need these features.
<B>Descreen</B> <B>Mode</B>
This appears on our first analysis to be just oversampling with
an anti-aliasing filter. Again, it seems to be implemented
entirely in software, so GIMP is your best bet for now.
<B>Gamma</B> <B>Tables</B>
This is under investigation, but for now only a simple gamma
profile (ie: the one returned during calibration) will be
loaded.
<B>Communication</B> <B>Problems</B>
ECP mode in libieee1284 doesn't always work properly, even with new
hardware. We believe that this is a ppdev problem. If you change the
configuration file to include <B>force_nibble</B> , the problem will go away,
but you will only be able to scan in nibble mode.
Sometimes the scanner can be left in a state where our code cannot
revive it. If the backend reports no scanner present, try unplugging
the power and plugging it back in. Also try unplugging printers from
the pass-through port.
The scanner will not respond correctly to our commands when you first
plug in the power. You may find if you try a scan very soon after
plugging in the power that the backend will incorrectly report that you
have no scanner present. To avoid this, give it about 10 seconds to
reset itself before attempting any scans.
<B>Repeated</B> <B>Lines</B>
Sometimes at high resolutions (ie. 600dpi) you will notice lines which
appear twice. These lines correspond to points where the scanner head
has stopped during the scan (it stops every time the internal 64kb
buffer is full). Basically it's a mechanical problem inside the scan-
ner, that the tolerance of movement for a start/stop event is greater
than 1/600 inches. I've never tried the windows driver so I'm not sure
how (or if) it works around this problem, but as we don't know how to
rewind the scanner head to do these bits again, there's currently no
nice way to deal with the problem.
<B>Grey-scale</B> <B>Scans</B>
Be aware that the scanner uses the green LEDs to read grey-scale scans,
meaning green coloured things will appear lighter than normal, and red
and blue coloured items will appear darker than normal. For high-accu-
racy grey-scale scans of colour items, it's best just to scan in colour
and convert to grey-scale in graphics software such as the GIMP.
<B>FB620P/FB320P</B> <B>Caveats</B>
These models can not be reset in the same way as the others. The win-
dows driver doesn't know how to reset them either - when left with an
inconsistent scanner, it will start scanning half way down the page!
Aborting is known to work correctly on the FB*30P models, and is known
to be broken on the FB*20P models. The FB620P which I tested on simply
returns garbage after a scan has been aborted using the method we know.
Aborting is able to leave the scanner in a state where it can be shut
down, but not where another scan can be made.
</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> http://canon-fb330p.sourceforge.net/
</PRE>
<H2>AUTHOR</H2><PRE>
This backend is primarily the work of Simon Krix (Reverse Engineering),
and Matthew Duggan (SANE interface).
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.12-cvs 1 October 2002 <B><A HREF="sane-canon_pp.5.html">sane-canon_pp(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>

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

@ -0,0 +1,79 @@
<HTML>
<HEAD>
<TITLE>sane-config.1</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-config.1</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-config.1.html">sane-config(1)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-config.1.html">sane-config(1)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-config - get information about the installed version of libsane
</PRE>
<H2>SYNOPSIS</H2><PRE>
<B>sane-config</B> <B>[--prefix]</B> <B>[--exec-prefix]</B> <B>[--libs]</B> <B>[--cflags]</B> <B>[--ldflags]</B>
<B>[--version]</B> <B>[--help</B> <I>[OPTION]</I><B>]</B>
</PRE>
<H2>DESCRIPTION</H2><PRE>
<B>sane-config</B> is a tool that is used to determine the compiler and linker
flags that should be used to compile and link <B>SANE</B> frontends to a <B>SANE</B>
backend library (libsane).
</PRE>
<H2>OPTIONS</H2><PRE>
<B>sane-config</B> accepts the following options:
<B>--version</B>
Print the currently installed version of libsane on the stan-
dard output.
<B>--help</B> <B>OPTION</B>
Print a short usage message. If OPTION is specified, help for
that option (e.g. --libs) is printed (if available).
<B>--libs</B> Print the additional libraries that are necessary to link a
<B>SANE</B> frontend to libsane.
<B>--ldflags</B>
Print the linker flags that are necessary to link a <B>SANE</B> fron-
tend to libsane.
<B>--cflags</B>
Print the compiler flags that are necessary to compile a <B>SANE</B>
frontend.
<B>--prefix</B>
Print the prefix used during compilation of libsane.
<B>--exec-prefix</B>
Print the exec-prefix used during compilation of libsane.
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>
</PRE>
<H2>AUTHOR</H2><PRE>
This manual page was written by Julien BLACHE &lt;jblache@debian.org&gt;, for
the Debian GNU/Linux system (but may be used by others).
sane-backends 1.0.12-cvs 15 October 2002 <B><A HREF="sane-config.1.html">sane-config(1)</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>

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

@ -0,0 +1,133 @@
<HTML>
<HEAD>
<TITLE>sane-coolscan.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-coolscan.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-coolscan - SANE backend for Nikon film-scanners
</PRE>
<H2>ABOUT THIS FILE</H2><PRE>
This file is a short descripton of the coolscan-backend for sane!
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-coolscan</B> library implements a SANE backend that provides the
interface to the following Nikon Coolscan Film scanners: Nikon LS20,
LS30, LS1000, LS2000.
<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>time.</B>
</PRE>
<H2>CONFIGURATION</H2><PRE>
The configuration file for this backend resides in
/usr/local/etc/sane.d/coolscan.conf.
Its contents is a list of device names that correspond to Nikon
Coolscan scanners. Empty lines and lines starting with a hash mark (#)
are ignored. A sample configuration file is shown below:
#scsi Vendor Model Type
scsi Nikon * Scanner
/dev/scanner
The special device name must be a generic SCSI device or a symlink to
such a device. To find out to which device your scanner is assigned
and how you have to set the permissions of that device, have a look at
sane-scsi.
</PRE>
<H2>SCSI ADAPTER TIPS</H2><PRE>
Some SCSI-adapters and low-level SCSI drivers do not work correctly
with this backend and the Coolscan scanners. These systems hang when
the autofocus command is send to the Scanner. To see a list of which
card/driver combinations work or dont work have a look at:
http://andreas.rick.free.fr/sane/autofocus.html.
</PRE>
<H2>FILES</H2><PRE>
The backend configuration file:
/usr/local/etc/sane.d/coolscan.conf.
The static library implementing this backend:
/usr/local/lib/sane/libsane-coolscan.a
The shared library implementing this backend:
/usr/local/lib/sane/libsane-coolscan.so
(present on systems that support dynamic loading)
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_COOLSCAN</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend. E.g., a
value of 128 requests all debug output to be printed. Smaller levels
reduce verbosity: SANE_DEBUG_COOLSCAN values
Examples:
on bash:
export SANE_DEBUG_COOLSCAN=8
on csh
setenv SANE_DEBUG_COOLSCAN 8
</PRE>
<H2>BUGS</H2><PRE>
The autofocus command does not work with some SCSI card/driver combi-
nations
The gamma table is not implemented for the LS1000 yet.
The dust-removal is not working yet
</PRE>
<H2>SEE ALSO</H2><PRE>
http://andreas.rick.free.fr/sane/ The homepage of this backend
http://www.sema.be/coolscan/ The original version of the coolscan
backend by Didier
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>
</PRE>
<H2>THANKS TO</H2><PRE>
Didier Carlier - For writing the original Coolscan backend (without it
I would not have started this)
Oliver.Rauch - For adapting xsane so quickly to the infrared stuff.
All the other people working on SANE.
</PRE>
<H2>AUTHOR</H2><PRE>
Andreas Rick
</PRE>
<H2>EMAIL-CONTACT</H2><PRE>
andreas.rick@free.fr
sane-backends 1.0.12-cvs 4 July 2000 <B><A HREF="sane-coolscan.5.html">sane-coolscan(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>

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

@ -0,0 +1,203 @@
<HTML>
<HEAD>
<TITLE>sane-coolscan2.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-coolscan2.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-coolscan2 - SANE backend for Nikon Coolscan film scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The library implements a SANE (Scanner Access Now Easy) backend that
provides access to Nikon Coolscan film scanners. Some functions of
this backend should be considered <B>beta-quality</B> software. Most functions
have been stable for a long time, but of course new development can not
and will not function properly from the very first day. Please report
any strange behaviour to the maintainer of the backend.
At present, the following scanners are known to work with this backend:
Model: Connection Type
--------------------------- -------------------
LS-30 (Coolscan III) SCSI
LS-2000 SCSI
LS-40 ED (Coolscan IV) USB
LS-4000 ED IEEE 1394
LS-8000 ED IEEE 1394
Please send mail to the backend author (andras@users.sourceforge.net)
to report successes or failures.
</PRE>
<H2>OPTIONS</H2><PRE>
The options the backend supports can either be selected through command
line options to programs like scanimage or through GUI elements in
xscanimage or xsane.
Valid command line options and their syntax can be listed by using
scanimage --help -d coolscan2:&lt;interface&gt;:&lt;device&gt;
where &lt;interface&gt; and &lt;device&gt; specify the device in question, as in
the configuration file (see next section). The "-d" parameter and its
argument can be omitted to obtain information on the first scanner
identified. Use the command
scanimage -L
to list all devices recognized by your SANE installation.
The options should be fully described by the description or tooltips
given by frontend. Here is a description of some of the most important
options, in the syntax with which they must be supplied to scanimage:
<I>--frame</I> <I>&lt;n&gt;</I>
This option specifies which frame to operate on, if a motorized
film strip feeder or APS adapter are used. The frame number <I>&lt;n&gt;</I>
ranges from 1 to the number of frames available, which is sensed
each time the backend is initialized (usually each time you
start the frontend).
<I>--subframe</I> <I>&lt;x&gt;</I>
This option shifts the scan window by the specified amount
(default unit is mm).
<I>--infrared=yes/no</I>
If set to "yes", the scanner will read the infrared channel,
thus allowing defect removal in software. The infrared image is
read during a second scan, with no options altered. The backend
must not be restarted between the scans. If you use scanimage,
perform a batch scan with batch-count=2 to obtain the IR infor-
mation.
<I>--depth</I> <I>&lt;n&gt;</I>
Here &lt;n&gt; can either be 8 or the maximum number of bits supported
by the scanner (10, 12, or 14). It specifies whether or not the
scanner reduces the scanned data to 8 bits before sending it to
the backend. If 8 bits are used, some information and thus image
quality is lost, but the amount of data is smaller compared to
higher depths. Also, many imaging programs and image formats
cannot handle depths greater than 8 bits.
<I>--autofocus</I>
Perform autofocus operation. Unless otherwise specified by the
other options ( <I>--focus-on-centre</I> and friends), focusing is per-
formed on the centre of the selected scan area.
<I>--ae-wb</I>
<I>--ae</I> Perform a pre-scan to calculate exposure values automatically.
<I>--ae-wb</I> will maintain the white balance, while <I>--ae</I> will adjust
each channel separately.
<I>--exposure</I>
Multiply all exposure times with this value. This allows expo-
sure correction without modifying white balance.
<I>--load</I> Load the next slide when using the slide loader.
<I>--eject</I>
Eject the film strip or mounted slide when using the slide
loader.
<I>--reset</I>
Reset scanner. The scanner will perform the same action as when
power is turned on: it will eject the film strip and calibrate
itself. Use this whenever the scanner refuses to load a film
strip properly, as a result of which <I>--eject</I> does not work.
</PRE>
<H2>CONFIGURATION FILE</H2><PRE>
The configuration file /usr/local/etc/sane.d/coolscan2.conf specifies
the device(s) that the backend will use. Owing to the nature of the
supported connection types SCSI, USB, and IEEE 1394, the default con-
figuration file supplied with the SANE distribution should work without
being edited.
Each line in the configuration file is either of the following, where
all entries are case-sensitive:
<I>blank</I> <I>or</I> <I>starting</I> <I>with</I> <I>a</I> <I>'#'</I> <I>character</I>
These lines are ignored, thus '#' can be used to include com-
ments.
<I>containing</I> <I>only</I> <I>the</I> <I>word</I> <I>"auto"</I>
This instructs the backend to probe for a scanner by scanning
the buses for devices with know identifiers. This is the action
taken when no configuration file is present.
<I>a</I> <I>line</I> <I>of</I> <I>the</I> <I>form</I> <I>&lt;interface&gt;:&lt;device&gt;</I>
Here &lt;interface&gt; can be one of "scsi" or "usb", and &lt;device&gt; is
the device file of the scanner. Note that IEEE 1394 devices are
handled by the SBP-2 module in the kernel and appear to SANE as
SCSI devices.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/lib/sane/libsane-coolscan2.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-coolscan2.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
<I>/usr/local/etc/sane.d/coolscan2.conf</I>
Configuration file for this backend, read each time the backend
is initialized.
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_COOLSCAN2</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
E.g., a value of 128 requests all debug output to be printed.
Smaller levels reduce verbosity.
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, <B><A HREF="xsane.1.html">xsane(1)</A></B>
</PRE>
<H2>BUGS</H2><PRE>
Currently, the SANE protocol does not allow automatically updating
options whenever the hardware changes. Thus the number of choices for
the <B>--frame</B> option will be fixed when the backend is initialized (usu-
ally when the user runs the frontend). In particular, if there is no
film strip in the automatic film strip feeder when the backend is ini-
tialized, the frame option will not appear at all. Also, restarting the
frontend after swapping film adapters is strongly recommended.
Linux kernels prior to 2.4.19 had a patch that truncated INQUIRY data
from IEEE 1394 scanners to 36 bytes, discarding vital information about
the scanner. The IEEE 1394 models therefore only work with 2.4.19 or
later.
No real bugs currently known, please report any to the backend main-
tainer or the SANE developers' email list.
</PRE>
<H2>AUTHORS</H2><PRE>
The backend is written and maintained by Andr?s Major
(andras@users.sourceforge.net).
sane-backends 1.0.12-cvs 22/08/2002 <B><A HREF="sane-coolscan2.5.html">sane-coolscan2(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>

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

@ -0,0 +1,134 @@
<HTML>
<HEAD>
<TITLE>sane-dc210.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-dc210.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-dc210.5.html">sane-dc210(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-dc210.5.html">sane-dc210(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-dc210 - SANE backend for Kodak DC210 Digital Camera
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-dc210</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to the Kodak DC210 camera. THIS IS
EXTREMELY ALPHA CODE! USE AT YOUR OWN RISK!!
</PRE>
<H2>DEVICE NAMES</H2><PRE>
The current version of the backend only allows one camera to be con-
nected. The device name is always "0".
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>dc210.conf</I> specify the serial port and baud rate to
use. The baud rate specifies the maximum rate to use while downloading
pictures. (The camera is always initialized using 9600 baud, then
switches to the higher rate). On my 90MHz Pentium, I usually have no
problems downloading at 115200 baud as long as the system is not exces-
sively busy and the "interrupt-unmask flag" is set in the IDE driver
(hdparm -u1). Supported baud rates are: 9600, 19200, 38400, 57600, and
115200.
The dumpinquiry line causes some information about the camera to be
printed.
cmdrespause specifies how many usec (1,000,000ths of a) between writing
the command and reading the result should be used. 125000 seems to be
the lowest I could go reliably.
breakpause is the time in 1,000,000ths of a usec between sending the
"back to default" break sending commands.
Empty lines and lines starting with a hash mark (#) are ignored. A
sample configuration file is shown below:
port=/dev/ttyS0
# this is a comment
baud=115200
dumpinquiry
cmdrespause=125000
breakpause=1000000
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/dc210.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-dc210.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-dc210.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the
configuration file is searched in two default directories:
first, the current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
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_DC210</B>
If the library was compiled with debugging support enabled, this
environment variable controls the debug level for this backend.
A value of 128 requests maximally copious debug output; smaller
levels reduce verbosity.
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>
</PRE>
<H2>AUTHOR</H2><PRE>
Brian J. Murrell
This backend is based somewhat on the dc25 backend included in this
package by Peter Fales.
The manpage was copied from the dc25 backend and somewhat edited by
Henning Meier-Geinitz.
</PRE>
<H2>BUGS</H2><PRE>
Known bugs/limitations are: ?
More general comments, suggestions, and inquiries about frontends or
SANE should go to the SANE Developers mailing list (see
http://www.mostang.com/sane/mail.html for details). You must be sub-
scribed to the list, otherwise your mail won't be sent to the sub-
scribers.
sane-backends 1.0.12-cvs 15 July 2000 <B><A HREF="sane-dc210.5.html">sane-dc210(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>

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

@ -0,0 +1,137 @@
<HTML>
<HEAD>
<TITLE>sane-dc240.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-dc240.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-dc240.5.html">sane-dc240(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-dc240.5.html">sane-dc240(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-dc240 - SANE backend for Kodak DC240 Digital Camera
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-dc240</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to the Kodak DC240 camera. THIS IS
EXTREMELY ALPHA CODE! USE AT YOUR OWN RISK!!
</PRE>
<H2>DEVICE NAMES</H2><PRE>
The current version of the backend only allows one camera to be con-
nected. The device name is always "0".
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>dc240.conf</I> specify the serial port and baud rate to
use. The baud rate specifies the maximum rate to use while downloading
pictures. (The camera is always initialized using 9600 baud, then
switches to the higher rate). On a 450MHz Pentium, I usually have no
problems downloading at 115200 baud, though the camera sometimes has to
resend packets due to lost characters. Results are better when the
"interrupt-unmask flag" is set in the IDE driver (hdparm -u1). Sup-
ported baud rates are: 9600, 19200, 38400, 57600, and 115200.
The dumpinquiry line causes some information about the camera to be
printed.
cmdrespause specifies how many usec (1,000,000ths of a) between writing
the command and reading the result should be used. 125000 seems to be
the lowest I could go reliably.
breakpause is the time in 1,000,000ths of a usec between sending the
"back to default" break sending commands.
Empty lines and lines starting with a hash mark (#) are ignored. A
sample configuration file is shown below:
port=/dev/ttyS0
# this is a comment
baud=115200
dumpinquiry
cmdrespause=125000
breakpause=1000000
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/dc240.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-dc240.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-dc240.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the
configuration file is searched in two default directories:
first, the current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
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_DC240</B>
If the library was compiled with debugging support enabled, this
environment variable controls the debug level for this backend.
A value of 128 requests maximally copious debug output; smaller
levels reduce verbosity.
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>
</PRE>
<H2>AUTHOR</H2><PRE>
Peter S. Fales
This backend borrows heavily from the dc210 backend by Brian J. Murrell
which is based somewhat on the dc25 backend by Peter Fales.
The manpage was largeley copied from the dc210 manpage.
</PRE>
<H2>BUGS</H2><PRE>
The major limitation that I know of is that the backend assumes the
directory in the camera is 100dc240. Once the camera has taken more
than 9999 pictures, the directory will increment to 101dc240. Not only
should we check for the additional directory, but pictures may actually
be found in multiple directories.
More general comments, suggestions, and inquiries about frontends or
SANE should go to the SANE Developers mailing list (see
http://www.mostang.com/sane/mail.html for details). You must be sub-
scribed to the list, otherwise your mail won't be sent to the sub-
scribers.
sane-backends 1.0.12-cvs 23 March 2001 <B><A HREF="sane-dc240.5.html">sane-dc240(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>

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

@ -0,0 +1,127 @@
<HTML>
<HEAD>
<TITLE>sane-dc25.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-dc25.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-dc25.5.html">sane-dc25(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-dc25.5.html">sane-dc25(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-dc25 - SANE backend for Kodak DC20/DC25 Digital Cameras
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-dc25</B> library implements a SANE (Scanner Access Now Easy) back-
end that provides access to Kodak DC20 and DC25 cameras. At present,
only the DC25 has been tested, but since the code is based on a DC20
interface program, it is likely to work for that model also.
</PRE>
<H2>DEVICE NAMES</H2><PRE>
The current version of the backend only allows one camera to be con-
nected. The device name is always "0".
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>dc25.conf</I> specify the serial port and baud rate to
use. The baud rate specifies the maximum rate to use while downloading
pictures. (The camera is always initialized using 9600 baud, then
switches to the higher rate). On my 90MHz Pentium, I usually have no
problems downloading at 115200 baud as long as the system is not exces-
sively busy and the "interrupt-unmask flag" is set in the IDE driver
(hdparm -u1). Supported baud rates are: 9600, 19200, 38400, 57600, and
115200.
The dumpinquiry line causes some information about the camera to be
printed to stderr during startup. Note: This is not compatible with
saned, so make sure you don't have any dumpinquiry lines if you are
using saned (i.e. scanning on a remote machine using a network).
Empty lines and lines starting with a hash mark (#) are ignored. A
sample configuration file is shown below:
port=/dev/ttyS0
# this is a comment
baud=115200
dumpinquiry
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/dc25.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-dc25.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-dc25.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_DC25</B>
If the library was compiled with debugging support enabled, this
environment variable controls the debug level for this backend.
A value of 128 requests maximally copious debug output; smaller
levels reduce verbosity.
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>
</PRE>
<H2>AUTHOR</H2><PRE>
Peter Fales, dc25-devel@fales-lorenz.net
</PRE>
<H2>BUGS</H2><PRE>
Known bugs/limitations are:
I haven't figured out how to trigger an option reload following a
"scan." This causes problems when a new picture is snapped for exam-
ple, the slider that is used to select the picture from the camera may
not be updated immediately.
More general comments, suggestions, and inquiries about frontends or
SANE should go to the SANE Developers mailing list (see
http://www.mostang.com/sane/mail.html for details). You must be sub-
scribed to the list, otherwise your mail won't be sent to the sub-
scribers.
sane-backends 1.0.12-cvs 12 April 1999 <B><A HREF="sane-dc25.5.html">sane-dc25(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>

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

@ -0,0 +1,159 @@
<HTML>
<HEAD>
<TITLE>sane-dll.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-dll.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-dll.5.html">sane-dll(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-dll - SANE dynamic backend loader
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-dll</B> library implements a SANE (Scanner Access Now Easy) back-
end that provides access to an arbitrary number of other SANE backends.
These backends may either be pre-loaded at the time the <B>sane-dll</B>
library is built or, on systems that support dynamic loading of shared
libraries, the backends may be loaded at runtime. In the latter case,
adding support for a new backend simply involves installing the rele-
vant library in <I>/usr/local/lib/sane</I> and adding an entry to the <I>dll.conf</I>
configuration file. In other words, no applications need to be modi-
fied or recompiled to add support for new devices.
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form:
<I>backend</I>:<I>device</I>
Where <I>backend</I> is the name of the backend and <I>device</I> is the name of the
device in this backend that should be addressed. If the device name
does not contain a colon (:), then the entire string is treated as the
<I>device</I> string for the default backend. The default backend is the
backend listed last in the configuration file (see below) or the first
pre-loaded backend (if any).
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>dll.conf</I> file is a list of backend names that may
be loaded dynamically upon demand. Empty lines are ignored, also
everything after a hash mark (#). A sample configuration file is shown
below:
net
# this is a comment
pnm
mustek
Note that backends that were pre-loaded when building this library do
not have to be listed in this configuration file. That is, if a back-
end was preloaded, then that backend will always be present, regardless
of whether it's listed in the configuration file or not.
The list of preloaded backends is determined by macro <B>PRELOADABLE_BACK-</B>
<B>ENDS</B> in file backend/Makefile.in of the SANE source code distribution.
After changing the value of this macro, it is necessary to reconfigure,
rebuild, and reinstall SANE for the change to take effect.
Aliases are defined in the config file <I>dll.aliases</I>. It can contain
entries of the form
alias SomeName SaneDeviceName
alias "Some Name" SaneDeviceName
hide SaneDeviceName
For example:
alias Epson net:somehost:epson:/dev/sgX
alias "Siemens ST400" st400:/dev/sgY
hide net:somehost:pnm:0
hide net:somehost:pnm:1
alias "Read from file" pnm:0
hide pnm:1
Aliased device names are automatically hidden.
The idea is that users don't have to deal with complicated device names
(especially for networked devices), and to hide other exported devices
which might confuse them. Note that a hidden device can still be
accessed if the device name is known, it just doesn't appear on the
list.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/dll.aliases</I>
The list of aliased or hidden backends.
<I>/usr/local/etc/sane.d/dll.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-dll.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-dll.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_DLL</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
E.g., a value of 128 requests all debug output to be printed.
Smaller levels reduce verbosity.
Value Description
0 print severe errors only
1 print normal errors and important messages
2 print normal messages
3 print debugging messages
4 print everything
Example:
export SANE_DEBUG_DLL=3
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B>sane-"backendname"</B>(5)
</PRE>
<H2>AUTHOR</H2><PRE>
David Mosberger
sane-backends 1.0.12-cvs 4 Dec 2002 <B><A HREF="sane-dll.5.html">sane-dll(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>

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

@ -0,0 +1,170 @@
<HTML>
<HEAD>
<TITLE>sane-dmc.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-dmc.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-dmc - SANE backend for the Polaroid Digital Microscope Camera
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-dmc</B> library implements a SANE (Scanner Access Now Easy) back-
end that provides access to the Polaroid Digital Microscope Camera.
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form:
<I>special</I>
Where <I>special</I> is the UNIX path-name for the special device that corre-
sponds to the scanner. The special device name must be a generic SCSI
device or a symlink to such a device. Under Linux, such a device name
could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example.
</PRE>
<H2>IMAGING MODES</H2><PRE>
The Polaroid DMC supports a number of imaging modes. This driver sup-
ports five of the imaging modes:
<B>Full</B> <B>Frame</B>
This mode corresponds to the 801-by-600 pixel full-color full-
frame image.
<B>Viewfinder</B>
This mode corresponds to the 270-by-201 pixel grey-scale
viewfinder image. This image is acquired very quickly.
<B>Raw</B> This mode corresponds to the 1599-by-600 pixel "raw" image from
the CCD. It is grey-scale, with pixels alternating horizontally
between red, green and blue stripes. The pixels are twice as
high as they are wide, so the image is distorted.
<B>Thumbnail</B>
This mode corresponds to the 80-by-60 pixel full-color thumbnail
image.
<B>Super</B> <B>Resolution</B>
This image is a 1599-by-1200 pixel full-color image constructed
by filtering and interpolating the "raw" image. The filtering
and interpolation is done in software, so this mode is very
slow. Also, this mode places restrictions on how the image is
read which means that the "preview" mode of xscanimage does not
work in Super Resolution mode. (xcam and the non-preview modes
of scanimage and xscanimage work fine, however.)
</PRE>
<H2>OTHER SETTINGS</H2><PRE>
<B>ASA</B> <B>Setting</B>
This setting adjusts the camera's sensitivity. You can choose
one of 25, 50, or 100 "equivalent" ASA.
<B>Shutter</B> <B>Speed</B>
You can select a shutter speed from 8 to 1000 milliseconds. The
shutter speed is quantized in units of 32 microseconds.
<B>White</B> <B>Balance</B>
You can choose one of "Daylight", "Incandescent" or "Fluores-
cent" white balances. This setting more-or-less corresponds to
the "Color Temperature" settings on Polaroid's Windows and Mac
software.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>dmc.conf</I> file is a list of device names that corre-
spond to DMC scanners. Empty lines and lines starting with a hash mark
(#) are ignored. A sample configuration file is shown below:
/dev/scanner
# this is a comment
/dev/sge
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/dmc.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-dmc.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-dmc.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_DMC</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>BUGS</H2><PRE>
In the "Full Frame" and "Raw" modes, images must be read in units of
entire lines. The driver performs no buffering in these modes; if you
ask sane_read to read a non-integral number of lines, it may read less
than you ask for. If you ask sane_read to read less than a single
line, it returns SANE_STATUS_INVAL.
In the "Super Resolution" mode, images must be read in units of <I>two</I>
lines (3198 pixels or 9594 bytes.) If you try to read less than two
lines, you get SANE_STATUS_INVAL. The Super Resolution mode is very
slow.
In the "Viewfinder" and "Thumbnail" modes, the entire image must be
read in one SCSI transfer. In this case, the driver performs buffering
and you can read the image in as small an increment as you like.
</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>
</PRE>
<H2>AUTHOR</H2><PRE>
David F. Skoll
The backend is derived from <B>sane-hp</B> by David Mosberger
sane-backends 1.0.12-cvs 13 May 1998 <B><A HREF="sane-dmc.5.html">sane-dmc(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>

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

@ -0,0 +1,295 @@
<HTML>
<HEAD>
<TITLE>sane-epson.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-epson.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-epson.5.html">sane-epson(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-epson.5.html">sane-epson(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-epson - SANE backend for EPSON scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-epson</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to Epson flatbed scanners. Some functions
of this backend should be considered <B>beta-quality</B> software! Most func-
tions have been stable for a long time, but of course new development
can not and often times will not function properly from the very first
day. Please report any strange behavior to the maintainer of the back-
end.
At present, the following scanners are known to work with this backend:
Model: Connection Type
--------------------------- -------------------
GT-5000 parallel
GT-6000 parallel
ActionScanner II parallel
GT-7000 SCSI
Perfection 636 SCSI
Perfection 636U USB
Perfection 610 USB
Perfection 640 USB
Perfection 1200S SCSI
Perfection 1200U USB
Perfection 1240 USB, SCSI
Perfection 1640 USB, SCSI
Perfection 1650 USB
Perfection 1660 USB
Perfection 2400 USB
Perfection 2450 USB, IEEE-1394
Expression 636 / GT-9500 SCSI
Expression 1600 USB, SCSI, IEEE-1394
Expression 1680 USB, SCSI, IEEE-1394
CX-3200 USB
CX-5200 USB
For other scanners the software may or may not work. Please send mail
to the backend author (khk@khk.net) to report success with scanners not
on the list or problems with scanners that are listed.
</PRE>
<H2>OPTIONS</H2><PRE>
The options the backend supports can either be selected through command
line options to programs like scanimage or through GUI elements in pro-
grams like xscanimage or xsane.
Valid command line options and their syntax can be listed by using
scanimage --help -d epson
Not all devices support all options.
<I>Scan</I> <I>Mode</I>
The <I>--mode</I> switch selects the basic mode of operation of the
scanner. Valid choices are Binary, Gray and Color. The Binary
mode is black and white only, Gray will produce 256 levels of
gray or more depending on the scanner and Color means 24 bit
color mode or more depending on the scanner. Some scanners will
internally use 36 bit color, their external interface however
may only support 24 bits.
The <I>--depth</I> option selects the bit depth the scanner is using.
This option is only available for scanners that support more
than one bit depth. Older scanners will always transfer the
image in 8bit mode. Newer scanners allow to select either 8
bits, 12 or 14 bits per color channel. For a color scan this
means an effective color depth of 36 or 42 bits over all three
channels. The valid choices depend on the scanner model.
The <I>--halftoning</I> switch selects the mode that is used in Binary
mode. Valid options are "None", "Halftone A (Hard Tone)",
"Halftone B (Soft Tone)", "Halftone C (Net Screen)", "Dither A
(4x4 Bayer)", "Dither B (4x4 Spiral)", "Dither C (4x4 Net
Screen)", "Dither D (8x4 Net Screen)", "Text Enhanced Technol-
ogy", "Download pattern A", and "Download pattern B".
The <I>--dropout</I> switch selects the so called dropout color. Vald
options are None, Red, Green and Blue. The default is None. The
dropout color is used for monochrome scanning and selects the
color that is not scanned. This can be used to e.g. scan an
original with a colored background.
The <I>--brightness</I> switch controls the brightness of the scan.
Valid options are integer values from -3 to 3. The default is 0.
The larger the brightness value, the brighter the image gets. If
a user defined table for the gamma correction is selected, the
brightness parameter is not available.
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".
The <I>--gamma-correction</I> switch controls the scanner's internal
gamma correction. Valid options are "Default", "User defined",
"High density printing" "Low density printing" and "High con-
trast printing".
The <I>--color-correction</I> switch controls the scanner's internal
color correction function. Valid options are "No Correction",
"Impact-dot printers", "Thermal printers", "Ink-jet printers"
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
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.
Valid options are "yes" and "no". The default is "no".
The <I>--speed</I> option can improve the scan speed in monochrome
mode. Valid options are "yes" or "no", the "yes" option will
speed up the scan if this option is supported.
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.
Valid options are "yes" and "no". The default is "yes".
The <I>--gamma-table</I> parameter can be used to download a user
defined gamma table. The option takes 256 values from the range
0-255. In color mode this option equally affects the red, green,
and blue channel.
The <I>--red-gamma-table</I> parameter can be used to download a user
defined gamma table for the red channel. The valid options are
the same as for --gamma-table.
The <I>--green-gamma-table</I> parameter can be used to download a user
defined gamma table for the green channel. The valid options are
the same as for --gamma-table.
The <I>--blue-gamma-table</I> parameter can be used to download a user
defined gamma table for the blue channel. The valid options are
the same as for --gamma-table.
The color correction coefficients <I>--cct-1</I> <I>--cct-2</I> <I>--cct-3</I> <I>...</I>
<I>--cct-9</I> will install color correction coefficients for the user
defined color correction. Values are specified as integers in
the range -127..127.
The <I>--preview</I> option requests a preview scan. The frontend soft-
ware automatically selects a low resolution. Valid options are
"yes" and "no". The default is "no".
The <I>--preview-speed</I> options will increase the scan speed if this
is supported by the scanner. Valid options are "yes" and "no",
the default is "no".
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.
The <I>--quick-format</I> option lets the user select a scan area with
predefined sizes. Valid parameters are "CD", "A5 portrait", "A5
landscape", "Letter", "A4" and "max". The default is "max",
which selects the largest possible area.
The <I>--source</I> option selects the scan source. Valid options
depend on the installed options. The default is "Flatbed".
The <I>--auto-eject</I> option will eject a page after scanning from
the document feeder.
The <I>--film-type</I> option will select the film type for scans with
the transparency unit. This option is only activated if the TPU
is selected as scan source. Valid options are "Negative Film"
and "Positive Film".
The <I>--focus-position</I> option selects the focus position for all
scans. Valid options are "Focus 2.5mm above glass" and "Focus on
glass". The focus on the 2.5mm point above the glass is neces-
sary for scans with the transparency unit, so that the scanner
can focus on the film if one of the film holders is used. This
option is only functional for selected scanners, all other scan-
ners will ignore this option.
</PRE>
<H2>CONFIGURATION FILE</H2><PRE>
The configuration file /usr/local/etc/sane.d/epson.conf specifies the
device(s) that the backend will use. Possible connection types are:
<I>SCSI</I> This is the default, and if nothing else is specified the back-
end software will open a given path as SCSI device. More infor-
mation about valid syntax for SCSI devices can be found in sane-
<B><A HREF="scsi.5.html">scsi(5)</A></B>.
<I>PIO</I> <I>-</I> <I>Parallel</I> <I>Interface</I>
The parallel interface can be configured in two ways: An integer
value starting at the beginning of a line will be interpreted as
the IO address of the parallel port. To make it clearer that a
configured IO address is a parallel port the port address can be
preceded by the string "PIO". The PIO connection does not use a
special device file in the /dev directory. The IO address can be
specified in hex mode (prefixed with "0x").
<I>USB</I> A device file that is preceded by the string "USB" is treated as
a scanner connected via the Universal Serial Bus. The correct
special device file has to be created prior to using it with
Sane. See the USB documentation for more information about how
to set up the USB subsystem and the required device files.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/lib/sane/libsane-epson.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-epson.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_EPSON</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
E.g., a value of 128 requests all debug output to be printed.
Smaller levels reduce verbosity.
<B>SANE_EPSON_CMD_LVL</B>
This allows to override the function or command level that the
backend uses to communicate with the scanner. The function level
a scanner supports is determined during the initialization of
the device. If the backend does not recognize the function level
reported by the scanner it will default to function level B5.
Valid function levels are A1, A2, B1, B2, B3, B4, B5, B6, B7,
B8, D1 and F5. Use this feature only if you know what you are
doing!
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, <B><A HREF="xsane.1.html">xsane(1)</A></B>
</PRE>
<H2>BUGS</H2><PRE>
None :-) At least none are currently known.
</PRE>
<H2>UNSUPPORTED DEVICES</H2><PRE>
The backend may be used with Epson scanners that are not yet listed
under the list of supported devices. A scanner that is not recognized
may default to the function level B3, which means that not all func-
tions that the scanner may be capable of are accessible.
If the scanner is not even recognized as an Epson scanner this is prob-
ably because the device name reported by the scanner is not in the cor-
rect format. Please send this information to the backend maintainer
(email address is in the AUTHOR section of this man page or in the
AUTHORS file of the SANE distribution).
The Perfection 600, Perfection 650, Perfection 660, Perfection 1250 and
Perfection 1260 are not supported by this backend.
</PRE>
<H2>AUTHOR</H2><PRE>
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.12-cvs 27-Dec-2000 <B><A HREF="sane-epson.5.html">sane-epson(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>

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

@ -0,0 +1,117 @@
<HTML>
<HEAD>
<TITLE>sane-find-scanner.1</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-find-scanner.1</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-find-scanner - find SCSI and USB scanners and their device files
</PRE>
<H2>SYNOPSIS</H2><PRE>
<B>sane-find-scanner</B> [<B>-h</B>|<B>-?</B>] [<B>-v</B>] [<B>-q</B>] [<B>-f</B>] [<I>devname</I>]
</PRE>
<H2>DESCRIPTION</H2><PRE>
<B>sane-find-scanner</B> is a command-line tool to find SCSI and USB scanners
and determine their Unix device files. Its primary aim is to make sure
that scanners can be detected by SANE backends.
For <B>SCSI</B> scanners, it checks the default generic SCSI device files
(e.g., <I>/dev/sg0</I>) and <I>/dev/scanner</I>. The test is done by sending a SCSI
inquiry command and looking for a device type of "scanner" or "proces-
sor" (some old HP scanners seem to send "processor"). So <B>sane-find-</B>
<B>scanner</B> will find any SCSI scanner connected to those default device
files even if it isn't supported by any SANE backend.
For <B>USB</B> scanners, first the USB kernel scanner device files (e.g.
<I>/dev/usb/scanner0</I>), <I>/dev/usb/scanner</I>, and <I>/dev/usbscanner</I>) are tested.
The files are opened and the vendor and device ids are determined, if
the operating system supports this feature. Currently USB scanners are
only found this way if they are supported by the Linux scanner module
or the FreeBSD or OpenBSD uscanner driver. After that test, <B>sane-find-</B>
<B>scanner</B> tries to scan for USB devices found by the USB library libusb
(if available). There is no special USB class for scanners, so the
heuristics used to distinguish scanners from other USB devices is not
perfect. <B>sane-find-scanner</B> also tries to find out the type of USB chip
used in the scanner. If detected, it will be printed after the vendor
and product ids. <B>sane-find-scanner</B> will even find USB scanners, that
are not supported by any SANE backend.
<B>sane-find-scanner</B> won't find parallel port scanners, or scanners con-
nected to proprietary ports.
</PRE>
<H2>OPTIONS</H2><PRE>
<B>-h,</B> <B>-?</B> Prints a short usage message.
<B>-v</B> Verbose output. If used once, <B>sane-find-scanner</B> shows every
device name and the test result. If used twice, SCSI inquiry
information and the USB device descriptors are also printed.
<B>-q</B> Be quiet. Print only the devices, no comments.
<B>-f</B> Force opening all explicitely given devices as SCSI and USB
devices. That's useful if <B>sane-find-scanner</B> is wrong in
determing the device type.
<B>devname</B> Test device file "devname". No other devices are checked if
devname is given.
</PRE>
<H2>EXAMPLE</H2><PRE>
<B>sane-find-scanner</B> <B>-v</B>
Check all SCSI and USB devices for available scanners and print a line
for every device file.
<B>sane-find-scanner</B> <B>/dev/scanner</B>
Look for a (SCSI) scanner only at /dev/scanner and print the result.
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>,
<B><A HREF="xsane.1.html">xsane(1)</A></B>, <B>sane-"backendname"</B>(5)
</PRE>
<H2>AUTHOR</H2><PRE>
Oliver Rauch, Henning Meier-Geinitz and others
</PRE>
<H2>SUPPORTED PLATFORMS</H2><PRE>
USB support is limited to Linux (kernel, libusb), FreeBSD (kernel,
libusb), NetBSD (libusb), OpenBSD (kernel, libusb). Detecting the ven-
dor and device ids only works with Linux or libusb.
SCSI support is available on Irix, EMX, Linux, Next, AIX, Solaris,
FreeBSD, NetBSD, OpenBSD, and HP-UX.
</PRE>
<H2>BUGS</H2><PRE>
No support for parallel port scanners yet.
Detection of USB chipsets is limited to GrandTech 6801 and 6816, Mustek
chips and National Semiconductor lm983x chips.
sane-backends 1.0.12-cvs 18 Jul 2003 <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</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>

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

@ -0,0 +1,168 @@
<HTML>
<HEAD>
<TITLE>sane-fujitsu.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-fujitsu.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-fujitsu - SANE backend for Fujitsu flatbed and ADF scanners
</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:
Vendor: Model: Rev:
-------- ---------------- -----
FUJITSU M3096Gm 02
FUJITSU M3093GX
FUJITSU M3093GD
FUJITSU M4097
FUJITSU fi-4220C
FUJITSU fi-4340C
FUJITSU M3091DCd BF21
FUJITSU M3092DCd
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.
</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.
</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:
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
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.
brightness b
Only supported for M3096
treshold t
Only supported for M3096
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).
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.
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.
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.
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".
</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
</PRE>
<H2>AUTHOR</H2><PRE>
3096/SP15 drivers: Randolph Bentson &lt;bentson@holmsjoen.com&gt;, with
credit to the unnamed author of the coolscan driver
3091 driver: Frederik Ramm &lt;frederik@remote.org&gt; 3093GD,fi-4340C, ipc
and cmp options: Oliver Schirrmeister &lt;oschirr@abm.de&gt; 3092 patch:
Mario Goppold &lt;mgoppold@tbzpariv.tcc-chemnitz.de&gt; fi-4220C patch and
USB support: Ronald B. Cemer &lt;ron@roncemer.com&gt;
</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.12-cvs 17 Apr 2002 <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(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>

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

@ -0,0 +1,142 @@
<HTML>
<HEAD>
<TITLE>sane-gphoto2.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-gphoto2.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-gphoto2 - SANE backend for gphoto2 supported cameras
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-gphoto2</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to the digital cameras supported by
gphoto2. This backend has only been tested with a handful of cameras
so far. Patches to support other models are welcome.
Because of the limited testing of this backend, it is commented out in
/usr/local/etc/sane.d/dll.conf by default. Either the comment charac-
ter must be removed or the backend must be called explicitly. E.g.
`scanimage -d gphoto2' or `xscanimage gphoto2'.
</PRE>
<H2>DEVICE NAMES</H2><PRE>
The current version of the backend only allows one camera to be con-
nected. The device name is always "0".
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>gphoto2.conf</I> specify the characteristics of the
camera to be used. Resolutions (high resolution, low resolution, and
thumbnail size) are required since they are needed by the sane fron-
tends, but can't be obtained through the gphoto2 interface. Valid
ports and cameras can be obtained by "gphoto2 --list-cameras" and
"gphoto2 --list-ports".
The dumpinquiry line causes some information about the camera to be
printed.
Empty lines and lines starting with a hash mark (#) are ignored. A
sample configuration file is shown below:
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
read "topfolder=/DCIM"
Some cameras don't implement a file structure and store all pictures in
the "/" directory. This is indicated by setting "subdirs=0" with "top-
folder=/"
port=usb:
camera=Kodak DC240
# this is a comment
high_resolution=1280x960
low_resolution=640x480
thumb_resolution=160x120
dumpinquiry
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/gphoto2.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-gphoto2.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-gphoto2.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_GPHOTO2</B>
If the library was compiled with debugging support enabled, this
environment variable controls the debug level for this backend.
A value of 128 requests maximally copious debug output; smaller
levels reduce verbosity.
<B>GP_DEBUG</B>
Set to 1, 2, or 3, to enable various levels of debugging within
the gphoto2 libraries.
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>
</PRE>
<H2>AUTHOR</H2><PRE>
Peter S. Fales
The manpage was largeley copied from the dc210 manpage.
</PRE>
<H2>BUGS</H2><PRE>
Many, no doubt.
More general comments, suggestions, and inquiries about frontends or
SANE should go to the SANE Developers mailing list (see
http://www.mostang.com/sane/mail.html for details). You must be sub-
scribed to the list, otherwise your mail won't be sent to the sub-
scribers.
sane-backends 1.0.12-cvs 04 September 2001 <B><A HREF="sane-gphoto2.5.html">sane-gphoto2(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>

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

@ -0,0 +1,238 @@
<HTML>
<HEAD>
<TITLE>sane-gt68xx.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-gt68xx.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-gt68xx - SANE backend for GT-68XX based USB flatbed scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-gt68xx</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to USB flatbed scanners based on the
Grandtech GT-6801 and GT-6816 chips. At present, the following scan-
ners are known to work with this backend:
Artec Ultima 2000 (only product 0x4002)
Artec Ultima 2000 e+
Boeder SmartScan Slim Edition
Fujitsu 1200CUS
Genius Colorpage Vivid3x
Genius Colorpage Vivid3xe
Lexmark X70
Lexmark X73
Medion/Lifetec/Tevion MD 4395
Medion/Lifetec/Tevion/Cytron MD/LT 9385
Medion/Lifetec/Tevion LT 9452
Medion/Lifetec/Tevion MD 9458
Mustek BearPaw 1200 CS
Mustek BearPaw 1200 CU (Plus)
Mustek BearPaw 1200 TA
Mustek BearPaw 2400 CS (Plus)
Mustek BearPaw 2400 CU (Plus)
Mustek BearPaw 2400 TA (Plus)
Mustek ScanExpress A3 USB
Mustek ScanExpress 1200 UB Plus
Mustek ScanExpress 2400 USB
Mustek ScanMagic 1200 UB Plus
Packard Bell Diamond 1200 (Plus)
Plustek OpticPro 1248U
RevScan 19200i
Trust Compact Scan USB 19200
Trust Flat Scan USB 19200
More details can be found on the gt68xx backend homepage
<I>http://www.meier-geinitz.de/sane/gt68xx/</I>.
The Artec E+ 48U and its clones are supported by the artec_eplus48u
backend, see <B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B> for details.
This is BETA software. Especially if you test new or untested scanners,
keep your hand at the scanner's plug and unplug it, if the head bumps
at the end of the scan area.
If you own a scanner other than the ones listed above that works with
this backend, please let me know this by sending the scanner's exact
model name and the USB vendor and device ids (e.g. from
<I>/proc/bus/usb/devices</I>, <I>sane-find-scanner</I> 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 looks at
<B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>.
The scanners based on the GT-6816 (Mustek BearPaw TA and BearPaw Plus
models, the Packard Bell and the Lexmark scanner) need a Linux kernel
2.4.12 or newer. Recent 2.2 kernels may also work, but I haven't
tested them. Older kernels or other operating systems won't work. Use
libusb instead.
The scanners based on the GT-6801 (all other scanners) need Linux ker-
nel 2.4.21 or newer. Older kernels will not work.
</PRE>
<H2>FIRMWARE FILE</H2><PRE>
You need a firmware file for your scanner. That's a small file contain-
ing software that will be uploaded to the scanner's memory. It's usu-
ally named *.usb, e.g. <I>PS1fw.usb</I>. It comes on the installation CD
that was provided by the manufacturer, but it may be packaged together
with the installation program in an .exe file. For Mustek scanners, the
file can be dowloaded from the gt68xx backend homepage. For other scan-
ners, check the CD for .usb files. If everything else fails, you must
install the Windows driver and get the firmware from there (usually in
the <I>windows/system</I> or <I>system32</I> directories). Put that firmware file
into <I>/usr/local/share/sane/gt68xx/</I>.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>gt68xx.conf</I> file is a list of usb lines containing
vendor and product ids that correspond to USB scanners. The file can
also contain option lines. Empty lines and lines starting with a hash
mark (#) are ignored. The scanners are autodetected by <B>usb</B> <B>vendor_id</B>
<B>product_id</B> statements which are already included into <I>gt68xx.conf</I>.
"vendor_id" and "product_id" are hexadecimal numbers that identfy the
scanner.
The <B>override</B>, <B>firmware</B>, <B>vendor</B>, <B>model</B>, and <B>afe</B> options must be placed
after the <B>usb</B> line they refer to.
Option <B>override</B> is used to override the default model parameters.
That's necessary for some scanners that use the same vendor/product ids
but are different. For these scanners there are already commented out
override lines in the configuration file. <B>override</B> <B>mustek-scanex-</B>
<B>press-1200-ub-plus</B> is necessary for the Mustek Scanexpress 1200 UB
Plus, the Medion/Lifetec/Tevion LT 9452, and the Trust Compact Scan USB
19200. <B>override</B> <B>artec-ultima-2000</B> is used for the Artec Ultima 2000,
the Boeder SmartScan Slim Edition, the Medion/ Lifetec/ Tevion/ Cytron
MD/LT 9385, the Medion/ Lifetec/ Tevion MD 9458, and the Trust Flat
Scan USB 19200. <B>override</B> <B>mustek-bearpaw-2400-cu</B> is necessary for the
Mustek BearPaw 2400 CU and the Fujitsu 1200CUS. The <B>override</B> option
must be the first one after the <B>usb</B> line.
Option <B>firmware</B> selects the name and path of the firmware file. It's
only necessary if the default (or override) doesn't work. The default
firmware directory is <I>/usr/local/share/sane/gt68xx/</I>. You may need to
create this directory. If you want to place the firmware files at a
different path, use a <B>firmware</B> line.
The <B>vendor</B> and <B>model</B> options are not absolutely necessary but for con-
venience. Quite a lot of scanners from different manufacturers share
the same vendor/product ids so you can set the "correct" name here.
The <B>afe</B> option allows to set custom offset and gain values for the Ana-
log FrontEnd of the scanner. This option can be either used to select
the AFE values if automatic coarse calibration is disabled, or to make
automatic coarse calibration faster. For the latter usage, enable debug
level 3 (see below), scan an image and look for debug line string with
"afe". Copy this line to <I>gt68xx.conf</I>. The option has six parameters:
res offset, red gain, green offset, green gain, blue offset, and blue
gain.
A sample configuration file is shown below:
usb 0x05d8 0x4002
override "mustek-scanexpress-1200-ub-plus"
firmware "/opt/gt68xx/SBfw.usb"
vendor "Trust"
model "Compact Scan USB 19200"
afe 0x20 0x02 0x22 0x03 0x1f 0x04
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/gt68xx.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-gt68xx.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-gt68xx.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_GT68XX</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_GT68XX=4
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B> <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>,
<B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>, <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>
<I>/usr/local/doc/sane-1.0.12-cvs/gt68xx/gt68xx.CHANGES</I>
<I>http://www.meier-geinitz.de/sane/gt68xx</I>
</PRE>
<H2>AUTHOR</H2><PRE>
Henning Meier-Geinitz &lt;henning@meier-geinitz.de&gt;
The original gt68xx driver was written by Sergey Vlasov, Andreas
Nowack, and David Stevenson. Thanks for sending patches and answering
questions to them and all the other contributors.
</PRE>
<H2>BUGS</H2><PRE>
Currently scanning seems to only work reliably under Linux. With
FreeBSD, NetBSD and OpenBSD scanning works only once. Then the scanner
isn't detected anymore and has to be replugged.
The first few lines of the image are garbage for the 2400 TA Plus.
Interpolation should be used instead of just copying data, when the X-
and Y-resolution differ.
Support for buttons is missing.
More detailed bug information is available at the gt68xx backend home-
page <I>http://www.meier-geinitz.de/sane/gt68xx</I>. Please contact me if you
find a bug or missing feature: &lt;henning@meier-geinitz.de&gt;. Please send
a debug log if your scanner isn't detected correctly (see
SANE_DEBUG_GT68XX above).
sane-backends 1.0.12-cvs 22 Jul 2003 <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(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>

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

@ -0,0 +1,244 @@
<HTML>
<HEAD>
<TITLE>sane-hp.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-hp.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-hp.5.html">sane-hp(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-hp.5.html">sane-hp(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-hp - SANE backend for HP ScanJet scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-hp</B> library implements a SANE (Scanner Access Now Easy) backend
that provides access to HP ScanJet scanners which support SCL (Scanner
Control Language by HP). The following scanners are known positively
to work with this backend:
Model: Product id: Interface:
---------- ----------- ----------
ScanJet Plus C9195A HP Parallel Interface Card
ScanJet IIc C1750A 3226 SCSI
ScanJet IIcx C2500A 3332 SCSI
ScanJet IIp C1790A SCSI
ScanJet 3C C2520A 3503 SCSI
ScanJet 3P C2570A 3406 SCSI
ScanJet 4C C2520A SCSI
ScanJet 4P C1130A 3540 SCSI
ScanJet 4100C C6290A USB
ScanJet 5P C5110A SCSI
ScanJet 5100C C5190A parallel port
ScanJet 5200C C7190A 3846 parallel port/USB
ScanJet 6100C C2520A 3644 SCSI
ScanJet 6200C C6270A 3828 SCSI/USB
ScanJet 6250C C6270A 3828 SCSI/USB
ScanJet 6300C C7670A SCSI/USB
ScanJet 6350C C7670A SCSI/USB
ScanJet 6390C C7670A SCSI/USB
PhotoSmart C5100A R029,R030,R032 SCSI
Support for models 5100C/5200C connected to the parallel port requires
the ppSCSI driver available at <I>http://www.torque.net/par-</I>
<I>port/ppscsi.html</I> (under development)
Support for models 5200C/62X0C/63X0C connected to the USB require the
kernel scanner driver or libusb. See <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B> for more details.
The "hp" backend no longer supports OfficeJet multi-function peripher-
als. For these devices use the external "hpoj" backend in version 0.90
and later of the "HP OfficeJet Linux driver", available at
<I>http://hpoj.sourceforge.net</I>
Because Hewlett-Packard does no longer produce scanners that support
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.mostang.com/sane</I>.
You can also watch the sane-devel mailinglist at
<I>http://www.mostang.com/sane/mail.html</I>.
More details about the hp backend can be found on its homepage
<I>http://www.kirchgessner.net/sane.html</I>.
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form:
<I>special</I>
Where <I>special</I> is the UNIX path-name for the special device that corre-
sponds to the scanner. For SCSI scanners the special device name must
be a generic SCSI device or a symlink to such a device. Under Linux,
such a device name could be <I>/dev/sga</I> or <I>/dev/sg2</I>, for example. If the
special device name contains "usb", "uscanner" or "ugen", it is assumed
that the scanner is connected by USB. For the HP ScanJet Plus the spe-
cial device name must be the device that corresponds to the parallel
interface card that was shipped with the scanner. That is <I>/dev/hpscan</I>.
A special driver is required for this card. See ftp://rvs.ctrl-
c.liu.se/pub/wingel/hpscan for details. If the link does not work, try
ftp://sunsite.unc.edu/pub/Linux/kernel/patches/scanners.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>hp.conf</I> file is a list of options and device names
that correspond to HP ScanJet scanners. Empty lines and lines starting
with a hash mark (#) are ignored. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> and <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B> on
details of what constitutes a valid device name.
Options specified in front of the first line that contains a device
name are defaults for all devices. Options specified below a line that
contains a device name apply just to the most recently mentioned
device.
Supported options are <B>connect-scsi</B>, <B>connect-device</B>, <B>enable-image-</B>
<B>buffering</B>, and <B>dumb-read</B>.
Option <B>connect-scsi</B> specifies that the scanner is connected to the sys-
tem by SCSI. Input/output is performed using SCSI-commands. This is
the default. But if your SCSI device name contains "usb", "uscanner"
or "ugen", option connect-scsi must be specified. Otherwise it is
assumed that the scanner is connected by USB.
Option <B>connect-device</B> specifies that the scanner is connected to the
system by a special device. Input/output is performed by
read()/write()-operations on the device. This option must be used for
HP ScanJet Plus or scanners connected to USB which are accessed through
a named device (e.g. /dev/usb/scanner0). For device names that contain
"usb", "uscanner" or "ugen", it is not necessary to specify option con-
nect-device.
Option <B>enable-image-buffering</B> stores the scanned image in memory before
passing it to the frontend. Could be used in case of forward/backward
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
devices which are working correctly. Otherwise startup of frontends
and changing parameters might be slower.
A sample configuration file is shown below:
/dev/scanner
# this is a comment
/dev/hpscan
option connect-device
/dev/scanner is typically a symlink to the actual SCSI scanner device.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/hp.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-hp.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-hp.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
<I>$HOME/.sane/calib-hp:&lt;device&gt;.dat</I>
Calibration data for HP PhotoSmart PhotoScanner that is
retrieved from the scanner after calibration. The data is
uploaded to the scanner at start of the backend if it is in
media mode 'print media' or if the media mode is changed to
'print media'.
</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_HP</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>BUGS</H2><PRE>
<B>HP</B> <B>PhotoSmart</B> <B>PhotoScanner</B>
In media mode 'slide' and 'negative', scan resolutions are
rounded to multiple of 300 dpi. The scanner does not scale the
data correctly on other resolutions. Some newer models (firmware
code R030 and later) do not support adjustment of con-
trast/intensity level and tone map. The backend will simulate
this by software, but only for gray and 24 bit color.
<B>Automatic</B> <B>Document</B> <B>Feeder</B> <B>(ADF)</B>
For use of the ADF with <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, first place paper in the
ADF and then change option scan source to 'ADF'. Press 'change
document' to load a sheet. Then press 'scan' to start a scan.
Maybe it is sufficient to press 'scan' without 'change document'
for repeated scans. The use of the preview window is not recom-
mended when working with the ADF. Setting a window to scan from
ADF is not supported with <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>. Try <B><A HREF="xsane.1.html">xsane(1)</A></B>.
<B>Immediate</B> <B>actions</B>
Some actions in <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B> (i.e. unload, select media, cali-
brate) have an immediate effect on the scanner without starting
a scan. These options can not be used with scanimage.
</PRE>
<H2>TODO</H2><PRE>
<B>HP</B> <B>PhotoSmart</B> <B>PhotoScanner</B>
PhotoScanners with firmware release R030 and up have no firmware
support for contrast/brightness/gamma table. In the current
backend this is simulated by software on 24 bits data. Simula-
tion on 30 bits should give better results.
<B>Data</B> <B>widths</B> <B>greater</B> <B>than</B> <B>8</B> <B>bits</B>
Custom gamma table does not work.
<B>Parallel</B> <B>scanner</B> <B>support</B>
Beside the ScanJet Plus which came with its own parallel inter-
face card, currently only the HP ScanJet 5100C/5200C are
supported. These scanners are using an internal parallel-to-
SCSI converter which is supported by the ppSCSI-driver (see
above).
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>
</PRE>
<H2>AUTHOR</H2><PRE>
The sane-hp backend was written by Geoffrey T. Dairiki. HP PhotoSmart
PhotoScanner support by Peter Kirchgessner.
sane-backends 1.0.12-cvs 06 Dec 2002 <B><A HREF="sane-hp.5.html">sane-hp(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>

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

@ -0,0 +1,121 @@
<HTML>
<HEAD>
<TITLE>sane-hp5400.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-hp5400.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-hp5400.5.html">sane-hp5400(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-hp5400.5.html">sane-hp5400(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-hp5400 - SANE backend for Hewlett-Packard 54XX scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-hp5400</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to the following Hewlett-Packard USB
flatbed scanners:
ScanJet 5400C
ScanJet 5470C
ScanJet 5490C
More details can be found on the hp5400 backend homepage
<I>http://hp5400backend.sourceforge.net/</I>.
This is ALPHA software. Keep your hand at the scanner's plug and unplug
it, if the head bumps at the end of the scan area. See also the BUGS
section.
If you own a scanner other than the ones listed above that works with
this backend, please let us know this by sending the scanner's exact
model name and the USB vendor and device ids (e.g. from
<I>/proc/bus/usb/devices</I>, <I>sane-find-scanner</I> or syslog) to us. Even if the
scanner's name is only slightly different from the models mentioned
above, please let us know.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>hp5400.conf</I> file is a list of usb lines containing
vendor and product ids that correspond to USB scanners. The file can
also contain the names of device files that correspond to an HP 54XX
scanner. Empty lines and lines starting with a hash mark (#) are
ignored. The scanners are autodetected by <B>usb</B> <B>vendor_id</B> <B>product_id</B>
statements which are already included into <I>hp5400.conf</I>. "vendor_id"
and "product_id" are hexadecimal numbers that identify the scanner. If
autodetection does not work, add the device name of your scanner to the
configuration file, e.g. <I>/dev/usb/scanner0</I>.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/hp5400.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-hp5400.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-hp5400.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_HP5400</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_HP5400=4
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>,
<I>http://hp5400backend.sourceforge.net/</I>
</PRE>
<H2>AUTHOR</H2><PRE>
Martijn van Oosterhout &lt;kleptog@svana.org&gt;, Thomas Soumarmon
&lt;soumarmt@nerim.net&gt;. Manpage by Henning Meier-Geinitz &lt;henning@meier-
geinitz.de&gt;.
</PRE>
<H2>BUGS</H2><PRE>
Scanning is only tested with Linux/ix86/gcc. Be careful when testing on
other operating systems and especially on big-endian platforms. The
scanner may get wrong data.
sane-backends 1.0.12-cvs 17 Apr 2003 <B><A HREF="sane-hp5400.5.html">sane-hp5400(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>

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

@ -0,0 +1,122 @@
<HTML>
<HEAD>
<TITLE>sane-hpsj5s.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-hpsj5s.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-hpsj5s.5.html">sane-hpsj5s(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-hpsj5s.5.html">sane-hpsj5s(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-hpsj5s - SANE backend for HP ScanJet 5S sheetfed 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.
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.
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
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.
Current version implements only gray scale scaning. True Color and B/W
modes are not supported for now.
That said, TESTERS ARE WELCOME. Send your bug reports and comments to
Max Vorobiev &lt;pcwizard@yandex.ru&gt;.
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form:
<I>special</I>
Where <I>special</I> is the parallel port name in form, libieee1284 expects.
It seems to be system dependent. Under Linux it's parport0, parport1,
etc.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>hpsj5s.conf</I> file is a list of parport names that
correspond to HP ScanJet 5S scanners. Empty lines and lines starting
with a hash mark (#) are ignored. Only one device name can be listed
in <I>hpsj5s.conf</I> for this moment. Future versions will support daisy
chain selection.
</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.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/hpsj5s.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-hpsj5s.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-hpsj5s.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SEE</B> <B>ALSO</B>
<B><A HREF="sane.7.html">sane(7)</A></B>
http://hpsj5s.sourceforge.net
http://cyberelk.net/tim/libieee1284
</PRE>
<H2>AUTHOR</H2><PRE>
Max Vorobiev
Man page mostly based on canon.man
sane-backends 1.0.12-cvs 24 Feb 2002 <B><A HREF="sane-hpsj5s.5.html">sane-hpsj5s(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
man/sane-ibm.5.html 100644
Wyświetl plik

@ -0,0 +1,105 @@
<HTML>
<HEAD>
<TITLE>sane-ibm.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-ibm.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-ibm.5.html">sane-ibm(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-ibm.5.html">sane-ibm(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-ibm - SANE backend for IBM and Ricoh SCSI flatbed scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-ibm</B> library implements a SANE (Scanner Access Now Easy) back-
end that provides access to the IBM 2456 and the Ricoh IS-410, IS-420,
and IS-430 flatbed scanners. Support for the IS-410 and IS-430 is
untested. Please contact the maintainer or the sane-devel mailing list
if you own such a scanner.
This backend is alpha-quality. It may have bugs and some scanners
haven't been tested at all. Be careful and pull the plug if the scanner
causes unusual noise.
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form:
<I>special</I>
Where <I>special</I> is either the path-name for the special device that cor-
responds to a SCSI scanner. The program <I>sane-find-scanner</I> helps to find
out the correct device. Under Linux, such a device name could be
<I>/dev/sg0</I> or <I>/dev/sga</I>, for example. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>ibm.conf</I> file is a list of device names that corre-
spond to SCSI 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.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/ibm.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-ibm.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-ibm.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_IBM</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>,
</PRE>
<H2>AUTHOR</H2><PRE>
mf &lt;massifr@tiscalinet.it&gt;
Maintained by Henning Meier-Geinitz &lt;henning@meier-geinitz.de&gt;
sane-backends 1.0.12-cvs 15 Apr 2003 <B><A HREF="sane-ibm.5.html">sane-ibm(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>

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

@ -0,0 +1,145 @@
<HTML>
<HEAD>
<TITLE>sane-leo.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-leo.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-leo.5.html">sane-leo(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-leo.5.html">sane-leo(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-leo - SANE backend for LEO Technologies scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-leo</B> library implements a SANE (Scanner Access Now Easy) back-
end that provides access to some LEO SCSI flatbed scanners. This back-
end should be considered <B>beta-quality</B> software! LEO scanners were also
sold under the Across Technologies brand.
The scanners that should work with this backend are:
Vendor Model status
---------------------- -----------
Across FS-1130 tested
Leo S3 tested
The options the backend supports can either be selected through command
line options to programs like scanimage or through GUI elements in
xscanimage or xsane.
If you have any strange behavior, please report to the backend main-
tainer or to the SANE mailing list.
Valid command line options and their syntax can be listed by using
scanimage --help -d leo
<B>Scan</B> <B>Mode</B>
<B>--mode</B> selects the basic mode of operation of the scanner valid choices
are <I>Black</I> <I>&amp;</I> <I>White</I> , <I>Grayscale</I> and <I>Color</I> The Black &amp; White mode
is black and white only (1 bit). Grayscale will produce 256 lev-
els of gray (8 bits). Color will produce a 24 bits color image.
<B>--resolution</B>
selects the resolution for a scan. The scanner can do all reso-
lutions between 1 and 300, in increments of 1.
<B>Geometry</B> <B>options</B>
<B>-l</B> <B>-t</B> <B>-x</B> <B>-y</B>
control the scan area: -l sets the top left x coordinate, -t the
top left y coordinate, -x selects the width and -y the height of
the scan area. All parameters are specified in millimeters by
default.
<B>Enhancement</B> <B>options</B>
<B>--custom-gamma</B>
(grayscale and color mode only) allows the user to specify a
gamma table (see the next 3 parameters).
<B>--red-gamma-table</B>
(color mode only) can be used to download a user defined gamma
table for the red channel. The table must be 256 bytes long.
<B>--green-gamma-table</B>
(color mode only) can be used to download a user defined gamma
table for the green channel. The table must be 256 bytes long.
<B>--blue-gamma-table</B>
(color mode only) can be used to download a user defined gamma
table for the blue channel. The table must be 256 bytes long.
<B>--halftone</B>
(Black &amp; White only) select the halftone mask to use. Possible
values are <I>Diamond</I> , <I>8x8</I> <I>Coarse</I> <I>Fatting</I> , <I>8x8</I> <I>Fine</I> <I>Fatting</I> , <I>8x8</I>
<I>Bayer</I> and <I>8x8</I> <I>Vertical</I> <I>Line</I>
<B>--preview</B>
requests a preview scan. The resolution used for that scan is 28
dpi and the scan area is the maximum allowed. The scan mode is
user selected. The default is "no".
</PRE>
<H2>CONFIGURATION FILE</H2><PRE>
The configuration file /usr/local/etc/sane.d/leo.conf supports only one
information: the device name to use (eg /dev/scanner).
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/lib/sane/libsane-leo.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-leo.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_LEO</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
E.g., a value of 128 requests all debug output to be printed.
Smaller levels reduce verbosity.
</PRE>
<H2>LIMITATIONS</H2><PRE>
The windows TWAIN driver has many more options than this SANE backend.
However they are only software adjustments. This backend only imple-
ments what the scanner can support.
</PRE>
<H2>BUGS</H2><PRE>
None known.
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, <B><A HREF="xsane.1.html">xsane(1)</A></B>, <B><A HREF="sane.7.html">sane(7)</A></B>
</PRE>
<H2>AUTHOR</H2><PRE>
The package is actively maintained by Frank Zago.
http://fz.eryx.net/sane/#leo
sane-backends 1.0.12-cvs 16 April 2002 <B><A HREF="sane-leo.5.html">sane-leo(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>

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

@ -0,0 +1,138 @@
<HTML>
<HEAD>
<TITLE>sane-ma1509.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-ma1509.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-ma1509 - SANE backend for Mustek BearPaw 1200F USB scanner
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-ma1509</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to the Mustek BearPaw 1200F USB flatbed
scanner. This scanner is based on the MA-1509 chipset. Other scanners
that use this chip (if they exist) may also work.
This backend is ALPHA software. Be careful and remove the power plug
immediately if your hear unusual noises.
More details can be found on the ma1509 backend homepage
<I>http://www.meier-geinitz.de/sane/ma1509-backend/</I>.
Other Mustek USB scanners are supported by the gt68xx, mustek_usb and
the plustek backends. See <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B> and <B>sane-</B>
<B><A HREF="plustek.5.html">plustek(5)</A></B> for details.
This backend can only work with scanners that are already detected by
the operating system. See <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B> for details.
If you own a scanner other than the Mustek BearPaw 1200F that works
with this backend, please let me know this by sending the scanner's
exact model name and the USB vendor and device ids (e.g. from
<I>/proc/bus/usb/devices</I> or syslog) to me.
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form:
<I>special</I>
Where <I>special</I> is a path-name for the special device that corresponds to
a USB scanner. With Linux, such a device name could be <I>/dev/usb/scan-</I>
<I>ner0</I> or <I>libusb:001:002</I>, for example.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>ma1509.conf</I> file is a list of options and device
names that correspond to Mustek BearPAw 1200F scanners. Empty lines
and lines starting with a hash mark (#) are ignored.
Instead of using the device name, the scanner can be autodetected by
<B>usb</B> <B>vendor_id</B> <B>product_id</B> statements which are already included into
<I>ma1509.conf</I>. This is only supported with Linux 2.4.8 and higher and
all systems that support libsub. "vendor_id" and "product_id" are hex-
adecimal numbers that identfy 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
<I>ma1509.conf</I>. The time is given in seconds after the option. The
default is 30 seconds.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/ma1509.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-ma1509.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-ma1509.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_MA1509</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>, <B>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>http://www.meier-geinitz.de/sane/ma1509-backend/</I>
</PRE>
<H2>AUTHOR</H2><PRE>
Henning Meier-Geinitz &lt;henning@meier-geinitz.de&gt;
</PRE>
<H2>BUGS</H2><PRE>
Resolutions higher than 600 dpi don't work
Transparency adapter and automatic document feeder is not supported yet
No support for "high-speed" mode (jpeg)
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.12-cvs 24 Feb 2003 <B><A HREF="sane-ma1509.5.html">sane-ma1509(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>

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

@ -0,0 +1,186 @@
<HTML>
<HEAD>
<TITLE>sane-matsushita.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-matsushita.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-matsushita.5.html">sane-matsushita(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-matsushita.5.html">sane-matsushita(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-matsushita - SANE backend for Panasonic KV-SS high speed scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-matsushita</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to some Panasonic KV-SS high speed scan-
ners. This backend is stable.
At present, the following scanners are known to work with this backend:
Product id
--------------
KV-SS 25
KV-SS 25D
Other Panasonic high speed scanners may or may not work with that back-
end.
Valid command line options and their syntax can be listed by using
scanimage --help -d matsushita
<B>Scan</B> <B>Mode</B>
<B>--mode</B> selects the basic mode of operation of the scanner.
<B>--resolution</B>
selects the resolution for a scan. Each model supports all or a
subset of these resolutions: 100, 150, 200, 240, 300, 360, 400.
<B>--duplex</B>
indicates whether to scan both side of the sheet.
<B>--feeder-mode</B>
selects the number of pages to scan (one or until the tray is
empty).
<B>Geometry</B>
<B>--paper-size</B> <B>A4|...|Legal|Letter</B> <B>[A4]</B>
options selects the area to scan. It adjust the <B>-l</B> <B>-t</B> <B>-x</B> <B>-y</B>
options accordingly. It does not need to be the real size of the
paper.
<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 aea. All parameters are specified in milimeters. It is
possible to use the option <I>--paper-size</I> instead.
<B>Enhancement</B>
<B>--brightness</B>
controls the brightness of the acquired image. The value varies
from 1 to 255, or less, depending on the scanner model.
<B>--contrast</B>
controls the contrast of the acquired image. Some models do not
support that option.
<B>--automatic-threshold</B>
automatically sets brightness, contrast, white level, gamma,
noise reduction and image emphasis. These options are not avail-
able when automatic-threshold is in use.
<B>--halftone-pattern</B>
option sets the tonal gradation for the halftone mode. Pattern
downloading is not implemented by the backend.
<B>--autoseparation</B>
provides automatic separation of text and images.
<B>--white-level</B>
option indicate the source of the white base.
<B>--noise-reduction</B>
reduces the isolated dot noise. This option is not supported by
all scanners.
<B>--image-emphasis</B>
option sets the image emphasis. Some selection are not available
on all scanners.
<B>--gamma</B>
options set the gamma curve. It is only valid for Gray modes,
and is not available on all scanners. Gamma downloading is not
implemented by the backend.
</PRE>
<H2>CONFIGURATION FILE</H2><PRE>
The configuration file /usr/local/etc/sane.d/matsushita.conf supports
the device name to use (eg /dev/scanner) and the scsi option to autode-
tect the scanners supported.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/lib/sane/libsane-matsushita.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-matsushita.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_MATSUSHITA</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
E.g., a value of 128 requests all debug output to be printed.
Smaller levels reduce verbosity.
</PRE>
<H2>LIMITATIONS</H2><PRE>
<B>Memory</B> <B>in</B> <B>the</B> <B>KV-SS</B> <B>25</B>
The KV-SS 25 has not enough internal memory to scan a whole A4
page in duplex mode at high densities. The frontend will return
a memory error in that case. Apparently, the KV-SS 25D has not
that problem.
<B>Pattern</B> <B>and</B> <B>gamma</B> <B>downloading</B>
The scanner, with the proper firmware, can download a halftone
pattern and a gamma table. This is not implemented.
<B>Sub-areas</B>
The scanner can support up to 3 sub-areas on each side to define
some more precise enhancment options. This is not implemented.
<B>Duplex</B> <B>mode</B>
The backend does not support the setting of different options
for each side. The scan will occur with the same options
(halftone pattern, brightness, image emphasis) for both sides.
</PRE>
<H2>SCANNING EXAMPLE</H2><PRE>
To date, the only frontend capable of using this scanner at full speed
is <B>scanadf.</B>
A scanadf command line would be:
scanadf -d matsushita --output-file scan%04d.pbm --start-count 0
--duplex --resolution 300 --feeder-mode="All pages" --paper-size="A4"
</PRE>
<H2>BUGS</H2><PRE>
None known.
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, <B><A HREF="xsane.1.html">xsane(1)</A></B>, <B><A HREF="sane.7.html">sane(7)</A></B>
</PRE>
<H2>AUTHOR</H2><PRE>
The package is actively maintained by Frank Zago.
http://fz.eryx.net/sane/#matsushita
sane-backends 1.0.12-cvs April 21s, 2002 <B><A HREF="sane-matsushita.5.html">sane-matsushita(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>

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

@ -0,0 +1,177 @@
<HTML>
<HEAD>
<TITLE>sane-microtek.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-microtek.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-microtek - SANE backend for Microtek scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-microtek</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to the "second generation" Microtek scan-
ners. At present, the following hardware is known to work with this
backend:
Microtek ScanMaker E2, E3, E6
Microtek ScanMaker II, IIG, IIHR, IISP, III
Microtek ScanMaker 35t, 35t+, 45t
Microtek ScanMaker 600GS, 600ZS (see bug notes)
Agfa StudioScan
Agfa StudioScan II, StudioScan IIsi
Agfa Arcus II (but not the "Arcus")
Agfa DuoScan (premliminary)
Vobis "Highscreen Realscan"
Microtek Color PageWiz (preliminary)
Transparent Media Adapter
Document AutoFeeder
The driver supports line art, halftone, 8bpp gray, and 24bpp color
scans at normal and "expanded" resolutions (i.e. 1200x1200 on an E6),
fast scans for color previews, and downloadable gamma tables.
The supported scanners are all SCSI scanners. However, some parallel
port models may work (under Linux), if they use a parport-&gt;scsi chip,
and if you can find a scsi-&gt;parport driver. This is known to be the
case for the Color PageWiz.
The driver does <B>not</B> support the newest Microtek scanners, such as the
V330 and V660, which use a new and very different SCSI-II command set.
For those, try the alternate <B>microtek2</B> backend. Most non-SCSI scanners
would use the new command set. Most scanners newer than the Scanmaker
E6 would use the new command set.
If you own a Microtek scanner other than the ones listed above, tell us
what happens --- see the <B>BUGS</B> section at the end of this document.
Although this manual page is generally updated with each release, up-
to-date information on new releases and extraneous helpful hints are
available from the backend homepage:
<B>http://www.mir.com/mtek/</B>
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form:
<I>special</I>
Where <I>special</I> is the UNIX path-name for the special device that corre-
sponds to the scanner. The special device name must be a generic SCSI
device or a symlink to such a device. Under Linux, such a device name
could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>microtek.conf</I> file is a list of device names that
correspond to Microtek scanners. Empty lines and lines starting with a
hash mark (#) are ignored. A sample configuration file is shown below:
/dev/scanner
# this is a comment
/dev/sge
The configuration file may also contain the special tokens <I>norealcal</I> or
<I>noprecal.</I> <I>norealcal</I> will disable the use of magic, undocumented scan-
ner calibration commands which are known to work on the E6, but may not
work with other models. <I>noprecal</I> will disable logic which tries to
avoid scanner precalibration. This logic would only have been acti-
vated if the magic calibration code was turned off.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/microtek.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-microtek.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-microtek.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_MICROTEK</B>
If the library was compiled with debugging support enabled, this
environment variable controls the debug level for this backend.
A value of 128 requests maximally copious debug output; smaller
levels reduce verbosity.
</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>
</PRE>
<H2>AUTHOR</H2><PRE>
Matt Marjanovic
</PRE>
<H2>BUGS</H2><PRE>
Known bugs/limitations are:
Brightness and contrast broken.
The 600GS is grayscale only, and will lock up if you select
color. (Unfortunately, the 600GS and 600ZS are indistinguish-
able by software.)
i.e. don't complain about these --- but if brightness and/or contrast
<B>do</B> work for you, please tell me.
If your scanner locks up, try setting the <I>norealcal</I> or <I>noprecal</I> option
in the configuration file (first one, then both), and see if it helps.
(If it does, report it.)
Send lengthy bug reports and new scanner information to <B>mtek-</B>
<B>bugs@mir.com</B>. All bug reports and new scanner inquiries should include
an error log file. You can generate copious stderr output by setting
the SANE_DEBUG_MICROTEK environment variable described above. For
example:
setenv SANE_DEBUG_MICROTEK 128
More general comments, suggestions, and inquiries about frontends or
SANE should go to <B>sane-devel@mostang.com</B>, the SANE Developers mailing
list. Have a look at http://www.mostang.com/sane/mail.html concerning
subscription to sane-devel.
sane-backends 1.0.12-cvs February 8, 2000 <B><A HREF="sane-microtek.5.html">sane-microtek(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>

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

@ -0,0 +1,294 @@
<HTML>
<HEAD>
<TITLE>sane-microtek2.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-microtek2.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-microtek2 - SANE backend for Microtek scanners with SCSI-2 command
set
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-microtek2</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to Microtek scanners with a SCSI-2 command
set. This backend can be considered alpha to beta. Some scanner models
are reported to work well, others not. New development versions of this
backend can be obtained from <B>http://karstenfestag.gmxhome.de</B>
There exists a different backend for Microtek scanners with SCSI-1 com-
mand set. Refer to <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B> for details.
And there is work in progress for the ScanMaker 3600. See
<B>http://sourceforge.net/projects/sm3600</B>
At present, the following scanners are known positively to work with
this backend:
Vendor Product id: Remark
-------- -------------- -------------
Microtek E3+ Parport and SCSI
Microtek X6 SCSI
Microtek X6EL SCSI
Microtek X6USB USB
Microtek ScanMaker V300 Parport and SCSI
Microtek ScanMaker V310 Parport and SCSI
Microtek ScanMaker V600 Parport and SCSI
Microtek ScanMaker 330 SCSI
Microtek ScanMaker 630 SCSI
Microtek ScanMaker 636 SCSI
Microtek ScanMaker 9600XL SCSI; only flatbed mode?
Microtek Phantom 330CX Parport
Microtek SlimScan C3 Parport
Microtek SlimScan C6 USB
Microtek Phantom 636 SCSI
Microtek Phantom 636CX Parport
Microtek V6USL SCSI and USB
Microtek V6UPL USB; not stable
Microtek X12USL SCSI; only 8bit color, work in progress
Vobis HighScan SCSI (E3+ based models)
Scanport SQ300 Parport?
Scanport SQ4836 SCSI
Scanpaq SQ2030 Parport
Additional information can be found at <B>http://www.mostang.com/sane/</B> <B>.</B>
If you own a Microtek scanner other than the ones listed above, it may
or may not work with SANE! Because equal scanners are sold under dif-
ferent names in different countries your model may be equivalent to one
of the above.
The parport scanners work with the ppscsi + onscsi kernel modules. See
<B>http://www.torque.net/parport/ppscsi.html</B>
The USB scanners work with the microtek kernel module. You may have to
add the vendor and model codes to microtek.c if they aren't yet listed
there.
Both parport and USB scanners need the generic SCSI support, so check
if you have loaded the scsi_mod and sg modules!
If you try your scanner for the first time keep an eye on it. If it
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!
If your scanner is a different one than the models mentioned above and
it is working please tell the author about it. It would be nice if you
add a logfile to this information (creation of the logfile: see below).
If your scanner is not working properly you also should create a log-
file and send it to the author. He will use the information to improve
the backend and possibly make your scanner work.
How to create the logfile?
- put the line
"option dump 2" into your <I>microtek2.conf</I>
file or change the existing "option dump" to "2"
- in a terminal (bash) type
"export SANE_DEBUG_MICROTEK2=30" and then
"scanimage -l0 -t0 -x100 -y20 2&gt;scan.log &gt;sout.pnm"
You get two files: scan.log contains the logfile and sout.pnm
the scanned image (if there was scanned something). Zip them
before sending.
</PRE>
<H2>FRONTEND OPTIONS</H2><PRE>
This backend dynamically enables the options for the frontend, that are
supported by the scanner in dependence of the scanning-mode and other
options. Not supported options are disabled.
The following options are supported by the Microtek2-driver:
Color, grayscale, halftone and lineart scans.
Highlight, midtone, shadow, contrast, brightness, exposure time con-
trol, gamma correction, threshold (dependent of the scan mode and the
scanner capabilities)
Transparency media adapter, automatic document feeder
Additional options can be enabled or disabled in the <I>microtek2.conf</I>
file. See the configuration section of this manpage.
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form:
<I>special</I>
Where <I>special</I> is the UNIX path-name for the special device that corre-
sponds to the scanner. The special device name must be a generic SCSI
device or a symlink to such a device. Under Linux, such a device name
could be <I>/dev/sga</I> or <I>/dev/sge</I> for example.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The configuration file for this backend resides in
<I>/usr/local/etc/sane.d/microtek2.conf</I> Its contents is a list of device
names that correspond to Microtek scanners with SCSI-2 interface. Empty
lines and lines starting with a hash mark (#) are ignored.
The configuration file may also contain options. Global options that
are valid for all devices are placed above the device names. Device-
specific options are placed under the device name. Note that, except
for option dump &lt;n&gt; and option strip-height &lt;n&gt;, the entry in the
microtek2.conf file only enables the corresponding option for being
showed in the frontend. There, in the frontend, you can switch the
options on and off. Currently the following options are supported:
option dump &lt;n&gt;
option strip-height &lt;n&gt;
option no-backtrack-option &lt;on/off&gt;
option lightlid-35 &lt;on/off&gt;
option toggle-lamp &lt;on/off&gt;
option lineart-autoadjust &lt;on/off&gt;
option backend-calibration &lt;on/off&gt;
option colorbalance-adjust &lt;on/off&gt;
<I>option</I> <I>dump</I> <I>&lt;n&gt;</I> enables printing of additional information about the
SCSI commands that are sent to the scanner to stderr. This option is
primarily useful for debugging purpose. This option has to be a global
option and is best placed at the top of the <I>microtek2.conf</I> file.
If n=1 the contents of the command blocks and the results for the
INQUIRY and READ SCANNER ATTRIBUTES command are printed to stderr.
If n=2 the contents of the command blocks for all other SCSI commands
are printed to stderr, too. If n=3 the contents of the gamma table is
printed, too. If n=4 all scan data is additionally printed to stderr.
The default is n=1.
<I>option</I> <I>strip-height</I> <I>&lt;n&gt;</I> , where &lt;n&gt; is a floating point number, limits
the amount of data that is read from the scanner with one read command.
The unit is inch and &lt;n&gt; defaults to 1.0, if this option is not set in
the configuration file. If less than &lt;n&gt; inch of data fit into the SCSI
buffer, then the smaller value is used and this option has no effect.
If your system has a big SCSI buffer and you want to make use of the
whole buffer, increase the value for &lt;n&gt;. For example, if &lt;n&gt; is set to
14.0, no restrictions apply for scanners with a letter, legal or A4
sized scan area.
The following options enable or disable additional frontend options. If
an option is set to &lt;on&gt; an appropriate option will appear in the fron-
tend.
<I>option</I> <I>no-backtrack-option</I> <I>&lt;on/off&gt;</I> prevents the scanner head from mov-
ing backwards between the read commands. This speeds up scanning. Try
it.
<I>option</I> <I>lightlid-35</I> <I>&lt;on/off&gt;</I> If you use the LightLid-35 transparency
adapter you get an advanced option which switches off the flatbed lamp
during the scan.
<I>option</I> <I>toggle-lamp</I> <I>&lt;on/off&gt;</I> You get a button in the frontend where you
can switch on and off the flatbed lamp.
<I>option</I> <I>lineart-autoadjust</I> <I>&lt;on/off&gt;</I> You can tell the backend to try to
determine a good value for the lineart threshold.
<I>option</I> <I>backend-calibration</I> <I>&lt;on/off&gt;</I> Some scanners (e.g. Phantom 330CX
and 636CX) need to have calibrated the data by the backend. Try this
option if you see vertical stripes in your pictures.
<I>option</I> <I>colorbalance-adjust</I> <I>&lt;on/off&gt;</I> Some scanners (e.g. Phantom 330CX
and 636CX) need to have corrected the color balance. If this option is
enabled you get advanced options where you can balance the colors. And
you will have a button to use the values that the firmware of the scan-
ner provides.
A sample configuration file is shown below:
option dump 1
option strip-height 1.0
/dev/scanner
option no-backtrack-option on
# this is a comment
/dev/sge
option lightlid-35 on
This backend also supports the new configuration file format which
makes it easier to detect scanners under Linux. If you have only one
scanner it would be best to use the following configuration file for
this backend:
option dump 1
option strip-height 14.0
option no-backtrack-option on
option backend-calibration on
option lightlid-35 on
option toggle-lamp on
option lineart-autoadjust on
option colorbalance-adjust off
scsi * * Scanner
In this case all SCSI-Scanners should be detected automatically because
of the
scsi * * Scanner
line.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/microtek2.conf</I>
The backend configuration file.
<I>/usr/local/lib/sane/libsane-microtek2.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-microtek2.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_MICROTEK2</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
E.g., a value of 255 requests all debug output to be printed.
Smaller levels reduce verbosity. To see error messages on stderr
set SANE_DEBUG_MICROTEK2 to 1 (Remark: The whole debugging lev-
els should be better revised).
E.g. just say:
export SANE_DEBUG_MICROTEK2=128
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane.7.html">sane(7)</A></B>
</PRE>
<H2>AUTHORS</H2><PRE>
Bernd Schroeder (not active anymore)
Karsten Festag karsten.festag@gmx.de
sane-backends 1.0.12-cvs 28 Jan 2002 <B><A HREF="sane-microtek2.5.html">sane-microtek2(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>

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

@ -0,0 +1,348 @@
<HTML>
<HEAD>
<TITLE>sane-mustek.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-mustek.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-mustek - SANE backend for Mustek SCSI flatbed scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-mustek</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to Mustek (and some relabeled Trust and
Primax) SCSI flatbed scanners. At present, the following scanners are
known to work more or less with this backend:
Paragon MFS-6000CX
Paragon MFS-12000CX
Paragon MFC-600S, 600 II CD, ScanMagic 600 II SP
Paragon MFC-800S, 800 II SP
Paragon MFS-6000SP
Paragon MFS-8000SP
Paragon MFS-1200SP, MFS-12000SP
ScanExpress 6000SP
ScanExpress 12000SP, 12000SP Plus, Paragon 1200 III SP, Scan-
Magic 9636S, 9636S Plus
Paragon 1200 LS
ScanExpress A3 SP
Paragon 1200 SP Pro
Paragon 1200 A3 Pro
Paragon 600 II N
Trust Imagery 1200
Trust Imagery 1200 SP
Trust Imagery 4800 SP
Trust SCSI Connect 19200
Primax Compact 4800 SCSI
More details can be found on the Mustek SCSI backend homepage
<I>http://www.meier-geinitz.de/sane/mustek-backend/</I>.
Don't mix up MFS (Paragon), Pro and ScanExpress models! They're com-
pletely different. Check the exact model name!
Note that most of the above scanners come with a SCSI interface. The
only non-SCSI scanner that has some support at this point is the 600 II
N scanner which comes with its own parallel port adapter (i.e., it does
<I>not</I> attach to the printer port). It uses the SCSI protocoll internally,
too. More info on how to use the 600 II N can be found below in section
<B>PARAGON</B> <B>600</B> <B>II</B> <B>N</B>. Other parallel port scanners are not supported by
this backend but you may be successful using the Mustek parallel port
backend mustek_pp, see <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>. USB scanners are also not
supported by this backend but the mustek_usb, gt68xx, and plustek back-
ends include support for some of them, see <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>, and <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>.
Mustek scanners have no protection against exceeding the physical scan
area height. That is, if a scan is attempted with a height that
exceeds the height of the scan surface, the scanner begins making loud
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.12-cvs/PROBLEMS</I> file.
If you own a Mustek (or Trust) scanner other than the ones listed above
that works with this backend, please let us know by sending the scan-
ner's exact model name (look at the front and back of the scanner) and
a debug output to <I>sane-devel@mostang.com</I>. You can get the debug output
by setting the environment variable <B>SANE_DEBUG_MUSTEK</B> to 5 and showing
the list of available scanners with scanimage -L . Please send all of
it to the mailing list. You must be subscribed to sane-devel before you
can send mail to the list. See <I>http://www.mostang.com/sane/mail.html</I>
for details.
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form:
<I>special</I>
Where <I>special</I> is either the path-name for the special device that cor-
responds to a SCSI scanner or the port number at which the 600 II N can
be found (see section <B>PARAGON</B> <B>600</B> <B>II</B> <B>N</B> below). For SCSI scanners, the
special device name must be a generic SCSI device or a symlink to such
a device. The program <I>sane-find-scanner</I> helps to find out the correct
device. Under Linux, such a device name could be <I>/dev/sga</I> or <I>/dev/sge</I>,
for example. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>mustek.conf</I> file is a list of options and device
names that correspond to Mustek 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 supported options are <B>linedistance-fix</B>, <B>lineart-fix</B>, <B>legal-size</B>,
<B>buffersize</B>, <B>blocksize</B>, <B>strip-height</B>, <B>disable-double-buffering</B>, <B>disable-</B>
<B>backtracking</B>, and <B>force-wait</B>.
Options come in two flavors: global and positional ones. Global
options apply to all devices managed by the backend whereas positional
options apply just to the most recently mentioned device. Note that
this means that the order in which the options appear matters!
Option <B>linedistance-fix</B> is positional and works around a problem that
occurs with some SCSI controllers (notably the ncr810 controller under
Linux). If color scans have horizontal stripes and/or the colors are
off, then it's likely that your controller suffers from this problem.
Turning on this option usually fixes the problem.
Option <B>lineart-fix</B> is positional and works around a timing problem that
seems to exist with certain MFS-12000SP scanners. The problem mani-
fests itself in dropped lines when scanning in lineart mode. Turning
on this option should fix the problem but may slow down scanning a bit.
Option <B>legal-size</B> is positional and sets the size of the scan area to
Legal format. Set this option if you own a Paragon 12000 LS. It can't
be distinguished by software from a ScanExpress 12000 SP (ISO A4 for-
mat).
Option <B>buffersize</B> is a positional option that overrides the default
value set for the size of the SCSI buffer. The buffer size is specified
in kilobytes. The default value is 128. Because of double buffering the
buffer actually sent to the scanner is half the size of this value. Try
to increase this value to achieve higher scan speeds. Note that some
ScanExpress scanners don't like buffer sizes above 64 kb (buffersize =
128). If your sg driver can't set SCSI buffer sizes at runtime you may
have to change that value, too. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details.
Option <B>blocksize</B> is a positional option that overrides the default
value set for the maximum amount of data scanned in one block. The
buffer size is specified in kilobytes. Some scanners freeze if this
value is bigger than 2048. The default value is 1 GB (so effectively no
limit) for most scanners. Don't change this value if you don't know
exactly what you do.
Option <B>strip-height</B> is a global option that limits the maximum height
of the strip scanned with a single SCSI read command. The height is
specified in inches and may contain a fractional part (e.g., 1.5).
Setting the strip-height to a small value (one inch, for example)
reduces the likelihood of encountering problems with SCSI driver time-
outs and/or timeouts with other devices on the same SCSI bus. Unfortu-
nately, it also increases scan times. With current SCSI adapters and
drivers this option shouldn't be needed any more.
Option <B>disable-double-buffering</B> is a global option. If set, the backend
will only send one buffer at a time to the scanner. Try this option if
you have trouble while scanning, e.g. SCSI errors, freezes, or the
first few cm are repeated over and over again in your image.
Option <B>disable-backtracking</B> is a positional option. If set, the scanner
will not move back its slider after each SCSI buffer is filled (`back-
tracking'). Setting this option will lead to faster scans but may also
produce horizontal stripes. This option doesn't work with every scanner
(only some of the paragon models can modify backtracking).
Finally, <B>force-wait</B> is a global option. If set, the backend will wait
until the device is ready before sending the inquiry command. Further
more the backend will force the scan slider to return to its starting
position (not implemented for all scanners). This option may be neces-
sary with the 600 II N or when scanimage is used multiple times (e.g.
in scripts). The default is off (not set).
A sample configuration file is shown below:
# limit strip height of all scanners to 1.5 inches:
option strip-height 1.5
/dev/scanner # first Mustek scanner
# 1 MB buffer for /dev/scanner:
option buffersize 1024
/dev/sge # second Mustek scanner
# turn on fixes for /dev/sge:
option lineart-fix
option linedistance-fix
</PRE>
<H2>SCSI ADAPTER TIPS</H2><PRE>
You need a SCSI adapter for the SCSI scanners. Even if the connector is
the same as that of parallel port scanners, connecting it to the com-
puters parallel port will NOT work.
Mustek SCSI scanners are typically delivered with an ISA SCSI adapter.
Unfortunately, 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 be very slow and put so much
load on the system, that it becomes almost unusable for other tasks.
If you already have a working SCSI controller in your system, you
should consider that Mustek scanners do not support the SCSI-2 discon-
nect/reconnect protocol and hence tie up the SCSI bus while a scan is
in progress. This means that no other SCSI device on the same bus can
be accessed while a scan is in progress.
Because the Mustek-supplied adapter is not worth much and because
Mustek scanners do not support the SCSI-2 disconnect/reconnect proto-
col, it is recommended to install a separate (cheap) SCSI controller
for Mustek scanners. For example, ncr810 based cards are known to work
fine and cost as little as fifty US dollars.
For Mustek scanners, it is typically necessary to configure the low-
level SCSI driver to disable synchronous transfers (sync negotiation),
tagged command queuing, and target disconnects. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for
driver- and platform-specific information.
The ScanExpress models have sometimes trouble with high resolution
color mode. If you encounter sporadic corrupted images (parts dupli-
cated or shifted horizontally) kill all other applications before scan-
ning and (if sufficient memory is available) disable swapping.
Details on how to get the Mustek SCSI adapters and other cards running
can be found at <I>http://www.meier-geinitz.de/sane/mustek-backend/#SCSI</I>.
</PRE>
<H2>PARAGON 600 II N</H2><PRE>
This backend has support for the Paragon 600 II N parallel port scan-
ner. Note that this scanner comes with its own ISA card that imple-
ments a funky parallel port (in other words, the scanner does not con-
nected to the printer parallel port).
This scanner can be configured by listing the port number of the
adapter in the mustek.conf file. Valid port numbers are <I>0x26b</I>, <I>0x2ab</I>,
<I>0x2eb</I>, <I>0x22b</I>, <I>0x32b</I>, <I>0x36b</I>, <I>0x3ab</I>, <I>0x3eb</I>. Pick one that doesn't con-
flict with the other hardware in your computer. Put only one number on
a single line. Example:
<I>0x3eb</I>
Note that for this scanner root privileges are required to access the
I/O ports. Thus, either make frontends such as <B><A HREF="scanimage.1.html">scanimage(1)</A></B> and <B>xscan-</B>
<B><A HREF="image.1.html">image(1)</A></B> setuid root (generally not recommended for safety reasons) or,
alternatively, access this backend through the network daemon <B><A HREF="saned.1.html">saned(1)</A></B>.
On systems which support this feature, the scanner can be accessed
through <I>/dev/port</I>. Don't forget to adjust the permissions for
<I>/dev/port</I>. At least with recent Linux kernels root privileges are nec-
essary for <I>/dev/port</I> access, even with full permissions set for all
users..
If your images have horizontal stripes in color mode, check option
<B>linedistance-fix</B> (see above). Apply this option for a scanner with
firmware version 2.x and disable it for version 1.x.
If the Mustek backend blocks while sending the inqiury command to the
scanner, add the option <B>force-wait</B> to <I>mustek.conf</I>.
Also note that after a while of no activity, some scanners themself
(not the SANE backend) turns off their CCFL lamps. This shutdown is not
always perfect with the result that the lamp sometimes continues to
glow dimly at one end. This doesn't appear to be dangerous since as
soon as you use the scanner again, the lamp turns back on to the normal
high brightness. However, the first image scanned after such a shutdown
may have stripes and appear to be over-exposed. When this happens,
just take another scan, and the image will be fine.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/mustek.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-mustek.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-mustek.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_MUSTEK</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Value Description
0 no output
1 print fatal errors
2 print important messages
3 print non-fatal errors and less important messages
4 print all but debugging messages
5 print everything
Example:
export SANE_DEBUG_MUSTEK=4
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B>sane-</B>
<B><A HREF="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.12-cvs/mustek/mustek.CHANGES</I>
<I>http://www.meier-geinitz.de/sane/mustek-backend/</I>
</PRE>
<H2>AUTHOR</H2><PRE>
David Mosberger, Andreas Czechanowski, Andreas Bolsch (SE extensions),
Henning Meier-Geinitz
</PRE>
<H2>BUGS</H2><PRE>
Scanning with the SCSI adapters supplied by Mustek is very slow at high
resolutions and wide scanareas.
Some scanners (e.g. Paragon 1200 A3 + Pro, SE A3) need more testing.
The gamma table supports only 256 colors, even if some scanners can do
more.
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.12-cvs 5 Dec 2002 <B><A HREF="sane-mustek.5.html">sane-mustek(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>

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

@ -0,0 +1,367 @@
<HTML>
<HEAD>
<TITLE>sane-mustek_pp.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-mustek_pp.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B> <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-mustek_pp - SANE backend for Mustek parallel port flatbed scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-mustek_pp</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to Mustek parallel port flatbed scanners
and OEM versions.
There are 2 classes of Mustek parallel port scanners: regular <B>CCD</B> (cold
cathode device) scanners and <B>CIS</B> (contact image sensor) scanners.
Previous versions of this backend only supported CCD type scanners.
Patches for CIS type scanners were available, but simultaneous support
for both types was not possible. The current version of the driver
enables both types to co-exist. The CIS drivers have been ported to it
already, and work is going on to port the CCD drivers too.
The following scanners might work with this backend:
<B>CCD</B> <B>scanners</B> (currently not hooked up yet)
Model: ASIC ID: CCD Type: works:
-------------------- --------- ---------- -------
SE 6000 P 1013 00 yes
SM 4800 P 1013/1015 04/01 yes
SE 1200 ED Plus 1015 01 partly
SM 1200 ED Plus 1015 01 partly
SE 12000 P 1505 05 no
600 III EP Plus 1013/1015 00/01 yes
SE 600 SEP 1013 ?? yes
600 II EP ???? ?? no
MD9848 1015 00 yes
Gallery 4800 ???? ?? yes
Viviscan Compact II 1013 00 yes
<B>CIS</B> <B>scanners</B>
Model: ASIC ID: works:
--------------------- --------- -------
Mustek 600 CP 1015 yes (*)
Mustek 1200 CP 1015 yes
Mustek 1200 CP+ 1015 yes
OEM versions Original works
--------------------- --------- ----------
Medion/LifeTec/Tevion
MD/LT 9350/9351 1200 CP yes
MD/LT 9850/9851 1200 CP maybe (**)
MD/LT 9858 1200 CP probably
MD/LT 9890/9891 1200 CP yes
Targa
Funline TS12EP 1200 CP yes
Funline TS6EP 600 CP yes
Trust
Easy Connect 9600+ 600 CP yes
(*) Calibration problems existed with earlier version of this
driver. They seem to be solved now.
(**) Problems have been reported in the past for the MD/LT9850 type
(striped scans, head moving in wrong direction at some resolu-
tions). It is not known whether the current version of the
driver still has these problems.
<B>IF</B> <B>YOU</B> <B>HEAR</B> <B>LOUD</B> <B>CLICKING</B> <B>NOISES,</B> <B>IMMEDIATELY</B> <B>UNPLUG</B> <B>THE</B> <B>SCANNER</B>
<B>!</B> (This holds for any type of scanner).
Please note that this backend is still under construction. Certain mod-
els are currently not supported and some may never be because the com-
munication protocol is still unknown (eg., SE 12000 P).
Some scanners work faster when <B>EPP/ECP</B> is enabled in the BIOS.
Note that the backend needs to run as root. To allow user access to the
scanner run the backend through the network interface (See <B><A HREF="saned.1.html">saned(1)</A></B> and
<B><A HREF="sane-net.5.html">sane-net(5)</A></B>). Note also that the backend <I>does</I> <I>not</I> support <I>parport</I> <I>shar-</I>
<I>ing</I> <I>,</I> i.e. if you try printing while scanning, your computer may crash.
This backend also conflicts with the <I>sane-musteka4s2</I> backend. You can
only enable one of them in your dll.conf. However, you have to enable
the backend explicitly in your dll.conf, just remove the hash mark in
the line "mustek_pp".
</PRE>
<H2>DEVICE DEFINITION</H2><PRE>
This backend allows multiple devices being defined and configured via
the <B>mustek_pp.conf</B> file (even simultaneously, provided that they are
connected to different parallel ports). Please make sure to edit this
file <B>before</B> you use the backend.
A device can be defined as follows:
<I>scanner</I> <I>&lt;name&gt;</I> <I>&lt;address&gt;</I> <I>&lt;driver&gt;</I>
where
<B>&lt;name&gt;</B> is an arbitrary name for the device, optionally enclosed by dou-
ble quotes, for instance "LifeTec 9350".
<B>&lt;address&gt;</B> is the port address of the parallel port to which the device
is connected. Known ports are <B>0x378,</B> <B>0x278,</B> and <B>0x3BC</B>. The
mapping of parallel ports (lp0, lp1, and lp2) to these addresses
can be different for different Linux kernel versions. For
instance, if you are using a Kernel 2.2.x or better and you have
only one parallel port, this port is named lp0 regardless of the
base address. However, this backend requires the base address of
your port. If you are not sure which port your scanner is con-
nected to, have a look at your /etc/conf.modules, /etc/mod-
ules.conf and/or /proc/ioports.
<B>&lt;driver&gt;</B> is the driver to use for this device. Currently available
drivers are:
<B>cis600</B> : for 600 CP &amp; OEM versions
<B>cis1200</B> : for 1200 CP &amp; OEM versions
<B>cis1200+</B> : for 1200 CP+ &amp; OEM versions
<B>Choosing</B> <B>the</B> <B>wrong</B> <B>driver</B> <B>can</B> <B>damage</B> <B>your</B> <B>scanner!</B>
Especially, using the 1200CP settings on a 600CP can be harmful.
If the scanner starts making a loud noice, turn it off immedi-
ately !!!
Using the cis600 driver on a 1200CP or a 1200CP+ is probably not
dangerous. The cis1200+ driver also works for the 1200CP, and
using the cis1200 driver on a 1200CP+ will typically result in
scans that cover only half of the width of the scan area (also
not dangerous).
If unsure about the exact model of your OEM version, check the
optical resolution in the manual or on the box: the 600CP has a
maximum optical resolution of 300x600 DPI, whereas the 1200CP
and 1200CP+ have a maximum optical resolution of 600x1200 DPI.
Examples:
scanner "LifeTec 9350" 0x378 cis1200
scanner Mustek_600CP 0x378 cis600
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <B>mustek_pp.conf</B> file is a list of device definitions
and device options that correspond to Mustek scanners. Empty lines and
lines starting with a hash mark (#) are ignored. Options have the fol-
lowing format:
<I>option</I> <I>&lt;name&gt;</I> <I>[&lt;value&gt;]</I>
Depending on the nature of the option, a value may or may not be
present. Options always apply to the scanner definition that preceeds
them. There are no global options. Options are also driver-specific:
not all drivers support all possible options.
<B>Common</B> <B>options</B>
<B>bw</B> <B>&lt;value&gt;</B> Black/white discrimination value to be used during lin-
eart scanning. Pixel values below this value are assumed to
be black, values above are assumed to be white.
Default value: 127
Minimum: 0
Maximum: 255
Example: option bw 150
<B>CIS</B> <B>driver</B> <B>options</B>
<B>top_adjust</B> <B>&lt;value&gt;</B> Vertical adjustment of the origin, expressed in
millimeter (floating point). This option can be used to
calibrate the position of the origin, within certain limits.
Note that CIS scanners are probably temperature sensitive,
and that a certain inaccuracy may be hard to avoid. Differ-
ences in offset between runs in the order of 1 to 2 mm are
not unusual.
Default value: 0.0
Minimum: -5.0
Maximum: 5.0
Example: option top_skip -2.5
<B>slow_skip</B> Turns fast skipping to the start of the scan region off.
When the region to scan does not start at the origin, the
driver will try to move the scanhead to the start of the
scan area at the fastest possible speed. On some models,
this may not work, resulting in large inaccuracies (up to
centimeters). By setting this option, the driver is forced
to use normal speed during skipping, which can circumvent
the accuracy problems. Currently, there are no models for
which these inaccuracy problems are known to occur.
By default, fast skipping is used.
Example: option slow_skip
<B>CCD</B> <B>driver</B> <B>options</B>
To be defined.
A sample configuration file is shown below:
#
# LifeTec/Medion 9350 on port 0x378
#
scanner "LifeTec 9350" 0x378 cis1200
# Some calibration options (examples!).
option bw 127
option top_skip -0.8
#
# A Mustek 600CP on port 0x3BC
#
scanner "Mustek 600CP" 0x3BC cis600
# Some calibration options (examples!).
option bw 120
option top_skip 1.2
#
# A Mustek 1200CP+ on port 0x278
#
scanner "Mustek 1200CP plus" 0x278 cis1200+
# Some calibration options (examples!).
option bw 130
option top_skip 0.2
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/mustek</I><B>_</B><I>pp.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-mustek</I><B>_</B><I>pp.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-mustek</I><B>_</B><I>pp.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_MUSTEK_PP</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
E.g., a value of 128 requests all debug output to be printed.
Smaller levels reduce verbosity.
level debug output
------- ------------------------------
0 nothing
1 errors
2 warnings &amp; minor errors
3 additional information
4 debug information
5 code flow (not supported yet)
6 special debug information
<B>SANE_DEBUG_SANEI_PA4S2</B>
This variable sets the debug level for the SANE interface for
the Mustek chipset A4S2. Note that enabling this will spam your
terminal with some million lines of debug output.
level debug output
------- -------------------------------
0 nothing
1 errors
2 warnings
3 things nice to know
4 code flow
5 detailed code flow
6 everything
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-net.5.html">sane-net(5)</A></B>, <B><A HREF="saned.1.html">saned(1)</A></B>
For latest bug fixes and information see
<I>http://www.penguin-breeder.org/?page=mustek</I><B>_</B><I>pp</I>
For the latest CIS driver versions, see
<I>http://home.tiscalinet.be/EddyDeGreef/</I>
</PRE>
<H2>AUTHORS</H2><PRE>
Jochen Eisinger &lt;jochen.eisinger@gmx.net&gt;
Eddy De Greef &lt;eddy_de_greef at tiscali dot be&gt;
</PRE>
<H2>BUGS</H2><PRE>
Too many... please send bug reports to <I>sane-devel@mostang.com</I> (note
that you have to subscribe first to the list before you can send
emails... see http://www.mostang.com/sane/mail.html)
* 1013 support isn't bullet proofed
* 1505 support isn't even present
* 1015 only works for CCD type 00 &amp; 01 (01 only bw/grayscale)
</PRE>
<H2>BUG REPORTS</H2><PRE>
If something doesn't work, please contact us (Jochen for the CCD scan-
ners, Eddy for the CIS scanners). But we need some information about
your scanner to be able to help you...
<I>SANE</I> <I>version</I>
run "scanimage -V" to determine this
<I>the</I> <I>backend</I> <I>version</I> <I>and</I> <I>your</I> <I>scanner</I> <I>hardware</I>
run "SANE_DEBUG_MUSTEK_PP=128 scanimage -L" as root. If you
don't get any output from the mustek_pp backend, make sure a
line "mustek_pp" is included into your
/usr/local/etc/sane.d/dll.conf. If your scanner isn't detected,
make sure you've defined the right port address in your
mustek_pp.conf.
<I>the</I> <I>name</I> <I>of</I> <I>your</I> <I>scanner/vendor</I>
also a worthy information. Please also include the optical reso-
lution and lamp type of your scanner, both can be found in the
manual of your scanner.
<I>any</I> <I>further</I> <I>comments</I>
if you have comments about the documentation (what could be done
better), or you think I should know something, please include
it.
<I>some</I> <I>nice</I> <I>greetings</I>
February 20 2002 <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(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>

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

@ -0,0 +1,186 @@
<HTML>
<HEAD>
<TITLE>sane-mustek_usb.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-mustek_usb.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-mustek_usb - SANE backend for Mustek USB flatbed scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-mustek_usb</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to Mustek USB flatbed scanners (including
a clone from Trust). At present, the following scanners are known to
work more or less with this backend:
Mustek 600 CU
Mustek 1200 UB
Mustek 1200 CU
Mustek 1200 CU Plus
Trust Compact Scan USB 19200
More details can be found on the Mustek USB backend homepage
<I>http://www.meier-geinitz.de/sane/mustek</I><B>_</B><I>usb-backend/</I>.
The Mustek BearPaw 1200 and 2400 scanners are supported by the plustek
backend. See <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B> for details. The Mustek BearPaw 1200F is
supported by the MA-1509 backend. See <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B> for details. Other
Mustek USB scanners are supported by the gt68xx backend, see <B>sane-</B>
<B><A HREF="gt68xx.5.html">gt68xx(5)</A></B>.
This backend can only work with scanners that are already detected by
the operating system. See <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B> for details.
If you own a Mustek (or Trust) 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 device ids (e.g. from
<I>/proc/bus/usb/devices</I> or syslog) to me.
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form:
<I>special</I>
Where <I>special</I> is a path-name for the special device that corresponds to
a USB scanner. With Linux, such a device name could be <I>/dev/usb/scan-</I>
<I>ner0</I> or <I>/dev/usbscanner1</I>, for example.
For FreeBSD use <I>/dev/uscanner0</I>.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>mustek</I><B>_</B><I>usb.conf</I> file is a list of options and
device names that correspond to Mustek USB scanners. Empty lines and
lines starting with a hash mark (#) are ignored. If a device name is
placed in <I>mustek</I><B>_</B><I>usb.conf</I>, it must be followed by a line containing the
keyword <B>option</B> and an option specifying the scanner type. The following
options can be used: <B>600cu</B>, <B>1200cu</B>, <B>1200cu_plus</B>, <B>1200ub</B>. For the Trust
Compact Scan USB 19200 use `option 1200ub'.
Instead of using the device name, the scanner can be autodetected by
<B>usb</B> <B>vendor_id</B> <B>product_id</B> statements which are already included into
<I>mustek</I><B>_</B><I>usb.conf</I>. This is only supported with Linux 2.4.8 and higher
and all systems that support libsub. "vendor_id" and "product_id" are
hexadecimal numbers that identfy 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.
The global <B>option</B> <B>max_block_size</B> can be used to limit the amount of
data acquired in one turn from the USB system. It may be worth trying,
if USB errors occur.
A sample configuration file is shown below:
# Comment
option max_block_size 1024
usb 0x055f 0x0001
/dev/usb/scanner0
option 600cu
The first line is ignored. The second line sets the buffer size to a
maximum of 1024 bytes. The third line tries to autodetect a scanner
with vendor id 0x055f and product id 0x0001 (Mustek 1200 CU). The
fourth line tells the backend to attach to <I>/dev/usb/scanner0</I> and the
fifth line specifies that <I>/dev/usb/scanner0</I> is a Mustek 600 CU.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/mustek</I><B>_</B><I>usb.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>usb.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-mustek</I><B>_</B><I>usb.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_MUSTEK_USB</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Value Descsription
0 no output
1 print fatal errors
2 print important messages
3 print non-fatal errors and less important messages
4 print all but debugging messages
5 print high level debugging messages
6 print medium level debugging messages
7 print low level debugging messages
Example:
export SANE_DEBUG_MUSTEK_USB=4
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-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.12-cvs/mustek</I><B>_</B><I>usb/mustek</I><B>_</B><I>usb.CHANGES</I>,
<I>/usr/local/doc/sane-1.0.12-cvs/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>
</PRE>
<H2>AUTHOR</H2><PRE>
Henning Meier-Geinitz &lt;henning@meier-geinitz.de&gt;
This backend is based on the Mustek 1200ub backend from Mustek, main-
tained by Tom Wang.
</PRE>
<H2>BUGS</H2><PRE>
These devices have a hardware bug: Once data is written to them, they
can't be resetted (toggle = DATA0). That means, any operation that
tries to reset the device will result in running into timeouts.
That means that this backend will fail when it is loaded the second
time in some configurations: E.g. using libusb, (Free|Open|Net)BSD or
with Linux if you unload and reload the scanner module. The only choice
is to replug the scanner in this case.
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.12-cvs 09 Jan 2003 <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(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>

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

@ -0,0 +1,78 @@
<HTML>
<HEAD>
<TITLE>sane-nec.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-nec.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-nec.5.html">sane-nec(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-nec.5.html">sane-nec(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-nec - SANE backend for NEC scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-nec</B> library implements a SANE (Scanner Access Now Easy) back-
end that provides access to NEC SCSI scanners. This backend should be
considered <B>alpha-quality</B> software! In the current state it is known to
work with PC-IN500/4C scanners. Another MultiReader scanner series is
not supported. PC-IN 500/4C and MultiReader scanner are only sold in
Japan.(except Multi Reader PetiScan.)
For other scanners, it may or may not work.
The backend has the following known problems:
- ColorLineart mode is not supported.
- device name is fixed to /dev/scanner
At present, the following scanners are known to work with this backend.
Vendor Product id
------ -----------
NEC PC-IN500/4C
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/nec.conf</I>
The backend configuration file.
<I>/usr/local/lib/sane/libsane-nec.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-nec.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_NEC</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
E.g., a value of 128 requests all debug output to be printed.
Smaller levels reduce verbosity.
</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>
</PRE>
<H2>AUTHORS</H2><PRE>
Kazuya Fukuda
sane-backends 1.0.12-cvs 17 Feb 2000 <B><A HREF="sane-nec.5.html">sane-nec(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>

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

@ -0,0 +1,142 @@
<HTML>
<HEAD>
<TITLE>sane-net.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-net.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-net.5.html">sane-net(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-net.5.html">sane-net(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-net - SANE network backend
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-net</B> library implements a SANE (Scanner Access Now Easy) back-
end that provides access to image acquisition devices through a network
connection. This makes it possible to control devices attached to a
remote host and also provides a means to grant users access to pro-
tected resources.
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form:
<I>host</I>:<I>device</I>
Where <I>host</I> is the name (or IP address) of the (remote-) host and <I>device</I>
is the name of the device on this host that should be addressed. If
the device name does not contain a colon (:), then the entire string is
treated as the <I>device</I> string for the default host. The default host is
the host listed last in the configuration file (see below).
An IPv6 address can be specified enclosed in square brackets:
<I>[::1]</I>:<I>device</I>
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>net.conf</I> file is a list of host names (or IP
addresses) that should be contacted for scan requests. Empty lines and
lines starting with a hash mark (#) are ignored. Note that IPv6
addresses in this file do not need to be enclosed in square brackets.
A sample configuration file is shown below:
scan-server.somedomain.firm
192.168.0.1
# this is a comment
localhost
::1
The above list of hosts can be extended at run-time using environment
variable <B>SANE_NET_HOSTS</B>. This environment variable is a colon-sepa-
rated list of hostnames or IP addresses that should be contacted in
addition to the hosts mentioned in the configuration file. For exam-
ple, a user could set the environment variable to the string:
new.scanner.com:[::1]:192.168.0.2:scanner.univ.edu
To request that hosts <I>new.scanner.com</I> , <I>[::1]</I> , <I>192.168.0.2</I> and <I>scan-</I>
<I>ner.univ.edu</I> are contacted in addition to the hosts listed above.
For this backend to function properly, it is also necessary to define
the <B>sane</B> service in <I>/etc/services</I>. The <B>sane</B> service should be defined
using a line of the following form:
sane 6566/tcp # SANE network scanner daemon
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/net.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-net.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-net.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SANE_NET_HOSTS</B>
A colon-separated list of host names or IP addresses to be con-
tacted by this backend.
<B>SANE_DEBUG_NET</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>BUGS</H2><PRE>
If saned has timed out, the net backend may loop with authorization
requests.
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="saned.1.html">saned(1)</A></B>, <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>
<I>http://www.penguin-breeder.org/?page=sane-net</I>
</PRE>
<H2>AUTHOR</H2><PRE>
David Mosberger and Andreas Beck
sane-backends 1.0.12-cvs 8 Oct 2002 <B><A HREF="sane-net.5.html">sane-net(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>

77
man/sane-pie.5.html 100644
Wyświetl plik

@ -0,0 +1,77 @@
<HTML>
<HEAD>
<TITLE>sane-pie.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-pie.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-pie.5.html">sane-pie(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-pie.5.html">sane-pie(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-pie - SANE backend for PIE, Devcom and AdLib SCSI flatbed scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-pie</B> library implements a SANE (Scanner Access Now Easy) back-
end that provides access to PIE, Devcom and AdLib SCSI flatbed scan-
ners.
At present, the following scanners should work with this backend:
Model: Status
---------------------- ------
Devcom 9636PRO OK
Devcom 9636S Untested
Devcom 9630S Untested
ScanAce 1236S Untested
ScanAce 1230S Untested
ScanAce II Untested
ScanAce III OK
ScanAce Plus Untested
ScanAce II Plus Untested
ScanAce III Plus Untested
ScanAce V Untested
ScanAce ScanMedia Untested
ScanAce ScanMedia II Untested
ScanAce 630S Untested
ScanAce 636S Untested
JetScan 630 OK
JetScan 636PRO Untested
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/pie.conf</I>
The backend configuration file
<I>/usr/local/lib/sane/libsane-pie.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-pie.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>
</PRE>
<H2>CONTACT AND BUG-REPORTS</H2><PRE>
Please send any information and bug-reports to:
<B>Simon</B> <B>Munton</B> <B>&lt;simon@munton.demon.co.uk&gt;</B>
sane-backends 1.0.12-cvs 7 Sept 2000 <B><A HREF="sane-pie.5.html">sane-pie(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>

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

@ -0,0 +1,146 @@
<HTML>
<HEAD>
<TITLE>sane-pint.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-pint.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-pint.5.html">sane-pint(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-pint.5.html">sane-pint(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-pint - SANE backend for scanners that use the PINT device driver
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-pint</B> library implements a SANE (Scanner Access Now Easy) back-
end that provides generic access to hand-held and flatbed scanners
using the PINT (PINT Is Not Twain) device driver. The PINT driver is
being actively developed on the OpenBSD platform, and has been ported
to a few other *nix-like operating systems.
PINT is designed to provide an <B><A HREF="ioctl.2.html">ioctl(2)</A></B> interface to many different
scanner types. However, this backend has only been tested with flatbed
single-pass scanners, and more work will probably be required to get it
to use other scanner types successfully.
If have successfully used the PINT driver with your scanner, but it
does not work using this SANE backend, please let us know. To do this,
send a mail with the relevant information for your scanner to
<I>sane-devel@mostang.com</I>. Have a look at
http://www.mostang.com/sane/mail.html concerning subscription to sane-
devel.
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form:
<I>special</I>
Where <I>special</I> is the UNIX path-name for the special device that corre-
sponds to the scanner. The special device name must be a PINT device
or a symlink to such a device. For example, under NetBSD or OpenBSD,
such a device name could be <I>/dev/ss0</I> or <I>/dev/scan0</I>.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>pint.conf</I>. file is a list of device names that
correspond to PINT scanners. Empty lines and lines starting with a
hash mark (#) are ignored. A sample configuration file is shown below:
/dev/scanner
# this is a comment
/dev/ss1
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/pint.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-pint.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-pint.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_PINT</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
E.g., a value of 128 requests all debug output to be printed.
Smaller levels reduce verbosity.
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>
</PRE>
<H2>AUTHOR</H2><PRE>
Gordon Matzigkeit, adapted from existing backends written by David Mos-
berger.
</PRE>
<H2>BUGS</H2><PRE>
There are minor roundoff errors when adjusting the ranges, since PINT
uses units of 1/1200 of an inch, and SANE normally uses millimeters.
Symptoms of these errors are skewed images. This should really be
fixed (no pun intended) as soon as possible, but I just don't know/care
enough about fixed-point representation and roundoff errors to do this
correctly. Workaround: use inches as the scanning unit, and everything
usually works fine.
The PINT 0.5e interface does not provide a way to determine valid
ranges for DPI, modes, and scan sizes. So, the SANE backend queries
the PINT device, and dynamically discovers valid ranges by doing a
binary search. This means that the driver takes longer to initialize
than seems necessary.
Resetting the scanner does not seem to work (at least not on my HP
ScanJet 4p). For that reason, the driver sends a SCIOCRESTART, then
gobbles up any remaining input until it hits EOF.
Not all of the scanners have been identified (i.e. whether they are
flatbed or handheld).
X and Y resolutions are assumed to be the same.
No testing has been done on three-pass or handheld scanners, or with
Automatic Document Feeder support.
sane-backends 1.0.12-cvs 13 May 1998 <B><A HREF="sane-pint.5.html">sane-pint(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>

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

@ -0,0 +1,501 @@
<HTML>
<HEAD>
<TITLE>sane-plustek.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-plustek.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-plustek - SANE backend for Plustek parallel port and LM983[1/2/3]
based USB flatbed scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-plustek</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to Plustek parallel port and USB flatbed
scanners. The USB support is part of the SANE package but for usage
with parallel port scanners you will need a kernel module, called
pt_drv which currently can be downloaded from
<B>http://www.gjaeger.de/scanner/plustek.html</B>
<B>!!!Please</B> <B>note</B> <B>that</B> <B>you</B> <B>need</B> <B>the</B> <B>kernel</B> <B>module</B> <B>only</B> <B>for</B> <B>parallel</B> <B>port</B>
<B>scanners!!!</B>
</PRE>
<H2>PARALLEL PORT SUPPORT</H2><PRE>
At present, the following scanners should work with this backend and
the corresponding kernel module:
<B>PLUSTEK</B> <B>SCANNERS</B>
Parallelport Model: ASIC: Properties:
---------------------- ----- ------------------------
OpticPro PT12 98003 600x1200 dpi 36bit 512Kb
OpticPro P12 98003 600x1200 dpi 36bit 512Kb
OpticPro 9636T/12000T 98001 600x1200 dpi 36bit 512Kb
OpticPro 12000P Turbo 98001 600x1200 dpi 36bit 512Kb
OpticPro 9636P+/Turbo 98001 600x1200 dpi 36bit 512Kb
OpticPro 9636P 96003 600x1200 dpi 36bit 128Kb
OpticPro 12000P/96000P 96003 600x1200 dpi 36bit 128Kb
OpticPro 1236P 96003 600x1200 dpi 30bit 128Kb
OpticPro 9600P 96003 600x1200 dpi 30bit 128Kb
OpticPro 9630P/FBIV 96003 600x1200 dpi 30bit 128Kb
OpticPro 9630PL (14") 96003 600x1200 dpi 30bit 128Kb
OpticPro A3I 96003 400x800 dpi 36bit 128Kb
OpticPro 600P/6000P 96003 300x600 dpi 30bit 32Kb
OpticPro 4831P 96003 300x600 dpi 30bit 32Kb
OpticPro 4830P/FBIII 96003 300x600 dpi 30bit 32Kb
OpticPro 4800P/FBII 96001 300x600 dpi 24bit 32Kb
<B>PRIMAX</B> <B>SCANNERS</B>
There are some scanners sold by Primax, but they are in fact Plustek
devices. These scanners are also supported. The following table will
show the relationship:
Model: Plustek Model: Remarks:
--------------------------- -------------- ------------
Colorado 4800 OpticPro 4800 not tested
Compact 4800 Direct OpticPro 600 mov=2
Compact 4800 Direct 30bit OpticPro 4830 mov=7
Compact 9600 Direct 30bit OpticPro 9630 works
<B>GENIUS</B> <B>SCANNERS</B>
The following devices are sold as Genius Scanners, but are in fact
Plustek devices. The table will show the relationship:
Model: Remarks:
--------------------------- ----------------------------
Colorpage Vivid III V2 Like P12 but has two buttons
and Wolfson DAC
<B>ARIES</B> <B>SCANNERS</B>
There's one scanner sold as Aries Scanner, but is in fact a Plustek
device. The following table will show the relationship:
Model: Plustek Model: Remarks:
--------------------------- -------------- ------------
Scan-It 4800 OpticPro 600 mov=2
<B>BrightScan</B> <B>SCANNERS</B>
There's one scanner sold as BrightScan OpticPro Scanner, this is also
rebadged Plustek device. The following table will show the relation-
ship:
Model: Remarks:
--------------------------- ----------------------------
BrightScan OpticPro OpticPro P12
</PRE>
<H2>USB SUPPORT</H2><PRE>
The Backend is able to support USB scanner based on the National Semi-
conductor chipset LM9831, LM9832 and LM9833. The following tables show
various devices which are currently reported to work. If your Plustek
scanner has another Product ID, then the device is <B>NOT</B> supported, as it
contains unsupported ASICs inside.
Vendor Plustek - ID: 0x07B3
----------------------------------------------------------
USB Model: ASIC: Properties: Prod-ID
----------------------------------------------------------
OpticPro U12 LM9831 600x1200dpi 42bit 512Kb 0x0010
OpticPro UT12 LM9831 600x1200dpi 42bit 512Kb 0x0013
OpticPro UT12 LM9832 600x1200dpi 42bit 512Kb 0x0017
OpticPro UT16 LM9832 600x1200dpi 42bit 512Kb 0x0017
OpticPro U24 LM9831 1200x2400dpi 42bit 2Mb 0x0011
OpticPro U24 LM9832 1200x2400dpi 42bit 2Mb 0x0015
OpticPro UT24 LM9832 1200x2400dpi 42bit 2Mb 0x0017
Vendor KYE/Genius - ID: 0x0458
----------------------------------------------------------
USB Model: ASIC: Properties: Prod-ID
----------------------------------------------------------
Colorpage HR6 V2 LM9832 600x1200dpi 42bit 512Kb 0x2007
Colorpage HR6 V2 LM9832 600x1200dpi 42bit 512Kb 0x2008
Colorpage HR6A LM9832 600x1200dpi 42bit 512Kb 0x2009
Colorpage HR7 LM9832 600x1200dpi 42bit 512Kb 0x2013
Colorpage HR7LE LM9832 600x1200dpi 42bit 512Kb 0x2015
Colorpage HR6X LM9832 600x1200dpi 42bit 512Kb 0x2016
Vendor Hewlett-Packard - ID: 0x03F0
----------------------------------------------------------
USB Model: ASIC: Properties: Prod-ID
----------------------------------------------------------
ScanJet 2100C LM9831 600x1200dpi 42bit 512Kb 0x0505
ScanJet 2200C LM9832 600x1200dpi 42bit 512Kb 0x0605
Vendor Mustek - ID: 0x0400
----------------------------------------------------------
USB Model: ASIC: Properties: Prod-ID
----------------------------------------------------------
BearPaw 1200 LM9831 600x1200dpi 42bit 512Kb 0x1000
BearPaw 2400 LM9832 1200x2400dpi 42bit 2Mb 0x1001
Vendor UMAX - ID: 0x1606
----------------------------------------------------------
USB Model: ASIC: Properties: Prod-ID
----------------------------------------------------------
UMAX 3400/3450 LM9832 600x1200dpi 42bit 512Kb 0x0060
UMAX 5400 LM9832 1200x2400dpi 42bit 512Kb 0x0160
Vendor COMPAQ - ID: 0x049F
----------------------------------------------------------
USB Model: ASIC: Properties: Prod-ID
----------------------------------------------------------
S4-100 LM9832 600x1200dpi 42bit 512Kb 0x001A
Vendor Epson - ID: 0x04B8
----------------------------------------------------------
USB Model: ASIC: Properties: Prod-ID
----------------------------------------------------------
Perfection 1250 LM9832 1200x2400dpi 42bit 512Kb 0x010F
Perfection 1260 LM9832 1200x2400dpi 42bit 512Kb 0x011D
Vendor CANON - ID: 0x04A9
----------------------------------------------------------
USB Model: ASIC: Properties: Prod-ID
----------------------------------------------------------
CanoScan N650/656U LM9832 600x1200dpi 42bit 512Kb 0x2206
CanoScan N1220U LM9832 1200x2400dpi 42bit 512Kb 0x2207
CanoScan N670/676U LM9833 600x1200dpi 48bit 512Kb 0x220D
CanoScan N1240U LM9833 1200x2400dpi 48bit 512Kb 0x220E
CanoScan LIDE20 LM9833 600x1200dpi 48bit 512Kb 0x220D
CanoScan LIDE30 LM9833 1200x2400dpi 48bit 512Kb 0x220E
</PRE>
<H2>OTHER PLUSTEK SCANNERS</H2><PRE>
The SCSI scanner OpticPro 19200S is a rebadged Artec AM12S scanner and
is supported by the <B>Artec</B> backend.
Only the National Semiconductor LM9831/2 based devices of Plustek are
supported by this driver. Older versions of the U12, the UT12, the
U1212 and U1248 (GrandTech chipset) are not supported.
Model Chipset backend
---------------------------
U1248 GrandTech gt68xx
UT16B GrandTech gt68xx
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects a default device called:
<I>/dev/pt</I><B>_</B><I>drv</I>
This default device will be used, if no configuration file can be
found.
The device-driver is currently not part of the SANE distribution. It
has to be downloaded from:
<B>http://www.gjaeger.de/scanner/plustek.html</B>
See the INSTALL file there for a proper setup. Currently only Linux is
supported by this driver (Kernel 2.2.x and higher).
As the backend and the driver support up to four devices per system, it
is possible to specify them in the configuration file
<I>/usr/local/etc/sane.d/plustek.conf</I>
See the plustek.conf file for examples.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The configuration of this backend can be divided into two sections:
<B>CONFIGURATION</B> <B>-</B> <B>parallel</B> <B>port</B> <B>scanner</B>
<B>CONFIGURATION</B> <B>-</B> <B>USB</B> <B>scanner</B>
Please make sure, that the configuration matches the real world, namely
your configuration. And note again, .I pt_drv is only needed
</PRE>
<H2>CONFIGURATION - PARALLEL PORT SCANNER</H2><PRE>
Beside the kernel-module options, which are described below, you need
to enable the parallel port device in the configuration file
<I>/usr/local/etc/sane.d/plustek.conf</I>
For a proper setup, you will need at least two entries:
<I>[parport]</I>
<I>device</I> <I>/dev/pt</I><B>_</B><I>drv</I>
<I>parport</I> tells the backend, that the following devicename (here
<I>/dev/pt</I><B>_</B><I>drv</I> ) has to be interpreted as parallel port scanner device.
To have this device, you will need to setup the kernel module. As the
driver is a loadable kernel module, it is configured by invoking insmod
with the appropriate parameters or appending the options to the file
<B>/etc/conf.modules</B>
<B>The</B> <B>Options:</B>
lampoff=lll
The value <I>lll</I> tells the driver, after how many seconds to
switch-off the lamp(s). The default value is 180. 0 will dis-
able this feature.
<B>HINT:</B> Do not use a value that is too small, because often
switching on/off the lamps will reduce their lifetime.
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.
warmup=www
<I>www</I> specifies the time in seconds, how long a lamp has to be on,
until the driver will start to scan. The default value is 30.
lOffonEnd=e
<I>e</I> specifies the behaviour when unloading the driver, 1 --&gt;
switch lamps off, 0 --&gt; do not change lamp status
slowIO=s
<I>s</I> specifies which I/O functions the driver should use, 1 --&gt; use
delayed functions, 0 --&gt; use the non-delayed ones
forceMode=fm
<I>fm</I> specifies port mode which should be used, 0 --&gt; autodetec-
tion, 1 --&gt; use SPP mode and 2 --&gt; use EPP mode
mov=m
<I>m</I> =0 - default: no override
<I>m</I> =1 - OpticPro 9630PL override (works if OP9630
has been detected) forces legal size (14")
<I>m</I> =2 - Primax 4800Direct override (works if OP600
has been detected) swaps red/green color
<I>m</I> =3 - OpticPro 9636 override (works if OP9636 has
been detected) disables backends
transparency/negativ capabilities
<I>m</I> =4 - OpticPro 9636P override (works if OP9636 has
been detected) disables backends
transparency/negativ capabilities
<I>m</I> =5 - OpticPro A3I override (works if OP12000 has
been detected) enables A3 scanning
<I>m</I> =6 - OpticPro 4800P override (works if OP600
has been detected) swaps red/green color
<I>m</I> =7 - Primax 4800Direct 30bit override (works if OP4830
has been detected)
Sample entry for file <B>/etc/modules.conf</B> :
<I>alias</I> <I>char-major-40</I> <I>pt</I><B>_</B><I>drv</I>
<I>pre-install</I> <I>pt</I><B>_</B><I>drv</I> <I>modprobe</I> <I>-k</I> <I>parport</I>
<I>options</I> <I>pt</I><B>_</B><I>drv</I> <I>lampoff=180</I> <I>warmup=15</I> <I>port=0x378</I> <I>lOffonEnd=0</I> <I>mov=0</I>
<I>slowIO=0</I> <I>forceMode=0</I>
For multidevice support, simply add values separated by commas to the
different options
<I>options</I> <I>pt</I><B>_</B><I>drv</I> <I>port=0x378,0x278</I> <I>mov=0,4</I> <I>slowIO=0,1</I> <I>forceMode=0,1</I>
Remember to call depmod after changing /etc/conf.modules.
<B>PARALLEL</B> <B>PORT</B> <B>MODES</B>
The current driver works best, when the parallel port has been set to
EPP-mode. When detecting any other mode such as ECP or PS/2 the driver
tries to set to a faster, supported mode. If this fails, it will use
the SPP mode, as this mode should work with all Linux supported paral-
lel ports.
Former Plustek scanner models (4830, 9630) supplied a ISA parallel port
adapter card. This card is <B>not</B> supported by the driver.
The ASIC 96001/3 based models have sometimes trouble with high resolu-
tion modes. If you encounter sporadic corrupted images (parts dupli-
cated or shifted horizontally) kill all other applications before scan-
ning and (if sufficient memory available) disable swapping.
</PRE>
<H2>CONFIGURATION - USB SCANNER</H2><PRE>
To use the USB device with this backend, you need at least two entries
in the configuration file
<I>/usr/local/etc/sane.d/plustek.conf</I>
<I>[usb]</I> <I>vendor-id</I> <I>product-id</I>
<I>device</I> <I>/dev/usbscanner</I>
<I>usb</I> tells the backend, that the following devicename (here
<I>/dev/usbscanner</I> ) has to be interpreted as USB scanner device. If ven-
dor- and product-id has not been specified, the backend tries to detect
this by its own. If device ist set to <I>auto</I>
then the next matching device is used.
<B>The</B> <B>Options:</B>
option warmup t
<I>t</I> specifies the warmup period in seconds
option lampOff t
<I>t</I> is the time in seconds for switching off the lamps in standby
mode
option lOffonEnd b
<I>b</I> specifies the behaviour when closing the backend, 1 --&gt; switch
lamps off, 0 --&gt; do not change lamp status
option invertNegatives b
<I>b</I> 0 --&gt; do not invert the picture during negativ scans, 1 --&gt;
invert picture
option skipCalibration b
<I>b</I> 0 --&gt; perform calibration, 1 --&gt; skip calibration (only non
Plustek devices)
option enableTPA b
<I>b</I> 0 --&gt; default behaviour, specified by the internal tables, 1
--&gt; override internal tables and allow TPA mode (EPSON only)
option posOffX x
option posOffY y
option tpaOffX x
option tpaOffY y
option negOffX x
option negOffY y
<I>x</I> <I>y</I> By using this settings, the user can adjust the given image
positions. <B>Please</B> <B>note,</B> <B>that</B> <B>there's</B> <B>no</B> <B>internal</B> <B>range</B> <B>checking</B>
<B>for</B> <B>this</B> <B>feature.</B>
option posShadingY p
option tpaShadingY p
option negShadingY p
<I>p</I> overrides the internal shading position. The values are in
steps. <B>Please</B> <B>note,</B> <B>that</B> <B>there's</B> <B>no</B> <B>internal</B> <B>range</B> <B>checking</B> <B>for</B>
<B>this</B> <B>feature.</B>
option redGamma r
option greenGamma g
option blueGamma b
option grayGamma gr
<I>r</I> <I>g</I> <I>b</I> <I>gr</I>
By using these values, the internal linear gamma table (r,g,b,gr = 1.0)
can be adjusted.
option red_gain r
option green_gain g
option blue_gain b
<I>r</I> <I>g</I> <I>b</I> These values can be used to adjust the internally detected
gain values of the AFE for each channel. The range is between 0
and 63.
See the plustek.conf file for examples.
<B>Note:</B>
You have to make sure, that the USB subsystem is loaded correctly and
the module <I>scanner</I> has been loaded too. To make this module recognize
your scanner, you might have to add the following line to your
<B>/etc/modules.conf</B> :
<I>options</I> <I>scanner</I> <I>vendor=0x7b3</I> <I>product=0x17</I>
If you're not sure about the vendor and product id of your device, sim-
ply load the USB subsystem and plug in your scanner. Then do a <I>cat</I>
<I>/proc/bus/usb/devices</I> and look for the scanner.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/plustek.conf</I>
The backend configuration file
<I>/usr/local/lib/sane/libsane-plustek.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-plustek.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
<I>/lib/modules/&lt;Kernel-Version&gt;/misc/pt</I><B>_</B><I>drv.o</I>
The Linux Kernelmodule.
</PRE>
<H2>CONTACT AND BUG-REPORTS</H2><PRE>
Please send any information and bug-reports to:
<B>Plustek</B> <B>Driver</B> <B>Mailing</B> <B>List</B> <B>&lt;plustek@linuxhacker.org&gt;</B>
or directly to:
<B>Gerhard</B> <B>Jaeger</B> <B>&lt;gerhard@gjaeger.de&gt;</B>
Additional info and hints can be obtained from our
Mailing-List archive at:
<B>http://www.linuxhacker.org/cgi-bin/ezmlm-cgi/3</B>
or directly from the projects' homepage at:
<B>http://www.gjaeger.de/scanner/plustek.html</B>
To obtain debug messages from the backend, please set the environment-
variable <I>SANE</I><B>_</B><I>DEBUG</I><B>_</B><I>PLUSTEK</I> before calling your favorite scan-frontend
(i.e. xscanimage).
<B>i.e.:</B> <B>export</B> <B>SANE_DEBUG_PLUSTEK=20</B> <B>;</B> <B>xscanimage</B>
The value controls the verbosity of the backend. Please note, that val-
ues greater than 19 force the backend to output raw data files, which
could be rather large. The ending of these files is ".raw". For prob-
lem reports it should be enough the set the verbosity to 13.
</PRE>
<H2>KNOWN BUGS & RESTRICTIONS</H2><PRE>
* The Halftoning works, but the quality is poor
* Printers (especially HP models) will start to
print during scanning. This in fact is a problem
to other printers too, using bidirectional protocol
(see www.plustek.com (TAIWAN) page for further details)
* The driver does not support these manic scalings up
to 16 times the physical resolution. The only scaling
is done on resolutions between the physical resolution
of the 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 800dpi steps.
* On some devices, the pictures seems to be bluished
ASIC 98001 based models:
* The 300dpi transparency and negative mode does not work
correctly.
* There is currently no way to distinguish a model with
and without transpareny unit.
* The scanned images seem to be too dark (P9636T)
ASIC 96003/1 based models:
* 30bit mode is currently not supported.
* On low-end systems and under heavy system load, the
driver will loosing data, this might causes the sensor
to hit the scan-bed and/or the picture is corrupted.
* The scanspeed on 600x1200 dpi models is slow.
* The scanquality of the A3I is poor
USB models:
* 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.
* Negative scanning quality is poor.
sane-backends 1.0.12-cvs 17 September 2003 <B><A HREF="sane-plustek.5.html">sane-plustek(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>

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

@ -0,0 +1,501 @@
<HTML>
<HEAD>
<TITLE>sane-plustek_pp.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-plustek_pp.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-plustek - SANE backend for Plustek parallel port and LM983[1/2/3]
based USB flatbed scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-plustek</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to Plustek parallel port and USB flatbed
scanners. The USB support is part of the SANE package but for usage
with parallel port scanners you will need a kernel module, called
pt_drv which currently can be downloaded from
<B>http://www.gjaeger.de/scanner/plustek.html</B>
<B>!!!Please</B> <B>note</B> <B>that</B> <B>you</B> <B>need</B> <B>the</B> <B>kernel</B> <B>module</B> <B>only</B> <B>for</B> <B>parallel</B> <B>port</B>
<B>scanners!!!</B>
</PRE>
<H2>PARALLEL PORT SUPPORT</H2><PRE>
At present, the following scanners should work with this backend and
the corresponding kernel module:
<B>PLUSTEK</B> <B>SCANNERS</B>
Parallelport Model: ASIC: Properties:
---------------------- ----- ------------------------
OpticPro PT12 98003 600x1200 dpi 36bit 512Kb
OpticPro P12 98003 600x1200 dpi 36bit 512Kb
OpticPro 9636T/12000T 98001 600x1200 dpi 36bit 512Kb
OpticPro 12000P Turbo 98001 600x1200 dpi 36bit 512Kb
OpticPro 9636P+/Turbo 98001 600x1200 dpi 36bit 512Kb
OpticPro 9636P 96003 600x1200 dpi 36bit 128Kb
OpticPro 12000P/96000P 96003 600x1200 dpi 36bit 128Kb
OpticPro 1236P 96003 600x1200 dpi 30bit 128Kb
OpticPro 9600P 96003 600x1200 dpi 30bit 128Kb
OpticPro 9630P/FBIV 96003 600x1200 dpi 30bit 128Kb
OpticPro 9630PL (14") 96003 600x1200 dpi 30bit 128Kb
OpticPro A3I 96003 400x800 dpi 36bit 128Kb
OpticPro 600P/6000P 96003 300x600 dpi 30bit 32Kb
OpticPro 4831P 96003 300x600 dpi 30bit 32Kb
OpticPro 4830P/FBIII 96003 300x600 dpi 30bit 32Kb
OpticPro 4800P/FBII 96001 300x600 dpi 24bit 32Kb
<B>PRIMAX</B> <B>SCANNERS</B>
There are some scanners sold by Primax, but they are in fact Plustek
devices. These scanners are also supported. The following table will
show the relationship:
Model: Plustek Model: Remarks:
--------------------------- -------------- ------------
Colorado 4800 OpticPro 4800 not tested
Compact 4800 Direct OpticPro 600 mov=2
Compact 4800 Direct 30bit OpticPro 4830 mov=7
Compact 9600 Direct 30bit OpticPro 9630 works
<B>GENIUS</B> <B>SCANNERS</B>
The following devices are sold as Genius Scanners, but are in fact
Plustek devices. The table will show the relationship:
Model: Remarks:
--------------------------- ----------------------------
Colorpage Vivid III V2 Like P12 but has two buttons
and Wolfson DAC
<B>ARIES</B> <B>SCANNERS</B>
There's one scanner sold as Aries Scanner, but is in fact a Plustek
device. The following table will show the relationship:
Model: Plustek Model: Remarks:
--------------------------- -------------- ------------
Scan-It 4800 OpticPro 600 mov=2
<B>BrightScan</B> <B>SCANNERS</B>
There's one scanner sold as BrightScan OpticPro Scanner, this is also
rebadged Plustek device. The following table will show the relation-
ship:
Model: Remarks:
--------------------------- ----------------------------
BrightScan OpticPro OpticPro P12
</PRE>
<H2>USB SUPPORT</H2><PRE>
The Backend is able to support USB scanner based on the National Semi-
conductor chipset LM9831, LM9832 and LM9833. The following tables show
various devices which are currently reported to work. If your Plustek
scanner has another Product ID, then the device is <B>NOT</B> supported, as it
contains unsupported ASICs inside.
Vendor Plustek - ID: 0x07B3
----------------------------------------------------------
USB Model: ASIC: Properties: Prod-ID
----------------------------------------------------------
OpticPro U12 LM9831 600x1200dpi 42bit 512Kb 0x0010
OpticPro UT12 LM9831 600x1200dpi 42bit 512Kb 0x0013
OpticPro UT12 LM9832 600x1200dpi 42bit 512Kb 0x0017
OpticPro UT16 LM9832 600x1200dpi 42bit 512Kb 0x0017
OpticPro U24 LM9831 1200x2400dpi 42bit 2Mb 0x0011
OpticPro U24 LM9832 1200x2400dpi 42bit 2Mb 0x0015
OpticPro UT24 LM9832 1200x2400dpi 42bit 2Mb 0x0017
Vendor KYE/Genius - ID: 0x0458
----------------------------------------------------------
USB Model: ASIC: Properties: Prod-ID
----------------------------------------------------------
Colorpage HR6 V2 LM9832 600x1200dpi 42bit 512Kb 0x2007
Colorpage HR6 V2 LM9832 600x1200dpi 42bit 512Kb 0x2008
Colorpage HR6A LM9832 600x1200dpi 42bit 512Kb 0x2009
Colorpage HR7 LM9832 600x1200dpi 42bit 512Kb 0x2013
Colorpage HR7LE LM9832 600x1200dpi 42bit 512Kb 0x2015
Colorpage HR6X LM9832 600x1200dpi 42bit 512Kb 0x2016
Vendor Hewlett-Packard - ID: 0x03F0
----------------------------------------------------------
USB Model: ASIC: Properties: Prod-ID
----------------------------------------------------------
ScanJet 2100C LM9831 600x1200dpi 42bit 512Kb 0x0505
ScanJet 2200C LM9832 600x1200dpi 42bit 512Kb 0x0605
Vendor Mustek - ID: 0x0400
----------------------------------------------------------
USB Model: ASIC: Properties: Prod-ID
----------------------------------------------------------
BearPaw 1200 LM9831 600x1200dpi 42bit 512Kb 0x1000
BearPaw 2400 LM9832 1200x2400dpi 42bit 2Mb 0x1001
Vendor UMAX - ID: 0x1606
----------------------------------------------------------
USB Model: ASIC: Properties: Prod-ID
----------------------------------------------------------
UMAX 3400/3450 LM9832 600x1200dpi 42bit 512Kb 0x0060
UMAX 5400 LM9832 1200x2400dpi 42bit 512Kb 0x0160
Vendor COMPAQ - ID: 0x049F
----------------------------------------------------------
USB Model: ASIC: Properties: Prod-ID
----------------------------------------------------------
S4-100 LM9832 600x1200dpi 42bit 512Kb 0x001A
Vendor Epson - ID: 0x04B8
----------------------------------------------------------
USB Model: ASIC: Properties: Prod-ID
----------------------------------------------------------
Perfection 1250 LM9832 1200x2400dpi 42bit 512Kb 0x010F
Perfection 1260 LM9832 1200x2400dpi 42bit 512Kb 0x011D
Vendor CANON - ID: 0x04A9
----------------------------------------------------------
USB Model: ASIC: Properties: Prod-ID
----------------------------------------------------------
CanoScan N650/656U LM9832 600x1200dpi 42bit 512Kb 0x2206
CanoScan N1220U LM9832 1200x2400dpi 42bit 512Kb 0x2207
CanoScan N670/676U LM9833 600x1200dpi 48bit 512Kb 0x220D
CanoScan N1240U LM9833 1200x2400dpi 48bit 512Kb 0x220E
CanoScan LIDE20 LM9833 600x1200dpi 48bit 512Kb 0x220D
CanoScan LIDE30 LM9833 1200x2400dpi 48bit 512Kb 0x220E
</PRE>
<H2>OTHER PLUSTEK SCANNERS</H2><PRE>
The SCSI scanner OpticPro 19200S is a rebadged Artec AM12S scanner and
is supported by the <B>Artec</B> backend.
Only the National Semiconductor LM9831/2 based devices of Plustek are
supported by this driver. Older versions of the U12, the UT12, the
U1212 and U1248 (GrandTech chipset) are not supported.
Model Chipset backend
---------------------------
U1248 GrandTech gt68xx
UT16B GrandTech gt68xx
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects a default device called:
<I>/dev/pt</I><B>_</B><I>drv</I>
This default device will be used, if no configuration file can be
found.
The device-driver is currently not part of the SANE distribution. It
has to be downloaded from:
<B>http://www.gjaeger.de/scanner/plustek.html</B>
See the INSTALL file there for a proper setup. Currently only Linux is
supported by this driver (Kernel 2.2.x and higher).
As the backend and the driver support up to four devices per system, it
is possible to specify them in the configuration file
<I>/usr/local/etc/sane.d/plustek.conf</I>
See the plustek.conf file for examples.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The configuration of this backend can be divided into two sections:
<B>CONFIGURATION</B> <B>-</B> <B>parallel</B> <B>port</B> <B>scanner</B>
<B>CONFIGURATION</B> <B>-</B> <B>USB</B> <B>scanner</B>
Please make sure, that the configuration matches the real world, namely
your configuration. And note again, .I pt_drv is only needed
</PRE>
<H2>CONFIGURATION - PARALLEL PORT SCANNER</H2><PRE>
Beside the kernel-module options, which are described below, you need
to enable the parallel port device in the configuration file
<I>/usr/local/etc/sane.d/plustek.conf</I>
For a proper setup, you will need at least two entries:
<I>[parport]</I>
<I>device</I> <I>/dev/pt</I><B>_</B><I>drv</I>
<I>parport</I> tells the backend, that the following devicename (here
<I>/dev/pt</I><B>_</B><I>drv</I> ) has to be interpreted as parallel port scanner device.
To have this device, you will need to setup the kernel module. As the
driver is a loadable kernel module, it is configured by invoking insmod
with the appropriate parameters or appending the options to the file
<B>/etc/conf.modules</B>
<B>The</B> <B>Options:</B>
lampoff=lll
The value <I>lll</I> tells the driver, after how many seconds to
switch-off the lamp(s). The default value is 180. 0 will dis-
able this feature.
<B>HINT:</B> Do not use a value that is too small, because often
switching on/off the lamps will reduce their lifetime.
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.
warmup=www
<I>www</I> specifies the time in seconds, how long a lamp has to be on,
until the driver will start to scan. The default value is 30.
lOffonEnd=e
<I>e</I> specifies the behaviour when unloading the driver, 1 --&gt;
switch lamps off, 0 --&gt; do not change lamp status
slowIO=s
<I>s</I> specifies which I/O functions the driver should use, 1 --&gt; use
delayed functions, 0 --&gt; use the non-delayed ones
forceMode=fm
<I>fm</I> specifies port mode which should be used, 0 --&gt; autodetec-
tion, 1 --&gt; use SPP mode and 2 --&gt; use EPP mode
mov=m
<I>m</I> =0 - default: no override
<I>m</I> =1 - OpticPro 9630PL override (works if OP9630
has been detected) forces legal size (14")
<I>m</I> =2 - Primax 4800Direct override (works if OP600
has been detected) swaps red/green color
<I>m</I> =3 - OpticPro 9636 override (works if OP9636 has
been detected) disables backends
transparency/negativ capabilities
<I>m</I> =4 - OpticPro 9636P override (works if OP9636 has
been detected) disables backends
transparency/negativ capabilities
<I>m</I> =5 - OpticPro A3I override (works if OP12000 has
been detected) enables A3 scanning
<I>m</I> =6 - OpticPro 4800P override (works if OP600
has been detected) swaps red/green color
<I>m</I> =7 - Primax 4800Direct 30bit override (works if OP4830
has been detected)
Sample entry for file <B>/etc/modules.conf</B> :
<I>alias</I> <I>char-major-40</I> <I>pt</I><B>_</B><I>drv</I>
<I>pre-install</I> <I>pt</I><B>_</B><I>drv</I> <I>modprobe</I> <I>-k</I> <I>parport</I>
<I>options</I> <I>pt</I><B>_</B><I>drv</I> <I>lampoff=180</I> <I>warmup=15</I> <I>port=0x378</I> <I>lOffonEnd=0</I> <I>mov=0</I>
<I>slowIO=0</I> <I>forceMode=0</I>
For multidevice support, simply add values separated by commas to the
different options
<I>options</I> <I>pt</I><B>_</B><I>drv</I> <I>port=0x378,0x278</I> <I>mov=0,4</I> <I>slowIO=0,1</I> <I>forceMode=0,1</I>
Remember to call depmod after changing /etc/conf.modules.
<B>PARALLEL</B> <B>PORT</B> <B>MODES</B>
The current driver works best, when the parallel port has been set to
EPP-mode. When detecting any other mode such as ECP or PS/2 the driver
tries to set to a faster, supported mode. If this fails, it will use
the SPP mode, as this mode should work with all Linux supported paral-
lel ports.
Former Plustek scanner models (4830, 9630) supplied a ISA parallel port
adapter card. This card is <B>not</B> supported by the driver.
The ASIC 96001/3 based models have sometimes trouble with high resolu-
tion modes. If you encounter sporadic corrupted images (parts dupli-
cated or shifted horizontally) kill all other applications before scan-
ning and (if sufficient memory available) disable swapping.
</PRE>
<H2>CONFIGURATION - USB SCANNER</H2><PRE>
To use the USB device with this backend, you need at least two entries
in the configuration file
<I>/usr/local/etc/sane.d/plustek.conf</I>
<I>[usb]</I> <I>vendor-id</I> <I>product-id</I>
<I>device</I> <I>/dev/usbscanner</I>
<I>usb</I> tells the backend, that the following devicename (here
<I>/dev/usbscanner</I> ) has to be interpreted as USB scanner device. If ven-
dor- and product-id has not been specified, the backend tries to detect
this by its own. If device ist set to <I>auto</I>
then the next matching device is used.
<B>The</B> <B>Options:</B>
option warmup t
<I>t</I> specifies the warmup period in seconds
option lampOff t
<I>t</I> is the time in seconds for switching off the lamps in standby
mode
option lOffonEnd b
<I>b</I> specifies the behaviour when closing the backend, 1 --&gt; switch
lamps off, 0 --&gt; do not change lamp status
option invertNegatives b
<I>b</I> 0 --&gt; do not invert the picture during negativ scans, 1 --&gt;
invert picture
option skipCalibration b
<I>b</I> 0 --&gt; perform calibration, 1 --&gt; skip calibration (only non
Plustek devices)
option enableTPA b
<I>b</I> 0 --&gt; default behaviour, specified by the internal tables, 1
--&gt; override internal tables and allow TPA mode (EPSON only)
option posOffX x
option posOffY y
option tpaOffX x
option tpaOffY y
option negOffX x
option negOffY y
<I>x</I> <I>y</I> By using this settings, the user can adjust the given image
positions. <B>Please</B> <B>note,</B> <B>that</B> <B>there's</B> <B>no</B> <B>internal</B> <B>range</B> <B>checking</B>
<B>for</B> <B>this</B> <B>feature.</B>
option posShadingY p
option tpaShadingY p
option negShadingY p
<I>p</I> overrides the internal shading position. The values are in
steps. <B>Please</B> <B>note,</B> <B>that</B> <B>there's</B> <B>no</B> <B>internal</B> <B>range</B> <B>checking</B> <B>for</B>
<B>this</B> <B>feature.</B>
option redGamma r
option greenGamma g
option blueGamma b
option grayGamma gr
<I>r</I> <I>g</I> <I>b</I> <I>gr</I>
By using these values, the internal linear gamma table (r,g,b,gr = 1.0)
can be adjusted.
option red_gain r
option green_gain g
option blue_gain b
<I>r</I> <I>g</I> <I>b</I> These values can be used to adjust the internally detected
gain values of the AFE for each channel. The range is between 0
and 63.
See the plustek.conf file for examples.
<B>Note:</B>
You have to make sure, that the USB subsystem is loaded correctly and
the module <I>scanner</I> has been loaded too. To make this module recognize
your scanner, you might have to add the following line to your
<B>/etc/modules.conf</B> :
<I>options</I> <I>scanner</I> <I>vendor=0x7b3</I> <I>product=0x17</I>
If you're not sure about the vendor and product id of your device, sim-
ply load the USB subsystem and plug in your scanner. Then do a <I>cat</I>
<I>/proc/bus/usb/devices</I> and look for the scanner.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/plustek.conf</I>
The backend configuration file
<I>/usr/local/lib/sane/libsane-plustek.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-plustek.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
<I>/lib/modules/&lt;Kernel-Version&gt;/misc/pt</I><B>_</B><I>drv.o</I>
The Linux Kernelmodule.
</PRE>
<H2>CONTACT AND BUG-REPORTS</H2><PRE>
Please send any information and bug-reports to:
<B>Plustek</B> <B>Driver</B> <B>Mailing</B> <B>List</B> <B>&lt;plustek@linuxhacker.org&gt;</B>
or directly to:
<B>Gerhard</B> <B>Jaeger</B> <B>&lt;gerhard@gjaeger.de&gt;</B>
Additional info and hints can be obtained from our
Mailing-List archive at:
<B>http://www.linuxhacker.org/cgi-bin/ezmlm-cgi/3</B>
or directly from the projects' homepage at:
<B>http://www.gjaeger.de/scanner/plustek.html</B>
To obtain debug messages from the backend, please set the environment-
variable <I>SANE</I><B>_</B><I>DEBUG</I><B>_</B><I>PLUSTEK</I> before calling your favorite scan-frontend
(i.e. xscanimage).
<B>i.e.:</B> <B>export</B> <B>SANE_DEBUG_PLUSTEK=20</B> <B>;</B> <B>xscanimage</B>
The value controls the verbosity of the backend. Please note, that val-
ues greater than 19 force the backend to output raw data files, which
could be rather large. The ending of these files is ".raw". For prob-
lem reports it should be enough the set the verbosity to 13.
</PRE>
<H2>KNOWN BUGS & RESTRICTIONS</H2><PRE>
* The Halftoning works, but the quality is poor
* Printers (especially HP models) will start to
print during scanning. This in fact is a problem
to other printers too, using bidirectional protocol
(see www.plustek.com (TAIWAN) page for further details)
* The driver does not support these manic scalings up
to 16 times the physical resolution. The only scaling
is done on resolutions between the physical resolution
of the 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 800dpi steps.
* On some devices, the pictures seems to be bluished
ASIC 98001 based models:
* The 300dpi transparency and negative mode does not work
correctly.
* There is currently no way to distinguish a model with
and without transpareny unit.
* The scanned images seem to be too dark (P9636T)
ASIC 96003/1 based models:
* 30bit mode is currently not supported.
* On low-end systems and under heavy system load, the
driver will loosing data, this might causes the sensor
to hit the scan-bed and/or the picture is corrupted.
* The scanspeed on 600x1200 dpi models is slow.
* The scanquality of the A3I is poor
USB models:
* 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.
* Negative scanning quality is poor.
sane-backends 1.0.12-cvs 17 September 2003 <B><A HREF="sane-plustek.5.html">sane-plustek(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>

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

@ -0,0 +1,85 @@
<HTML>
<HEAD>
<TITLE>sane-pnm.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-pnm.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-pnm.5.html">sane-pnm(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-pnm.5.html">sane-pnm(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-pnm - SANE PNM image reader pseudo-backend
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-pnm</B> library implements a SANE (Scanner Access Now Easy) back-
end that provides access to PNM (Portable aNyMap files, which covers
PBM bitmap files, PGM grayscale files, and PPM pixmap files). The pur-
pose of this backend is primarly to aid in debugging of SANE frontends.
It also serves as an illustrative example of a minimal SANE backend.
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend provides two devices called <B>0</B> and <B>1.</B>
</PRE>
<H2>CONFIGURATION</H2><PRE>
No configuration required.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/lib/sane/libsane-pnm.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-pnm.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_PNM</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
E.g., a value of 128 requests all debug output to be printed.
Smaller levels reduce verbosity.
</PRE>
<H2>BUGS</H2><PRE>
If the pnm backend is installed and saned is used to allow users on
remote computers to scan on the local machine, pnm files can be read by
the remote user. This is limited to the files saned can access (usually
it's running as user "sane"). All pnm files can be read if saned runs
as root which isn't recommended anyway. The pnm backend is disabled by
default. If you want to use it, enable it with configure (see configure
--help for details). Be sure that only trusted users can access the pnm
backend over saned.
</PRE>
<H2>AUTHOR</H2><PRE>
Andreas Beck, Gordon Matzigkeit, and David Mosberger
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>
sane-backends 1.0.12-cvs 22 April 2001 <B><A HREF="sane-pnm.5.html">sane-pnm(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>

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

@ -0,0 +1,120 @@
<HTML>
<HEAD>
<TITLE>sane-qcam.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-qcam.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-qcam.5.html">sane-qcam(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-qcam.5.html">sane-qcam(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-qcam - SANE backend for Connectix QuickCam cameras
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-qcam</B> library implements a SANE (Scanner Access Now Easy) back-
end that provides access Connectix QuickCam cameras.
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form:
<I>port</I>
Where <I>port</I> is the I/O port address at which the device resides. This
address is normally specified in hexadecimal using C syntax (e.g.,
0x37b) and may be prefixed with the letter "u" (e.g., u0x37b) to force
the backend to access the camera in uni-directional mode.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>qcam.conf</I> file is a list port addresses that may be
connected to a Connectix QuickCam. Empty lines and everything starting
from a hash mark (#) up to the end of a line are ignored. A sample
configuration file is shown below:
0x37b # /dev/lp0
0x378 # /dev/lp1
u0x278 # /dev/lp2 forced in uni-directional mode
0x3bc # /dev/lp0 (alternate address)
In general, it is safest to list only the port addresses that really
correspond to a QuickCam. For example, if one of the listed addresses
actually connect to a printer, then starting up this backend will cause
the printer to perform a device reset (which is generally undesirable).
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/qcam.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-qcam.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-qcam.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_QCAM</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>AUTHOR</H2><PRE>
David Mosberger
</PRE>
<H2>BUGS</H2><PRE>
Support is currently limited to the color version of the QuickCam. The
black-and-white camera is starting to work too, but I don't believe it
works in all cases yet. Reportedly, acquiring images of certain sizes
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 camera's I/O ports.
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>
sane-backends 1.0.12-cvs 25 October 1997 <B><A HREF="sane-qcam.5.html">sane-qcam(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>

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

@ -0,0 +1,96 @@
<HTML>
<HEAD>
<TITLE>sane-ricoh.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-ricoh.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-ricoh - SANE backend for Ricoh flatbed scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-ricoh</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to the following Ricoh flatbed scanners:
IS50
IS60
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form:
<I>special</I>
Where <I>special</I> is the path-name for the special device that corresponds
to a SCSI scanner. The special device name must be a generic SCSI
device or a symlink to such a device. The program <I>sane-find-scanner</I>
helps to find out the correct device. Under Linux, such a device name
could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for
details.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/ricoh.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-ricoh.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-ricoh.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_RICOH</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_RICOH=4
</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>
</PRE>
<H2>AUTHOR</H2><PRE>
Feico W. Dillema
sane-backends 1.0.12-cvs 24 Jun 2000 <B><A HREF="sane-ricoh.5.html">sane-ricoh(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>

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

@ -0,0 +1,94 @@
<HTML>
<HEAD>
<TITLE>sane-s9036.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-s9036.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-s9036.5.html">sane-s9036(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-s9036.5.html">sane-s9036(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-s9036 - SANE backend for Siemens 9036 flatbed scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-s9036</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to Siemens 9036 flatbed scanners.
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form:
<I>special</I>
Where <I>special</I> is the path-name for the special device that corresponds
to a SCSI scanner. The special device name must be a generic SCSI
device or a symlink to such a device. The program <I>sane-find-scanner</I>
helps to find out the correct device. Under Linux, such a device name
could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for
details.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/s9036.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-s9036.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-s9036.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_S9036</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_S9036=4
</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>
</PRE>
<H2>AUTHOR</H2><PRE>
Ingo Schneider
sane-backends 1.0.12-cvs 24 Jun 2000 <B><A HREF="sane-s9036.5.html">sane-s9036(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>

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

@ -0,0 +1,158 @@
<HTML>
<HEAD>
<TITLE>sane-sceptre.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-sceptre.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-sceptre - SANE backend for SCEPTRE scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-sceptre</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to Sceptre flatbed scanners. This backend
should be considered <B>beta-quality</B> software! Please report any strange
behavior to the maintainer of the backend or to the SANE mailing list.
At present, only one scanner is known to work with this backend:
Model Connection Type
--------------------------- -------------------
Sceptre VividScan S1200 SCSI
The make of this scanner is KINPO, so other scanners from that manufac-
turer may also work (eg. the S600).
</PRE>
<H2>OPTIONS</H2><PRE>
The options the backend supports can either be selected through command
line options to programs like scanimage or through GUI elements in
xscanimage or xsane.
Valid command line options and their syntax can be listed by using
scanimage --help -d sceptre
<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
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
exports 24.
<B>--resolution</B>
selects the resolution for a scan. The scanner can do several
resolutions between 50 and 1200.
<B>--halftone-pattern</B>
selects the pattern mode that is used in Halftone mode. Valid
options are 1, 2, 3 and 4.
<B>--gamma-correction</B>
controls the scanner internal gamma correction. Valid options
are "Default", "User defined", "High density printing" "Low den-
sity printing" and "High contrast printing".
<B>--custom-gamma</B>
(color mode only) allows the user to specify a gamma table (see
the next 3 parameters).
<B>--red-gamma-table</B>
(color mode only) can be used to download a user defined gamma
table for the red channel. The table must be 256 bytes long.
<B>--green-gamma-table</B>
(color mode only) can be used to download a user defined gamma
table for the green channel. The table must be 256 bytes long.
<B>--blue-gamma-table</B>
(color mode only) can be used to download a user defined gamma
table for the blue channel. The table must be 256 bytes long.
<B>--threshold</B>
sets the threshold for black and white pixels in lineart mode.
Possible values are from 0 (darker) to 255 (lighter).
<B>--preview</B>
requests a preview scan. The resolution used for that scan is 30
dpi and the scan area is the maximum allowed. The scan mode is
user selected. The default is "no".
<B>The</B> <B>geometry</B> <B>options</B>
<B>-l</B> <B>-t</B> <B>-x</B> <B>-y</B>
control the scan area: -l sets the top left x coordinate, -t the
top left y coordinate, -x selects the width and -y the height of
the scan area. All parameters are specified in milimeters by
default.
</PRE>
<H2>CONFIGURATION FILE</H2><PRE>
The configuration file /usr/local/etc/sane.d/sceptre.conf supports only
one information: the device name to use (eg /dev/scanner).
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/lib/sane/libsane-sceptre.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-sceptre.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_SCEPTRE</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
E.g., a value of 128 requests all debug output to be printed.
Smaller levels reduce verbosity.
</PRE>
<H2>LIMITATIONS</H2><PRE>
<B>Resolutions</B>
The windows TWAIN driver can be set to any resolution between 50
to 1200 (excluding software interpolation). This backend cannot.
Only a handful of resolution are available, although they should
be numerous enough.
</PRE>
<H2>BUGS</H2><PRE>
None known.
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, <B><A HREF="xsane.1.html">xsane(1)</A></B>, <B><A HREF="sane.7.html">sane(7)</A></B>
</PRE>
<H2>AUTHOR</H2><PRE>
The package is actively maintained by Frank Zago.
http://fz.eryx.net/sane/#sceptre
sane-backends 1.0.12-cvs April 21st, 2002 <B><A HREF="sane-sceptre.5.html">sane-sceptre(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>

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

@ -0,0 +1,312 @@
<HTML>
<HEAD>
<TITLE>sane-scsi.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-scsi.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-scsi - SCSI adapter tips for scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
This manual page contains various operating-system specific tips and
tricks on how to get scanners with a SCSI interface working.
</PRE>
<H2>GENERAL INFO</H2><PRE>
For scanners with a SCSI interface, it may be necessary to edit the
appropriate backend configuration file before using SANE for the first
time. For most systems, the configuration file should list the name of
the generic SCSI device that the scanner is connected to (e.g., under
Linux, <B>/dev/sg4</B> or <B>/dev/sge</B> is such a generic SCSI device). It is cus-
tomary to create a symlink from <B>/dev/scanner</B> to the generic SCSI device
that the scanner is connected to. In this case, the configuration file
simply lists the line <B>/dev/scanner</B>. For a detailed description of each
backend's configuration file, please refer to the relevant backend man-
ual page (e.g., <B><A HREF="sane-epson.5.html">sane-epson(5)</A></B> for Epson scanners, <B><A HREF="sane-hp.5.html">sane-hp(5)</A></B> for HP
scanners, etc.).
For some operating systems (e.g. Linux and OS/2), there is an alternate
way of specifying scanner devices. This alternate way allows to iden-
tify scanners by the SCSI vendor and model string and/or by the SCSI
device address (consisting of bus number, channel number, id, and logi-
cal unit number). The syntax for specifying a scanner in this way is:
scsi <I>VENDOR</I> <I>MODEL</I> <I>TYPE</I> <I>BUS</I> <I>CHANNEL</I> <I>ID</I> <I>LUN</I>
where <I>VENDOR</I> is the SCSI vendor string, <I>MODEL</I> is the SCSI model string,
<I>TYPE</I> is type SCSI device type string, <I>BUS</I> is the SCSI bus number (named
"host" in /proc/scsi/scsi), <I>CHANNEL</I> is the SCSI channel number, <I>ID</I> is
the SCSI id, and <I>LUN</I> is the logical unit number of the scanner device.
The first two fields are strings which must be enclosed in double-
quotes if they contain any whitespace. The remaining four fields are
non-negative integer numbers. The correct values for these fields can
be found by using operating system specific tools, e.g. for Linux by
looking at the output of the command "cat /proc/scsi/scsi". To sim-
plify configuration, a field's value can be replaced with an asterisk
symbol (``*''). An asterisk has the effect that any value is allowed
for that particular field. This can have the effect that a single
scsi-line matches multiple devices. When this happens, each matching
device will be probed by the backend one by one and registered if the
backend thinks it is a compatible device. For example, the line
scsi MUSTEK MFS-06000CX Scanner 0 00 03 00
would attach the Mustek SCSI scanner with the following /proc/scsi/scsi
entry:
Host: scsi0 Channel: 00 Id: 03 Lun: 00
Vendor: MUSTEK Model: MFS-06000CX Rev: 4.04
Type: Scanner ANSI SCSI revision: 0
Usually it's sufficient to use vendor and model strings only or even
only the vendor string. The following example
scsi MUSTEK * * * * * *
would have the effect that all SCSI devices in the system with a vendor
string of MUSTEK would be probed and recognized by the backend.
If the remainder of a scsi-string consists of asterisks only, the
asterisks can be omitted. For example, the following line is equiva-
lent to the one specified previously:
scsi MUSTEK
On some platforms (e.g., OpenStep), SANE device names take a special
form. This is explained below in the relevant platform-specific sec-
tion.
When using a SCSI scanner, ensure that the access permission for the
generic SCSI device is set appropriately. We recommend to add a group
"scanner" to /etc/group which contains all users that should have
access to the scanner. The permission of the device should then be set
to allow group read and write access. For example, if the scanner is
at generic SCSI device <B>/dev/sg0</B>, then the following two commands would
set the permission correctly:
$ chgrp scanner /dev/sg0
$ chmod 660 /dev/sg0
When your system uses the device filesystem (devfs), you have to edit
<B>/etc/devfs/perms.</B> There you should search the line
REGISTER ^sg[^/]* PERMISSIONS root.root 0600
and add a new line (eg. for changing permissions of sg4):
REGISTER ^sg4 PERMISSIONS root.scanner 0660
</PRE>
<H2>FREEBSD INFO</H2><PRE>
Auto-configuration using the "scsi *" lines in the config files doesn't
seem to work. Set a link <I>/dev/scanner</I> to the appropriate /dev/uk
device.
Adaptec AHA1542CF
Reported to work fine under FreeBSD 2.2.2R with the <B>aha</B>
driver.
Adaptec 2940
Reported to work fine under FreeBSD 2.2.2.
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.
Adaptec 1505
Works on FreeBSD 2.2.5R and 3.0 using the <B>aic</B> driver,
provided that Plug-and-Play support is disabled on the
card. If there are no <I>uk</I> devices, just do a ``sh MAKEDEV
uk0'' in the <B>/dev</B> directory. The scanner should then be
accessible as <B>/dev/uk0</B> <B>if</B> <B>it</B> <B>was</B> <B>probed</B> during boot.
Tekram DC390
Reported to work fine under FreeBSD 2.2.2R with the <B>amd</B>
driver.
</PRE>
<H2>LINUX INFO</H2><PRE>
First, make sure your kernel has SCSI generic support enabled. In
``make xconfig'', this shows up under ``SCSI support-&gt;SCSI generic sup-
port''.
To keep scanning times to a minimum, it is strongly recommended to use
a large buffer size for the generic SCSI driver. From SG driver version
2.0 on, the maximum buffer size can be changed at program run time, and
there is no restriction in size. This driver version is part of the
Linux kernels from version 2.2.7 on. If the new SG driver is available
some backends (e.g. sane-umax, sane-mustek, sane-sharp) automatically
request larger scsi buffers. If a backend does not automatically
request a larger scsi buffer, set the environment variable
<B>SANE_SG_BUFFERSIZE</B> to the desired buffer size in bytes. It is not rec-
ommended to use more than 1 MB, because for large values the probabil-
ity increases that the SG driver cannot allocate the necessary
buffer(s). For ISA cards, even 1 MB might be a too large value. For a
detailed discussion of memory issues of the SG driver, see
http://www.torque.net/sg.
For Linux kernels before version 2.2.7 the size of the buffer is only
32KB. This works, but for many cheaper scanners this causes scanning
to be slower by about a factor of four than when using a size of 127KB.
Linux defines the size of this buffer by macro <B>SG_BIG_BUFF</B> in header
file <I>/usr/include/scsi/sg.h</I>. Unless a system is seriously short on
memory, it is recommended to increase this value to the maximum legal
value of 128*1024-512=130560 bytes. After changing this value, it is
necessary to recompile both the kernel (or the SCSI generic module) and
the SCSI backends. Keep in mind that this is only necessary with older
Linux kernels.
A common issue with SCSI scanners is what to do when you booted the
system while the scanner was turned off? In such a case, the scanner
won't be recognized by the kernel and SANE won't be able to access it.
Fortunately, Linux provides a simple mechanism to probe a SCSI device
on demand. Suppose you have a scanner connected to SCSI bus 2 and the
scanner has a SCSI id of 5. When the system is up and running and the
scanner is turned on, you can issue the command:
echo "scsi add-single-device 2 0 5 0" &gt; /proc/scsi/scsi
and the kernel will probe and recognize your scanner (this needs to be
done as root). It's also possible to dynamically remove a SCSI device
by using the ``remove-single-device'' command. For details, please
refer to to the SCSI-2.4-HOWTO.
Scanners are known to work with the following SCSI adapters under
Linux. This list isn't complete, usually any SCSI adapter supported by
Linux should work.
Acard/Advance SCSI adapters
Some old versions of the kernel driver (atp870u.c) cut
the inquiry information. Therefore the scanner couldn't
be detected correctly. Use a current kernel.
Adaptec AHA-1505/AHA-1542/AHA-2940
Reported to work fine with Linux since v2.0. If you
encounter kernel freezes or other unexpected behaviour
get the latest Linux kernel (2.2.17 seems to work) or
reduce SCSI buffer size to 32 kB.
ASUS SC200
Reported to work fine with Linux v2.0.
BusLogic BT958
To configure the BusLogic card, you may need to follow
these instructions (contributed by Jeremy
&lt;jeremy@xxedgexx.com&gt;): During boot, when your BusLogic
adapter is being initialized, press Ctrl-B to enter your
BusLogic adapter setup. Choose the address which your
BusLogic containing your scanner is located. Choose
``SCSI Device Configuration''. Choose ``Scan SCSI Bus''.
Choose whatever SCSI id that contains your scanner and
then choose ``View/Modify SCSI configuration''. Change
``Negotiation'' to ``async'' and change ``Disconnect'' to
``off''. Press Esc, save, and Esc again until you are
asked to reboot.
NCR/Symbios 53c400/53c400a or Domex DTC3181E/L/LE (DTCT436/436P)
ISA SCSI card
This card is supplied by Mustek (and other vendors). It's
supported since Linux 2.2. The SCSI cards are supported
by the module g_NCR5380. It's necessary to tell the ker-
nel the io port and type of card. Example for a 53c400a:
``modprobe g_NCR5380 ncr_addr=0x280 ncr_53c400a=1''.
Once the kernel detects the card, it should work all
right. However, while it should work, do not expect good
performance out of this card---it has no interrupt line
and therefore while a scan is in progress, the system
becomes almost unusable. You may change the values of
the USLEEP macros in drivers/scsi/g_NCR5380.c. Some doc-
umentation is in this file and NCR5380.c.
NCR/Symbios 810
For some scanners it may be necssary 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
ncr53c8xx. Try both if you have trouble.
For Linux kernels before 2.0.33 it may be necessary to
increase the SCSI timeout. The default timeout for the
Linux kernels before 2.0.33 is 10 seconds, which is way
too low when scanning large area. If you get messages of
the form ``restart (ncr dead ?)'' in your /var/log/mes-
sages file or on the system console, it's an indication
that the timeout is too short. In this case, find the
line ``if (np-&gt;latetime&gt;10)'' in file ncr53c8xx.c (nor-
mally in directory /usr/src/linux/drivers/scsi) and
change the constant 10 to, say, 60 (one minute). Then
rebuild the kernel/module and try again.
Tekram DC315
The driver can be downloaded from
http://www.garloff.de/kurt/linux/dc395/. For some older
scanners it may be necessary to disable all the more
advanced features by using e.g. modprobe dc395x_trm
dc395x_trm=7,5,1,32.
Tekram DC390
Version 1.11 of the Tekram driver seems to work fine
mostly, except that the scan does not terminate properly
(it causes a SCSI timeout after 10 minutes). The generic
AM53C974 also seems to work fine and does not suffer from
the timeout problems.
</PRE>
<H2>SOLARIS, OPENSTEP AND NEXTSTEP INFO</H2><PRE>
Under Solaris, OpenStep and NeXTStep, the generic SCSI device name
refers to a SCSI bus, not to an individual device. For example,
<B>/dev/sg0</B> refers to the first SCSI bus. To tell SANE which device to
use, append the character 'a'+target-id to the special device name.
For example, the SCSI device connected to the first SCSI controller and
with target-id 0 would be called <B>/dev/sg0a</B>, and the device with target-
id 1 on that same bus would be called <B>/dev/sg0b,</B> and so on.
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_SANEI_SCSI</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for the generic
SCSI I/O subsystem. E.g., a value of 128 requests all debug
output to be printed by the backend. A value of 255 also prints
kernel messages from the SCSI subsystem (where available).
Smaller levels reduce verbosity.
<B>SANE_SCSICMD_TIMEOUT</B>
sets the timeout value for SCSI commands in seconds. Overriding
the default value of 120 seconds should only be necessary for
very slow scanners.
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>, <B>sane-"backendname"</B>(5), <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>
</PRE>
<H2>AUTHOR</H2><PRE>
David Mosberger
sane-backends 1.0.12-cvs 07 Dec 2002 <B><A HREF="sane-scsi.5.html">sane-scsi(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>

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

@ -0,0 +1,377 @@
<HTML>
<HEAD>
<TITLE>sane-sharp.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-sharp.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-sharp - SANE backend for SHARP scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-sharp</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to Sharp SCSI scanners. This backend
should be considered <B>beta-quality</B> software! In the current state it is
known to work with JX-610 and JX-250 scanners. It is prepared for usage
with the JX-330 series scanners, but we are not able to test it with
these devices.
For other Sharp scanners, it may or may not work.
At present, the following scanners are known to work with this backend.
Vendor Product id:
----- -----------
Sharp JX-610
Sharp JX-250
Sharp JX-320
Sharp JX-330
Sharp JX-350
The following scanners are detected by the backend, but not tested:
Vendor Product id:
----- -----------
Sharp JX-325
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form:
<I>special</I>
Where <I>special</I> is either the path-name for the special device that cor-
responds to a SCSI scanner. The special device name must be a generic
SCSI device or a symlink to such a device. Under Linux, such a device
name could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for
details.
</PRE>
<H2>SCAN OPTIONS</H2><PRE>
<B>Scan</B> <B>Mode</B> (parameter <B>--mode</B> for scanimage). Possible settings:
<B>Lineart</B> (1 bit black &amp; white scans),
<B>Gray</B> (8 bit gray scale scans),
<B>Lineart</B> <B>Color</B> (bi-level color scans),
<B>Color</B> (8 bit RGB scans).
The default value is <B>Color.</B>
<B>Halftone</B> <B>Pattern</B> (parameter <B>--halftone-pattern</B> for scanimage). Avail-
able only for the JX-330 series scanners. Possible settings:
<B>none</B>
<B>Dither</B> <B>Bayer</B>
<B>Dither</B> <B>Spiral</B>
<B>Dither</B> <B>Dispersed</B>
<B>Error</B> <B>Diffusion</B>
The default value is <B>none.</B>
<B>Paper</B> <B>Source</B> (parameter <B>--source</B> for scanimage). This option is only
available, if an automatic document feeder or a transparency adapter is
installed. Possible settings:
<B>Flatbed</B>
<B>Automatic</B> <B>Document</B> <B>Feeder</B>
<B>Transparency</B> <B>Adapter</B>
If an ADF or a transparency adapter is installed, using it is the
default selection.
<B>Custom</B> <B>Gamma</B> (parameter <B>--custom-gamma</B> for scanimage). This option
determines whether a builtin or a custom gamma-table is used. Possible
settings:
<B>yes</B> enables custom gamma tables
<B>no</B> enables a built gamma table
<B>Gamma</B> (parameter <B>--Gamma</B> for scanimage). This option is only available,
if <B>Custom</B> <B>Gamma</B> is set to <B>no.</B> Possible values:
<B>1.0</B>
<B>2.2</B>
The default value is 2.2. (The JX-250 and JX-350 have no built in gamma
correction; for these scanner, a gamma table is downloaded to the scan-
ner by the backend.)
<B>Gamma</B> <B>Table</B> (parameter <B>--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). 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
values: 0..255; 256 numbers must be defined. The default values are 0,
1, 2, .. 255 (i.e., gamma == 1).
<B>Green</B> <B>Gamma</B> <B>Table</B> (paramter <B>--green-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).
<B>Blue</B> <B>Gamma</B> <B>Table</B> (paramter <B>--blue-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).
<B>Resolution</B> in pixel per inch (parameter <B>--resolution</B> for scanimage).
Selects the resolution of the scanned image. Allowed values:
<B>30..600</B> (JX-330, JX-350 and JX-610) resp. <B>30..400</B> (JX-250)
The default value is 150.
<B>Scan</B> <B>Window</B>
The possible settings depend on the scanner model and, for the JX-250
and the JX-350, also on the usage of the automatic document feeder
resp. the transparency adapter. Please refer to the values allowed by
xscanimage, or xsane. With scanimage, enter one of the following com-
mands:
<I>scanimage</I> <I>-d</I> <I>sharp</I> <I>--source</I> <I>"Automatic</I> <I>Document</I> <I>Feeder"</I> <I>--help</I>
<I>scanimage</I> <I>-d</I> <I>sharp</I> <I>--source</I> <I>Flatbed</I> <I>--help</I>
<I>scanimage</I> <I>-d</I> <I>sharp</I> <I>--source</I> <I>"Transparency</I> <I>Adapter"</I> <I>--help</I>
in order to see the allowed parameter values for the scan window.
The scan window parameters are:
Top-left x position of scan area (parameter <B>-l</B> for scanimage);
Top-left y position of scan area (parameter <B>-t</B> for scanimage);
bottom right x position of scan area (parameter <B>-x</B> for scanim-
age);
bottom right y position of scan area (parameter <B>-y</B> for scanim-
age);
<B>Edge</B> <B>emphasis</B> (parameter <B>--Edge</B> <B>emphasis</B> for scanimage). This option is
not available for the JX-250 and the JX-350. Possible settings:
<B>None</B>
<B>Middle</B>
<B>Strong</B>
<B>Blur</B>
The default value is <B>None.</B>
<B>Threshold</B> (parameter <B>--threshold</B> for scanimage). Sets the threshold for
black and white pixels in lineart mode. Possible values:
<B>1..255</B>
The default value is <B>128.</B> This option is only available in scan mode
lineart.
<B>Threshold</B> <B>Red</B> (parameter <B>--threshold-red</B> for scanimage). Sets the
threshold for the red component of a pixel in in lineart color scan
mode. Possible values:
<B>1..255</B>
The default value is <B>128.</B> This option is only available in scan mode
color lineart.
<B>Threshold</B> <B>Green</B> (parameter <B>--threshold-green</B> for scanimage). Sets the
threshold for the green component of a pixel in in lineart color scan
mode. Possible values:
<B>1..255</B>
The default value is <B>128.</B> This option is only available in scan mode
color lineart.
<B>Threshold</B> <B>Blue</B> (parameter <B>--threshold-blue</B> for scanimage). Sets the
threshold for the blue component of a pixel in in lineart color scan
mode. Possible values:
<B>1..255</B>
The default value is <B>128.</B> This option is only available in scan mode
color lineart.
<B>Light</B> <B>Color</B> (parameter <B>--LightColor</B> for scanimage). Sets the color of
the light source. Possible values:
<B>white</B>
<B>red</B>
<B>green</B>
<B>blue</B>
The default value is <B>white.</B> This option is only available in scan
modes lineart color and color.
</PRE>
<H2>ADF USAGE</H2><PRE>
If a paper jam occured, 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.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>sharp.conf</I> file is a list of options and device
names that correspond to Sharp scanners. Empty lines and lines begin-
ning with a hash mark (#) are ignored. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details
about device names.
Lines setting an option start with the key word <B>option,</B> followed by the
option's name and the option's value. At present, three options are
defined: <B>buffers,</B> <B>buffersize,</B> and <B>readqueue.</B>
Options defined at the start of <I>sharp.conf</I> apply to all devices;
options defined after a device name apply to this device.
The options <B>buffers</B> and <B>readqueue</B> are only significant if the backend
has been compiled so that for each scan a second process is forked
(switch <B>USE_FORK</B> in <I>sharp.c</I> ). This process reads the scan data from
the scanner and writes this data into a block of shared memory. The
parent process reads the data from this memory block and delivers it to
the frontend. The options control the size and usage of this shared
memory block.
<B>option</B> <B>buffers</B> defines the number of buffers used. The smallest number
allowed is 2.
<B>option</B> <B>buffersize</B> defines the size of one buffer. Since each buffer is
filled with a single read command sent to the scanner, its size is lim-
ited automatically to the size allowed by the operating system or by
the Sane SCSI library for SCSI read commands. A buffer size of 128 kB
or 256 kB is recommended for scan resolutions of 300 dpi and above.
<B>option</B> <B>readqueue</B> defines how many read commands to be sent to the scan-
ner are queued. At present, the Sane SCSI library supports queued read
commands only for for Linux. For other operating systems, <B>option</B> <B>read-</B>
<B>queue</B> should be set to 0. For Linux, <B>option</B> <B>readqueue</B> should be set to
2. Larger values than 2 for <B>option</B> <B>readqueue</B> are not reasonable in most
cases. <B>option</B> <B>buffers</B> should be greater than <B>option</B> <B>readqueue.</B>
</PRE>
<H2>Performance Considarations</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.
That means that the backend must read the data as fast as possible from
the scanner in order to avoid carriage stops.
Even the JX-250 needs only less than 10 seconds for a 400 dpi A4 gray
scale scan, which results in a data transfer rate of more than 1.6 MB
per second. This means that the data produced by the scanner must be
processed fairly fast. Due to the small internal buffer of the JX-250,
the backend must issue a read request for the next data block as soon
as possible after reading a block of data in order to avoid carriage
stops.
Stops of the carriage can be caused by the following reasons:
- 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
slow.
Too much "traffic" on the SCSI bus: This happens for example, if hard
disks are connected to the same SCSI bus as the scanner, and when data
transfer from/to these hard disks requires a considerable part of the
SCSI bandwidth during a scan. If this is the case, you should consider
to connect the scanner to a separate SCSI adapter.
Slow responses by the backend to the scanner: Unfortunately, Unix-like
operating systems generally have no real time capabilities. Thus there
is no guarantee that the backend is under any circumstances able to
communicate with the scanner as fast as required. To minimize this
problem, the backend should be compiled so that a separate reader pro-
cess is forked: Make sure that <B>USE_FORK</B> is defined when you compile
<I>sharp.c.</I> If slow responses of the backend remain to be problem, you
could try to reduce the load of the system. Even while the backend and
the reader process need only a minor amount of processor time, other
running processes can cause an increase in the time delay between two
time slices given to the reader process. On slower systems, such an
increased delay can be enough to cause a carriage stop with the JX-250.
For Linux, the usage of the SG driver version 2.1.36 or above is recom-
mended, because it supports, in combination with the SCSI library of
Sane version 1.0.2, command queueing within the kernel. This queueing
implementation, combined with a buffer size of at least 128 kB, should
avoid most carirage 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
slow to transfer the scan data as fast as they are produced by the
scanner. If you have enough memory available, you can increase <B>option</B>
<B>buffers,</B> so that an entire image can be stored in these buffers.
In order to see, if the backend is too slow or if the further process-
ing of the data is too slow, set the environment variable
<B>SANE_DEBUG_SHARP</B> to 1. When a scan is finished, the backend writes the
line "buffer full conditions: <I>nn"</I> to stderr. If <I>nn</I> is zero, carriage
stops are caused by too slow responses of the backend or too much
"traffic" on the SCSI bus. If <I>nn</I> is greater than zero, the backend had
to wait <I>nn</I> times until a buffer has been processed by the frontend.
(Please note that <B>option</B> <B>buffers</B> must be greater than <B>option</B> <B>readqueue</B>
in order to get useful output for "buffer full conditions".)
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/sharp.conf</I>
The backend configuration file.
<I>/usr/local/lib/sane/libsane-sharp.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-sharp.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_SHARP</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
E.g., a value of 128 requests all debug output to be printed.
Smaller levels reduce verbosity.
</PRE>
<H2>KNOWN PROBLEMS</H2><PRE>
1. ADF Mode
After several ADF scans, the scanner moves the carriage back to
the idle position and back to ADF scan position, before a scan
starts. We do not know, if this is a problem of the scanner, or
if this is a bug of the backend. At present, the scanner must
power off and on to stop this annoying behaviour.
2. Threshold level does not work (only JX-610)
3. The maximum resolution is limited to 600 dpi(JX-610 supported to
1200 dpi) resp. 400 dpi (JX-250)
4. If the JX250 is used with an ADF, the following situation can occur:
After several scans, the scanner moves, after loading a new sheet of
paper, the carriage to the idle position, and then back to the position
used for ADF scans. This happens for <I>every</I> scan, in contrast to the
calibration, which is done after 10 scans. (For the calibration, the
carriage is also moved to the idle position.) We do not know, if this
behavior is caused by the backend, or if it is a bug in the firmware of
the scanner.
5. Usage of a transparency adapter (film scan unit) is supported, but
not tested.
</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>
</PRE>
<H2>AUTHORS</H2><PRE>
Kazuya Fukuda, Abel Deuring
</PRE>
<H2>CREDITS</H2><PRE>
The Sharp backend is based on the Canon backend written by Helmut Koe-
berle
Parts of this man page are a plain copy of <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B> by David Mos-
berger-Tang, Andreas Czechanowski and Andreas Bolsch
sane-backends 1.0.12-cvs 21 Nov 2000 <B><A HREF="sane-sharp.5.html">sane-sharp(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>

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

@ -0,0 +1,121 @@
<HTML>
<HEAD>
<TITLE>sane-sm3600.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-sm3600.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-sm3600 - SANE backend for Microtek scanners with M011 USB chip
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-sm3600</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to some Microtek scanners with the Toshiba
M011 custom USB chip. This backend should be considered alpha.
There exist a backends for Microtek scanners with SCSI command set.
Refer to <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B> and <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B> for details.
At present, the following scanners are known positively to work with
this backend:
Vendor Product id: Remark:
-------- -------------- -----------
Microtek ScanMaker 3600 all modes ok
Microtek ScanMaker 3700 reported to work
Microtek ScanMaker 3750 reported to work
If you own a Microtek scanner with the M011 chip other than the ones
listed above, it may or may not work with SANE!
</PRE>
<H2>FRONTEND OPTIONS</H2><PRE>
This backend dynamically enables the options for the frontend, that are
supported by the scanner in dependence of the scanning-mode and other
options. Not supported options are disabled.
The following options are supported by the Microtek2-driver:
Color, grayscale, halftone and lineart scans.
contrast, brightness, control, gamma correction.
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend does not support device names in a standardized form.
</PRE>
<H2>CONFIGURATION</H2><PRE>
This backend does not support a configuration file right now.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/lib/sane/libsane-sm3600.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-sm3600.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>PERMISSIONS AND INTERFACES</H2><PRE>
The backend uses <B>libusb</B> and it's pseudo files in <I>/proc/bus/usb/*</I>. Since
<B>libusb</B> versions 0.1.3b and 0.1.4 have incompatible binary data struc-
tures, You must be shure not to have obsolete header files. When You
mix wrong versions, the scanner detection code will raise a "segment
violation".
These files are normally owned by <B>root</B> and You are responsible to get
access to these files, for example <B>chown</B>-ing them to Yourself. If You
have no right permissions, the backend will find the device, but You'll
get an I/O error.
The better way is to use automatical <B>hotplugging</B>. See
<I>http://sm3600.sf.net/hotplug.html</I> for instructions and useful links.
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_SM3600</B>
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. To see error messages on stderr
set SANE_DEBUG_SM3600 to 1.
E.g. just say:
export SANE_DEBUG_SM3600=5
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B>, http://sm3600.sourceforge.net
</PRE>
<H2>AUTHOR</H2><PRE>
Marian Eichholz (eichholz@computer.org)
Glenn Ramsey (glenn@componic.com)
sane-backends 1.0.12-cvs 10.02.2002 <B><A HREF="sane-sm3600.5.html">sane-sm3600(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>

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

@ -0,0 +1,125 @@
<HTML>
<HEAD>
<TITLE>sane-snapscan.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-snapscan.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-snapscan - SANE backend for AGFA SnapScan flatbed scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-snapscan</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to AGFA SnapScan flatbed scanners. At
present, the following scanners are supported from this backend: AGFA
SnapScan 300, 310, 600, and 1236s, 1236u, 1212u, e20, e25, e40, e50,
e60, Vuego 310s, Acer 300f, 310s, 610s, 610plus, Prisa 620s, Prisa
620u, Prisa 620ut, Prisa 640u, Prisa 640bu, Prisa 1240, Prisa 3300,
Prisa 4300, Prisa 5300 and Guillemot Maxi Scan A4 Deluxe (SCSI) (with
varying success).
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form:
<I>special</I>
Where <I>special</I> is the path-name for the special device that corresponds
to a SCSI scanner. For SCSI scanners, the special device name must be a
generic SCSI device or a symlink to such a device. Under Linux, such a
device name could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example. See sane-
<B><A HREF="scsi.5.html">scsi(5)</A></B> for details.
For USB scanners the devicename must contain the keyword "usb", as in
<I>/dev/usbscanner</I> or <I>/dev/usb/scanner0</I>. For scanners that need a
firmware upload before scanning add a line starting with "firmware"
followed by the fully qualified path to your firmware file, e.g.
firmware /path/to/my/firmware.bin
For further details read http://snapscan.sourceforge.net.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>snapscan.conf</I> file is a list of device names that
correspond to SnapScan 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 consti-
tutes a valid device name.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/snapscan.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-snapscan.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-snapscan.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_SNAPSCAN</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.
</PRE>
<H2>BUGS</H2><PRE>
Man page doesn't provide much information yet.
</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>
http://www.cs.ualberta.ca/~charter/SnapScan/snapscan.html
http://sourceforge.net/projects/snapscan/ (new development website)
</PRE>
<H2>AUTHOR</H2><PRE>
Kevin Charter, Franck Schneider, Michel Roelofs, Emmanuel Blot, Mikko
Tyolajarvi, David Mosberger-Tang, Wolfgang Goeller, Petter Reinholdt-
sen, Gary Plewa, Sebastien Sable, Oliver Schwartz and Mikael Magnusson.
Man page by Henning Meier-Geinitz (mostly based on the web pages and
source code).
sane-backends 1.0.12-cvs 26 May 2001 <B><A HREF="sane-snapscan.5.html">sane-snapscan(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>

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

@ -0,0 +1,89 @@
<HTML>
<HEAD>
<TITLE>sane-sp15c.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-sp15c.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-sp15c - SANE backend for Fujitsu ScanPartner 15C flatbed scanner
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-sp15c</B> library implements a SANE (Scanner Access Now Easy)
backend which provides access to the Fujitsu flatbed scanners. At
present, the following scanner is known to work with these backend:
Vendor: Model: Rev:
-------- ---------------- -----
FCPA ScanPartner 15C 1.01
The ScanPartner 15C driver supports lineart (1-bit), halftone (1-bit),
grayscale (4-bit and 8-bit), and color (3 x 8-bit) scanning.
Other scanners in these families may work. The ScanPartner 15C seems
to be a repackaging of the ScanPartner 600C. People are encouraged to
try these driver with the other scanners and to contact the author with
test results.
</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.
</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-fujitsu.5.html">sane-fujitsu(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
</PRE>
<H2>AUTHOR</H2><PRE>
Randolph Bentson &lt;bentson@holmsjoen.com&gt;, with credit to the unnamed
author of the coolscan driver
</PRE>
<H2>LIMITATIONS</H2><PRE>
Testing limited to a Linux 2.2.5 kernel
Can't quite get the scan page/minute performance in ADF modes. This
may be due to limited system buffer size.
</PRE>
<H2>BUGS</H2><PRE>
I'm sure there are plenty, and not too well hidden, but I haven't seen
them yet.
Both scanners claim to have separate control of resolution in X and Y
directions. I confess I haven't tested this yet. I have found that
xsane doesn't even display this capability.
Threshold settings on the SP15C don't seem to affect the results of
lineart mode scans.
It might be possible to merge these two drivers without much effort
since the SP15C driver was derived from the M3096G driver. They were
split so as to keep the second driver development from breaking the
working first driver. Watch this space for changes.
sane-backends 1.0.12-cvs 17 Apr 2002 <B><A HREF="sane-sp15c.5.html">sane-sp15c(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>

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

@ -0,0 +1,164 @@
<HTML>
<HEAD>
<TITLE>sane-st400.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-st400.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-st400.5.html">sane-st400(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-st400.5.html">sane-st400(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-st400 - SANE backend for Siemens ST/Highscan flatbed scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-st400</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to Siemens ST400 flatbed scanners and com-
patibles. At present, the following scanners are supported by this
backend:
Siemens ST400 (6 bit gray scale)
Siemens ST800 (6 bit gray scale)
The driver supports line art and gray scans up to 8bpp.
The Siemens ST/Highscan series includes several more models, e.g. the
ST300 and ST600. If you own one of these scanners, or a scanner other
than the ones listed above that works with this backend, please let us
know by sending the scanner's model name, SCSI ID, and firmware revi-
sion to <I>sane-devel@mostang.com</I>. Have a look at
http://www.mostang.com/sane/mail.html concerning subscription to sane-
devel.
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form:
<I>special</I>
Where <I>special</I> is either the path-name for the special device that cor-
responds to a SCSI scanner. For SCSI scanners, the special device name
must be a generic SCSI device or a symlink to such a device. Under
Linux, such a device name could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example.
See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>st400.conf</I> file is a list of device names that cor-
respond to Siemens scanners. Empty lines and lines starting with a
hash mark (#) are ignored. A sample configuration file is shown below:
/dev/scanner
# this is a comment
/dev/sge
The default configuration file that is distributed with SANE looks like
this:
scsi SIEMENS "ST 400" Scanner * * 3 0
In this configuration, the driver can only access the ST400 model at
SCSI ID 3 LUN 0 (see section "BUGS" below for the reason). To use the
driver with other scanner models, add an appropriate line to the con-
figuration file. For example, to use it with an ST800 at SCSI ID 3 LUN
0, add the line:
scsi SIEMENS "ST 800" Scanner * * 3 0
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/st400.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-st400.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-st400.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in /etc/sane.d. If the
value of the environment variable ends with the directory sepa-
rator character, then the default directories are searched after
the explicitly specified directories. For example, setting
<B>SANE_CONFIG_DIR</B> to "/tmp/config:" would result in directories
"tmp/config", ".", and "/etc/sane.d" being searched (in this
order).
<B>SANE_DEBUG_ST400</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
E.g., a value of 128 requests all debug output to be printed.
Smaller levels reduce verbosity.
</PRE>
<H2>MISSING FUNCTIONALITY</H2><PRE>
Everything but the most basic stuff.
</PRE>
<H2>BUGS</H2><PRE>
Currently, the backend does not check if the attached device really is
a ST400. It will happily accept everything that matches the configura-
tion entries. This makes it easy to test the backend with other scan-
ners: Just add an appropriate line to the configuration file. The con-
figuration file as distributed (see above) only works with the ST400.
Be careful: If there is no config file at all, the backend defaults to
/dev/scanner.
The ST400 answers on all eight SCSI LUNs. Normally this is not a prob-
lem, as LUN support is usually disabled in SCSI drivers, but if you are
seeing multiple instances of the scanner in a device list, either dis-
able LUNs in your SCSI setup or change the entry in the configuration
file to match LUN 0 only.
</PRE>
<H2>DEBUG</H2><PRE>
If you encounter a bug please set the environment variable
SANE_DEBUG_ST400 to 128 and try to regenerate the problem. Then send me
a report with the log attached.
If you encounter a SCSI bus error or trimmed and/or displaced images
please also set the environment variable SANE_DEBUG_SANEI_SCSI to 128
before sending me the report.
</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>
http://www.informatik.uni-oldenburg.de/~ingo/sane/
</PRE>
<H2>AUTHOR</H2><PRE>
Ingo Wilken &lt;Ingo.Wilken@informatik.uni-oldenburg.de&gt;
sane-backends 1.0.12-cvs 08 Mar 1999 <B><A HREF="sane-st400.5.html">sane-st400(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>

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

@ -0,0 +1,98 @@
<HTML>
<HEAD>
<TITLE>sane-tamarack.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-tamarack.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-tamarack.5.html">sane-tamarack(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-tamarack.5.html">sane-tamarack(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-tamarack - SANE backend for Tamarack flatbed scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-tamarack</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to the following Tamarack flatbed scan-
ners:
Artiscan 6000C
Artiscan 8000C
Artiscan 12000C
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form:
<I>special</I>
Where <I>special</I> is the path-name for the special device that corresponds
to a SCSI scanner. The special device name must be a generic SCSI
device or a symlink to such a device. The program <I>sane-find-scanner</I>
helps to find out the correct device. Under Linux, such a device name
could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for
details.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/tamarack.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-tamarack.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-tamarack.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_TAMARACK</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_TAMARACK=4
</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>
</PRE>
<H2>AUTHOR</H2><PRE>
Roger Wolff
sane-backends 1.0.12-cvs 24 Jun 2000 <B><A HREF="sane-tamarack.5.html">sane-tamarack(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>

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

@ -0,0 +1,177 @@
<HTML>
<HEAD>
<TITLE>sane-teco1.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-teco1.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-teco1.5.html">sane-teco1(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-teco1.5.html">sane-teco1(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-teco1 - SANE backend for TECO / RELISYS scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-teco1</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to some TECO SCSI flatbed scanners. This
backend should be considered <B>beta-quality</B> software! TECO scanners are
sold under various brands like RELISYS, PIOTECH, TRUST. This backend
may or may not support yours.
The scanners that should work with this backend are:
Vendor Model TECO model status
---------------------- -------------- -----------
Relisys AVEC 2400 VM3520 tested
Relisys AVEC 2412 VM3520+ untested
Relisys AVEC 4800 VM4530 untested
Relisys AVEC 4816 VM4530+ untested
Relisys RELI 2400 VM3530 untested
Relisys RELI 2412 VM3530+ tested
Relisys RELI 2412 VM3530+ untested
Relisys RELI 4816 VM4540 untested
Relisys RELI 4830 VM4542 tested
Relisys RELI 9600 VM6530 untested
Relisys RELI 9612 VM6530* untested
Relisys RELI 9624 VM6530+ untested
Relisys RELI 9630 VM6540 untested
Relisys RELI DS15 VM3440 untested
Relisys RELI DS6 VM3420 untested
Dextra DF-600P VM3510 tested
Dextra DF-4830T VM4542 untested
Dextra DF-1200T+ VM3530+ untested
Dextra DF-9624 VM6530+ untested
Note that the untested scanner will not be directly supported. You
should contact the author for that.
The TECO VM number can usually be found at the back of the scanner. It
is also part of the FCC ID. "sane-find-scanner -v" will also show the
scsi inquiry, and if it is a TECO scanner, the name will be there too.
The options the backend supports can either be selected through command
line options to programs like scanimage or through GUI elements in
xscanimage or xsane.
If you have any success with a scanner 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 teco1
<B>Scan</B> <B>Mode</B>
<B>--mode</B> selects the basic mode of operation of the scanner valid choices
are <I>Black</I> <I>&amp;</I> <I>White</I> , <I>Grayscale</I> and <I>Color</I> The Black &amp; White mode
is black and white only (1 bit). Grayscale will produce 256 lev-
els of gray (8 bits). Color will produce a 24 bits color image.
<B>--resolution</B>
selects the resolution for a scan. The scanner can do all reso-
lutions between 1 and 600, in increments of 1.
<B>Geometry</B> <B>options</B>
<B>-l</B> <B>-t</B> <B>-x</B> <B>-y</B>
control the scan area: -l sets the top left x coordinate, -t the
top left y coordinate, -x selects the width and -y the height of
the scan area. All parameters are specified in millimeters by
default.
<B>Enhancement</B> <B>options</B>
<B>--custom-gamma</B>
(color mode only) allows the user to specify a gamma table (see
the next 3 parameters).
<B>--red-gamma-table</B>
(color mode only) can be used to download a user defined gamma
table for the red channel. The table must be 256 bytes long.
<B>--green-gamma-table</B>
(color mode only) can be used to download a user defined gamma
table for the green channel. The table must be 256 bytes long.
<B>--blue-gamma-table</B>
(color mode only) can be used to download a user defined gamma
table for the blue channel. The table must be 256 bytes long.
<B>--dither</B>
(Black &amp; White only) select the dither mask to use. Possible
values are <I>Line</I> <I>art</I> , <I>2x2</I> , <I>3x3</I> , <I>4x4</I> <I>bayer</I> , <I>4x4</I> <I>smooth</I> , <I>8x8</I>
<I>bayer</I> , <I>8x8</I> <I>smooth</I> , <I>8x8</I> <I>horizontal</I> and <I>8x8</I> <I>vertical</I>
<B>--preview</B>
requests a preview scan. The resolution used for that scan is 22
dpi and the scan area is the maximum allowed. The scan mode is
user selected. The default is "no".
</PRE>
<H2>CONFIGURATION FILE</H2><PRE>
The configuration file /usr/local/etc/sane.d/teco1.conf supports only
one information: the device name to use (eg /dev/scanner).
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/lib/sane/libsane-teco1.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-teco1.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_TECO1</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
E.g., a value of 128 requests all debug output to be printed.
Smaller levels reduce verbosity.
</PRE>
<H2>LIMITATIONS</H2><PRE>
The windows TWAIN driver has many more options than this SANE backend.
However they are only software adjustments. This backend only imple-
ments what the scanner can support.
</PRE>
<H2>BUGS</H2><PRE>
None known.
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, <B><A HREF="xsane.1.html">xsane(1)</A></B>, <B><A HREF="sane.7.html">sane(7)</A></B>
</PRE>
<H2>AUTHOR</H2><PRE>
The package is actively maintained by Frank Zago.
http://fz.eryx.net/sane/#teco
</PRE>
<H2>CREDITS</H2><PRE>
Thanks to Gerard Delafond for the VM4542 support. Thanks to Jean-Yves
Simon for the VM3510 support.
sane-backends 1.0.12-cvs August 30th, 2002 <B><A HREF="sane-teco1.5.html">sane-teco1(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>

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

@ -0,0 +1,187 @@
<HTML>
<HEAD>
<TITLE>sane-teco2.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-teco2.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-teco2 - SANE backend for TECO / RELISYS scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-teco2</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to some TECO SCSI flatbed scanners. This
backend should be considered <B>beta-quality</B> software! TECO scanners are
sold under various brands like Relisys, Piotech, TRUST. This backend
may or may not support yours.
The scanners that should work with this backend are:
Vendor Model TECO model status
---------------------- -------------- -----------
Primax Jewel 4800 VM356A tested
Primax Profi 9600 VM6575 tested
Primax Profi 19200 VM6586 tested
Relisys APOLLO Express 3 VM356A tested
Relisys APOLLO Express 6 VM6565 tested
Relisys APOLLO Express 12 ? untested
Relisys AVEC II S3 VM3564 tested
Relisys AVEC Super 3 VM3575 tested
Relisys SCORPIO Pro VM6575 tested
Relisys SCORPIO Pro-S VM6586 tested
Relisys SCORPIO Super 3 VM3575 tested
For all these scanners, black&amp;white and grayscale mode work well. How-
ever, most of them do not support more than a handful of resolutions in
color mode. See the backend home page (under AUTHOR) for the exact sta-
tus of each scanner.
Note that the untested scanner will not be directly supported. You
should contact the author for that.
The TECO VM number can usually be found at the back of the scanner. It
is also part of the FCC ID.
The options the backend supports can either be selected through command
line options to programs like scanimage or through GUI elements in
xscanimage or xsane.
If you have any success with a scanner 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 teco2
<B>Scan</B> <B>Mode</B>
<B>--mode</B> selects the basic mode of operation of the scanner valid choices
are <I>Black</I> <I>&amp;</I> <I>White</I> , <I>Grayscale</I> and <I>Color</I> The Black &amp; White mode
is black and white only (1 bit). Grayscale will produce 256 lev-
els of gray (8 bits). Color will produce a 24 bits color image.
<B>--resolution</B>
selects the resolution for a scan. The scanner can do all reso-
lutions between 1 and 600, in increments of 1.
<B>Geometry</B> <B>options</B>
<B>-l</B> <B>-t</B> <B>-x</B> <B>-y</B>
control the scan area: -l sets the top left x coordinate, -t the
top left y coordinate, -x selects the width and -y the height of
the scan area. All parameters are specified in millimeters by
default.
<B>Enhancement</B> <B>options</B>
<B>--custom-gamma</B>
(color mode only) allows the user to specify a gamma table (see
the next 3 parameters).
<B>--red-gamma-table</B>
(color mode only) can be used to download a user defined gamma
table for the red channel. The table must be 256 bytes long.
<B>--green-gamma-table</B>
(color mode only) can be used to download a user defined gamma
table for the green channel. The table must be 256 bytes long.
<B>--blue-gamma-table</B>
(color mode only) can be used to download a user defined gamma
table for the blue channel. The table must be 256 bytes long.
<B>--preview</B>
requests a preview scan. The resolution used for that scan is 22
dpi and the scan area is the maximum allowed. The scan mode is
user selected. The default is "no".
</PRE>
<H2>CONFIGURATION FILE</H2><PRE>
The configuration file /usr/local/etc/sane.d/teco2.conf supports only
one information: the device name to use (eg /dev/scanner).
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/lib/sane/libsane-teco2.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-teco2.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_TECO2</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
E.g., a value of 128 requests all debug output to be printed.
Smaller levels reduce verbosity.
<B>SANE_TECO2_CAL_ALGO</B>
Either 0 or 1. Selects the algorithm for the calibration. A
value of 1 seems to give better scans on the VM3575. Feedback on
it is welcome.
</PRE>
<H2>LIMITATIONS</H2><PRE>
The windows TWAIN driver has many more options than this SANE backend.
However they are only software adjustments. This backend only imple-
ments what the scanner can support.
</PRE>
<H2>BUGS</H2><PRE>
Plenty. Parts of this backend are still under development.
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, <B><A HREF="xsane.1.html">xsane(1)</A></B>, <B><A HREF="sane.7.html">sane(7)</A></B>
</PRE>
<H2>AUTHORS</H2><PRE>
The package is actively maintained by Frank Zago.
http://fz.eryx.net/sane/#teco2
Gerard Klaver contributed a patch to support the VM3564 and VM356A.
</PRE>
<H2>CREDITS</H2><PRE>
Thanks to:
Gerard Klaver for his relentless VM3575 testings.
Mark Plowman for providing the first SCSI traces from a VM3575.
Andreas Klaedtke for providing the first SCSI traces from a VM6586 and
for his testing, and to Stefan von Dombrowski for his testing.
Nicolas Peyresaubes for providing the first SCSI traces from a VM656A
and for his testing.
Dave Parker for testing the support for the VM6575.
sane-backends 1.0.12-cvs 19 March 2002 <B><A HREF="sane-teco2.5.html">sane-teco2(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>

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

@ -0,0 +1,150 @@
<HTML>
<HEAD>
<TITLE>sane-teco3.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-teco3.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-teco3.5.html">sane-teco3(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-teco3.5.html">sane-teco3(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-teco3 - SANE backend for TECO / RELISYS scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-teco3</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to some TECO SCSI flatbed scanners. This
backend should be considered <B>alpha-quality</B> software! TECO scanners are
sold under various brands like RELYSIS, PIOTECH, TRUST. This backend
may or may not support yours.
The scanners that should work with this backend are:
Vendor Model TECO model status
--------------------------- ---------- ----------
Relisys Scorpio VM3552 tested
Plustek OpticPro 2400SP VM3552 untested
PIOTECH Splendeur 3024 VM3552 tested
Trust Imagery 2400 SP VM3552 tested
Trust Imagery 4800 SP+ VM3552 tested
Trust Imagery 9600 SP VM3552 untested
The TECO VM number can usually be found at the back of the scanner. It
is also part of the FCC ID.
The options the backend supports can either be selected through command
line options to programs like scanimage or through GUI elements in
xscanimage or xsane.
If you have any success with a scanner 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 teco3
<B>Scan</B> <B>Mode</B>
<B>--mode</B> selects the basic mode of operation of the scanner valid choices
are <I>Black</I> <I>&amp;</I> <I>White</I> , <I>Grayscale</I> and <I>Color</I> The Black &amp; White mode
is black and white only (1 bit). Grayscale will produce 256 lev-
els of gray (8 bits). Color will produce a 24 bits color image.
<B>--resolution</B>
selects the resolution for a scan. The scanner can do all reso-
lutions between 1 and 1200, in increments of 1.
<B>Geometry</B> <B>options</B>
<B>-l</B> <B>-t</B> <B>-x</B> <B>-y</B>
control the scan area: -l sets the top left x coordinate, -t the
top left y coordinate, -x selects the width and -y the height of
the scan area. All parameters are specified in millimeters by
default.
<B>Enhancement</B> <B>options</B>
<B>--custom-gamma</B>
(color mode only) allows the user to specify a gamma table (see
the next 3 parameters).
<B>--red-gamma-table</B>
(color mode only) can be used to download a user defined gamma
table for the red channel. The table must be 1024 bytes long.
<B>--green-gamma-table</B>
(color mode only) can be used to download a user defined gamma
table for the green channel. The table must be 1024 bytes long.
<B>--blue-gamma-table</B>
(color mode only) can be used to download a user defined gamma
table for the blue channel. The table must be 1024 bytes long.
<B>--preview</B>
requests a preview scan. The resolution used for that scan is 22
dpi and the scan area is the maximum allowed. The scan mode is
user selected. The default is "no".
</PRE>
<H2>CONFIGURATION FILE</H2><PRE>
The configuration file /usr/local/etc/sane.d/teco3.conf supports only
one information: the device name to use (eg /dev/scanner).
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/lib/sane/libsane-teco3.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-teco3.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_TECO3</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
E.g., a value of 128 requests all debug output to be printed.
Smaller levels reduce verbosity.
</PRE>
<H2>LIMITATIONS</H2><PRE>
The windows TWAIN driver has many more options than this SANE backend.
However they are only software adjustments. This backend only imple-
ments what the scanner can support.
</PRE>
<H2>BUGS</H2><PRE>
Not much.
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, <B><A HREF="xsane.1.html">xsane(1)</A></B>, <B><A HREF="sane.7.html">sane(7)</A></B>
</PRE>
<H2>AUTHOR</H2><PRE>
The package is actively maintained by Frank Zago.
http://fz.eryx.net/sane/#teco3
sane-backends 1.0.12-cvs 25 July 2002 <B><A HREF="sane-teco3.5.html">sane-teco3(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>

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

@ -0,0 +1,290 @@
<HTML>
<HEAD>
<TITLE>sane-test.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-test.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-test.5.html">sane-test(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-test.5.html">sane-test(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-test - SANE backend for testing frontends
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-test</B> library implements a SANE (Scanner Access Now Easy) back-
end that allows testing the SANE installation and SANE frontends. It
provides access to a (nearly) unlimited number of virtual devices.
There is no support for real scanners or cameras. However, the backend
simulates scanning and setting options.
The idea is not only to find bugs in frontends but also to show all
capabilities of SANE. Therefore <B>sane-test</B> implements functions and
options that are not (or seldomly) 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'.
</PRE>
<H2>SCAN MODE OPTIONS</H2><PRE>
Option <B>mode</B> selects the scan mode (Gray or Color).
Option <B>depth</B> determines the number of bits per sample (1. 8, or 16).
Keep in mind, that this value refers to the sample, not the pixel. So
depth=16 results in 48 bits per pixel in color mode. The most usual
combinations are mode=Gray, depth=1 for lineart, mode=Gray, depth=8 for
gray and mode=Color, depth=8 for color mode. The combination of color
and 1-bit mode is quite obscure (8 colors) but allowed in the SANE
standard. However, the meaning of bits is not defined. Currently 1 =
high intensity and 0 = low intensity is used.
Setting option <B>hand-scanner</B> results in the test-backend behaving like a
hand-scanner. Hand-scanners do not know the image height a priori.
Instead, they return a height of -1. Setting this option allows to
test whether a frontend can handle this correctly. This option also
enables a fixed width of 11 cm.
Setting option <B>three-pass</B> simulates a three-pass scanner. Older color
scanners needed to scan the image once per color (reg/green/blue) to
get the full image. Therefore, in this mode three single frames are
transmitted in color mode.
Option <B>three-pass-order</B> provides support for changing the order of the
three frames (see option three-pass above). A frontend should support
all orders.
Option <B>resolution</B> sets the resolution of the image in dots per inch.
</PRE>
<H2>SPECIAL OPTIONS</H2><PRE>
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:
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
endianess.
If option <B>read-limit</B> is set, the maximum amount of data tranferred with
each call to sane_read() is limited.
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
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
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
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
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
start of the scan (which it shouldn't).
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
for detecting if sane_read() will return data.
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
standard error.
</PRE>
<H2>GEOMETRY OPTIONS</H2><PRE>
Option <B>tl-x</B> determines the top-left x position of the scan area.
Option <B>tl-y</B> determines the top-left y position of the scan area.
Option <B>br-x</B> determines the bottom-right x position of the scan area.
Option <B>br-y</B> determines the bottom-right y position of the scan area.
</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
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
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
pressing a button at the device).
Option <B>bool-hard-select</B> (3/6) is a bool test option that has hard
select (and advanced) capabilities. That means the option can't be set
by the frontend but by the user (e.g. by pressing a button at the
device) and can't be read by the frontend.
Option <B>bool-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)
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-
bilities. This option can be automatically set by the backend.
</PRE>
<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
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
bits and constraint word list set.
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-
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 with unit percent and using an array a word list constraint.
</PRE>
<H2>FIXED TEST OPTIONS</H2><PRE>
There are 3 fixed test options in total.
Option <B>fixed</B> (1/3) is a fixed test option with no unit and no con-
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
32767.9999, and quant is 2.0.
Option <B>fixed-constraint-word-list</B> (3/3) is a Fixed test option with no
unit and constraint word list set.
</PRE>
<H2>STRING TEST OPTIONS</H2><PRE>
There are 3 string test options in total.
Option <B>string</B> (1/3) is a string test option without constraint.
Option <B>string-constraint-string-list</B> (2/3) is a string test option with
string list constraint.
Option <B>string-constraint-long-string-list</B> (3/3) is a string test option
with string list constraint. Contains some more entries...
</PRE>
<H2>BUTTON TEST OPTION</H2><PRE>
Option <B>button</B> (1/1) is a Button test option. Prints some text...
</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
SANE options can be configured in this file. A template contain-
ing all the default values is provided together with this back-
end. One of the more interesting values may be <B>num-</B>
<B>ber_of_devices</B>. It can be used to check the frontend's ability
to show a long list of devices. The config values concerning
resolution and geometry can be useful to test the handling of
big file sizes.
<I>/usr/local/lib/sane/libsane-test.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-test.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_TEST</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_TEST=4
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <I>http://www.meier-geinitz.de/sane/test-backend/</I>
</PRE>
<H2>AUTHOR</H2><PRE>
Henning Meier-Geinitz &lt;henning@meier-geinitz.de&gt;
</PRE>
<H2>BUGS</H2><PRE>
- config file values aren't tested for correctness
sane-backends 1.0.12-cvs 24 Jul 2002 <B><A HREF="sane-test.5.html">sane-test(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>

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

@ -0,0 +1,279 @@
<HTML>
<HEAD>
<TITLE>sane-umax.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-umax.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-umax.5.html">sane-umax(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-umax.5.html">sane-umax(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-umax - SANE backend for UMAX scanners
</PRE>
<H2>ABOUT THIS FILE</H2><PRE>
This file only is a short descripton of the umax-backend for sane! For
detailled information take a look at sane-umax-doc.html (it is included
in the sane source directory and in the xsane online help)!
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-umax</B> library implements a SANE backend that provides acces to
several UMAX-SCSI-scanners and some Linotye Hell SCSI-scanners, paral-
lel- and USB-scanners are not (and propably will never be) supported!
<B>I</B> <B>suggest</B> <B>you</B> <B>hold</B> <B>one</B> <B>hand</B> <B>on</B> <B>the</B> <B>power-button</B> <B>of</B> <B>the</B> <B>scanner</B> <B>while</B>
<B>you</B> <B>try</B> <B>the</B> <B>first</B> <B>scans!</B>
</PRE>
<H2>CONFIGURATION</H2><PRE>
The configuration file for this backend resides in
/usr/local/etc/sane.d/umax.conf.
Its contents is a list of device names that correspond to UMAX and UMAX
compatible scanners. Empty lines and lines starting with a hash mark
(#) are ignored. A sample configuration file is shown below:
# this is a comment
#
option scsi-maxqueue 4
option scsi-buffer-size-min 65536
option scsi-buffer-size-max 131072
option scan-lines 40
option preview-lines 10
option scsi-maxqueue 2
option execute-request-sense 0
option force-preview-bit-rgb 0
option slow-speed -1
option care-about-smearing -1
option calibration-full-ccd -1
option calibration-width-offset -1
option calibration-bytes-pixel -1
option exposure-time-rgb-bind -1
option invert-shading-data -1
option lamp-control-available 0
option gamma-lsb-padded 0
/dev/sge
#scsi Vendor Model Type Bus Channel ID LUN
# The following scanner supports lamp control
option lamp-control-available 1
scsi UMAX * Scanner * * * * *
# scanner on /dev/scanner does not support lamp control
option lamp-control-available 0
/dev/scanner
- execute-request-sense:
values:
0 = disabled
1 = enabled
default = 0
If set to 1 umax_do_request_sense is called in
umax_do_calibration. This can hang the system
(but has been enabled until this version)
- scsi-buffer-size-min, scsi-buffer-size-max:
values: 4096-1048576, default min=32768, max=131072
Especially the minimum value is very important.
If this value is set too small the backend is not
able to send gamma tables to the scanner or to
do a correct color calibration. This may result in
strange color effects. If the minimum value is set
too large then the backend is not able to allocate
the requested scsi buffer size and aborts with
out of memory error. The default is 32KB, for
some scanners it should be increased to 64KB.
- scan-lines, preview-lines:
values: 1-65535,
default: scan-lines=40, preview-lines=10
define the maximum number of lines that are scanned
into one buffer
- force-preview-bit-rgb:
values:
0 = disabled
1 = enabled
default = 0
set preview bit in rgb real scan
- slow-speed, care-about-smearing:
values:
-1 = auto
0 = disabled
1 = enabled
default = -1
dangerous options, needed for some scanners
do not changed these options until you really know
what you do, you may destroy your scanner when you
define wrong values for this options
- calibration-full-ccd:
values:
-1 = auto
0 = disabled
1 = enabled
default = -1
do calibration for each pixel of ccd instead of
selected image
- calibration-width-offset:
values: -99999=auto, &gt;-99999 set value
add an offset width to the calculated with for
image/ccd
- calibration-bytes-pixel:
values:
-1 = disabled
0 = not set
1 = 1 byte/pixel,
2 = 2 bytes/pixel
use # bytes per pixel for calibration
- exposure-time-rgb-bind:
values:
-1 = automatically set by driver - if known
0 = disabled (own selection for red, green and blue)
1 = enabled (same values for red, green and blue)
- invert-shading-data:
values:
-1 = automatically set by driver - if known
0 = disabled
1 = enabled
default = -1
invert shading data before sending it back to the scanner
- lamp-control-available:
values:
0 = automatically set by driver - if known
1 = available
default = 0
- gamma-lsb-padded:
values:
-1 = automatically set by driver - if known
0 = gamma data is msb padded
1 = gamma data is lsb padded
default = -1
- handle-bad-sense-error:
values:
0 = handle as device busy
1 = handle as ok
2 = handle as i/o error
3 = ignore bad error code - continue sense handler,
default = 0
- scsi-maxqueue:
values:
1..# (maximum defined at compile time)
default = 2
most scsi drivers allow internal command queueing with a depth
of 2 commands. In most cases it does not mprove anything when you
increase this value. When your scsi driver does not support any
command queueing you can try to set this value to 1.
The special device name must be a generic SCSI device or a symlink to
such a device. To find out to which device your scanner is assigned
and how you have to set the permissions of that device, have a look at
sane-scsi.
</PRE>
<H2>SCSI ADAPTER TIPS</H2><PRE>
The ISA-SCSI-adapters that are shipped with some Umax-scanners are not
supported very well by Linux (I suggest not to use it), the PCI-SCSI-
adapters that come with some Umax-scanners are not supported at all (as
far as I know). On other platforms these SCSI-adapters are not sup-
ported. So you typically need to purchase another SCSI-adapter that is
supported by your platform. See the relevant hardware FAQs and HOWTOs
for your platform for more information.
The UMAX-scanners do block the scsi-bus for a few seconds while scan-
ning. It is not necessary to connect the scanner to its own SCSI-
adapter. But if you need short response time for your SCSI-harddisk
(e.g. if your computer is a file-server) or other scsi devices, I sug-
gest you use an own SCSI-adapter for your UMAX-scanner.
If you have any problems with your Umax scanner, check your scsi chain
(cable length, termination, ...).
See also: <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>
</PRE>
<H2>FILES</H2><PRE>
The backend configuration file:
/usr/local/etc/sane.d/umax.conf
The static library implementing this backend:
/usr/local/lib/sane/libsane-umax.a
The shared library implementing this backend :
/usr/local/lib/sane/libsane-umax.so
(present on systems that support dynamic loading)
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_UMAX</B>
If the library was compiled with debug support enabled, this environ-
ment 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_UMAX values
Number Remark
0 print important errors (printed each time)
1 print errors
2 print sense
3 print warnings
4 print scanner-inquiry
5 print informations
6 print less important informations
7 print called procedures
8 print reader_process messages
10 print called sane-init-routines
11 print called sane-procedures
12 print sane infos
13 print sane option-control messages
Example:
export SANE_DEBUG_UMAX=8
</PRE>
<H2>BUGS</H2><PRE>
X-resolutions greater than 600 dpi sometimes make problems
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>
</PRE>
<H2>AUTHOR</H2><PRE>
Oliver Rauch
</PRE>
<H2>EMAIL-CONTACT</H2><PRE>
Oliver.Rauch@Rauch-Domain.DE
sane-backends 1.0.12-cvs 29 november 2002 <B><A HREF="sane-umax.5.html">sane-umax(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>

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

@ -0,0 +1,145 @@
<HTML>
<HEAD>
<TITLE>sane-umax1220u.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-umax1220u.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-umax1220u.5.html">sane-umax1220u(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-umax1220u.5.html">sane-umax1220u(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-umax1220u - SANE backend for the UMAX Astra 1220U scanner
</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.
For the latest information on this backend, please visit
<I>http://umax1220u-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?
</PRE>
<H2>CONFIGURATION</H2><PRE>
The configuration file for this backend resides in
/usr/local/etc/sane.d/umax1220u.conf.
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:
#usb vendor product
usb 0x1606 0x0010
# Device list for non-linux systems
/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.
</PRE>
<H2>FILES</H2><PRE>
The backend configuration file:
/usr/local/etc/sane.d/umax1220u.conf
The static library implementing this backend:
/usr/local/lib/sane/libsane-umax1220u.a
The shared library implementing this backend :
/usr/local/lib/sane/libsane-umax1220u.so
(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 environ-
ment 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
Number Remark
1 print failures
2 print information
3 print high-level function calls
4 print high-level function checkpoints
9 print mid-level function calls
10 print mid-level function checkpoints
80 print protocol-level function entry
90 print protocol-level function exit
Example:
export SANE_DEBUG_UMAX1220U=10
</PRE>
<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
to reset it.
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
default, the scan area is zero.
</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>
For latest bug fixes and information see
<I>http://umax1220u-sane.sourceforge.net/</I>
</PRE>
<H2>AUTHOR</H2><PRE>
Marcio Luis Teixeira &lt;marciot@users.sourceforge.net&gt;
</PRE>
<H2>EMAIL-CONTACT</H2><PRE>
umax1220u-sane-devel@lists.sourceforge.net
</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.
sane-backends 1.0.12-cvs 6 Jan 2002 <B><A HREF="sane-umax1220u.5.html">sane-umax1220u(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>

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

@ -0,0 +1,245 @@
<HTML>
<HEAD>
<TITLE>sane-umax_pp.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-umax_pp.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-umax_pp.5.html">sane-umax_pp(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-umax_pp.5.html">sane-umax_pp(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-umax_pp - SANE backend for Umax Astra parallel port flatbed scan-
ners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-umax_pp</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to Umax parallel port flatbed scanners.
The following scanners work with this backend:
Model:
--------------------
Astra 1220P
HP3200C
Astra 1600P
Astra 2000P
This backend handles 75x75, 150x150, 300x300, 600x600 and 600x1200 dpi
scan resolutions, in color and gray levels. There is a software lineart
mode.
These scanners share the same ASIC. Only parts such as CCD and ADC
change from one to another. They even all reports being UMAX Astra
1220P via IEEE1284. There isn't software way to recognize them prop-
erly. Under windows, model is set by the driver installed, regardless
of the hardware.
<B>EPP</B> <B>MODE</B> <B>ONLY</B>
The current version of the backend use only EPP mode to communi-
cate with the scanner. PS/2 and SPP mode aren't implemented. It
is recommended that you set your parallel port to EPP in BIOS
with the current version of this backend. ECPEPP will only work
if you use a 2.4 kernel with ppdev character device support.
This backend does support parport sharing only <I>if</I> <I>you</I> <I>have</I> <I>a</I> <I>kernel</I>
<I>with</I> <I>ppdev</I> <I>support.</I>
Note that if you don't use the ppdev character device, the backend
needs to run as root. To allow user access to the scanner run the back-
end through the network interface (See <B><A HREF="saned.1.html">saned(1)</A></B> and <B><A HREF="sane-net.5.html">sane-net(5)</A></B>). A
more relaxed solution (security wise) is to add suid bit to the fron-
tend (See <B><A HREF="chmod.1.html">chmod(1)</A></B>). The backend drop root priviledges as soon as it
can, right after gaining direct access to IO ports, which lessen risks
when being root.
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form:
<I>port</I> <I>value</I>
Where <B>value</B> is the base address, or the ppdev device name of the port
your scanner is attached to. Known ports are <B>0x378</B>, <B>0x278</B> and <B>0x3BC</B> .
Or the name of the parallel port character device user interface, such
as /dev/parport0 for the linux ppdev, or /dev/ppi0 for FreeBSD ppi.
Under linux, if you are not sure which port your scanner is connected
to, may have a look at your /etc/modules.conf. Also typing dmesg|grep
parport in a command shell should show you a line like:
parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COM-
PAT,ECP,DMA]
telling you about port address and mode.
If you are using the linux ppdev character device, you will have to
specify the device name, which is /dev/parport0 for the first parallel
port. Check the permissions on /dev/paraport0, many linux distributions
restrict them for root only access. Get sure they are like:
crw-rw-rw- 1 root root 99, 0 mai 20 2002 /dev/parport0
crw-rw-rw- 1 root root 99, 1 mai 20 2002 /dev/parport1
crw-rw-rw- 1 root root 99, 2 mai 20 2002 /dev/parport2
crw-rw-rw- 1 root root 99, 3 mai 20 2002 /dev/parport3
The same apply with the /dev/ppi0 character device under FreeBSD.
You can rename any device using the
<I>name</I> <I>devname</I>
<I>model</I> <I>model</I>
<I>vendor</I> <I>vendor</I>
options. These options apply to the last port option.
</PRE>
<H2>CONFIGURATION</H2><PRE>
Please make sure to edit umax_pp.conf <B>before</B> you use the backend.
The contents of the <B>umax_pp.conf</B> file is a list of options and device
names that correspond to Umax scanners. Empty lines and lines starting
with a hash mark (#) are ignored.
The height options supported are <B>red-brightness</B>, <B>green-brightness</B>,
<B>blue-brightness</B>, <B>red-contrast</B>, <B>green-contrast</B>, <B>blue-contrast</B>, <B>astra</B>,
and <B>buffer</B>.
Options <B>red-brightness</B> , <B>green-brightness</B> and <B>blue-brightness</B> allow you
to adjust the sensitivy of your scanner for the given color. Values
range from 0 (lowest brightness) to 15 (highest). If the advanced
option "Brightness" isn't checked in the frontend, the backend does
automatic brightness calibration, and do not use user provided values.
Options <B>red-contrast</B> , <B>green-contrast</B> and <B>blue-contrast</B> allow you to
adjust the contrast of your scanner for the given color. Values range
from 0 (lowest contrast) to 15 (highest).
Option <B>astra</B> allows you to change the model of your scanner. Current
auto detection is based on side effects on scanning when using 1220P
command set on other models, so it may fail on unkown hardware combina-
tion. Valid values are 1220, 1600 and 2000. It is usefull only when
autodetection fails to detect properly your scanner model. If your
scanner work properly but is reported wrongly, let it be that way. The
only valid case to change the model is when your scanner produces
'black' or
'inverted' scans. In this case you can put the model. Be aware that
it will prevent autodetection.
Option <B>buffer</B> allows you to change the size of the scan buffer. The
size must be specified in bytes. The default value is 2 megabytes.
Decreasing this value will improve the progress status reporting in the
frontend, but will stall the scan more often.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/umax</I><B>_</B><I>pp.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-umax</I><B>_</B><I>pp.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-umax</I><B>_</B><I>pp.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_UMAX_PP</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
E.g., a value of 128 requests all debug output to be printed.
Smaller levels reduce verbosity.
level debug output
------- ------------------------------
0 nothing
1 errors
2 warnings &amp; minor errors
3 additional information
4 debug information
5 code flow (not supported yet)
6 special debug information
<B>SANE_DEBUG_UMAX_PP_LOW</B>
This variable sets the debug level for the SANE interface for
the Umax ASIC. Note that enabling this will spam your terminal
with some million lines of debug output.
level debug output
------- -------------------------------
0 nothing
1 errors
8 command blocks
16 detailed code flow
32 dump datafiles
255 everything
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-net.5.html">sane-net(5)</A></B>, <B><A HREF="saned.1.html">saned(1)</A></B>
For latest bug fixes and information see
<I>http://umax1220p.sourceforge.net/</I>
</PRE>
<H2>AUTHOR</H2><PRE>
St?phane VOLTZ &lt;svoltz@wanadoo.fr&gt;, man page derived from mustek_pp man
page by Jochen Eisinger &lt;jochen.eisinger@gmx.net&gt;
</PRE>
<H2>BUG REPORTS</H2><PRE>
If something doesn't work, please contact me. But I need some informa-
tion about your scanner to be able to help you...
<I>SANE</I> <I>version</I>
run "scanimage -V" to determine this
<I>the</I> <I>backend</I> <I>version</I> <I>and</I> <I>your</I> <I>scanner</I> <I>hardware</I>
run "SANE_DEBUG_UMAX=255 scanimage -L 2&gt;log" as root. If you
don't get any output from the umax_pp backend, make sure a line
"umax_pp" is included into your /usr/local/etc/sane.d/dll.conf.
If your scanner isn't detected, make sure you've defined the
right port address, or the correct device in your umax_pp.conf.
<I>the</I> <I>name</I> <I>of</I> <I>your</I> <I>scanner/vendor</I>
also a worthy information. Please also include the optical reso-
lution and lamp type of your scanner, both can be found in the
manual of your scanner.
<I>any</I> <I>further</I> <I>comments</I>
if you have comments about the documentation (what could be done
better), or you think I should know something, please include
it.
sane-backends 1.0.12-cvs 16 September 2003 <B><A HREF="sane-umax_pp.5.html">sane-umax_pp(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>

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

@ -0,0 +1,227 @@
<HTML>
<HEAD>
<TITLE>sane-usb.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-usb.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-usb.5.html">sane-usb(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-usb - USB configuration tips for SANE
</PRE>
<H2>DESCRIPTION</H2><PRE>
This manual page contains information on how to access scanners with a
USB interface. It focusses on two main topics: getting the scanner
detected by the operating system kernel and using it with SANE.
This page applies to most backends and scanners, as they use the
generic sanei_usb interface. However, there are some exceptions: USB
Scanners supported by the avision and microtek2 backends need special
USB kernel drivers, see <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B> and <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B> for
details. The sm3600 backend supports only access via libusb. See the
appropriate section in this manpage and <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B>.
</PRE>
<H2>QUICK START</H2><PRE>
This is a short HOWTO-like section. For the full details, read the fol-
lowing sections. The goal of this section is to get the scanner
detected by <B><A HREF="sane-find-scanner.5.html">sane-find-scanner(5)</A></B>.
Run sane-find-scanner. If it lists your scanner with the correct vendor
and product ids, you are done. See section <B>SANE</B> <B>ISSUES</B> for details on
how to go on.
Sane-find-scanner lists your scanner, but can't detect the vendor- and
product ids? Scanning may work nevertheless, just try with section <B>SANE</B>
<B>ISSUES</B>. If it doesn't, install libusb (see section <B>LIBUSB</B>) or, if you
use Linux, upgrade your kernel (see section <B>GENERIC</B> <B>KERNEL</B> <B>SCANNER</B>
<B>DRIVER</B>).
Sane-find-scanner doesn't list your scanner? Does it work as root? If
yes, there is a permission issue. If sane-find-scanner lists a device
name starting with <I>libusb:</I>, read <B>LIBUSB</B>, otherwise have a look at the
section <B>GENERIC</B> <B>KERNEL</B> <B>SCANNER</B> <B>DRIVER</B>).
Nothing is found even as root? Either install libusb (see section
<B>LIBUSB</B>), or make sure, that the kernel scanner driver knows the ids of
your scanner (see section <B>GENERIC</B> <B>KERNEL</B> <B>SCANNER</B> <B>DRIVER</B>).
</PRE>
<H2>USB ACCESS METHODS</H2><PRE>
Two methods for accessing USB devices are currently in use: direct
access using the kernel scanner driver and access over libusb. By
default, both methods are tried by SANE, if they are available. Cur-
rently USB access is tested for Linux (kernel, libusb), FreeBSD (ker-
nel, libsub), NetBSD (libusb), OpenBSD (kernel, libusb) and MacOS X
(libusb). Testing on MacOS X is very limited and not all scanners seem
to work reliably with the BSDs. For installation issues, also check the
/usr/local/doc/sane-1.0.12-cvs/README.platform files.
Generally speaking, if your scanner works with one method, there is no
need to switch to the other one.
Libusb is the more general approach and is able to access any scanner.
Also, it supports more platforms.
Autodetecting scanners and using USB control messages with the kernel
access method only works with recent (&gt;=v2.4.12) Linux kernels. If you
need one of these two features on a different platform, use libusb
instead. Also, the kernel scanner driver may be removed from Linux
2.5/2.6 in future so libusb will be the only access method.
</PRE>
<H2>LIBUSB</H2><PRE>
SANE can only use libusb 0.1.6 or newer. It needs to be installed at
build-time.
Libusb can only access your scanner if it's not claimed by the kernel
scanner driver. If you want to use libusb, unload the kernel driver
(e.g. rmmod scanner under Linux) or disable the driver when compiling a
new kernel. For Linux, your kernel needs support for the USB filesystem
(usbfs). For kernels older than 2.4.19, replace "usbfs" with "usbdevfs"
because the name has changed. This filesystem must be mounted. That's
done automatically at boot time, if /etc/fstab contains a line like
this:
none /proc/bus/usb usbfs defaults 0 0
The permissions for the device files used by libusb must be adjusted
for user access. Otherwise only root can use SANE devices. For <I>Linux</I>,
the devices are located in /proc/bus/usb/. There are directories named
e.g. "001" (the bus name) containing files "001", "002" etc. (the
device files). The right device files can be found out by running scan-
image -L as root. Setting permissions with "chmod" is not permanent,
however. They will be resetted after reboot or replugging the scanner.
It's also possible to mount the usbfs with the option "devmode=0666",
e.g. by using the following line in /etc/fstab:
none /proc/bus/usb usbfs defaults,devmode=0666 0 0
However, this way everyone has access to all USB devices. Another way
to set permissions is to use the hotplug utilities (<I>http://linux-hot-</I>
<I>plug.sourceforge.net/</I>), which support dynamic setting of access permis-
sions. Last, the frontends can be run as root. However, that's not rec-
ommended for security reasons.
For the <B>BSDs</B>, the device files are named <I>/dev/ugen*</I>. Use chmod to
apply appropriate permissions.
</PRE>
<H2>GENERIC KERNEL SCANNER DRIVER</H2><PRE>
Ensure that the access permissions for the USB device are set appropri-
ately. We recommend to add a group "scanner" to <I>/etc/group</I> which con-
tains all users that should have access to the scanner. The permission
of the device should then be set to allow group read and write access.
For example, if the scanner is at USB device <B>/dev/usb/scanner0</B>, then
the following two commands would set the permission correctly:
$ chgrp scanner /dev/usb/scanner0
$ chmod 660 /dev/usb/scanner0
If your scanner isn't detected automatically by your operating system's
scanner driver, you need to tell the kernel the vendor and product ids
of your scanner. For <B>Linux</B>, this can be done with modprobe parameters:
First, remove the scanner module (<I>rmmod</I> <I>scanner</I>), then load it again:
<I>modprobe</I> <I>scanner</I> <I>vendor=0x0001</I> <I>product=0x0002</I>. Use the appropriate
vendor and product ids (e.g. from <I>/var/log/messages</I>, <I>dmesg</I>, or <I>cat</I>
<I>/proc/bus/usb/devices</I>). Some scanners supported by the gt68xx backend
are not supported by the current version of the generic scanner driver.
See <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B> for details. For these scanners, there will be a
message concerning "only 2 or three endpoints" in syslog.
For OpenBSD the kernel may need to be recompiled. For details look at
/usr/local/doc/sane-1.0.12-cvs/README.openbsd. Similar approaches
should be used for the other BSDs.
Linux kernel messages in syslog like "kernel: scanner.c:
<B><A HREF="open_scanner.1.html">open_scanner(1)</A></B>: Unable to access minor data" can be ignored. They are
generated when SANE scans all available USB devices for scanners.
</PRE>
<H2>SANE ISSUES</H2><PRE>
This section assumes that your scanner is detected by sane-find-scan-
ner. It doesn't make sense to go on, if this is not the case. While
sane-find-scanner is able to detect any USB scanner, actual scanning
will only work if the scanner is supported by a SANE backend. Informa-
tion on the level of support can be found on the SANE webpage
(<I>http://www.mostang.com/sane/</I>), and the individual backend manpages.
Most backends can detect USB scanners automatically using "usb" config-
uration file lines. This method allows to identify scanners by the USB
vendor and product numbers. The syntax for specifying a scanner this
way is:
usb <I>VENDOR</I> <I>PRODUCT</I>
where <I>VENDOR</I> is the USB vendor id, and <I>PRODUCT</I> is the USB product id of
the scanner. Both ids are non-negative integer numbers in decimal or
hexadecimal format. The correct values for these fields can be found by
looking into the syslog (e.g., /var/log/messages) or under Linux by
issuing the command "cat /proc/bus/usb/devices/". This is an example
of a config file line:
usb 0x055f 0x0006
would have the effect that all USB devices in the system with a vendor
id of 0x55f and a product id of 0x0006 would be probed and recognized
by the backend.
If your scanner is not detected automatically, it may be necessary to
edit the appropriate backend configuration file before using SANE for
the first time. For most systems, the configuration file should list
the name of the USB device file that the scanner is connected to (e.g.,
under Linux, <B>/dev/usb/scanner0</B> or <B>/dev/usbscanner0</B> is such a USB
device, the device file for FreeBSD is e.g. <B>/dev/uscanner0</B>). If
libusb is used, the device name looks like the following example:
<B>libusb:001:002</B>.
For a detailed description of each backend's configuration file, please
refer to the relevant backend manual page (e.g. <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B> for
Mustek USB scanners).
Do <B>not</B> create a symlink from <I>/dev/scanner</I> to the USB device because
this link is used by the SCSI backends. The scanner may be confused if
it receives SCSI commands.
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_SANEI_USB</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for the USB I/O
subsystem. E.g., a value of 128 requests all debug output to be
printed. Smaller levels reduce verbosity. Values greater than 4
enable libusb debugging (if available). Example: export
SANE_DEBUG_SANEI_USB=4.
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>, <B>sane-"backendname"</B>(5), <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>
</PRE>
<H2>AUTHOR</H2><PRE>
Henning Meier-Geinitz
sane-backends 1.0.12-cvs 27 Nov 2002 <B><A HREF="sane-usb.5.html">sane-usb(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>

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

@ -0,0 +1,115 @@
<HTML>
<HEAD>
<TITLE>sane-v4l.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-v4l.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-v4l.5.html">sane-v4l(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-v4l.5.html">sane-v4l(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-v4l - SANE interface for Video for Linux API
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-v4l</B> library implements a SANE (Scanner Access Now Easy) back-
end that provides generic access to video cameras and similar equipment
using the V4L (Video for Linux) API.
This is ALPHA software. Really! Important features are missing and
there are lots of bugs. The code is currently only tested on a Linux
2.4 system with a Hauppauge WinTV video card.
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form:
<I>special</I>
Where <I>special</I> is the UNIX path-name for the special device that corre-
sponds to the v4l device. The special device name must be a v4l device
or a symlink to such a device. For example, such a device name could
be <I>/dev/video0</I> or <I>/dev/bttv0</I>.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>v4l.conf</I> file is a list of device names that corre-
spond to v4l devices. Empty lines and lines starting with a hash mark
(#) are ignored. A sample configuration file is shown below:
/dev/bttv0
# this is a comment
/dev/video3
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/v4l.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-v4l.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-v4l.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_V4L</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>AUTHOR</H2><PRE>
Juergen G. Schimmer, Henning Meier-Geinitz
</PRE>
<H2>BUGS:</H2><PRE>
If more than one video card is present, a crash may occur. Frequency
and geometry selection is missing.
Send bug reports to the SANE mailing list: sane-devel@mostang.com. You
must be subscribed to the list to send mail. See
http://www.mostang.com/sane/mail.html for details.
</PRE>
<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.12-cvs 28 Aug 2002 <B><A HREF="sane-v4l.5.html">sane-v4l(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>

642
man/sane.7.html 100644
Wyświetl plik

@ -0,0 +1,642 @@
<HTML>
<HEAD>
<TITLE>sane.7</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane.7</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane.7.html">sane(7)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane.7.html">sane(7)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane - Scanner Access Now Easy: API for accessing scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
<B>SANE</B> is an application programming interface (API) that provides stan-
dardized access to any raster image scanner hardware. The standardized
interface makes it possible to write just one driver for each scanner
device instead of one driver for each scanner and application.
While <B>SANE</B> is primarily targeted at a UNIX environment, the standard
has been carefully designed to make it possible to implement the API on
virtually any hardware or operating system.
This manual page provides a summary of the information available about
<B>SANE</B>.
If you have trouble getting your scanner detected, read the PROBLEMS
section.
</PRE>
<H2>TERMINOLOGY</H2><PRE>
An application that uses the <B>SANE</B> interface is called a <B>SANE</B> <B>frontend.</B>
A driver that implements the <B>SANE</B> interface is called a <B>SANE</B> <B>backend.</B>
A <B>meta</B> <B>backend</B> provides some means to manage one or more other back-
ends.
</PRE>
<H2>SOFTWARE PACKAGES</H2><PRE>
The package `<B>sane-backends</B>' contains a lot of backends, documentation
(including the <B>SANE</B> standard), networking support, and the command line
frontend `<B>scanimage</B>'. The frontends `<B>xscanimage</B>', `<B>xcam</B>', and
`<B>scanadf</B>' are included in the package `<B>sane-frontends</B>'. Both packages
can be downloaded from the <B>SANE</B> homepage
(<I>http://www.mostang.com/sane/</I>). Information about other frontends and
backends can be found on the frontend page
(<I>http://www.mostang.com/sane/frontends.html</I>).
</PRE>
<H2>GENERAL INFORMATION</H2><PRE>
The following sections provide short descriptions and links to more
information about several aspects of <B>SANE.</B> A name with a number in
parenthesis (e.g. `<B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>') points to a manual page. In this case
`<B>man</B> <B>5</B> <B>sane-dll</B>' will display the page. Entries like
`<I>/usr/local/doc/sane-1.0.12-cvs/sane.tex</I>' are references to text files
that were copied to the <B>SANE</B> documentation directory
(<I>/usr/local/doc/sane-1.0.12-cvs/</I>) during installation. Everything else
is a URL to a resource on the web.
<B>SANE</B> <B>homepage</B>
Information on all aspects of SANE including a tutorial and a link to
the SANE FAQ can be found on the SANE homepage:
<I>http://www.mostang.com/sane/</I>.
<B>SANE</B> <B>device</B> <B>lists</B>
The <B>SANE</B> device lists contain information about the status of <B>SANE</B>
support for a specific device. If your scanner is not listed there
(either supported or unsupported), please contact us. See section HOW
CAN YOU HELP SANE for details. There are lists for specific releases
of SANE, for the current development version and a search engine:
<I>http://www.mostang.com/sane/sane-supported-devices.html</I>. The lists
are also installed on your system at /usr/local/doc/sane-1.0.12-cvs/.
<B>SANE</B> <B>mailing</B> <B>list</B>
There is a mailing list for the purpose of discussing the SANE stan-
dard and its implementations: sane-devel. Despite its name, the list
is not only intended for developers, but also for users. Since this
is currently the only mailing list devoted to SANE, it's perfectly OK
to ask questions that are not strictly related to SANE development.
How to subscribe and unsubscribe:
<I>http://www.mostang.com/sane/mail.html</I>.
<B>SANE</B> <B>IRC</B> <B>channel</B>
The IRC (Internet Relay Chat) channel #sane can be found on the
Freenode network (irc.freenode.net). It's for discussing <B>SANE</B> prob-
lems, talking about development and general <B>SANE</B> related chatting.
Before asking for help, please read the other documentation mentioned
in this manual page.
<B>Compiling</B> <B>and</B> <B>installing</B> <B>SANE</B>
Look at <I>/usr/local/doc/sane-1.0.12-cvs/README</I> and the os-dependent
README files for information about compiling and installing <B>SANE.</B>
<B>SCSI</B> <B>configuration</B>
For information about various systems and SCSI controllers see
<B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>.
<B>USB</B> <B>configuration</B>
For information about USB configuration see <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>.
</PRE>
<H2>FRONTENDS AND MISCELLANEOUS PROGRAMS</H2><PRE>
<B>scanimage</B>
Command-line frontend. See <B><A HREF="scanimage.1.html">scanimage(1)</A></B>.
<B>saned</B>
<B>SANE</B> network daemon that allows remote clients to access image acqui-
sition devices available on the local host. See <B><A HREF="saned.1.html">saned(1)</A></B>.
<B>sane-find-scanner</B>
Command-line tool to find SCSI and USB scanners and determine their
Unix device files. See <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>.
Also, have a look at the <B>sane-frontends</B> package (including <B>xscanimage</B>,
<B>xcam</B>, and <B>scanadf</B>) and the frontend information page at
<I>http://www.mostang.com/sane/sane-frontends.html</I>.
</PRE>
<H2>BACKENDS FOR SCANNERS</H2><PRE>
<B>abaton</B>
The SANE backend for Abaton flatbed scanners supports the Scan 300/GS
(8bit, 256 levels of gray) and the Scan 300/S (black and white,
untested). See <B><A HREF="sane-abaton.5.html">sane-abaton(5)</A></B> for details.
<B>agfafocus</B>
This backend supports AGFA Focus scanners and the Siemens S9036
(untested). See <B><A HREF="sane-agfafocus.5.html">sane-agfafocus(5)</A></B> for details.
<B>apple</B>
The SANE backend for Apple flatbed scanners supports the following
scanners: AppleScanner, OneScanner and ColorOneScanner. See
<B><A HREF="sane-apple.5.html">sane-apple(5)</A></B> for details.
<B>artec</B>
The SANE Artec backend supports several Artec/Ultima SCSI flatbed
scanners as well as the BlackWidow BW4800SP and the Plustek 19200S.
See <B><A HREF="sane-artec.5.html">sane-artec(5)</A></B> for details.
<B>artec_eplus48u</B>
The SANE artec_eplus48u backend supports the scanner Artec E+ 48U and
re-badged models like Tevion MD 9693, Medion MD 9693, Medion MD 9705
and Trust Easy Webscan 19200. See <B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B> for details.
<B>as6e</B>
This is a SANE backend for using the Artec AS6E parallel port inter-
face scanner. See <B><A HREF="sane-as6e.5.html">sane-as6e(5)</A></B> for details.
<B>avision</B>
This backend supports several Avision based scanners. This includes
the original Avision scanners (like AV 630, AV 620, ...) as well as
the HP ScanJet 53xx and 74xx series, Fujitsu ScanPartner, some Mit-
subishi and Minolta film-scanners. See <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B> for details.
<B>bh</B>
The bh backend provides access to Bell+Howell Copiscan II series doc-
ument scanners. See <B><A HREF="sane-bh.5.html">sane-bh(5)</A></B> for details.
<B>canon</B>
The canon backend supports the CanoScan 300, CanoScan 600, and
CanoScan 2700F SCSI flatbed scanners. See <B><A HREF="sane-canon.5.html">sane-canon(5)</A></B> for details.
<B>canon630u</B>
The canon630u backend supports the CanoScan 630u and 636u USB scan-
ners. See <B><A HREF="sane-canon630u.5.html">sane-canon630u(5)</A></B> for details.
<B>canon_pp</B>
The canon_pp backend supports the CanoScan FB330P, FB630P, N340P and
N640P parallel port scanners. See <B><A HREF="sane-canon_pp.5.html">sane-canon_pp(5)</A></B> for details.
<B>coolscan</B>
This is a SANE backend for Nikon Coolscan film-scanners. See
<B><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B> for details.
<B>coolscan2</B>
This is a SANE backend for Nikon Coolscan film-scanners. See
<B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B> or <I>http://coolscan2.sourceforge.net</I> for details.
<B>epson</B>
The SANE epson backend provides support for Epson SCSI, parallel port
and USB flatbed scanners. See <B><A HREF="sane-epson.5.html">sane-epson(5)</A></B> for details.
<B>fujitsu</B>
The fujitsu backend provides support for Fujitsu 3091, 3093, 3096 and
fi-4340 SCSI scanners. See <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B> for details.
<B>gt68xx</B>
The gt68xx backend provides support for scanners based on the
Grandtech GT-6801 and GT-6816 chips like the Artec Ultima 2000 and
several Mustek BearPaw CU and TA models. Some Genius, Lexmark,
Medion, Packard Bell, Plustek, and Trust scanners are also supported.
See <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B> for details.
<B>hp</B>
The SANE hp backend provides access to Hewlett-Packard ScanJet scan-
ners which support SCL (Scanner Control Language by HP). See
<B><A HREF="sane-hp.5.html">sane-hp(5)</A></B> for details.
<B>hpsj5s</B>
The SANE backend for the Hewlett-Packard ScanJet 5S scanner. See
<B><A HREF="sane-hpsj5s.5.html">sane-hpsj5s(5)</A></B> for details.
<B>hp5400</B>
The SANE backend for the Hewlett-Packard ScanJet 54XXC series. See
<B><A HREF="sane-hp5400.5.html">sane-hp5400(5)</A></B> for details.
<B>ibm</B>
The SANE backend for some IBM and Ricoh SCSI scanners. See
<B><A HREF="sane-ibm.5.html">sane-ibm(5)</A></B> for details.
<B>leo</B>
This backend supports the Leo S3 and the Across FS-1130, which is a
re-badged LEO FS-1130 scanner. See <B><A HREF="sane-leo.5.html">sane-leo(5)</A></B> for details.
<B>ma1509</B>
The ma1509 backend supports the Mustek BearPaw 1200F USB flatbed
scanner. See <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B> for details.
<B>matsushita</B>
This backend supports some Panasonic KVSS high speed scanners. See
<B><A HREF="sane-matsushita.5.html">sane-matsushita(5)</A></B> for details.
<B>microtek</B>
The microtek backend provides access to the "second generation"
Microtek scanners with SCSI-1 command set. See <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B> for
details.
<B>microtek2</B>
The microtek2 backend provides access to some Microtek scanners with
a SCSI-2 command set. See <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B> for details.
<B>mustek</B>
The SANE mustek backend supports most Mustek SCSI flatbed scanners
including the Paragon and ScanExpress series and the 600 II N (non-
SCSI). Some Trust scanners are also supported. See <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B> for
details.
<B>mustek_pp</B>
The mustek_pp backend provides access to Mustek parallel port flatbed
scanners. See <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B> for details.
<B>mustek_usb</B>
The mustek_usb backend provides access to some Mustek ScanExpress USB
flatbed scanners. See <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B> for details.
<B>nec</B>
The SANE nec backend supports the NEC PC-IN500/4C SCSI scanner. See
<B><A HREF="sane-nec.5.html">sane-nec(5)</A></B> for details.
<B>pie</B>
The pie backend provides access to Pacific Image Electronics (PIE)
and Devcom SCSI flatbed scanners. See <B><A HREF="sane-pie.5.html">sane-pie(5)</A></B> for details.
<B>plustek</B>
The SANE plustek backend supports Plustek parallel port and
LM983[1/2/3] based USB flatbed scanners. Scanners using the LM983x
chips include some models from Plustek, KYE/Genius, Hewlett-Packard,
Mustek, Umax, Epson, and Canon. See <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B> for details.
<B>ricoh</B>
The ricoh backend provides access to the following Ricoh flatbed
scanners: IS50 and IS60. See <B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B> for details.
<B>s9036</B>
The s9036 backend provides access to Siemens 9036 flatbed scanners.
See <B><A HREF="sane-s9036.5.html">sane-s9036(5)</A></B> for details.
<B>sceptre</B>
The sceptre backend provides access to the Sceptre S1200 flatbed
scanner. See <B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B>
for details.
<B>sharp</B>
The SANE sharp backend supports Sharp SCSI scanners. See
<B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B> for details.
<B>sm3600</B>
The SANE sm3600 backend supports the Microtek ScanMaker 3600 USB
scanner. See <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B> for details.
<B>snapscan</B>
The snapscan backend supports AGFA SnapScan flatbed scanners. See
<B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B> for details.
<B>sp15c</B>
This backend supports the Fujitsu FCPA ScanPartner 15C flatbed scan-
ner. See <B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B> for details.
<B>st400</B>
The sane-st400 backend provides access to Siemens ST400 and ST800.
See <B><A HREF="sane-st400.5.html">sane-st400(5)</A></B> for details.
<B>tamarack</B>
The SANE tamarack backend supports Tamarack Artiscan flatbed scan-
ners. See <B><A HREF="sane-tamarack.5.html">sane-tamarack(5)</A></B> for details.
<B>teco1</B> <B>teco2</B> <B>teco3</B>
The SANE teco1, teco2 and teco3 backends support some TECO scanners,
usually sold under the Relisys, Trust, Primax, Piotech, Dextra names.
See <B><A HREF="sane-teco1.5.html">sane-teco1(5)</A></B>, <B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B> and <B><A HREF="sane-teco3.5.html">sane-teco3(5)</A></B> for details.
<B>umax</B>
The sane-umax backend provides access to several UMAX-SCSI-scanners
and some Linotype Hell SCSI-scanners. See <B><A HREF="sane-umax.5.html">sane-umax(5)</A></B> for details.
<B>umax_pp</B>
The sane-umax_pp backend provides access to Umax parallel port
flatbed scanners and the HP 3200C. See <B><A HREF="sane-umax_pp.5.html">sane-umax_pp(5)</A></B> for details.
<B>umax1200u</B>
The sane-umax1220u backend supports the UMAX Astra 1220U (USB)
flatbed scanner (and also the UMAX Astra 2000U, sort of). See
<B><A HREF="sane-umax1220u.5.html">sane-umax1220u(5)</A></B> for details.
Also, have a look at the backend information page at
<I>http://www.mostang.com/sane/sane-supported-devices.html</I> and the list of
projects in <I>/usr/local/doc/sane-1.0.12-cvs/PROJECTS</I>.
</PRE>
<H2>BACKENDS FOR DIGITAL CAMERAS</H2><PRE>
<B>dc210</B>
Backend for Kodak DC210 Digital Camera. See <B><A HREF="sane-dc210.5.html">sane-dc210(5)</A></B>.
<B>dc240</B>
Backend for Kodak DC240 Digital Camera. See <B><A HREF="sane-dc240.5.html">sane-dc240(5)</A></B>.
<B>dc25</B>
Backend for Kodak DC20/DC25 Digital Cameras. See <B><A HREF="sane-dc25.5.html">sane-dc25(5)</A></B>.
<B>dmc</B>
Backend for the Polaroid Digital Microscope Camera. See <B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B>.
<B>gphoto2</B>
Backend for digital cameras supported by the gphoto2 library package.
(See <I>http://www.gphoto.org</I> for more information and a list of sup-
ported cameras.) Gphoto2 supports over 140 different camera models.
However, please note that more development and testing is needed
before all of these cameras will be supported by <B>SANE</B> backend. See
<B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>.
<B>qcam</B>
Backend for Connectix QuickCam cameras. See <B><A HREF="sane-qcam.5.html">sane-qcam(5)</A></B>.
Also, have a look at the backend information page at
<I>http://www.mostang.com/sane/sane-supported-devices.html</I> and the list of
projects in <I>/usr/local/doc/sane-1.0.12-cvs/PROJECTS</I>.
</PRE>
<H2>MISCELLANEOUS BACKENDS</H2><PRE>
<B>dll</B>
The sane-dll library implements a <B>SANE</B> backend that provides access
to an arbitrary number of other <B>SANE</B> backends by dynamic loading. See
<B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>.
<B>net</B>
The <B>SANE</B> network daemon saned provides access to scanners located on
different computers in connection with the net backend. See
<B><A HREF="sane-net.5.html">sane-net(5)</A></B> and <B><A HREF="saned.1.html">saned(1)</A></B>.
<B>pnm</B>
PNM image reader pseudo-backend. The purpose of this backend is pri-
marily to aid in debugging of <B>SANE</B> frontends. See <B><A HREF="sane-pnm.5.html">sane-pnm(5)</A></B>.
<B>pint</B>
Backend for scanners that use the <B>PINT</B> (Pint Is Not Twain) device
driver. The <B>PINT</B> driver is being actively developed on the OpenBSD
platform, and has been ported to a few other *nix-like operating sys-
tems. See <B><A HREF="sane-pint.5.html">sane-pint(5)</A></B>.
<B>test</B>
The <B>SANE</B> test backend is for testing frontends and the <B>SANE</B> installa-
tion. It provides test pictures and various test options. See
<B><A HREF="sane-test.5.html">sane-test(5)</A></B>.
<B>v4l</B>
The sane-v4l library implements a <B>SANE</B> backend that provides generic
access to video cameras and similar equipment using the <B>V4L</B> (Video
for Linux) API. See <B><A HREF="sane-v4l.5.html">sane-v4l(5)</A></B><B>.</B>
Also, have a look at the backend information page at
<I>http://www.mostang.com/sane/sane-supported-devices.html</I> and the list of
projects in <I>/usr/local/doc/sane-1.0.12-cvs/PROJECTS</I>.
</PRE>
<H2>CHANGING THE TOP-LEVEL BACKEND</H2><PRE>
By default, all <B>SANE</B> backends (drivers) are loaded dynamically by the
<B>sane-dll</B> meta backend. If you have any questions about the dynamic
loading, read <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>. <B>SANE</B> frontend can also be linked to other
backends directly by copying or linking a backend to <B>libsane.so</B> in
<I>/usr/local/lib/sane</I>.
</PRE>
<H2>DEVELOPER'S DOCUMENTATION</H2><PRE>
It's not hard to write a <B>SANE</B> backend. It can take some time, however.
You should have basic knowledege of C and enough patience to work
through the documentation and find out how your scanner works. Appended
is a list of some documents that help to write backends and frontends.
The <B>SANE</B> standard defines the application programming interface (API)
that is used to communicate between frontends and backends. It can be
found at <I>/usr/local/doc/sane-1.0.12-cvs/sane.ps</I> (if latex is installed
on your system) and on the <B>SANE</B> website:
<I>http://www.mostang.com/sane/html/</I> (HTML), or
<I>http://www.mostang.com/sane/sane.ps</I> (Postscript).
There is some more information for programmers in
<I>/usr/local/doc/sane-1.0.12-cvs/backend-writing.txt</I>. Most of the inter-
nal <B>SANE</B> routines (<B>sanei</B>) are documented using doxygen:
<I>http://sanei.meier-geinitz.de/</I>. Before a new backend or frontend
project is started, have a look at
<I>/usr/local/doc/sane-1.0.12-cvs/PROJECTS</I> for projects that are planned
or not yet included into the <B>SANE</B> distribution and at the todo list:
<I>/usr/local/doc/sane-1.0.12-cvs/TODO</I>.
There are some links on how to find out about the protocol of a scan-
ner: <I>http://www.meier-geinitz.de/sane/misc/develop.html</I>.
If you start writing a backend or frontend or any other part of <B>SANE,</B>
please contact the sane-devel mailing list for coordination so the same
work isn't done twice.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/*.conf</I>
The backend configuration files.
<I>/usr/local/lib/sane/libsane-*.a</I>
The static libraries implementing the backends.
<I>/usr/local/lib/sane/libsane-*.so</I>
The shared libraries implementing the backends (present on sys-
tems that support dynamic loading).
<I>/usr/local/doc/sane-1.0.12-cvs/*</I>
<B>SANE</B> documentation: The standard, READMEs, text files for back-
ends etc.
</PRE>
<H2>PROBLEMS</H2><PRE>
If your device isn't found but you know that it is supported, make sure
that it is detected by your operating system. For SCSI and USB scan-
ners, use the <B>sane-find-scanner</B> tool (see <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B> for
details). It prints one line for each scanner it has detected and some
comments (#). If <B>sane-find-scanner</B> finds your scanner only as root but
not as normal user, the permissions for the device files are not
adjusted correctly. If the scanner isn't found at all, the operating
system hasn't detected it and may need some help. Depending on the type
of your scanner, read <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B> or <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>. If your scanner (or
other device) is not connected over the SCSI bus or USB, read the back-
end's manual page for details on how to set it up.
Now your scanner is detected by the operating system but not by <B>SANE</B>?
Try <B>scanimage</B> <B>-L</B>. If the scanner is not found, check that the back-
end's name is mentioned in <I>/usr/local/etc/sane.d/dll.conf</I>. Some back-
ends are commented out by default. Remove the comment sign for your
backend in this case. Also some backends aren't compiled at all if one
of their prerequisites are missing. Examples include dc210, dc240,
canon_pp, hpsj5s, gphoto2, pint, qcam, v4l, net, sm3600, snapscan, pnm.
If you need one of these backends and they aren't available, read the
build instructions in the <B>README</B> file and the individual manual pages
of the backends.
Another reason for not beeing detected by <B>scanimage</B> <B>-L</B> may be a missing
or wrong configuration in the backend's configuration file. While <B>SANE</B>
tries to automatically find most scanners, some can't be setup cor-
rectly without the intervention of the administrator. Also on some
operating systems auto-detection may not work. Check the backend's man-
ual page for details.
If your scanner is still not found, try setting the various environment
variables that are available to assist in debugging. The environment
variables are documented in the relevant manual pages. For example, to
get the maximum amount of debug information when testing a Mustek SCSI
scanner, set environment variables <B>SANE_DEBUG_DLL</B>, <B>SANE_DEBUG_MUSTEK</B>,
and <B>SANE_DEBUG_SANEI_SCSI</B> to 128 and then invoke <B>scanimage</B> <B>-L</B> <B>.</B> The
debug messages for the dll backend tell if the mustek backend was found
and loaded at all. The mustek messages explain what the mustek backend
is doing while the SCSI debugging shows the low level handling. If you
can't find out what's going on by checking the messages carefully, con-
tact the sane-devel mailing list for help (see REPORTING BUGS below).
Now that your scanner is found by <B>scanimage</B> <B>-L</B>, try to do a scan: <B>scan-</B>
<B>image</B> <B>&gt;image.pnm</B>. This command starts a scan for the default scanner
with default settings. All the available options are listed by running
<B>scanimage</B> <B>--help</B>. If scanning aborts with an error message, turn on
debugging as mentioned above. Maybe the configuration file needs some
tuning, e.g. to setup the path to a firmware that is needed by some
scanners. See the backend's maunal page for details. If you can't find
out what's wrong, contact sane-devel.
To check that the <B>SANE</B> libraries are installed correctly you can use
the test backend, even if you don't have a scanner or other <B>SANE</B>
device:
<B>scanimage</B> <B>-d</B> <I>test</I> <B>-T</B>
You should get a list of PASSed tests. You can do the same with your
backend by changing "test" to your backend's name.
So now scanning with <B>scanimage</B> works and you want to use one of the
graphical frontends like <B>xsane</B>, <B>xscanimage</B>, or <B>quiteinsane</B> but those
frontends don't detect your scanner? One reason may be that you
installed two versions of <B>SANE</B>. E.g. the version that was installed by
your distribution in <I>/usr</I> and one you installed from source in
<I>/usr/local/</I>. Make sure that only one version is installed. Another
possible reason is, that your system's dynamic loader can't find the
<B>SANE</B> libraries. For Linux, make sure that <I>/etc/ld.so.conf</I> contains
<I>/usr/local/lib</I> and does <B>not</B> contain <I>/usr/local/lib/sane</I>. See also the
documentation of the frontends.
</PRE>
<H2>HOW CAN YOU HELP SANE</H2><PRE>
We appreciate any help we can get. Here are some topics on which you
can work:
<B>Writing</B> <B>backends</B>
Without a backend, a scanner doesn't work. So it's crucial we
have backends for as much devices as possible. It's not neces-
sary to be an experienced programmer to start writing a backend.
If you have an unsupported scanner, writing a backend yourself
is probably the only way to get it supported. See DEVELOPER'S
DOCUMENTATION for details. But first make sure that you get any
information about your scanner that is available (see below),
and check if your scanner can be supported by an already exist-
ing backend with only small modifications.
<B>Writing</B> <B>frontends</B>
There are already some very capable frontends. So helping with
improving the existing frontends may make more sense than to
write yet another one. On the other hand there may be reasons to
start writing a completely new frontend, like support for a spe-
cific widget set, a programming language or a special type of
devices (e.g. cameras, slide scanners). In any case, keep the
sane-devel mailinglist informed of your plans.
<B>Reporting</B> <B>unsupported</B> <B>scanners</B>
Even if you can't write a backend for your unsupported scanner,
please send us all the information you have about it. We need
the make and the model name of your scanner. Also provide an
output of <B>sane-find-scanner</B> <B>-v</B> <B>-v</B>. For Linux: If it's a SCSI
scanner, show us the output of <B>cat</B> <B>/proc/scsi/scsi</B>, for a USB
scanner: <B>cat</B> <B>/proc/bus/usb/devices</B> (if the file is not there, do
<B>mount</B> <B>-t</B> <B>usbdevfs</B> <B>/proc/bus/usb</B> <B>/proc/bus/usb</B>). See CONTACT
section.
<B>Reporting</B> <B>bugs</B> <B>and</B> <B>missing</B> <B>features</B>
If you think something in <B>SANE</B> isn't working as it should,
please don't hesiate to contact us (see COTACT scetion). Please
provide as many details as possible. Describe which software you
are using (operating system + version, distribution, version of
sane-backends and of the frontend you use). Explain exactly what
doesn't work, is wrong or missing.
<B>Adding</B> <B>and</B> <B>fixing</B> <B>documentation</B>
If you found a bug in any documentation (man pages, web site,
READMEs), please contact us (see CONTACT section). Also write us
if you think some documentation is missing. Please include a
patch in this case, if possible. Don't hesitate to send spelling
and grammar mistakes.
<B>Translations</B>
The options of the backends can be translated. For some lan-
guages, the translations are almost complete, but some are lack-
ing a lot of words and for most languages there is no transla-
tion at all. If you want to help to translate the options to
your native language (or a language you speak fluently), contact
the sane-devel mailing list and have a look at the <I>po/</I> directory
in the source code.
<B>Success</B> <B>reports</B>
If you had success using <B>SANE</B> we want to know about that, too.
Especially if your scanner is not in the lists yet or is marked
"untested".
</PRE>
<H2>CONTACT</H2><PRE>
If you want to comment on a backend-specific problem, contact the
author of your backend. Usually the email address can be found in the
<I>/usr/local/doc/sane-1.0.12-cvs/AUTHORS</I> file or the backend's manpage.
If the author isn't marked as `active maintainer' or doesn't answer,
you can also contact the <B>SANE</B> mailing list sane-devel (see
<I>http://www.mostang.com/sane/mail.html</I> for details). You must be sub-
scribed to the list, otherwise your mail won't be sent to the sub-
scribers.
If you want to report bugs concerning security, compilation, installa-
tion, porting, and documentation of <B>SANE</B>, you can also contact the
author of this manual page: &lt;henning@meier-geinitz.de&gt;.
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="saned.1.html">saned(1)</A></B>, <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="sane-abaton.5.html">sane-abaton(5)</A></B>,
<B><A HREF="sane-agfafocus.5.html">sane-agfafocus(5)</A></B>, <B><A HREF="sane-apple.5.html">sane-apple(5)</A></B>, <B><A HREF="sane-artec.5.html">sane-artec(5)</A></B>,
<B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B>, <B><A HREF="sane-as6e.5.html">sane-as6e(5)</A></B>, <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B>, <B><A HREF="sane-bh.5.html">sane-bh(5)</A></B>,
<B><A HREF="sane-canon.5.html">sane-canon(5)</A></B>, <B><A HREF="sane-canon630u.5.html">sane-canon630u(5)</A></B>, <B><A HREF="sane-canon_pp.5.html">sane-canon_pp(5)</A></B>, <B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B>,
<B><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B>, <B><A HREF="sane-dc210.5.html">sane-dc210(5)</A></B>, <B><A HREF="sane-dc240.5.html">sane-dc240(5)</A></B>, <B><A HREF="sane-dc25.5.html">sane-dc25(5)</A></B>,
<B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>, <B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B>, <B><A HREF="sane-epson.5.html">sane-epson(5)</A></B>, <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>,
<B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>, <B><A HREF="sane-hp.5.html">sane-hp(5)</A></B>, <B><A HREF="sane-hpsj5s.5.html">sane-hpsj5s(5)</A></B>,
<B><A HREF="sane-hp5400.5.html">sane-hp5400(5)</A></B> <B><A HREF="sane-ibm.5.html">sane-ibm(5)</A></B>, <B><A HREF="sane-leo.5.html">sane-leo(5)</A></B>, <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>, <B>sane-mat-</B>
<B><A HREF="sushita.5.html">sushita(5)</A></B>, <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B>, <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>,
<B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>, <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B><A HREF="sane-nec.5.html">sane-nec(5)</A></B>, <B><A HREF="sane-net.5.html">sane-net(5)</A></B>,
<B><A HREF="sane-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-pnm.5.html">sane-pnm(5)</A></B>, <B><A HREF="sane-qcam.5.html">sane-qcam(5)</A></B>,
<B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B>, <B><A HREF="sane-s9036.5.html">sane-s9036(5)</A></B>, <B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>,
<B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B>, <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B>, <B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B>, <B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B>,
<B><A HREF="sane-st400.5.html">sane-st400(5)</A></B>, <B><A HREF="sane-tamarack.5.html">sane-tamarack(5)</A></B>, <B><A HREF="sane-teco1.5.html">sane-teco1(5)</A></B>, <B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B>,
<B><A HREF="sane-teco3.5.html">sane-teco3(5)</A></B>, <B><A HREF="sane-test.5.html">sane-test(5)</A></B>, <B><A HREF="sane-umax1220u.5.html">sane-umax1220u(5)</A></B>, <B><A HREF="sane-umax.5.html">sane-umax(5)</A></B>,
<B><A HREF="sane-umax_pp.5.html">sane-umax_pp(5)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-v4l.5.html">sane-v4l(5)</A></B>
</PRE>
<H2>AUTHOR</H2><PRE>
David Mosberger-Tang and many many more (see
<I>/usr/local/doc/sane-1.0.12-cvs/AUTHORS</I> for details). This man page was
written by Henning Meier-Geinitz. Quite a lot of text was taken from
the <B>SANE</B> standard, several man pages, and README files.
sane-backends 1.0.12-cvs 19 Apr 2003 <B><A HREF="sane.7.html">sane(7)</A></B>
</PRE>
<HR>
<ADDRESS>
Man(1) output converted with
<a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a>
</ADDRESS>
</BODY>
</HTML>

181
man/saned.1.html 100644
Wyświetl plik

@ -0,0 +1,181 @@
<HTML>
<HEAD>
<TITLE>saned.1</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>saned.1</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="saned.1.html">saned(1)</A></B> SANE Scanner Access Now Easy <B><A HREF="saned.1.html">saned(1)</A></B>
</PRE>
<H2>NAME</H2><PRE>
saned - SANE network daemon
</PRE>
<H2>SYNOPSIS</H2><PRE>
<B>saned</B> [<B>-d</B>|<B>-s</B> [<I>n</I>]]
</PRE>
<H2>DESCRIPTION</H2><PRE>
<B>saned</B> is the SANE (Scanner Access Now Easy) daemon that allows remote
clients to access image acquisition devices available on the local
host.
</PRE>
<H2>OPTIONS</H2><PRE>
The <B>-d</B> and <B>-s</B> flags request that <B>saned</B> run in debug mode (as opposed to
<B><A HREF="inetd.8.html">inetd(8)</A></B> mode). In this mode, <B>saned</B> explicitly waits for a connection
request. When compiled with debugging enabled, these flags may be fol-
lowed by a number to request debug info. The larger the number, the
more verbose the debug output. E.g., <B>-d128</B> will request printing of
all debug info. Debug level 0 means no debug output at all. The default
value is 2. If flag <B>-d</B> is used, the debug messages will be printed to
stderr while <B>-s</B> requests using syslog.
If <B>saned</B> is run from inetd or xinetd, no option can be given.
</PRE>
<H2>CONFIGURATION</H2><PRE>
First and foremost: <B>saned</B> is not intended to be exposed to the internet
or other non-trusted networks. Make sure that access is limited by tcp-
wrappers and/or a firewall setup. Don't depend only on <B>saned</B>'s own
authentification. Don't run <B>saned</B> as root if it's not necessary. And do
<B>not</B> install <B>saned</B> as setuid root.
The contents of the <I>saned.conf</I> file is a list of host names or IP
addresses that are permitted to use local SANE devices. Connections
from localhost are always permitted. Empty lines and lines starting
with a hash mark (#) are ignored. A line containing the single charac-
ter ``+'' is interpreted to match any hostname. This allows any remote
machine to use your scanner and may present a security risk, so this
shouldn't be used unless you know what you're doing. A sample configu-
ration file is shown below:
scan-client.somedomain.firm
# this is a comment
192.168.0.1
::1
The case of the host names does not matter, so AHost.COM is considered
identical to ahost.com. IPv6 addresses should always be specified in
their compressed form.
For <B>saned</B> to work properly, it is also necessary to add a configuration
line to <I>/etc/inetd.conf</I>. Note that your inetd must support IPv6 if you
want to connect to saned over IPv6 ; xinetd and openbsd-inetd are known
to support IPv6, check the documentation for your inetd daemon.
The configuration line normally looks like this:
sane stream tcp nowait saned.saned /usr/local/sbin/saned saned
However, if your system uses <B><A HREF="tcpd.8.html">tcpd(8)</A></B> for additional security screening,
you may want to disable saned access control by putting ``+'' in
<I>saned.conf</I> and use a line of the following form in <I>/etc/inetd.conf</I>
instead:
sane stream tcp nowait saned.saned /usr/sbin/tcpd
/usr/local/sbin/saned
Note that both examples assume that there is a <B>saned</B> group and a <B>saned</B>
user. If you follow this example, please make sure that the access
permissions on the special device are set such that <B>saned</B> can access
the scanner (the program generally needs read and write access to scan-
ner devices).
If xinetd is installed on your system instead of inetd the following
example for xinetd.conf may be helpful:
# default: off
# description: The sane server accepts requests
# for network access to a local scanner via the
# network.
service sane
{
port = 6566
socket_type = stream
wait = no
user = saned
group = saned
server = /usr/local/sbin/saned
}
Finally, it is also necessary to add a line of the following form to
<I>/etc/services</I>:
sane 6566/tcp # SANE network scanner daemon
</PRE>
<H2>RESTRICTIONS</H2><PRE>
In addition to the control connection (port 6566) saned also uses a
data connection. The port of this socket is selected by the operating
system and can't be specified by the user currently. This may be a
problem if the connection must go through a firewall (packet filter).
</PRE>
<H2>FILES</H2><PRE>
<I>/etc/hosts.equiv</I>
The hosts listed in this file are permitted to access all local
SANE devices. Caveat: this file imposes serious security risks
and its use is not recommended.
<I>/usr/local/etc/sane.d/saned.conf</I>
Contains a list of hosts permitted to access local SANE devices
(see also description of <B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/etc/sane.d/saned.users</I>
If this file contains lines of the form
user:password:backend
access to the listed backends is restricted. A backend may be
listed multiple times for different user/password combinations.
The server uses MD5 encryption if supported by the client.
</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).
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, <B><A HREF="xcam.1.html">xcam(1)</A></B>, <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>, <B>sane-</B>
<B><A HREF="net.5.html">net(5)</A></B>, <B>sane-"backendname"</B>(5)
<I>http://www.penguin-breeder.org/?page=sane-net</I>
</PRE>
<H2>AUTHOR</H2><PRE>
David Mosberger
sane-backends 1.0.12-cvs 9 Feb 2003 <B><A HREF="saned.1.html">saned(1)</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>

151
man/scanadf.1.html 100644
Wyświetl plik

@ -0,0 +1,151 @@
<HTML>
<HEAD>
<TITLE>scanadf.1</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>scanadf.1</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
</PRE>
<H2>SYNOPSIS</H2><PRE>
<B>scanadf</B> [<B>-d</B>|<B>--device-name</B> <I>dev</I>] [<B>-h</B>|<B>--help</B>] [<B>-L</B>|<B>--list-devices</B>]
[<B>-v</B>|<B>--verbose</B>] [<B>-V</B>|<B>--version</B>] [<B>-o</B>|<B>--output-file</B> <I>name</I>] [<B>-S</B>|<B>--scan-script</B>
<I>name</I>] [<B>-s</B>|<B>--start-count</B> <I>num</I>] [<B>-e</B>|<B>--end-count</B> <I>num</I>] [<B>-r</B>|<B>--raw</B>] [<I>device-</I>
<I>specific-options</I>]
</PRE>
<H2>DESCRIPTION</H2><PRE>
<B>scanadf</B> is a command-line interface to control image acquisition
devices which are capable of returning a series of images (e.g. a scan-
ner with an automatic document feeder (ADF)). The device is controlled
via command-line options. After command-line processing, <B>scanadf</B> nor-
mally proceeds to acquire a series of images until the device returns
the <B>SANE_STATUS_NO_DOCS</B> status code.
The images are written to output files, specified by the <B>--output-file</B>
option. These files are typically written in one of the PNM (portable
aNyMaP) formats (PBM for black-and-white images, PGM for grayscale
images, and PPM for color images). Several optional frame formats
(SANE_FRAME_JPEG, SANE_FRAME_G31D, SANE_FRAME_G32D, SANE_FRAME_G42D,
and SANE_FRAME_TEXT) are supported. In each case, the data is written
out to the output file as-is without a header. Unrecognized frame for-
mats are handled in the same way, although a warning message is printed
in verbose mode.
Typically, the optional frame formats are used in conjunction with a
scan script (specified by the <B>--scanscript</B> option) which is invoked for
each acquired image. The script is provided with a series of environ-
ment variables which describe the parameters and format of the image
file.
<B>scanadf</B> accesses image acquisition devices through the SANE (Scanner
Access Now Easy) interface and can thus support any device for which
there exists a SANE backend (try "apropos sane-" to get a list of
available backends).
</PRE>
<H2>OPTIONS</H2><PRE>
The <B>-d</B> or <B>--device-name</B> options must be followed by a SANE device-name.
A (partial) list of available devices can be obtained with the <B>--list-</B>
<B>devices</B> option (see below). If no device-name is specified explicitly,
<B>scanadf</B> will attempt to open the first available device.
The <B>-h</B> or <B>--help</B> options request help information. The information is
printed on standard output and in this case, no attempt will be made to
acquire an image.
The <B>-L</B> or <B>--list-devices</B> option requests a (partial) list of devices
that are available. The list is not complete since some devices may be
available, but are not listed in any of the configuration files (which
are typically stored in directory /usr/local/etc/sane.d). This is par-
ticularly the case when accessing scanners through the network. If a
device is not listed in a configuration file, the only way to access it
is by its full device name. You may need to consult your system admin-
istrator to find out the names of such devices.
replacement in the output file name; this will be replaced with the
current page number. The default format string is image-%04d.
The <B>-S</B> or <B>--scan-script</B> option specifies the name of script to run
after each scanned image is acquired. The script receives the name of
the image output file as its first and only command line argument.
Additionally the scan script can reference the following environment
variables to get information about the parameters of the image.
<B>SCAN_RES</B> - the image resolution (in DPI)
<B>SCAN_WIDTH</B> - the image width (in pixels)
<B>SCAN_HEIGHT</B> - the image height (in pixels)
<B>SCAN_DEPTH</B> - the image bit-depth (in bits)
<B>SCAN_FORMAT</B> - a string representing the image format (e.g. gray,
g42d, text, etc)
<B>SCAN_FORMAT_ID</B> - the numeric image format identifier
The <B>-s</B> or <B>--start-count</B> option specifies the page number of first
scanned image.
The <B>-e</B> or <B>--end-count</B> option specifies the last page number to scan.
Using this option, you can request a specific number of pages to be
scanned, rather than scanning until there are no more images available.
The <B>-r</B> or <B>--raw</B> option specifies that the raw image data be written to
the output file as-is without interpretation. This disables the writ-
ing of the PNM header for basic frame types. This feature is usually
used in conjunction with the <B>--scan-script</B> option where the scan script
uses the environment variables to understand the format and parameters
of the image and converts the file to a more useful format. NOTE: With
support for the optional frame types and the default handling of unrec-
ognized frametypes, this option becomes less and less useful.
As you might imagine, much of the power of <B>scanadf</B> comes from the fact
that it can control any SANE backend. Thus, the exact set of command-
line options depends on the capabilities of the selected device. To
see the options for a device named <I>dev</I>, invoke <B>scanadf</B> via a command-
line of the form:
scanadf --help --device <I>dev</I>
The documentation for the device-specific options printed by <B>--help</B> is
explained in the manual page for <B>scanimage.</B>
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d</I>
This directory holds various configuration files. For details,
please refer to the manual pages listed below.
Please send reports to <I>sane-devel@mostang.com</I>
This program relies on the backend to return the <B>SANE_STATUS_NO_DOCS</B>
status code when the automatic document feeder is out of paper. Use of
this program with backends that do not support ADFs (e.g. flatbed scan-
ners) will likely result in repeated scans of the same document. In
this case, it is essential to use the start-count and end-count to con-
trol the number of images acquired.
Only a subset of the SANE backends support feeders and return SANE_STA-
TUS_NO_DOCS appropriately. Backends which are known to work at this
time are:
<B>sane-bh</B> - Bell+Howell Copiscan II series scanners.
<B>sane-hp</B> - Hewlett Packard scanners. A patch to the sane-hp
backend is necessary. The --scantype=ADF option must be speci-
fied (earlier versions of the backend used the --scan-from-adf
option, instead).
<B>sane-umax</B> - UMAX scanners. Support exists in build 12 and
later. The --source="Automatic Document Feeder" option must be
specified.
15 Sep 1999 <B><A HREF="scanadf.1.html">scanadf(1)</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>

283
man/scanimage.1.html 100644
Wyświetl plik

@ -0,0 +1,283 @@
<HTML>
<HEAD>
<TITLE>scanimage.1</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>scanimage.1</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="scanimage.1.html">scanimage(1)</A></B> SANE Scanner Access Now Easy <B><A HREF="scanimage.1.html">scanimage(1)</A></B>
</PRE>
<H2>NAME</H2><PRE>
scanimage - scan an image
</PRE>
<H2>SYNOPSIS</H2><PRE>
<B>scanimage</B> [<B>-d</B>|<B>--device-name</B> <I>dev</I>] [<B>--format</B> <I>format</I>] [<B>-i</B>|<B>--icc-profile</B>
<I>profile</I>] [<B>-L</B>|<B>--list-devices</B>] [<B>-f</B>|<B>--formatted-device-list</B> <I>format</I>]
[<B>--batch</B> [=<I>format</I>]] [<B>--batch-start</B> <I>start</I>] [<B>--batch-count</B> <I>count</I>]
[<B>--batch-increment</B> <I>increment</I>] [<B>--batch-double</B>] [<B>--accept-md5-only</B>]
[<B>-n</B>|<B>--dont-scan</B>] [<B>-T</B>|<B>--test</B>] [<B>-h</B>|<B>--help</B>] [<B>-v</B>|<B>--verbose</B>] [<B>-V</B>|<B>--version</B>]
[<I>device-specific-options</I>]
</PRE>
<H2>DESCRIPTION</H2><PRE>
<B>scanimage</B> is a command-line interface to control image acquisition
devices such as flatbed scanners or cameras. The device is controlled
via command-line options. After command-line processing, <B>scanimage</B>
normally proceeds to acquire an image. The image data is written to
standard output in one of the PNM (portable aNyMaP) formats (PBM for
black-and-white images, PGM for grayscale images, and PPM for color
images) or in TIFF (black-and-white, grayscale or color). <B>scanimage</B>
accesses image acquisition devices through the <B>SANE</B> (Scanner Access Now
Easy) interface and can thus support any device for which there exists
a <B>SANE</B> backend (try <B>apropos</B> <I>sane-</I> to get a list of available backends).
</PRE>
<H2>EXAMPLES</H2><PRE>
To get a list of devices:
scanimage -L
To scan with default settings to the file image.pnm:
scanimage &gt;image.pnm
To print all available options:
scanimage -h
</PRE>
<H2>OPTIONS</H2><PRE>
The <B>-d</B> or <B>--device-name</B> options must be followed by a <B>SANE</B> device-name
like `<I>epson:/dev/sg0</I>' or `<I>hp:/dev/usbscanner0</I>'. A (partial) list of
available devices can be obtained with the <B>--list-devices</B> option (see
below). If no device-name is specified explicitly, <B>scanimage</B> reads a
device-name from the environment variable <B>SANE_DEFAULT_DEVICE</B>. If this
variable is not set, <B>scanimage</B> will attempt to open the first available
device.
The <B>--format</B> <I>format</I> option selects how image data is written to stan-
dard output. <I>format</I> can be <B>pnm</B> or <B>tiff.</B> If <B>--format</B> is not used, PNM
is written.
The <B>-i</B> or <B>--icc-profile</B> option is used to include an ICC profile into a
TIFF file.
The <B>-L</B> or <B>--list-devices</B> option requests a (partial) list of devices
that are available. The list is not complete since some devices may be
available, but are not listed in any of the configuration files (which
are typically stored in directory <I>/usr/local/etc/sane.d</I>). This is par-
ticularly the case when accessing scanners through the network. If a
device is not listed in a configuration file, the only way to access it
is by its full device name. You may need to consult your system admin-
istrator to find out the names of such devices.
The <B>-f</B> or <B>--formatted-device-list</B> option works similar to <B>--list-</B>
<B>devices</B>, but requires a format string. <B>scanimage</B> replaces the place-
holders <B>%d</B> <B>%v</B> <B>%m</B> <B>%t</B> <B>%i</B> with the device name, vendor name, model name,
scanner type and an index number respectively. The command
<B>scanimage</B> <B>-f</B> <I>"</I> <I>scanner</I> <I>number</I> <I>%i</I> <I>device</I> <I>%d</I> <I>is</I> <I>a</I> <I>%t,</I> <I>model</I> <I>%m,</I>
<I>produced</I> <I>by</I> <I>%v</I> <I>"</I>
will produce something like:
scanner number 0 device sharp:/dev/sg1 is a flatbed scanner,
model JX250 SCSI, produced by SHARP
The <B>--batch*</B> options provide the features for scanning documents using
document feeders. <B>--batch</B> [<I>format</I>] is used to specify the format of
the filename that each page will be written to. Each page is written
out to a single file. If <I>format</I> is not specified, the default of
out%d.pnm (or out%d.tif for --format tiff) will be used. <I>format</I> is
given as a printf style string with one integer parameter. <B>--batch-</B>
<B>start</B> <I>start</I> selects the page number to start naming files with. If this
option is not given, the counter will start at 0. <B>--batch-count</B> <I>count</I>
specifies the number of pages to attempt to scan. If not given, scan-
image will continue scanning until the scanner returns a state other
than OK. Not all scanners with document feeders signal when the ADF is
empty, use this command to work around them. With <B>--batch-increment</B>
<I>increment</I> you can change the amount that the number in the filename is
incremented by. Generally this is used when you are scanning double-
sided documents on a single-sided document feeder. A specific command
is provided to aid this: <B>--batch-double</B> will automatically set the
increment to 2.
The <B>--accept-md5-only</B> option only accepts user authorization requests
that support MD5 security. The <B>SANE</B> network daemon (<B>saned</B>) is capable
of doing such requests. See <B><A HREF="saned.1.html">saned(1)</A></B>.
The <B>-n</B> or <B>--dont-scan</B> option requests that <B>scanimage</B> only sets the
options provided by the user but doesn't actually perform a scan. This
option can be used to e.g. turn off the scanner's lamp (if supported by
the backend).
The <B>-T</B> or <B>--test</B> option requests that <B>scanimage</B> performs a few simple
sanity tests to make sure the backend works as defined by the <B>SANE</B> API
(in particular the <B>sane_read</B> function is excercised by this test).
The <B>-h</B> or <B>--help</B> options request help information. The information is
printed on standard output and in this case, no attempt will be made to
acquire an image.
The <B>-v</B> or <B>--verbose</B> options increase the verbosity of the operation of
<B>scanimage.</B> The option may be specified repeatedly, each time increas-
ing the verbosity level.
The <B>-V</B> or <B>--version</B> option requests that <B>scanimage</B> prints the program
and package name, the version number of the <B>SANE</B> distribution that it
came with and the version of the backend that it loads. Usually that's
the dll backend. If more information about the version numbers of the
backends are necessary, the <B>DEBUG</B> variable for the dll backend can be
used. Example: SANE_DEBUG_DLL=3 scanimage -L.
As you might imagine, much of the power of <B>scanimage</B> comes from the
fact that it can control any <B>SANE</B> backend. Thus, the exact set of com-
mand-line options depends on the capabilities of the selected device.
To see the options for a device named <I>dev</I>, invoke <B>scanimage</B> via a com-
mand-line of the form:
<B>scanimage</B> <B>--help</B> <B>--device-name</B> <I>dev</I>
The documentation for the device-specific options printed by <B>--help</B> is
best explained with a few examples:
--brightness -100..100% [0]
Controls the brightness of the acquired image.
The description above shows that option <B>--brightness</B> expects an
option value in the range from -100 to 100 percent. The value
in square brackets indicates that the current option value is 0
percent.
--default-enhancements
Set default values for enhancement controls.
The description above shows that option <B>--default-enhancements</B>
has no option value. It should be thought of as having an imme-
diate effect at the point of the command-line at which it
appears. For example, since this option resets the <B>--brightness</B>
option, the option-pair <B>--brightness</B> <B>50</B> <B>--default-enhancements</B>
would effectively be a no-op.
--mode Lineart|Gray|Color [Gray]
Selects the scan mode (e.g., lineart or color).
The description above shows that option <B>--mode</B> accepts an argu-
ment that must be one of the strings <B>Lineart</B>, <B>Gray</B>, or <B>Color</B>.
The value in the square bracket indicates that the option is
currently set to <B>Gray</B>. For convenience, it is legal to abbrevi-
ate the string values as long as they remain unique. Also, the
case of the spelling doesn't matter. For example, option set-
ting <B>--mode</B> <B>col</B> is identical to <B>--mode</B> <B>Color</B>.
--custom-gamma[=(yes|no)] [inactive]
Determines whether a builtin or a custom gamma-table
should be used.
The description above shows that option <B>--custom-gamma</B> expects
either no option value, a "yes" string, or a "no" string. Spec-
ifying the option with no value is equivalent to specifying
"yes". The value in square-brackets indicates that the option
is not currently active. That is, attempting to set the option
would result in an error message. The set of available options
typically depends on the settings of other options. For exam-
ple, the <B>--custom-gamma</B> table might be active only when a
grayscale or color scan-mode has been requested.
Note that the <B>--help</B> option is processed only after all other
options have been processed. This makes it possible to see the
option settings for a particular mode by specifying the appro-
priate mode-options along with the <B>--help</B> option. For example,
the command-line:
<B>scanimage</B> <B>--help</B> <B>--mode</B> <I>color</I>
would print the option settings that are in effect when the
color-mode is selected.
--gamma-table 0..255,...
Gamma-correction table. In color mode this option
equally affects the red, green, and blue channels
simultaneously (i.e., it is an intensity gamma table).
The description above shows that option <B>--gamma-table</B> expects
zero or more values in the range 0 to 255. For example, a legal
value for this option would be "3,4,5,6,7,8,9,10,11,12". Since
it's cumbersome to specify long vectors in this form, the same
can be expressed by the abbreviated form "[0]3-[9]12". What
this means is that the first vector element is set to 3, the
9-th element is set to 12 and the values inbetween are interpo-
lated linearly. Of course, it is possible to specify multiple
such linear segments. For example, "[0]3-[2]3-[6]7,[7]10-[9]6"
is equivalent to "3,3,3,4,5,6,7,10,8,6". The program
<B>gamma4scanimage</B> can be used to generate such gamma tables (see
<B><A HREF="gamma4scanimage.1.html">gamma4scanimage(1)</A></B> for details).
--filename &lt;string&gt; [/tmp/input.ppm]
The filename of the image to be loaded.
The descriptoin above is an example of an option that takes an
arbitrary string value (which happens to be a filename). Again,
the value in brackets show that the option is current set to the
filename <B>/tmp/input.ppm</B>.
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEFAULT_DEVICE</B>
The default device-name.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d</I>
This directory holds various configuration files. For details,
please refer to the manual pages listed below.
<I>~/.sane/pass</I>
This file contains lines of the form
user:password:resource
scanimage uses this information to answer user authorization
requests automatically. The file must have 0600 permissions or
stricter. You should use this file in conjunction with the
--accept-md5-only option to avoid server-side attacks. The
resource may contain any character but is limited to 127 charac-
ters.
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="gamma4scanimage.1.html">gamma4scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, <B>xcam(1)</B>, <B>xsane(1)</B>,
<B><A HREF="scanadf.1.html">scanadf(1)</A></B>, <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>, <B><A HREF="sane-net.5.html">sane-net(5)</A></B>, <B>sane-"backendname"</B>(5)
</PRE>
<H2>AUTHOR</H2><PRE>
David Mosberger, Andreas Beck, Gordon Matzigkeit and Caskey Dickson
</PRE>
<H2>BUGS</H2><PRE>
For vector options, the help output currently has no indication as to
how many elements a vector-value should have.
sane-backends 1.0.12-cvs 15 Apr 2003 <B><A HREF="scanimage.1.html">scanimage(1)</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>

52
man/xcam.1.html 100644
Wyświetl plik

@ -0,0 +1,52 @@
<HTML>
<HEAD>
<TITLE>xcam.1</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>xcam.1</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
</PRE>
<H2>SYNOPSIS</H2><PRE>
<B>xcam</B>
</PRE>
<H2>DESCRIPTION</H2><PRE>
Should be straightforward to use. Just be sure to use a very recent
version of GTK.
</PRE>
<H2>FILES</H2><PRE>
<I>$HOME/.sane/xcam/devicename.rc</I>
For each device, there is one rc-file that holds the saved set-
tings for that particular device. Normally, this file should
not be manipulated directly. Instead, the user should use the
<B>xcam</B> interface to select appropriate values and then save the
device settings using the "Preferences-&gt;Save as default set-
tings" menubar entry.
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B> and the backend man-
pages
</PRE>
<H2>AUTHOR</H2><PRE>
David Mosberger-Tang
24 Jun 2000 <B><A HREF="xcam.1.html">xcam(1)</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>

135
man/xscanimage.1.html 100644
Wyświetl plik

@ -0,0 +1,135 @@
<HTML>
<HEAD>
<TITLE>xscanimage.1</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>xscanimage.1</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
</PRE>
<H2>SYNOPSIS</H2><PRE>
<B>xscanimage</B> [<B>--version</B>|<B>-V</B>] [<B>--help</B>|<B>-h</B>] [<B>--display</B> <I>d</I>] [<B>--no-xshm</B>]
[<B>--sync</B>] [<I>devicename</I>]
</PRE>
<H2>DESCRIPTION</H2><PRE>
<B>xscanimage</B> provides a graphical user-interface to control an image
acquisition device such as a flatbed scanner or a camera. It allows
previewing and scanning invidual images and can be invoked either
directly from the command-line or through The GIMP image manipulation
program. In the former case, <B>xscanimage</B> acts as a stand-alone program
that saves acquired images in a suitable PNM format (PBM for black-and-
white images, PGM for grayscale images, and PPM for color images). In
the latter case, the images are directly passed to The GIMP for further
processing.
<B>xscanimage</B> accesses image acquisition devices through the SANE (Scanner
Access Now Easy) interface. The list of available devices depends on
installed hardware and configuration. When invoked without an explicit
devicename argument, <B>xscanimage</B> presents a dialog listing of all known
and available devices. If the environment variable SANE_DEFAULT_DEVICE
is set to the devicename, the device is preselected in the dialog. To
access an available device that is not known to the system, the device-
name must be specified explicitly. The format of devicename is backend-
name:devicefile (e.g. umax:/dev/sga).
</PRE>
<H2>RUNNING UNDER THE GIMP</H2><PRE>
To run <B>xscanimage</B> under the <B><A HREF="gimp.1.html">gimp(1)</A></B>, simply copy it to one of the
<B><A HREF="gimp.1.html">gimp(1)</A></B> plug-ins directories. If you want to conserve disk-space, you
can create a symlink instead. For example, for gimp-1.0.x the command
ln -s /usr/local/bin/xscanimage ~/.gimp/plug-ins/
and for gimp-1.2.x the command
ln -s /usr/local/bin/xscanimage ~/.gimp-1.2/plug-ins/
adds a symlink for the <B>xscanimage</B> binary to the user's plug-ins direc-
tory. After creating this symlink, <B>xscanimage</B> will be queried by
<B><A HREF="gimp.1.html">gimp(1)</A></B> the next time it's invoked. From then on, <B>xscanimage</B> can be
invoked through "File-&gt;Acquire-&gt;Xscanimage-&gt;Device dialog..." menu
entry.
You'll also find that the "File-&gt;Acquire-&gt;Xscanimage" menu contains
short-cuts to the SANE devices that were available at the time <B>xscanim-</B>
<B>age</B> was queried. For example, the first PNM pseudo-device is typically
available as the short-cut "File-&gt;Acquire-&gt;Xscanimage-&gt;pnm:0". Note
that <B><A HREF="gimp.1.html">gimp(1)</A></B> caches these short-cuts in ~/.gimp/pluginrc. Thus, when
the list of available devices changes (e.g., a new scanner is
installed), then it is typically desirable to rebuild this cache. To
do this, you can either <B><A HREF="touch.1.html">touch(1)</A></B> the <B>xscanimage</B> binary (e.g., "touch
/usr/local/bin/xscanimage") or delete the plug-ins cache (e.g., "rm
~/.gimp/plug-ins"). Either way, invoking <B><A HREF="gimp.1.html">gimp(1)</A></B> afterwards will cause
the pluginrc to be rebuilt.
buggy X11 servers. Unless your X11 server dies when running this pro-
gram, there is no need or advantage to specify this flag.
The <B>--sync</B> flag requests a synchronous connection with the X11 server.
This is for debugging purposes only.
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEFAULT_DEVICE</B>
The default device-name. Example:
SANE_DEFAULT_DEVICE="hp:/dev/scanner".
<B>SANE_DEBUG_XSCANIMAGE</B>
This environment variable controls the debug level xscanimage.
Higher debug levels increase the verbosity of the output.
Value Descsription
0 print fatal errors
1 print errors
2 print warnings
3 print information messages
4 print everything
Example:
SANE_DEBUG_XSCANIMAGE=3
</PRE>
<H2>FILES</H2><PRE>
<I>$HOME/.sane/xscanimage/xscanimage.rc</I>
This files holds the user preferences. Normally, this file
should not be manipulated directly. Instead, the user should
customize the program through the "Preferences" dialog.
<I>$HOME/.sane/xscanimage/devicename.rc</I>
For each device, there is one rc-file that holds the saved set-
tings for that particular device. Normally, this file should
not be manipulated directly. Instead, the user should use the
<B>xscanimage</B> interface to select appropriate values and then save
the device settings using the "Preferences-&gt;Save Device Set-
tings" menubar entry.
<I>$HOME/.sane/preview-devicename.ppm</I>
After acquiring a preview, <B>xscanimage</B> normally saves the preview
image in this device-specific file. Thus, next time the program
is started up, the program can present the old preview image.
This feature can be turned off through the "Preferences-&gt;Preview
Options..." dialog.
<I>/usr/local/share/sane-style.rc</I>
This system-wide file controls the aspects of the user-interface
such as colors and fonts. It is a GTK style file and provides
fine control over the visual aspects of the user-interface.
<I>$HOME/.sane/sane-style.rc</I>
This file serves the same purpose as the system-wide style file.
If present, it takes precedence over the system wide style file.
</PRE>
<HR>
<ADDRESS>
Man(1) output converted with
<a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a>
</ADDRESS>
</BODY>
</HTML>