kopia lustrzana https://gitlab.com/sane-project/website
Updated HTML manpages from sane-backends CVS.
Henning Geinitz
rodzic
0917ebfc03
commit
3e3e4e699d
|
|
@ -59,7 +59,7 @@
|
|||
|
||||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="scanimage.7.html">scanimage(7)</A></B>
|
||||
<B><A HREF="scanimage.1.html">scanimage(1)</A></B>
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -71,7 +71,7 @@
|
|||
<H2>EMAIL-CONTACT</H2><PRE>
|
||||
Oliver.Rauch@Rauch-Domain.DE
|
||||
|
||||
sane-backends 1.0.13 11 Sep 2002 <B><A HREF="gamma4scanimage.1.html">gamma4scanimage(1)</A></B>
|
||||
sane-backends 1.0.14-cvs 11 Sep 2002 <B><A HREF="gamma4scanimage.1.html">gamma4scanimage(1)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -142,7 +142,7 @@
|
|||
The sane-abaton backend was partially written by David Huggins-Daines,
|
||||
based on the sane-apple backend by Milon Firikis.
|
||||
|
||||
sane-backends 1.0.13 19 Nov 1998 <B><A HREF="sane-abaton.5.html">sane-abaton(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 19 Nov 1998 <B><A HREF="sane-abaton.5.html">sane-abaton(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -178,7 +178,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
Ingo Schneider and Karl Anders Øygard.
|
||||
|
||||
sane-backends 1.0.13 17 Oct 1998 <B><A HREF="sane-agfafocus.5.html">sane-agfafocus(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 17 Oct 1998 <B><A HREF="sane-agfafocus.5.html">sane-agfafocus(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -283,7 +283,7 @@
|
|||
Firikis. It is mostly based on the mustek backend from David Mosberger
|
||||
and Andreas Czechanowski
|
||||
|
||||
sane-backends 1.0.13 13 May 1998 <B><A HREF="sane-apple.5.html">sane-apple(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 13 May 1998 <B><A HREF="sane-apple.5.html">sane-apple(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -172,7 +172,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
Chris Pinkham (cpinkham@corp.infi.net)
|
||||
|
||||
sane-backends 1.0.13 24 Jan 2000 <B><A HREF="sane-artec.5.html">sane-artec(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 24 Jan 2000 <B><A HREF="sane-artec.5.html">sane-artec(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -187,7 +187,7 @@
|
|||
<I>http://www.angelfire.com/linux/crapsite</I>. Please contact me if you find
|
||||
a bug or missing feature: <crapsite@gmx.net>
|
||||
|
||||
sane-backends 1.0.13 19 Nov 2002 <B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 19 Nov 2002 <B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@
|
|||
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
|
||||
<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).
|
||||
|
|
@ -50,7 +50,7 @@
|
|||
<H2>EMAIL-CONTACT</H2><PRE>
|
||||
yossarian@users.sourceforge.net
|
||||
|
||||
sane-backends 1.0.13 Apr 2nd, 2003 <B><A HREF="sane-as6e.5.html">sane-as6e(5)</A></B>
|
||||
sane-backends 1.0.14-cvs Dec 14th, 2003 <B><A HREF="sane-as6e.5.html">sane-as6e(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -176,7 +176,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
René Rebe and Meino Christian Cramer
|
||||
|
||||
sane-backends 1.0.13 04 Mar 2003 <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 04 Mar 2003 <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -502,7 +502,7 @@
|
|||
Reifschneider of tummy.com ltd. Some 8000 enhancements added by Mark
|
||||
Temple.
|
||||
|
||||
sane-backends 1.0.13 15 Sep 1999 <B><A HREF="sane-bh.5.html">sane-bh(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 15 Sep 1999 <B><A HREF="sane-bh.5.html">sane-bh(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -108,7 +108,7 @@
|
|||
support by Mitsuru Okaniwa; FS2710S support by Ulrich Deiters
|
||||
Man page by Henning Meier-Geinitz (mostly based on canon.README)
|
||||
|
||||
sane-backends 1.0.13 03 May 2001 <B><A HREF="sane-canon.5.html">sane-canon(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 03 May 2001 <B><A HREF="sane-canon.5.html">sane-canon(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -17,41 +17,32 @@
|
|||
|
||||
</PRE>
|
||||
<H2>DESCRIPTION</H2><PRE>
|
||||
The <B>sane-canon</B> library implements a SANE (Scanner Access Now Easy)
|
||||
The <B>sane-canon630u</B> library implements a SANE (Scanner Access Now Easy)
|
||||
backend that provides access to the following Canon flatbed scanners:
|
||||
|
||||
CanoScan 630u
|
||||
CanoScan 636u (hopefully)
|
||||
CanoScan 636u
|
||||
|
||||
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.
|
||||
Color scanning is supported at 75, 150, 300, and 600 dpi, and gamma and
|
||||
analog gain are adjustable.
|
||||
|
||||
That said, TESTERS ARE WELCOME. Send your bug reports and comments to
|
||||
Nathan Rutman <nathan@gordian.com>
|
||||
|
||||
|
||||
</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.
|
||||
TESTERS ARE WELCOME. Send your bug reports and comments to Nathan Rut-
|
||||
man <nthn1@yahoo.com>
|
||||
|
||||
|
||||
</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>.
|
||||
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>. The program <I>sane-find-scanner</I> helps to find out the
|
||||
correct device. Under Linux, such a device name could be <I>/dev/usb/scan-</I>
|
||||
<I>ner0</I> for example. See <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B> for details.
|
||||
|
||||
This product-specific scanner driver uses the lower-level kernel USB
|
||||
driver "scanner". Check for "Driver=usbscanner" under
|
||||
/proc/bus/usb/devices. If "Driver=(none)", try forcing it with "insmod
|
||||
scanner vendor=0x04a9 product=0x2204"
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -64,10 +55,12 @@
|
|||
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"
|
||||
Some users have reported that this driver doesn't work at all. This
|
||||
seems to be a hardware specific issue, although I don't know what
|
||||
exactly the problem is. If you are having problems, please send me the
|
||||
info in /proc/bus/usb/devices, /proc/pci, the kernel scanner.c driver
|
||||
version from /var/log/messages, and the output from
|
||||
"SANE_DEBUG_CANON630U=12 scanimage > /dev/null"
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -86,8 +79,7 @@
|
|||
<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.
|
||||
lost power. Deleting this file will force recalibration.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -95,23 +87,24 @@
|
|||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in
|
||||
/usr/local/etc/sane.d. If the value of the environment variable
|
||||
ends with the directory separator character, then the default
|
||||
ends with the directory separator character, then the default
|
||||
directories are searched after the explicitly specified directo-
|
||||
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
|
||||
would result in directories "tmp/config", ".", and
|
||||
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
|
||||
would result in directories "tmp/config", ".", and
|
||||
"/usr/local/etc/sane.d" being searched (in this order).
|
||||
|
||||
<B>SANE_DEBUG_CANON630U</B>
|
||||
If the library was compiled with debug support enabled, this
|
||||
environment variable controls the debug level for this backend.
|
||||
If the library was compiled with debug support enabled, this
|
||||
environment variable controls the debug level for this backend.
|
||||
Higher debug levels increase the verbosity of the output.
|
||||
|
||||
Example: SANE_DEBUG_CANON630U=12 scanimage > /dev/null
|
||||
Example:
|
||||
SANE_DEBUG_CANON630U=12 scanimage > /dev/null
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -124,7 +117,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
Nathan Rutman
|
||||
|
||||
sane-backends 1.0.13 06 Apr 2002 <B><A HREF="sane-canon630u.5.html">sane-canon630u(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 06 Apr 2002 <B><A HREF="sane-canon630u.5.html">sane-canon630u(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -222,7 +222,7 @@
|
|||
Many thanks to Kevin Easton for his comments and help, and Kent A. Sig-
|
||||
norini for his help with the N340P.
|
||||
|
||||
sane-backends 1.0.13 1 October 2002 <B><A HREF="sane-canon_pp.5.html">sane-canon_pp(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 1 October 2002 <B><A HREF="sane-canon_pp.5.html">sane-canon_pp(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -30,25 +30,26 @@
|
|||
|
||||
</PRE>
|
||||
<H2>OPTIONS</H2><PRE>
|
||||
<B>sane-config</B> accepts the following options:
|
||||
<B>sane-config</B> accepts the following options (you can't use more than one
|
||||
option at the same time):
|
||||
|
||||
<B>--version</B>
|
||||
Print the currently installed version of libsane on the stan-
|
||||
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
|
||||
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>--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-
|
||||
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>
|
||||
Print the compiler flags that are necessary to compile a <B>SANE</B>
|
||||
frontend.
|
||||
|
||||
<B>--prefix</B>
|
||||
|
|
@ -68,7 +69,7 @@
|
|||
This manual page was written by Julien BLACHE <jblache@debian.org>, for
|
||||
the Debian GNU/Linux system (but may be used by others).
|
||||
|
||||
sane-backends 1.0.13 15 October 2002 <B><A HREF="sane-config.1.html">sane-config(1)</A></B>
|
||||
sane-backends 1.0.14-cvs 8 Jan 2004 <B><A HREF="sane-config.1.html">sane-config(1)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -122,7 +122,7 @@
|
|||
<H2>EMAIL-CONTACT</H2><PRE>
|
||||
andreas.rick@free.fr
|
||||
|
||||
sane-backends 1.0.13 4 July 2000 <B><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 4 July 2000 <B><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -192,7 +192,7 @@
|
|||
The backend is written and maintained by András Major
|
||||
(andras@users.sourceforge.net).
|
||||
|
||||
sane-backends 1.0.13 22/08/2002 <B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 22/08/2002 <B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -123,7 +123,7 @@
|
|||
be subscribed to the list, otherwise your mail won't be sent to the
|
||||
subscribers.
|
||||
|
||||
sane-backends 1.0.13 15 July 2000 <B><A HREF="sane-dc210.5.html">sane-dc210(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 15 July 2000 <B><A HREF="sane-dc210.5.html">sane-dc210(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -126,7 +126,7 @@
|
|||
be subscribed to the list, otherwise your mail won't be sent to the
|
||||
subscribers.
|
||||
|
||||
sane-backends 1.0.13 23 March 2001 <B><A HREF="sane-dc240.5.html">sane-dc240(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 23 March 2001 <B><A HREF="sane-dc240.5.html">sane-dc240(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -116,7 +116,7 @@
|
|||
be subscribed to the list, otherwise your mail won't be sent to the
|
||||
subscribers.
|
||||
|
||||
sane-backends 1.0.13 12 April 1999 <B><A HREF="sane-dc25.5.html">sane-dc25(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 12 April 1999 <B><A HREF="sane-dc25.5.html">sane-dc25(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -148,7 +148,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
David Mosberger
|
||||
|
||||
sane-backends 1.0.13 4 Dec 2002 <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 4 Dec 2002 <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -159,7 +159,7 @@
|
|||
|
||||
The backend is derived from <B>sane-hp</B> by David Mosberger
|
||||
|
||||
sane-backends 1.0.13 13 May 1998 <B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 13 May 1998 <B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -246,7 +246,7 @@
|
|||
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.
|
||||
reported by the scanner it will default to function level B3.
|
||||
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!
|
||||
|
|
@ -284,7 +284,7 @@
|
|||
The package is actively maintained by Karl Heinz Kremer (khk@khk.net).
|
||||
The software is based on work by Christian Bucher and Kazuhiro Sasayama
|
||||
|
||||
sane-backends 1.0.13 27-Dec-2000 <B><A HREF="sane-epson.5.html">sane-epson(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 27-Dec-2000 <B><A HREF="sane-epson.5.html">sane-epson(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@
|
|||
|
||||
</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>]
|
||||
<B>sane-find-scanner</B> [<B>-h</B>|<B>-?</B>] [<B>-v</B>] [<B>-q</B>] [<B>-p</B>] [<B>-f</B>] [<I>devname</I>]
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -47,8 +47,10 @@
|
|||
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.
|
||||
<B>sane-find-scanner</B> won't find most parallel port scanners, or scanners
|
||||
connected to proprietary ports. Some <B>parallel</B> <B>port</B> scanners may be
|
||||
detected by <B>sane-find-scanner</B> <B>-p.</B> At the time of writing this will
|
||||
only detect Mustek parallel port scanners.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -61,6 +63,8 @@
|
|||
|
||||
<B>-q</B> Be quiet. Print only the devices, no comments.
|
||||
|
||||
<B>-p</B> Probe parallel port scanners.
|
||||
|
||||
<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.
|
||||
|
|
@ -78,6 +82,9 @@
|
|||
<B>sane-find-scanner</B> <B>/dev/scanner</B>
|
||||
Look for a (SCSI) scanner only at /dev/scanner and print the result.
|
||||
|
||||
<B>sane-find-scanner</B> <B>-p</B>
|
||||
Probe for parallel port scanners.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
|
|
@ -102,11 +109,11 @@
|
|||
|
||||
</PRE>
|
||||
<H2>BUGS</H2><PRE>
|
||||
No support for parallel port scanners yet.
|
||||
No support for most 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.13 18 Jul 2003 <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>
|
||||
sane-backends 1.0.14-cvs 18 Jul 2003 <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -157,7 +157,7 @@
|
|||
them yet. I don't know if the ScanPartner 15C still works, because I'm
|
||||
not able to test it. 3091/3092 don't support halftone
|
||||
|
||||
sane-backends 1.0.13 17 Apr 2002 <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 17 Apr 2002 <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -131,7 +131,7 @@
|
|||
be subscribed to the list, otherwise your mail won't be sent to the
|
||||
subscribers.
|
||||
|
||||
sane-backends 1.0.13 04 September 2001 <B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 04 September 2001 <B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -27,7 +27,12 @@
|
|||
Boeder SmartScan Slim Edition
|
||||
Fujitsu 1200CUS
|
||||
Genius Colorpage Vivid3x
|
||||
Genius Colorpage Vivid3 V2
|
||||
Genius Colorpage Vivid3xe
|
||||
Genius Colorpage Vivid4
|
||||
Genius Colorpage Vivid4x
|
||||
Genius Colorpage Vivid4xe
|
||||
Googlegear 2000
|
||||
Lexmark X70
|
||||
Lexmark X73
|
||||
Medion/Lifetec/Tevion MD 4395
|
||||
|
|
@ -40,13 +45,19 @@
|
|||
Mustek BearPaw 2400 CS (Plus)
|
||||
Mustek BearPaw 2400 CU (Plus)
|
||||
Mustek BearPaw 2400 TA (Plus)
|
||||
Mustek BearPaw 2448 CS Plus
|
||||
Mustek BearPaw 2448 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)
|
||||
Packard Bell Diamond 2450
|
||||
Plustek OpticPro 1248U
|
||||
Plustek OpticPro U16B (+)
|
||||
Plustek OpticPro UT16B (+)
|
||||
Plustek OpticSlim 1200
|
||||
Plustek OpticSlim 2400
|
||||
RevScan 19200i
|
||||
Trust Compact Scan USB 19200
|
||||
Trust Flat Scan USB 19200
|
||||
|
|
@ -97,52 +108,53 @@
|
|||
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>.
|
||||
into <I>/usr/local/share/sane/gt68xx/</I>. Make sure that it's readable by
|
||||
everyone.
|
||||
|
||||
|
||||
</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
|
||||
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
|
||||
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.
|
||||
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
|
||||
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
|
||||
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
|
||||
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 <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
|
||||
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
|
||||
level 3 (see below), scan an image and look for debug line string with
|
||||
"afe". Copy this line to <I>gt68xx.conf</I>. The option has six parameters:
|
||||
red offset, red gain, green offset, green gain, blue offset, and blue
|
||||
gain.
|
||||
|
||||
A sample configuration file is shown below:
|
||||
|
|
@ -158,7 +170,7 @@
|
|||
</PRE>
|
||||
<H2>FILES</H2><PRE>
|
||||
<I>/usr/local/etc/sane.d/gt68xx.conf</I>
|
||||
The backend configuration file (see also description of
|
||||
The backend configuration file (see also description of
|
||||
<B>SANE_CONFIG_DIR</B> below).
|
||||
|
||||
<I>/usr/local/lib/sane/libsane-gt68xx.a</I>
|
||||
|
|
@ -174,61 +186,64 @@
|
|||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in
|
||||
/usr/local/etc/sane.d. If the value of the environment variable
|
||||
ends with the directory separator character, then the default
|
||||
ends with the directory separator character, then the default
|
||||
directories are searched after the explicitly specified directo-
|
||||
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
|
||||
would result in directories "tmp/config", ".", and
|
||||
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
|
||||
would result in directories "tmp/config", ".", and
|
||||
"/usr/local/etc/sane.d" being searched (in this order).
|
||||
|
||||
<B>SANE_DEBUG_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.
|
||||
If the library was compiled with debug support enabled, this
|
||||
environment variable controls the debug level for this backend.
|
||||
Higher debug levels increase the verbosity of the output. If the
|
||||
debug level is set to 1 or higher, some debug options become
|
||||
available that are normally hidden. Handle them with care.
|
||||
|
||||
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.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.13/gt68xx/gt68xx.CHANGES</I>
|
||||
<I>/usr/local/doc/sane-1.0.14-cvs/gt68xx/gt68xx.CHANGES</I>
|
||||
<I>http://www.meier-geinitz.de/sane/gt68xx</I>
|
||||
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>AUTHOR</H2><PRE>
|
||||
Henning Meier-Geinitz <henning@meier-geinitz.de>
|
||||
The original gt68xx driver was written by Sergey Vlasov, Andreas
|
||||
Nowack, and David Stevenson. Thanks for sending patches and answering
|
||||
The original gt68xx driver was written by Sergey Vlasov, Andreas
|
||||
Nowack, and David Stevenson. Thanks for sending patches and answering
|
||||
questions to them and all the other contributors.
|
||||
|
||||
|
||||
</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
|
||||
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-
|
||||
Interpolation should be used instead of just copying data, when the X-
|
||||
and Y-resolution differ.
|
||||
|
||||
Support for buttons is missing.
|
||||
|
||||
More detailed bug information is available at the gt68xx backend home-
|
||||
More detailed bug information is available at the gt68xx backend home-
|
||||
page <I>http://www.meier-geinitz.de/sane/gt68xx</I>. Please contact me if you
|
||||
find a bug or missing feature: <henning@meier-geinitz.de>. Please send
|
||||
a debug log if your scanner isn't detected correctly (see
|
||||
find a bug or missing feature: <henning@meier-geinitz.de>. Please send
|
||||
a debug log if your scanner isn't detected correctly (see
|
||||
SANE_DEBUG_GT68XX above).
|
||||
|
||||
sane-backends 1.0.13 30 Sept 2003 <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 4 Apr 2004 <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -183,6 +183,19 @@
|
|||
Scanner. Must be set to the directory where the directory .sane
|
||||
is located. Is used to save and read the calibration file.
|
||||
|
||||
<B>SANE_HP_KEEPOPEN_SCSI</B>
|
||||
|
||||
<B>SANE_HP_KEEPOPEN_USB</B>
|
||||
|
||||
<B>SANE_HP_KEEPOPEN_DEVICE</B>
|
||||
For each type of connection (connect-scsi, connect-usb, connect-
|
||||
device) it can be specified if the connection to the device
|
||||
should be kept open ("1") or not ("0"). Usually the connections
|
||||
are closed after an operation is performed. Keeping connection
|
||||
open to SCSI-devices can result in errors during device IO when
|
||||
the scanner has not been used for some time. By default, USB-
|
||||
connections are kept open. Other connections are closed.
|
||||
|
||||
<B>SANE_HP_RDREDO</B>
|
||||
Specifies number of retries for read operation before returning
|
||||
an EOF error. Only supported for non-SCSI devices. Default: 1
|
||||
|
|
@ -242,7 +255,7 @@
|
|||
The sane-hp backend was written by Geoffrey T. Dairiki. HP PhotoSmart
|
||||
PhotoScanner support by Peter Kirchgessner.
|
||||
|
||||
sane-backends 1.0.13 09 Oct 2003 <B><A HREF="sane-hp.5.html">sane-hp(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 27 Mar 2004 <B><A HREF="sane-hp.5.html">sane-hp(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -110,7 +110,7 @@
|
|||
other operating systems and especially on big-endian platforms. The
|
||||
scanner may get wrong data.
|
||||
|
||||
sane-backends 1.0.13 17 Apr 2003 <B><A HREF="sane-hp5400.5.html">sane-hp5400(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 17 Apr 2003 <B><A HREF="sane-hp5400.5.html">sane-hp5400(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -111,7 +111,7 @@
|
|||
Max Vorobiev
|
||||
Man page mostly based on canon.man
|
||||
|
||||
sane-backends 1.0.13 24 Feb 2002 <B><A HREF="sane-hpsj5s.5.html">sane-hpsj5s(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 24 Feb 2002 <B><A HREF="sane-hpsj5s.5.html">sane-hpsj5s(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -94,7 +94,7 @@
|
|||
mf <massifr@tiscalinet.it>
|
||||
Maintained by Henning Meier-Geinitz <henning@meier-geinitz.de>
|
||||
|
||||
sane-backends 1.0.13 15 Apr 2003 <B><A HREF="sane-ibm.5.html">sane-ibm(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 15 Apr 2003 <B><A HREF="sane-ibm.5.html">sane-ibm(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -134,7 +134,7 @@
|
|||
The package is actively maintained by Frank Zago.
|
||||
http://www.zago.net/sane/#leo
|
||||
|
||||
sane-backends 1.0.13 16 April 2002 <B><A HREF="sane-leo.5.html">sane-leo(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 16 April 2002 <B><A HREF="sane-leo.5.html">sane-leo(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -127,7 +127,7 @@
|
|||
More detailed bug information is available at the MA-1509 backend home-
|
||||
page <I>http://www.meier-geinitz.de/sane/ma1509-backend/</I>.
|
||||
|
||||
sane-backends 1.0.13 24 Feb 2003 <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 24 Feb 2003 <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -25,8 +25,17 @@
|
|||
|
||||
Product id
|
||||
--------------
|
||||
KV-SS 25
|
||||
KV-SS 25D
|
||||
KV-SS25
|
||||
KV-SS25D
|
||||
KV-SS55EX (*)
|
||||
KV-S2025C (*)
|
||||
KV-S2045C (*)
|
||||
KV-S2065L (*)
|
||||
|
||||
(*) WARNING: None of the advanced options of these scanners are avail-
|
||||
able (ie no color, no high resolution, no automatic cropping). Basi-
|
||||
cally, the driver does no more than what it does for the KV-SS25. I
|
||||
don't have access to such scanners, and thus cannot add these options.
|
||||
|
||||
Other Panasonic high speed scanners may or may not work with that back-
|
||||
end.
|
||||
|
|
@ -59,8 +68,8 @@
|
|||
<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.
|
||||
the scan area. All parameters are specified in millimeters. It
|
||||
is possible to use the option <I>--paper-size</I> instead.
|
||||
|
||||
<B>Enhancement</B>
|
||||
|
||||
|
|
@ -104,8 +113,8 @@
|
|||
</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.
|
||||
the device name to use (eg /dev/scanner) and the SCSI option to auto-
|
||||
detect the scanners supported.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -131,7 +140,7 @@
|
|||
<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
|
||||
page in duplex mode at high resolution. The frontend will return
|
||||
a memory error in that case. Apparently, the KV-SS 25D has not
|
||||
that problem.
|
||||
|
||||
|
|
@ -141,22 +150,22 @@
|
|||
|
||||
<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.
|
||||
some more precise enhancement options. This is not implemented.
|
||||
|
||||
<B>Duplex</B> <B>mode</B>
|
||||
The backend does not support the setting of different options
|
||||
for each side. The scan will occur with the same options
|
||||
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
|
||||
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
|
||||
scanadf -d matsushita --output-file scan%04d.pbm --start-count 0
|
||||
--duplex --resolution 300 --feeder-mode="All pages" --paper-size="A4"
|
||||
|
||||
|
||||
|
|
@ -175,7 +184,7 @@
|
|||
The package is actively maintained by Frank Zago.
|
||||
http://www.zago.net/sane/#matsushita
|
||||
|
||||
sane-backends 1.0.13 April 21s, 2002 <B><A HREF="sane-matsushita.5.html">sane-matsushita(5)</A></B>
|
||||
sane-backends 1.0.14-cvs February 11th, 2004 <B><A HREF="sane-matsushita.5.html">sane-matsushita(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -166,7 +166,7 @@
|
|||
ers mailing list. Have a look at http://www.sane-project.org/mail-
|
||||
ing-lists.html concerning subscription to sane-devel.
|
||||
|
||||
sane-backends 1.0.13 February 8, 2000 <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B>
|
||||
sane-backends 1.0.14-cvs February 8, 2000 <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -283,7 +283,7 @@
|
|||
Karsten Festag karsten.festag@gmx.de
|
||||
|
||||
|
||||
sane-backends 1.0.13 28 Jan 2002 <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 28 Jan 2002 <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -12,15 +12,16 @@
|
|||
|
||||
</PRE>
|
||||
<H2>NAME</H2><PRE>
|
||||
sane-mustek - SANE backend for Mustek SCSI flatbed scanners
|
||||
sane-mustek - SANE backend for Mustek SCSI flatbed scanners (and some
|
||||
other devices)
|
||||
|
||||
|
||||
</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:
|
||||
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 and parport flatbed scanners. At present, the following
|
||||
scanners are known to work more or less with this backend:
|
||||
|
||||
Paragon MFS-6000CX
|
||||
Paragon MFS-12000CX
|
||||
|
|
@ -30,12 +31,13 @@
|
|||
Paragon MFS-8000SP
|
||||
Paragon MFS-1200SP, MFS-12000SP
|
||||
ScanExpress 6000SP
|
||||
ScanExpress 12000SP, 12000SP Plus, Paragon 1200 III SP, Scan-
|
||||
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 EP
|
||||
Paragon 600 II N
|
||||
Trust Imagery 1200
|
||||
Trust Imagery 1200 SP
|
||||
|
|
@ -46,20 +48,21 @@
|
|||
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-
|
||||
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>.
|
||||
Note that most of the above scanners come with a SCSI interface. The
|
||||
only non-SCSI scanners that have some support at this point is the 600
|
||||
II N and 600 II EP scanners. The former one comes with its own parallel
|
||||
port adapter (i.e., it does <I>not</I> attach to the printer port). Both scan-
|
||||
ners use the SCSI protocoll internally, too. More info on how to use
|
||||
these parallel port scanners can be found below in section <B>PARALLEL</B>
|
||||
<B>PORT</B> <B>SCANNERS</B>. Other parallel port scanners are not supported by this
|
||||
backend but you may be successful using the Mustek parallel port back-
|
||||
end mustek_pp, see <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>. USB scanners are also not sup-
|
||||
ported by this backend but the ma1509, mustek_usb, gt68xx, and plustek
|
||||
backends include support for some of them, see <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>, <B>sane-</B>
|
||||
<B><A HREF="mustek_usb.5.html">mustek_usb(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>, and <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>.
|
||||
|
||||
Mustek scanners have no protection against exceeding the physical scan
|
||||
area height. That is, if a scan is attempted with a height that
|
||||
|
|
@ -67,7 +70,7 @@
|
|||
noises and the scan mechanism may be damaged. Thus, if you hear such a
|
||||
noise, IMMEDIATELY turn off the scanner. This shouldn't happen if your
|
||||
scanner is in the list of known scanners. There is more information in
|
||||
the <I>/usr/local/doc/sane-1.0.13/PROBLEMS</I> file.
|
||||
the <I>/usr/local/doc/sane-1.0.14-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-
|
||||
|
|
@ -87,87 +90,88 @@
|
|||
<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.
|
||||
responds to a SCSI scanner or the port number at which the parallel
|
||||
port scanners can be found (see section <B>PARALLEL</B> <B>PORT</B> <B>SCANNERS</B> below).
|
||||
For SCSI scanners, the special device name must be a generic SCSI
|
||||
device or a symlink to such a device. The program <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/sg3</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
|
||||
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
|
||||
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>,
|
||||
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
|
||||
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.
|
||||
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
|
||||
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-
|
||||
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
|
||||
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
|
||||
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
|
||||
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
|
||||
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-
|
||||
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
|
||||
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
|
||||
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
|
||||
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.
|
||||
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:
|
||||
|
|
@ -186,74 +190,67 @@
|
|||
</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-
|
||||
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.
|
||||
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
|
||||
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
|
||||
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
|
||||
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
|
||||
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-
|
||||
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>.
|
||||
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).
|
||||
<H2>PARALLEL PORT SCANNERS</H2><PRE>
|
||||
This backend has support for the Paragon 600 II EP and Paragon 600 II N
|
||||
parallel port scanners. Note that the latter scanner comes with its
|
||||
own ISA card that implements a funky parallel port (in other words, the
|
||||
scanner does not connected 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:
|
||||
These scanners can be configured by listing the port number of the
|
||||
adapter or the parallel port in the mustek.conf file. Valid port num-
|
||||
bers for the 600 II N are <I>0x26b</I>, <I>0x2ab</I>, <I>0x2eb</I>, <I>0x22b</I>, <I>0x32b</I>, <I>0x36b</I>,
|
||||
<I>0x3ab</I>, <I>0x3eb</I>. For the 600 II EP use one of these: <I>0x378</I>, <I>0x278</I>, <I>0x3bc</I>.
|
||||
Pick one that doesn't conflict with the other hardware in your com-
|
||||
puter. Put only one number on a single line. Example:
|
||||
|
||||
<I>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.
|
||||
Note that for these scanners usually root privileges are required to
|
||||
access the I/O ports. Thus, either make frontends such as <B><A HREF="scanimage.1.html">scanimage(1)</A></B>
|
||||
and <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B> setuid root (generally not recommended for safety
|
||||
reasons) or, alternatively, access this backend through the network
|
||||
daemon <B><A HREF="saned.1.html">saned(1)</A></B>.
|
||||
|
||||
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
|
||||
Also note that after a while of no activity, some scanners themselves
|
||||
(not the SANE backend) turns off their CCFL lamps. This shutdown is not
|
||||
always perfect with the result that the lamp sometimes continues to
|
||||
glow dimly at one end. This doesn't appear to be dangerous since as
|
||||
|
|
@ -314,14 +311,14 @@
|
|||
<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.13/mustek/mustek.CHANGES</I>
|
||||
<I>/usr/local/doc/sane-1.0.14-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
|
||||
Henning Meier-Geinitz, James Perry (600 II EP).
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -337,7 +334,7 @@
|
|||
More detailed bug information is available at the Mustek backend home-
|
||||
page: <I>http://www.meier-geinitz.de/sane/mustek-backend/</I>.
|
||||
|
||||
sane-backends 1.0.13 5 Dec 2002 <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 25 Dec 2002 <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -24,24 +24,19 @@
|
|||
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. Currently
|
||||
there is no CCD support however. For CCD scanners, use the <B>sane-</B>
|
||||
<B>mustek_pp_ccd(5)</B> backend.
|
||||
The current version of this backend supports both CCD type scanners and
|
||||
CIS type scanners.
|
||||
|
||||
The following scanners might work with this backend:
|
||||
|
||||
<B>CCD</B> <B>scanners</B> (currently not hooked up yet, use mustek_pp_ccd backend)
|
||||
<B>CCD</B> <B>scanners</B>
|
||||
|
||||
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 1200 ED Plus 1015 01 no
|
||||
SM 1200 ED Plus 1015 01 no
|
||||
SE 12000 P 1505 05 no
|
||||
600 III EP Plus 1013/1015 00/01 yes
|
||||
SE 600 SEP 1013 ?? yes
|
||||
|
|
@ -71,18 +66,18 @@
|
|||
Trust
|
||||
Easy Connect 9600+ 600 CP yes
|
||||
|
||||
(*) Calibration problems existed with earlier version of this
|
||||
(*) Calibration problems existed with earlier version of this
|
||||
driver. They seem to be solved now.
|
||||
|
||||
(**) Problems have been reported in the past for the MD/LT9850 type
|
||||
(striped scans, head moving in wrong direction at some resolu-
|
||||
tions). It is not known whether the current version of the
|
||||
(**) 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-
|
||||
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.
|
||||
|
|
@ -91,17 +86,17 @@
|
|||
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
|
||||
This backend also conflicts with the <I>sane-musteka4s2</I> backend. You can
|
||||
only enable one of them in your dll.conf. However, you have to enable
|
||||
the backend explicitly in your dll.conf, just remove the hash mark in
|
||||
the line "mustek_pp".
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>DEVICE DEFINITION</H2><PRE>
|
||||
This backend allows multiple devices being defined and configured via
|
||||
the <B>mustek_pp.conf</B> file (even simultaneously, provided that they are
|
||||
connected to different parallel ports). Please make sure to edit this
|
||||
This backend allows multiple devices being defined and configured via
|
||||
the <B>mustek_pp.conf</B> file (even simultaneously, provided that they are
|
||||
connected to different parallel ports). Please make sure to edit this
|
||||
file <B>before</B> you use the backend.
|
||||
|
||||
A device can be defined as follows:
|
||||
|
|
@ -113,28 +108,32 @@
|
|||
<B><name></B> is an arbitrary name for the device, optionally enclosed by dou-
|
||||
ble quotes, for instance "LifeTec 9350".
|
||||
|
||||
<B><port</B> <B>name></B> is the name of the parallel port to which the device is
|
||||
connected. In case libieee1284 is used for communication with
|
||||
the port <I>(default</I> <I>setup)</I>, valid port names are <B>parport0</B>, <B>par-</B>
|
||||
<B><port</B> <B>name></B> is the name of the parallel port to which the device is
|
||||
connected. In case libieee1284 is used for communication with
|
||||
the port <I>(default</I> <I>setup)</I>, valid port names are <B>parport0</B>, <B>par-</B>
|
||||
<B>port1</B>, and <B>parport2</B>.
|
||||
|
||||
In case the backend is configured for raw IO <I>(old</I> <I>setup)</I>, port
|
||||
addresses have to be used instead of port names: <B>0x378</B>, <B>0x278</B>,
|
||||
or <B>0x3BC</B>. The mapping of parallel ports (lp0, lp1, and lp2) to
|
||||
In case the backend is configured for raw IO <I>(old</I> <I>setup)</I>, port
|
||||
addresses have to be used instead of port names: <B>0x378</B>, <B>0x278</B>,
|
||||
or <B>0x3BC</B>. The mapping of parallel ports (lp0, lp1, and lp2) to
|
||||
these addresses can be different for different Linux kernel ver-
|
||||
sions. For instance, if you are using a Kernel 2.2.x or better
|
||||
and you have only one parallel port, this port is named lp0
|
||||
regardless of the base address. However, this backend requires
|
||||
the base address of your port. If you are not sure which port
|
||||
sions. For instance, if you are using a Kernel 2.2.x or better
|
||||
and you have only one parallel port, this port is named lp0
|
||||
regardless of the base address. However, this backend requires
|
||||
the base address of your port. If you are not sure which port
|
||||
your scanner is connected to, have a look at your /etc/conf.mod-
|
||||
ules, /etc/modules.conf and/or /proc/ioports.
|
||||
|
||||
If you are unsure which port to use, you can use the magic value
|
||||
<B>*</B> to probe for your scanner.
|
||||
|
||||
<B><driver></B> is the driver to use for this device. Currently available
|
||||
drivers are:
|
||||
|
||||
<B>cis600</B> : for 600 CP, 96 CP & OEM versions
|
||||
<B>cis1200</B> : for 1200 CP & OEM versions
|
||||
<B>cis1200+</B> : for 1200 CP+ & OEM versions
|
||||
<B>ccd300</B> : for 600 IIIE P & OEM version
|
||||
|
||||
<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.
|
||||
|
|
@ -156,6 +155,12 @@
|
|||
|
||||
scanner Mustek_600CP 0x378 cis600
|
||||
|
||||
scanner Mustek_600IIIEP * ccd300
|
||||
|
||||
If in doubt which port you have to use, or whether your scanner is
|
||||
detected at all, you can use <B>sane-find-scanner</B> <B>-p</B> to probe all config-
|
||||
ured ports.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONFIGURATION</H2><PRE>
|
||||
|
|
@ -212,7 +217,23 @@
|
|||
|
||||
<B>CCD</B> <B>driver</B> <B>options</B>
|
||||
|
||||
To be defined.
|
||||
<B>top</B> <B><value></B> Number of scanlines to skip to the start of the scan
|
||||
area. The number can be any positive integer. Values known
|
||||
to me are 47 and 56.
|
||||
Default value: 47
|
||||
Minimum: 0
|
||||
Maximum: none
|
||||
|
||||
Example: option top 56
|
||||
|
||||
<B>waitbank</B> <B><value></B> The number of usecs to wait for a bank change. You
|
||||
should not touch this value actually. May be any positive
|
||||
integer
|
||||
Default value: 700
|
||||
Minimum: 0
|
||||
Maximum: none
|
||||
|
||||
Example: option waitbank 700
|
||||
|
||||
A sample configuration file is shown below:
|
||||
|
||||
|
|
@ -243,6 +264,15 @@
|
|||
option bw 130
|
||||
option top_skip 0.2
|
||||
|
||||
#
|
||||
# A Mustek 600 III EPP on port parport0
|
||||
#
|
||||
scanner "Mustek 600 III EPP" parport0 ccd300
|
||||
|
||||
# Some calibration options (examples!).
|
||||
option bw 130
|
||||
option top 56
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>FILES</H2><PRE>
|
||||
|
|
@ -308,10 +338,10 @@
|
|||
|
||||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-mustek_pp_ccd.5.html">sane-mustek_pp_ccd(5)</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>
|
||||
<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>, <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>
|
||||
|
||||
For latest bug fixes and information see
|
||||
<I>http://www.penguin-breeder.org/?page=mustek</I><B>_</B><I>pp</I>
|
||||
<I>http://www.penguin-breeder.org/sane/mustek</I><B>_</B><I>pp/</I>
|
||||
|
||||
For the latest CIS driver versions, see
|
||||
<I>http://home.tiscalinet.be/EddyDeGreef/</I>
|
||||
|
|
@ -330,10 +360,6 @@
|
|||
first to the list before you can send emails... see
|
||||
http://www.sane-project.org/mailing-lists.html)
|
||||
|
||||
* 1013 support isn't bullet proofed
|
||||
* 1505 support isn't even present
|
||||
* 1015 only works for CCD type 00 & 01 (01 only bw/grayscale)
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>BUG REPORTS</H2><PRE>
|
||||
|
|
@ -364,7 +390,7 @@
|
|||
|
||||
<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>
|
||||
November 17 2003 <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -149,8 +149,8 @@
|
|||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>, <B>sane-plus-</B>
|
||||
<B><A HREF="tek.5.html">tek(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>, <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>
|
||||
<I>/usr/local/doc/sane-1.0.13/mustek</I><B>_</B><I>usb/mustek</I><B>_</B><I>usb.CHANGES</I>,
|
||||
<I>/usr/local/doc/sane-1.0.13/mustek</I><B>_</B><I>usb/mustek</I><B>_</B><I>usb.TODO</I>
|
||||
<I>/usr/local/doc/sane-1.0.14-cvs/mustek</I><B>_</B><I>usb/mustek</I><B>_</B><I>usb.CHANGES</I>,
|
||||
<I>/usr/local/doc/sane-1.0.14-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>
|
||||
|
||||
|
||||
|
|
@ -164,20 +164,19 @@
|
|||
</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.
|
||||
can't be reset (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. The workaround for Linux is to
|
||||
use the scanner module (modprobe scanner) instead of libusb. See <B>sane-</B>
|
||||
<B><A HREF="usb.5.html">usb(5)</A></B> for details.
|
||||
In earlier versions this backend failed when it is loaded the second
|
||||
time in some configurations. The only choice was to replug the scanner
|
||||
in this case. The backend uses a workaround for that bug now but it's
|
||||
only tested on Linux. Reports for other operating systems are apprici-
|
||||
ated.
|
||||
|
||||
More detailed bug information is available at the Mustek backend home-
|
||||
More detailed bug information is available at the Mustek backend home-
|
||||
page <I>http://www.meier-geinitz.de/sane/mustek</I><B>_</B><I>usb-backend/</I>.
|
||||
|
||||
sane-backends 1.0.13 21 Oct 2003 <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 3 Mar 2004 <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@
|
|||
<H2>AUTHORS</H2><PRE>
|
||||
Kazuya Fukuda
|
||||
|
||||
sane-backends 1.0.13 17 Feb 2000 <B><A HREF="sane-nec.5.html">sane-nec(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 17 Feb 2000 <B><A HREF="sane-nec.5.html">sane-nec(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -131,7 +131,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
David Mosberger and Andreas Beck
|
||||
|
||||
sane-backends 1.0.13 8 Oct 2002 <B><A HREF="sane-net.5.html">sane-net(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 8 Oct 2002 <B><A HREF="sane-net.5.html">sane-net(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -66,7 +66,7 @@
|
|||
Please send any information and bug-reports to:
|
||||
<B>Simon</B> <B>Munton</B> <B><simon@munton.demon.co.uk></B>
|
||||
|
||||
sane-backends 1.0.13 7 Sept 2000 <B><A HREF="sane-pie.5.html">sane-pie(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 7 Sept 2000 <B><A HREF="sane-pie.5.html">sane-pie(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -135,7 +135,7 @@
|
|||
No testing has been done on three-pass or handheld scanners, or with
|
||||
Automatic Document Feeder support.
|
||||
|
||||
sane-backends 1.0.13 13 May 1998 <B><A HREF="sane-pint.5.html">sane-pint(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 13 May 1998 <B><A HREF="sane-pint.5.html">sane-pint(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -12,8 +12,7 @@
|
|||
|
||||
</PRE>
|
||||
<H2>NAME</H2><PRE>
|
||||
sane-plustek - SANE backend for Plustek parallel port and LM983[1/2/3]
|
||||
based USB flatbed scanners
|
||||
sane-plustek - SANE backend for LM983[1/2/3] based USB flatbed scanners
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -30,8 +29,8 @@
|
|||
The Backend is able to support USB scanner based on the National Semi-
|
||||
conductor chipsets 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 an unsupported ASIC inside.
|
||||
scanner has another Product ID, then the device is <B>NOT</B> supported by
|
||||
this backend.
|
||||
|
||||
Vendor Plustek - ID: 0x07B3
|
||||
----------------------------------------------------------
|
||||
|
|
@ -68,7 +67,9 @@
|
|||
USB Model: ASIC: Properties: Prod-ID
|
||||
----------------------------------------------------------
|
||||
BearPaw 1200 LM9831 600x1200dpi 42bit 512Kb 0x1000
|
||||
BearPaw 1200 LM9832 600x1200dpi 42bit 512Kb 0x1001*
|
||||
BearPaw 2400 LM9832 1200x2400dpi 42bit 2Mb 0x1001
|
||||
* see also description for model override switch below!
|
||||
|
||||
Vendor UMAX - ID: 0x1606
|
||||
----------------------------------------------------------
|
||||
|
|
@ -96,6 +97,7 @@
|
|||
----------------------------------------------------------
|
||||
CanoScan N650/656U LM9832 600x1200dpi 42bit 512Kb 0x2206
|
||||
CanoScan N1220U LM9832 1200x2400dpi 42bit 512Kb 0x2207
|
||||
CanoScan D660U LM9832 600x1200dpi 42bit 512Kb 0x2208
|
||||
CanoScan N670/676U LM9833 600x1200dpi 48bit 512Kb 0x220D
|
||||
CanoScan N1240U LM9833 1200x2400dpi 48bit 512Kb 0x220E
|
||||
CanoScan LIDE20 LM9833 600x1200dpi 48bit 512Kb 0x220D
|
||||
|
|
@ -108,13 +110,18 @@
|
|||
The SCSI scanner OpticPro 19200S is a rebadged Artec AM12S scanner and
|
||||
is supported by the <B>Artec</B> backend.
|
||||
Only the National Semiconductor LM983[1/2/] based devices of Plustek
|
||||
are supported by this driver. Older versions of the U12, the UT12, the
|
||||
are supported by this backend. 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
|
||||
U12 P98003 u12
|
||||
UT12 P98003 u12
|
||||
1212U P98003 u21
|
||||
For a more complete and up to date list see: <B>http://www.sane-</B>
|
||||
<B>project.org/sane-supported-devices.html</B>
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -127,9 +134,9 @@
|
|||
|
||||
<I>device</I> <I>/dev/usbscanner</I>
|
||||
|
||||
<I>[usb]</I> tells the backend, that the following devicename (here <I>/dev/usb-</I>
|
||||
<I>scanner</I> ) has to be interpreted as USB scanner device. If vendor- and
|
||||
product-id has not been specified, the backend tries to detect this by
|
||||
<I>[usb]</I> tells the backend, that the following devicename (here <I>/dev/usb-</I>
|
||||
<I>scanner</I> ) has to be interpreted as USB scanner device. If vendor- and
|
||||
product-id has not been specified, the backend tries to detect this by
|
||||
its own. If device ist set to <I>auto</I>
|
||||
then the next matching device is used.
|
||||
|
||||
|
|
@ -139,13 +146,21 @@
|
|||
<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
|
||||
<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 --> switch
|
||||
lamps off, 0 --> do not change lamp status
|
||||
|
||||
option mov m
|
||||
<I>m</I> is the model override switch. It works only with Mustek
|
||||
BearPaw devices.
|
||||
m/PID | 0x1000 | 0x1001
|
||||
------+--------------+--------------
|
||||
0 | BearPaw 1200 | BearPaw 2400
|
||||
1 | no function | BearPaw 1200
|
||||
|
||||
option invertNegatives b
|
||||
<I>b</I> 0 --> do not invert the picture during negativ scans, 1 -->
|
||||
invert picture
|
||||
|
|
@ -211,17 +226,9 @@
|
|||
|
||||
<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.
|
||||
Alternatively, the backend is able to access your scanner via libusb.
|
||||
You might use <B>sane-find-scanner</B> to check that you have access to your
|
||||
device.
|
||||
you have access to the device-node. For more details see <B>sane-usb</B> <B>(5)</B>
|
||||
manpage. You might use <B>sane-find-scanner</B> to check that you have access
|
||||
to your device.
|
||||
|
||||
<B>Note:</B>
|
||||
If there's no configuration file, the backend defaults to <B>device</B> <B>auto</B>
|
||||
|
|
@ -240,6 +247,37 @@
|
|||
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_PLUSTEK</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_PLUSTEK=10
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>,
|
||||
<I>/usr/local/doc/sane-1.0.14-cvs/plustek/Plustek-USB.changes</I>
|
||||
<I>http://www.gjaeger.de/scanner/plustek.html</I>
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONTACT AND BUG-REPORTS</H2><PRE>
|
||||
Please send any information and bug-reports to:
|
||||
|
|
@ -254,14 +292,14 @@
|
|||
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
|
||||
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-
|
||||
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.
|
||||
|
||||
|
||||
|
|
@ -273,7 +311,7 @@
|
|||
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.
|
||||
600dpi but the motor is capable to perform 1200dpi steps.
|
||||
* Plusteks' model policy is somewhat inconsistent. This
|
||||
means, they sell technical different devices under the
|
||||
same product name. Therefore it is possible that some
|
||||
|
|
@ -282,7 +320,7 @@
|
|||
the one your device has.
|
||||
* Negative/Slide scanning quality is poor.
|
||||
|
||||
sane-backends 1.0.13 27 October 2003 <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 22 Mar 2004 <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -113,13 +113,13 @@
|
|||
|
||||
<I>/usr/local/etc/sane.d/plustek</I><B>_</B><I>pp.conf</I>
|
||||
|
||||
See the plustek_pp.conf file for examples.
|
||||
See this file for examples.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONFIGURATION</H2><PRE>
|
||||
Beside the kernel-module options, which are described below, you need
|
||||
to enable the parallel port device in the configuration file
|
||||
This section decribes the backends' configuration file entries. The
|
||||
file is located at:
|
||||
|
||||
<I>/usr/local/etc/sane.d/plustek</I><B>_</B><I>pp.conf</I>
|
||||
|
||||
|
|
@ -135,24 +135,89 @@
|
|||
|
||||
<I>device</I> <I>/dev/pt</I><B>_</B><I>drv</I>
|
||||
|
||||
<I>direct</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.
|
||||
<I>direct</I> tells the backend, that the following devicename (here <I>0x378</I> )
|
||||
has to be interpreted as parallel port scanner device. In fact it is
|
||||
the address to use, alternatively you can use <I>/dev/parport0</I> if the
|
||||
backend has been compiled with libieee1284 support. <I>kernel</I> should only
|
||||
be used, when a kernel-module has been built out of the backend
|
||||
sources. See below for more instructions about this.
|
||||
|
||||
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>
|
||||
Further options:
|
||||
|
||||
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 --> switch
|
||||
lamps off, 0 --> do not change lamp status
|
||||
|
||||
option mov m
|
||||
<I>m</I> is the model override switch, which only works in direct mode.
|
||||
<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)
|
||||
|
||||
See the plustek_pp.conf file for examples.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>BUILDING THE KERNEL MODULE</H2><PRE>
|
||||
As mentioned before, the plustek_pp backend code can also be compiled
|
||||
and installed as linux kernel module. To do so, you will need the
|
||||
source-files of this sane-backend installation. Unpack this tar-ball
|
||||
and go to the directory:
|
||||
<I>sane-backends/doc/plustek</I>
|
||||
Within this directory, you should find a file called:
|
||||
<I>Makefile.module</I>
|
||||
Now if your Linux kernelsources are installed correctly, it should be
|
||||
possible to build, install and load the module <B>pt_drv.</B> Try
|
||||
<I>make</I> <I>-f</I> <I>Makefile.module</I>
|
||||
to obtain a help text, about the targets, the makefile supports.
|
||||
Use
|
||||
<I>make</I> <I>-f</I> <I>Makefile.module</I> <I>all</I>
|
||||
to build the module. Use
|
||||
<I>make</I> <I>-f</I> <I>Makefile.module</I> <I>install</I>
|
||||
to install the module. Use
|
||||
<I>make</I> <I>-f</I> <I>Makefile.module</I> <I>load</I>
|
||||
to load the module.
|
||||
<B>Note:</B> <B>Installing</B> <B>and</B> <B>loading</B> <B>the</B> <B>can</B> <B>only</B> <B>be</B> <B>done</B> <B>as</B> <B>superuser.</B>
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>KERNEL MODULE SETUP</H2><PRE>
|
||||
The configuration of the kernel module is done by providing some or
|
||||
more options found below to the kernel module at load time. This can be
|
||||
done by invoking insmod with the appropriate parameters or appending
|
||||
the options to the file <B>/etc/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-
|
||||
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
|
||||
<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-
|
||||
<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
|
||||
|
|
@ -160,7 +225,7 @@
|
|||
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 -->
|
||||
<I>e</I> specifies the behaviour when unloading the driver, 1 -->
|
||||
switch lamps off, 0 --> do not change lamp status
|
||||
|
||||
slowIO=s
|
||||
|
|
@ -168,7 +233,7 @@
|
|||
delayed functions, 0 --> use the non-delayed ones
|
||||
|
||||
forceMode=fm
|
||||
<I>fm</I> specifies port mode which should be used, 0 --> autodetec-
|
||||
<I>fm</I> specifies port mode which should be used, 0 --> autodetec-
|
||||
tion, 1 --> use SPP mode and 2 --> use EPP mode
|
||||
|
||||
mov=m
|
||||
|
|
@ -187,8 +252,8 @@
|
|||
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)
|
||||
<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>
|
||||
|
|
@ -196,19 +261,20 @@
|
|||
<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
|
||||
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.
|
||||
</PRE>
|
||||
<H2>PARALLEL PORT MODES</H2><PRE>
|
||||
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 parallel ports.
|
||||
|
||||
Former Plustek scanner models (4830, 9630) supplied a ISA parallel port
|
||||
adapter card. This card is <B>not</B> supported by the driver.
|
||||
|
|
@ -221,12 +287,6 @@
|
|||
See the plustek_pp.conf file for examples.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>BUILDING THE KERNEL MODULE</H2><PRE>
|
||||
As mentioned before, the plustek_pp backend code can also be compiled
|
||||
and installed as linux kernel module...
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>FILES</H2><PRE>
|
||||
<I>/usr/local/etc/sane.d/plustek</I><B>_</B><I>pp.conf</I>
|
||||
|
|
@ -243,6 +303,37 @@
|
|||
The Linux Kernelmodule.
|
||||
|
||||
|
||||
</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_PLUSTEK_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_PLUSTEK_PP=10
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>,
|
||||
<I>/usr/local/doc/sane-1.0.14-cvs/plustek/Plustek-PARPORT.changes</I>
|
||||
<I>http://www.gjaeger.de/scanner/plustek.html</I>
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONTACT AND BUG-REPORTS</H2><PRE>
|
||||
Please send any information and bug-reports to:
|
||||
|
|
@ -258,8 +349,8 @@
|
|||
<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).
|
||||
variable <I>SANE</I><B>_</B><I>DEBUG</I><B>_</B><I>PLUSTEK</I><B>_</B><I>PP</I> before calling your favorite scan-fron-
|
||||
tend (i.e. xscanimage).
|
||||
<B>i.e.:</B> <B>export</B> <B>SANE_DEBUG_PLUSTEK_PP=20</B> <B>;</B> <B>xscanimage</B>
|
||||
|
||||
The value controls the verbosity of the backend.
|
||||
|
|
@ -296,7 +387,7 @@
|
|||
* The scanspeed on 600x1200 dpi models is slow.
|
||||
* The scanquality of the A3I is poor
|
||||
|
||||
sane-backends 1.0.13 24 September 2003 <B><A HREF="sane-plustek_pp.5.html">sane-plustek_pp(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 13 Jan 2004 <B><A HREF="sane-plustek_pp.5.html">sane-plustek_pp(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -74,7 +74,7 @@
|
|||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>
|
||||
|
||||
sane-backends 1.0.13 22 April 2001 <B><A HREF="sane-pnm.5.html">sane-pnm(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 22 April 2001 <B><A HREF="sane-pnm.5.html">sane-pnm(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -109,7 +109,7 @@
|
|||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>
|
||||
|
||||
sane-backends 1.0.13 25 October 1997 <B><A HREF="sane-qcam.5.html">sane-qcam(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 25 October 1997 <B><A HREF="sane-qcam.5.html">sane-qcam(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -85,7 +85,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
Feico W. Dillema
|
||||
|
||||
sane-backends 1.0.13 24 Jun 2000 <B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 24 Jun 2000 <B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -83,7 +83,7 @@
|
|||
Ingo Schneider
|
||||
|
||||
|
||||
sane-backends 1.0.13 24 Jun 2000 <B><A HREF="sane-s9036.5.html">sane-s9036(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 24 Jun 2000 <B><A HREF="sane-s9036.5.html">sane-s9036(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -147,7 +147,7 @@
|
|||
The package is actively maintained by Frank Zago.
|
||||
http://www.zago.net/sane/#sceptre
|
||||
|
||||
sane-backends 1.0.13 April 21st, 2002 <B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B>
|
||||
sane-backends 1.0.14-cvs April 21st, 2002 <B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -303,7 +303,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
David Mosberger
|
||||
|
||||
sane-backends 1.0.13 28 Oct 2003 <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 28 Oct 2003 <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -366,7 +366,7 @@
|
|||
Parts of this man page are a plain copy of <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B> by David Mos-
|
||||
berger-Tang, Andreas Czechanowski and Andreas Bolsch
|
||||
|
||||
sane-backends 1.0.13 21 Nov 2000 <B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 21 Nov 2000 <B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -110,7 +110,7 @@
|
|||
Marian Eichholz (eichholz@computer.org)
|
||||
Glenn Ramsey (glenn@componic.com)
|
||||
|
||||
sane-backends 1.0.13 10.02.2002 <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 10.02.2002 <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -114,7 +114,7 @@
|
|||
Man page by Henning Meier-Geinitz (mostly based on the web pages and
|
||||
source code).
|
||||
|
||||
sane-backends 1.0.13 26 May 2001 <B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 26 May 2001 <B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -78,7 +78,7 @@
|
|||
working first driver. Watch this space for changes.
|
||||
|
||||
|
||||
sane-backends 1.0.13 17 Apr 2002 <B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 17 Apr 2002 <B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -153,7 +153,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
Ingo Wilken <Ingo.Wilken@informatik.uni-oldenburg.de>
|
||||
|
||||
sane-backends 1.0.13 08 Mar 1999 <B><A HREF="sane-st400.5.html">sane-st400(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 08 Mar 1999 <B><A HREF="sane-st400.5.html">sane-st400(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -87,7 +87,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
Roger Wolff
|
||||
|
||||
sane-backends 1.0.13 24 Jun 2000 <B><A HREF="sane-tamarack.5.html">sane-tamarack(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 24 Jun 2000 <B><A HREF="sane-tamarack.5.html">sane-tamarack(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -28,13 +28,13 @@
|
|||
Vendor Model TECO model status
|
||||
---------------------- -------------- -----------
|
||||
Relisys AVEC 2400 VM3520 tested
|
||||
Relisys AVEC 2412 VM3520+ untested
|
||||
Relisys AVEC 2412 VM3520+ tested
|
||||
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 4816 VM4540 tested
|
||||
Relisys RELI 4830 VM4542 tested
|
||||
Relisys RELI 9600 VM6530 untested
|
||||
Relisys RELI 9612 VM6530* untested
|
||||
|
|
@ -166,7 +166,7 @@
|
|||
Thanks to Gerard Delafond for the VM4542 support. Thanks to Jean-Yves
|
||||
Simon for the VM3510 support.
|
||||
|
||||
sane-backends 1.0.13 August 30th, 2002 <B><A HREF="sane-teco1.5.html">sane-teco1(5)</A></B>
|
||||
sane-backends 1.0.14-cvs August 30th, 2002 <B><A HREF="sane-teco1.5.html">sane-teco1(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -29,17 +29,17 @@
|
|||
---------------------- -------------- -----------
|
||||
|
||||
Mustek ScanMagic 4830S VM3575 untested
|
||||
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
|
||||
Primax Jewel 4800 VM356A basic
|
||||
Primax Profi 9600 VM6575 basic
|
||||
Primax Profi 19200 VM6586 good
|
||||
Relisys APOLLO Express 3 VM356A basic
|
||||
Relisys APOLLO Express 6 VM6565 good
|
||||
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
|
||||
Relisys AVEC II S3 VM3564 basic
|
||||
Relisys AVEC Super 3 VM3575 basic
|
||||
Relisys SCORPIO Pro VM6575 good
|
||||
Relisys SCORPIO Pro-S VM6586 untested
|
||||
Relisys SCORPIO Super 3 VM3575 basic
|
||||
|
||||
For all these scanners, black&white and grayscale mode work well. How-
|
||||
ever, most of them do not support more than a handful of resolutions in
|
||||
|
|
@ -104,20 +104,33 @@
|
|||
(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>--white-level</B>
|
||||
(VM3564, VM356A, VM3575 only)can be used to reduce the noise,
|
||||
when scanning some sheets by changing the calibration value
|
||||
loaded into the scanner.
|
||||
<B>--white-level-r</B>
|
||||
(VM3564, VM356A, VM3575 only) Selects what red radiance level
|
||||
should be considered "white", when scanning some sheets by
|
||||
changing the calibration value loaded into the scanner. Scale
|
||||
0..64 in steps of 1.
|
||||
|
||||
<B>--white-level-g</B>
|
||||
(VM3564, VM356A, VM3575 only) Selects what green radiance level
|
||||
should be considered "white", when scanning some sheets by
|
||||
changing the calibration i value loaded into the scanner. Scale
|
||||
0..64 in steps of 1.
|
||||
|
||||
<B>--white-level-g</B>
|
||||
(VM3564, VM356A, VM3575 only) Selects what blue radiance level
|
||||
should be considered "white", when scanning some sheets by
|
||||
changing the calibration value loaded into the scanner. Scale
|
||||
0..64 in steps of 1.
|
||||
|
||||
<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
|
||||
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
|
||||
The configuration file /usr/local/etc/sane.d/teco2.conf supports only
|
||||
one information: the device name to use (eg /dev/scanner).
|
||||
|
||||
|
||||
|
|
@ -134,13 +147,13 @@
|
|||
</PRE>
|
||||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_DEBUG_TECO2</B>
|
||||
If the library was compiled with debug support enabled, this
|
||||
environment variable controls the debug level for this backend.
|
||||
E.g., a value of 128 requests all debug output to be printed.
|
||||
If the library was compiled with debug support enabled, this
|
||||
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
|
||||
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. For VM356A and VM3575 default 1. For other sup-
|
||||
ported types default 0.
|
||||
|
|
@ -148,8 +161,8 @@
|
|||
|
||||
</PRE>
|
||||
<H2>LIMITATIONS</H2><PRE>
|
||||
The windows TWAIN driver has many more options than this SANE backend.
|
||||
However they are only software adjustments. This backend only imple-
|
||||
The windows TWAIN driver has many more options than this SANE backend.
|
||||
However they are only software adjustments. This backend only imple-
|
||||
ments what the scanner can support.
|
||||
|
||||
|
||||
|
|
@ -165,33 +178,32 @@
|
|||
|
||||
</PRE>
|
||||
<H2>AUTHORS</H2><PRE>
|
||||
The package is actively maintained by Frank Zago, Gerard Klaver.
|
||||
http://www.zago.net/sane/#teco2
|
||||
http://gkall.hobby.nl/index.html
|
||||
Frank Zago http://www.zago.net/sane/#teco2
|
||||
|
||||
Gerard Klaver contributed a patch to support the VM3564 and VM356A.
|
||||
The package is actively maintained by Gerard Klaver.
|
||||
http://gkall.hobby.nl/teco2.html
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CREDITS</H2><PRE>
|
||||
Thanks to:
|
||||
|
||||
Gerard Klaver for his relentless VM3575 testings.
|
||||
Gerard Klaver for his relentless VM3575 testings and contributed a
|
||||
patch to support the VM3564 and VM356A.
|
||||
|
||||
Mark Plowman for providing the first SCSI traces from a VM3575.
|
||||
|
||||
Andreas Klaedtke for providing the first SCSI traces from a VM6586 and
|
||||
Andreas Klaedtke for providing the first SCSI traces from a VM6586 and
|
||||
for his testing, and to Stefan von Dombrowski for his testing.
|
||||
|
||||
Nicolas Peyresaubes for providing the first SCSI traces from a VM656A
|
||||
Nicolas Peyresaubes for providing the first SCSI traces from a VM656A
|
||||
and for his testing.
|
||||
|
||||
Dave Parker for testing the support for the VM6575.
|
||||
|
||||
Michael Hoeller for his testing the VM356A.
|
||||
|
||||
|
||||
sane-backends 1.0.13 23 October 2003 <B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 15 January 2004 <B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -139,7 +139,7 @@
|
|||
The package is actively maintained by Frank Zago.
|
||||
http://www.zago.net/sane/#teco3
|
||||
|
||||
sane-backends 1.0.13 25 July 2002 <B><A HREF="sane-teco3.5.html">sane-teco3(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 25 July 2002 <B><A HREF="sane-teco3.5.html">sane-teco3(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -279,7 +279,7 @@
|
|||
<H2>BUGS</H2><PRE>
|
||||
- config file values aren't tested for correctness
|
||||
|
||||
sane-backends 1.0.13 24 Jul 2002 <B><A HREF="sane-test.5.html">sane-test(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 24 Jul 2002 <B><A HREF="sane-test.5.html">sane-test(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -0,0 +1,172 @@
|
|||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>sane-u12.5</TITLE>
|
||||
</HEAD>
|
||||
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="/images/sane.png" HEIGHT=117 WIDTH=346></H1>
|
||||
<H1>sane-u12.5</H1>
|
||||
<HR>
|
||||
<PRE>
|
||||
<!-- Manpage converted by man2html 3.0.1 -->
|
||||
<B><A HREF="sane-u12.5.html">sane-u12(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-u12.5.html">sane-u12(5)</A></B>
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>NAME</H2><PRE>
|
||||
sane-u12 - SANE backend for Plustek USB flatbed scanners, based on
|
||||
older parport designs
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>DESCRIPTION</H2><PRE>
|
||||
The <B>sane-u12</B> library implements a SANE (Scanner Access Now Easy) back-
|
||||
end that provides access to USB flatbed scanners based on Plusteks'
|
||||
ASIC 98003 (parallel-port ASIC) and a GeneSys Logics' USB-parport
|
||||
bridge chip.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>SUPPORTED DEVICES</H2><PRE>
|
||||
The backend is able to support some early Plustek USB scanner based
|
||||
their old parport design around the ASIC 98003 and other rebadged Plus-
|
||||
tek devices. The following tables will give you a short overview.
|
||||
|
||||
If your Plustek scanner has another Product ID, then the device is <B>NOT</B>
|
||||
supported by this backend.
|
||||
|
||||
Vendor Plustek - ID: 0x07B3
|
||||
----------------------------------------------------------
|
||||
Model: Vendor-ID: Product-ID:
|
||||
----------------------------------------------------------
|
||||
OpticPro U12 0x07B3 0x0001
|
||||
OpticPro U1212 0x07B3 0x0001
|
||||
OpticPro UT12 0x07B3 0x0001
|
||||
|
||||
Vendor KYE/Genius
|
||||
--------------------------------------------------------
|
||||
USB Model: Vendor-ID: Product-ID:
|
||||
--------------------------------------------------------
|
||||
ColorPage Vivid III USB 0x07B3 0x0001
|
||||
ColorPage HR6 V1 0x0458 0x2004
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONFIGURATION</H2><PRE>
|
||||
To use your scanner with this backend, you need at least two entries in
|
||||
the configuration file
|
||||
<I>/usr/local/etc/sane.d/u12.conf</I>
|
||||
|
||||
<I>[usb]</I> <I>vendor-id</I> <I>product-id</I>
|
||||
|
||||
<I>device</I> <I>/dev/usbscanner</I>
|
||||
|
||||
<I>[usb]</I> tells the backend, that the following devicename (here <I>/dev/usb-</I>
|
||||
<I>scanner</I> ) has to be interpreted as USB scanner device. If vendor- and
|
||||
product-id has not been specified, the backend tries to detect this by
|
||||
its own. If device 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 --> switch
|
||||
lamps off, 0 --> do not change lamp status
|
||||
|
||||
See the u12.conf file for examples.
|
||||
|
||||
<B>Note:</B>
|
||||
You have to make sure, that the USB subsystem is loaded correctly and
|
||||
you have access to the device-node. For more details see <B>sane-usb</B> <B>(5)</B>
|
||||
manpage. You might use <B>sane-find-scanner</B> to check that you have access
|
||||
to your device.
|
||||
|
||||
<B>Note:</B>
|
||||
If there's no configuration file, the backend defaults to <B>device</B> <B>auto</B>
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>FILES</H2><PRE>
|
||||
<I>/usr/local/etc/sane.d/u12.conf</I>
|
||||
The backend configuration file
|
||||
|
||||
<I>/usr/local/lib/sane/libsane-u12.a</I>
|
||||
The static library implementing this backend.
|
||||
|
||||
<I>/usr/local/lib/sane/libsane-u12.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_U12</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_U12=10
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>,
|
||||
<I>/usr/local/doc/sane-1.0.14-cvs/u12/U12.changes</I>
|
||||
<I>http://www.gjaeger.de/scanner/u12.html</I>
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONTACT AND BUG-REPORTS</H2><PRE>
|
||||
Please send any information and bug-reports to:
|
||||
<B>SANE</B> <B>Mailing</B> <B>List</B>
|
||||
|
||||
Additional info and hints can be obtained from our
|
||||
Mailing-List archive at:
|
||||
<B>http://www.sane-project.org/mailing-lists.html</B>
|
||||
|
||||
or directly from the projects' homepage at:
|
||||
<B>http://www.gjaeger.de/scanner/u12.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>U12</I> before calling your favorite scan-frontend
|
||||
(i.e. xscanimage).
|
||||
<B>i.e.:</B> <B>export</B> <B>SANE_DEBUG_U12=20</B> <B>;</B> <B>xscanimage</B>
|
||||
|
||||
The value controls the verbosity of the backend.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>KNOWN BUGS & RESTRICTIONS</H2><PRE>
|
||||
* The driver is in alpha state, so please don't expect too
|
||||
much!!!
|
||||
* When using libusb, it might be, that the backend hangs.
|
||||
In that case, reconnect the scanner.
|
||||
|
||||
sane-backends 1.0.14-cvs 23 Apr 2004 <B><A HREF="sane-u12.5.html">sane-u12(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>
|
||||
|
|
@ -268,7 +268,7 @@
|
|||
<H2>EMAIL-CONTACT</H2><PRE>
|
||||
Oliver.Rauch@Rauch-Domain.DE
|
||||
|
||||
sane-backends 1.0.13 29 november 2002 <B><A HREF="sane-umax.5.html">sane-umax(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 29 november 2002 <B><A HREF="sane-umax.5.html">sane-umax(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -134,7 +134,7 @@
|
|||
When reporting bugs, please run the backend with SANE_DEBUG_UMAX1220U
|
||||
set to 10 and attach a copy of the log messages.
|
||||
|
||||
sane-backends 1.0.13 6 Jan 2002 <B><A HREF="sane-umax1220u.5.html">sane-umax1220u(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 6 Jan 2002 <B><A HREF="sane-umax1220u.5.html">sane-umax1220u(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -24,6 +24,7 @@
|
|||
|
||||
Model:
|
||||
--------------------
|
||||
Astra 610P
|
||||
Astra 1220P
|
||||
HP3200C
|
||||
Astra 1600P
|
||||
|
|
@ -39,22 +40,26 @@
|
|||
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.
|
||||
<B>EPP/ECP</B> <B>MODES</B> <B>ONLY</B>
|
||||
The current version of the backend uses only EPP or ECP mode to
|
||||
communicate with the scanner. PS/2 and SPP mode aren't imple-
|
||||
mented. It is recommended that you set your parallel port to EPP
|
||||
in BIOS with the current version of this backend. You can leave
|
||||
it to ECP or ECP+EPP, but in this case you may not use ppdev but
|
||||
only direct hardware access if you have to use ECP. ECPEPP will
|
||||
only
|
||||
work if you use a 2.4 or 2.6 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>
|
||||
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
|
||||
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
|
||||
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.
|
||||
|
||||
|
||||
|
|
@ -88,7 +93,7 @@
|
|||
<B>NOTE:</B> in all cases, you must have sufficient priviledges
|
||||
to get access to the chosen device or address. Depending on the
|
||||
security settings, devices may not be available for all users.
|
||||
You have to change permissions on the dev/ppi* or /dev/parport*
|
||||
You have to change permissions on the dev/ppi* or /dev/parport*
|
||||
devices.
|
||||
|
||||
You can rename any device using the
|
||||
|
|
@ -104,44 +109,43 @@
|
|||
<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
|
||||
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>,
|
||||
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.
|
||||
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
|
||||
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
|
||||
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
|
||||
tion. Valid values are 610, 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
|
||||
only valid case to change the model is when your scanner produces
|
||||
'black' or prevent scanner model autodetection.
|
||||
|
||||
Option <B>buffer</B> allows you to change the size of the scan buffer. The
|
||||
size must be specified in bytes. The default value is 2 megabytes.
|
||||
Decreasing this value will improve the smoothness of the updates of
|
||||
progress status in the frontend, but will stall the scan more often.
|
||||
|
||||
Option <B>buffer</B> allows you to change the size of the scan buffer. The
|
||||
size must be specified in bytes. The default value is 2 megabytes.
|
||||
Decreasing this value will improve the smoothness of progress bar in
|
||||
the frontend, but will stall the scan more often.
|
||||
|
||||
|
||||
</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
|
||||
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>
|
||||
|
|
@ -157,21 +161,21 @@
|
|||
<B>SANE_CONFIG_DIR</B>
|
||||
This environment variable specifies the list of directories that
|
||||
may contain the configuration file. Under UNIX, the directories
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
are separated by a colon (`:'), under OS/2, they are separated
|
||||
by a semi-colon (`;'). If this variable is not set, the config-
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in
|
||||
uration file is searched in two default directories: first, the
|
||||
current working directory (".") and then in
|
||||
/usr/local/etc/sane.d. If the value of the environment variable
|
||||
ends with the directory separator character, then the default
|
||||
ends with the directory separator character, then the default
|
||||
directories are searched after the explicitly specified directo-
|
||||
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
|
||||
would result in directories "tmp/config", ".", and
|
||||
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
|
||||
would result in directories "tmp/config", ".", and
|
||||
"/usr/local/etc/sane.d" being searched (in this order).
|
||||
|
||||
<B>SANE_DEBUG_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.
|
||||
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
|
||||
|
|
@ -185,8 +189,8 @@
|
|||
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
|
||||
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
|
||||
|
|
@ -199,7 +203,6 @@
|
|||
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>
|
||||
|
|
@ -215,30 +218,30 @@
|
|||
|
||||
</PRE>
|
||||
<H2>BUG REPORTS</H2><PRE>
|
||||
If something doesn't work, please contact me. But I need some informa-
|
||||
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_PP=255 scanimage -L 2>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.
|
||||
run "SANE_DEBUG_UMAX_PP=255 scanimage -L 2>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
|
||||
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
|
||||
better), or you think I should know something, please include
|
||||
it.
|
||||
|
||||
sane-backends 1.0.13 16 September 2003 <B><A HREF="sane-umax_pp.5.html">sane-umax_pp(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 16 September 2003 <B><A HREF="sane-umax_pp.5.html">sane-umax_pp(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -64,7 +64,8 @@
|
|||
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.13/README.platform files.
|
||||
/usr/local/doc/sane-1.0.14-cvs/README.platform files. The scanner mod-
|
||||
ule is on longer available on Linux 2.6 and later. Use libusb instead.
|
||||
|
||||
Generally speaking, if your scanner works with one method, there is no
|
||||
need to switch to the other one.
|
||||
|
|
@ -102,108 +103,113 @@
|
|||
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:
|
||||
In Linux versions before 2.6 it was 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
|
||||
|
||||
<B>DUE</B> <B>TO</B> <B>A</B> <B>KERNEL</B> <B>BUG</B> <B>THIS</B> <B>WON'T</B> <B>WORK</B> <B>WITH</B> <B>CURRENT</B> <B>2.6</B> <B>KERNELS.</B> <B>USE</B> <B>HOT-</B>
|
||||
<B>PLUG</B> <B>INSTEAD</B>
|
||||
|
||||
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.
|
||||
sions. SANE comes with hotplug scripts in the directory tools/hotplug.
|
||||
They can be used for setting permissions. Last, the frontends can be
|
||||
run as root. However, that's not recommended for security reasons.
|
||||
|
||||
For the <B>BSDs</B>, the device files are named <I>/dev/ugen*</I>. Use chmod to
|
||||
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-
|
||||
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
|
||||
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
|
||||
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
|
||||
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.13/README.openbsd. Similar approaches should be
|
||||
used for the other BSDs.
|
||||
For OpenBSD the kernel may need to be recompiled. For details look at
|
||||
/usr/local/doc/sane-1.0.14-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.
|
||||
Linux kernel messages in syslog like "kernel: scanner.c: open_scan-
|
||||
<B><A HREF="ner.1.html">ner(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
|
||||
This section assumes that your scanner is detected by sane-find-scan-
|
||||
ner. It doesn't make sense to go on, if this is not the case. While
|
||||
sane-find-scanner is able to detect any USB scanner, actual scanning
|
||||
will only work if the scanner is supported by a SANE backend. Informa-
|
||||
tion on the level of support can be found on the SANE webpage
|
||||
(<I>http://www.sane-project.org/</I>), and the individual backend manpages.
|
||||
|
||||
Most backends can detect USB scanners automatically using "usb" config-
|
||||
uration file lines. This method allows to identify scanners by the USB
|
||||
vendor and product numbers. The syntax for specifying a scanner this
|
||||
uration file lines. This method allows to identify scanners by the USB
|
||||
vendor and product numbers. The syntax for specifying a scanner this
|
||||
way is:
|
||||
|
||||
usb <I>VENDOR</I> <I>PRODUCT</I>
|
||||
|
||||
where <I>VENDOR</I> is the USB vendor id, and <I>PRODUCT</I> is the USB product id of
|
||||
the scanner. Both ids are non-negative integer numbers in decimal or
|
||||
the scanner. Both ids are non-negative integer numbers in decimal or
|
||||
hexadecimal format. The correct values for these fields can be found by
|
||||
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
|
||||
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
|
||||
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
|
||||
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:
|
||||
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
|
||||
Do <B>not</B> create a symlink from <I>/dev/scanner</I> to the USB device because
|
||||
this link is used by the SCSI backends. The scanner may be confused if
|
||||
it receives SCSI commands.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_DEBUG_SANEI_USB</B>
|
||||
If the library was compiled with debug support enabled, this
|
||||
environment variable controls the debug level for the USB I/O
|
||||
If the library was compiled with debug support enabled, this
|
||||
environment variable controls the debug level for the USB I/O
|
||||
subsystem. E.g., a value of 128 requests all debug output to be
|
||||
printed. Smaller levels reduce verbosity. Values greater than 4
|
||||
enable libusb debugging (if available). Example: export
|
||||
enable libusb debugging (if available). Example: export
|
||||
SANE_DEBUG_SANEI_USB=4.
|
||||
|
||||
|
||||
|
|
@ -216,7 +222,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
Henning Meier-Geinitz
|
||||
|
||||
sane-backends 1.0.13 27 Nov 2002 <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 8 Mar 2004 <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -105,7 +105,7 @@
|
|||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="xcam.1.html">xcam(1)</A></B>.
|
||||
|
||||
sane-backends 1.0.13 28 Aug 2002 <B><A HREF="sane-v4l.5.html">sane-v4l(5)</A></B>
|
||||
sane-backends 1.0.14-cvs 28 Aug 2002 <B><A HREF="sane-v4l.5.html">sane-v4l(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
256
man/sane.7.html
256
man/sane.7.html
|
|
@ -59,10 +59,10 @@
|
|||
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.13/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.13/</I>) during installation. Everything else is a
|
||||
URL to a resource on the web.
|
||||
`<I>/usr/local/doc/sane-1.0.14-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.14-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
|
||||
|
|
@ -76,30 +76,30 @@
|
|||
CAN YOU HELP SANE for details. There are lists for specific releases
|
||||
of SANE, for the current development version and a search engine:
|
||||
<I>http://www.sane-project.org/sane-supported-devices.html</I>. The lists
|
||||
are also installed on your system at /usr/local/doc/sane-1.0.13/.
|
||||
are also installed on your system at /usr/local/doc/sane-1.0.14-cvs/.
|
||||
|
||||
<B>SANE</B> <B>mailing</B> <B>list</B>
|
||||
There is a mailing list for the purpose of discussing the SANE stan-
|
||||
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 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.sane-project.org/mail-</I>
|
||||
to ask questions that are not strictly related to SANE development.
|
||||
How to subscribe and unsubscribe: <I>http://www.sane-project.org/mail-</I>
|
||||
<I>ing-lists.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.
|
||||
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.13/README</I> and the os-dependent README
|
||||
files for information about compiling and installing <B>SANE.</B>
|
||||
Look at <I>/usr/local/doc/sane-1.0.14-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
|
||||
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>
|
||||
|
|
@ -116,10 +116,10 @@
|
|||
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
|
||||
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>,
|
||||
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.sane-project.org/sane-frontends.html</I>.
|
||||
|
||||
|
|
@ -128,52 +128,52 @@
|
|||
<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,
|
||||
(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
|
||||
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
|
||||
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.
|
||||
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
|
||||
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-
|
||||
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.
|
||||
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.
|
||||
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-
|
||||
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
|
||||
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>
|
||||
|
|
@ -181,7 +181,7 @@
|
|||
<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
|
||||
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>
|
||||
|
|
@ -193,148 +193,143 @@
|
|||
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,
|
||||
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-
|
||||
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
|
||||
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
|
||||
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
|
||||
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
|
||||
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
|
||||
The ma1509 backend supports the Mustek BearPaw 1200F USB flatbed
|
||||
scanner. See <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B> for details.
|
||||
|
||||
<B>matsushita</B>
|
||||
This backend supports some Panasonic KVSS high speed scanners. See
|
||||
This backend supports some Panasonic KVSS high speed scanners. See
|
||||
<B><A HREF="sane-matsushita.5.html">sane-matsushita(5)</A></B> for details.
|
||||
|
||||
<B>microtek</B>
|
||||
The microtek backend provides access to the "second generation"
|
||||
Microtek scanners with SCSI-1 command set. See <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B> for
|
||||
The microtek backend provides access to the "second generation"
|
||||
Microtek scanners with SCSI-1 command set. See <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B> for
|
||||
details.
|
||||
|
||||
<B>microtek2</B>
|
||||
The microtek2 backend provides access to some Microtek scanners with
|
||||
The microtek2 backend provides access to some Microtek scanners with
|
||||
a SCSI-2 command set. See <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B> for details.
|
||||
|
||||
<B>mustek</B>
|
||||
The SANE mustek backend supports most Mustek SCSI flatbed scanners
|
||||
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.
|
||||
The SANE mustek backend supports most Mustek SCSI flatbed scanners
|
||||
including the Paragon and ScanExpress series and the 600 II N and 600
|
||||
II EP (non-SCSI). Some Trust scanners are also supported. See
|
||||
<B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B> for details.
|
||||
|
||||
<B>mustek_pp</B>
|
||||
The mustek_pp backend provides access to Mustek parallel port flatbed
|
||||
scanners with a CIS sensor. See <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B> for details.
|
||||
|
||||
<B>mustek_pp_ccd</B>
|
||||
The mustek_pp_ccd backend provides access to Mustek parallel port
|
||||
flatbed scanners with a CCD sensor. See <B><A HREF="sane-mustek_pp_ccd.5.html">sane-mustek_pp_ccd(5)</A></B> for
|
||||
details.
|
||||
scannersr. 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
|
||||
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)
|
||||
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 USB flatbed scanners that use the
|
||||
The SANE plustek backend supports USB flatbed scanners that use the
|
||||
National Semiconductor LM983[1/2/3]-chipset aka Merlin. Scanners
|
||||
using this LM983x chips include some models from Plustek, KYE/Genius,
|
||||
Hewlett-Packard, Mustek, Umax, Epson, and Canon. See <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
|
||||
Hewlett-Packard, Mustek, Umax, Epson, and Canon. See <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
|
||||
for details.
|
||||
|
||||
<B>plustek_pp</B>
|
||||
The SANE plustek_pp backend supports Plustek parallel port flatbed
|
||||
The SANE plustek_pp backend supports Plustek parallel port flatbed
|
||||
scanners. Scanners using the Plustek ASIC P96001, P96003, P98001 and
|
||||
P98003 include some models from Plustek, KYE/Genius, Primax. See
|
||||
P98003 include some models from Plustek, KYE/Genius, Primax. See
|
||||
<B><A HREF="sane-plustek_pp.5.html">sane-plustek_pp(5)</A></B> for details.
|
||||
|
||||
<B>ricoh</B>
|
||||
The ricoh backend provides access to the following Ricoh flatbed
|
||||
The ricoh backend provides access to the following Ricoh flatbed
|
||||
scanners: IS50 and IS60. See <B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B> for details.
|
||||
|
||||
<B>s9036</B>
|
||||
The s9036 backend provides access to Siemens 9036 flatbed scanners.
|
||||
The s9036 backend provides access to Siemens 9036 flatbed scanners.
|
||||
See <B><A HREF="sane-s9036.5.html">sane-s9036(5)</A></B> for details.
|
||||
|
||||
<B>sceptre</B>
|
||||
The sceptre backend provides access to the Sceptre S1200 flatbed
|
||||
The sceptre backend provides access to the Sceptre S1200 flatbed
|
||||
scanner. See <B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B>
|
||||
for details.
|
||||
|
||||
<B>sharp</B>
|
||||
The SANE sharp backend supports Sharp SCSI scanners. See
|
||||
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
|
||||
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
|
||||
The snapscan backend supports AGFA SnapScan flatbed scanners. See
|
||||
<B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B> for details.
|
||||
|
||||
<B>sp15c</B>
|
||||
This backend supports the Fujitsu FCPA ScanPartner 15C flatbed scan-
|
||||
This backend supports the Fujitsu FCPA ScanPartner 15C flatbed scan-
|
||||
ner. See <B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B> for details.
|
||||
|
||||
<B>st400</B>
|
||||
The sane-st400 backend provides access to Siemens ST400 and ST800.
|
||||
The sane-st400 backend provides access to Siemens ST400 and ST800.
|
||||
See <B><A HREF="sane-st400.5.html">sane-st400(5)</A></B> for details.
|
||||
|
||||
<B>tamarack</B>
|
||||
The SANE tamarack backend supports Tamarack Artiscan flatbed scan-
|
||||
The SANE tamarack backend supports Tamarack Artiscan flatbed scan-
|
||||
ners. See <B><A HREF="sane-tamarack.5.html">sane-tamarack(5)</A></B> for details.
|
||||
|
||||
<B>teco1</B> <B>teco2</B> <B>teco3</B>
|
||||
The SANE teco1, teco2 and teco3 backends support some TECO scanners,
|
||||
The SANE teco1, teco2 and teco3 backends support some TECO scanners,
|
||||
usually sold under the Relisys, Trust, Primax, Piotech, Dextra names.
|
||||
See <B><A HREF="sane-teco1.5.html">sane-teco1(5)</A></B>, <B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B> and <B><A HREF="sane-teco3.5.html">sane-teco3(5)</A></B> for details.
|
||||
|
||||
<B>umax</B>
|
||||
The sane-umax backend provides access to several UMAX-SCSI-scanners
|
||||
The sane-umax backend provides access to several UMAX-SCSI-scanners
|
||||
and some Linotype Hell SCSI-scanners. See <B><A HREF="sane-umax.5.html">sane-umax(5)</A></B> for details.
|
||||
|
||||
<B>umax_pp</B>
|
||||
The sane-umax_pp backend provides access to Umax parallel port
|
||||
The sane-umax_pp backend provides access to Umax parallel port
|
||||
flatbed scanners and the HP 3200C. See <B><A HREF="sane-umax_pp.5.html">sane-umax_pp(5)</A></B> for details.
|
||||
|
||||
<B>umax1200u</B>
|
||||
The sane-umax1220u backend supports the UMAX Astra 1220U (USB)
|
||||
flatbed scanner (and also the UMAX Astra 2000U, sort of). See
|
||||
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
|
||||
Also, have a look at the backend information page at
|
||||
<I>http://www.sane-project.org/sane-supported-devices.html</I> and the list of
|
||||
projects in <I>/usr/local/doc/sane-1.0.13/PROJECTS</I>.
|
||||
projects in <I>/usr/local/doc/sane-1.0.14-cvs/PROJECTS</I>.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -349,91 +344,92 @@
|
|||
Backend for Kodak DC20/DC25 Digital Cameras. See <B><A HREF="sane-dc25.5.html">sane-dc25(5)</A></B>.
|
||||
|
||||
<B>dmc</B>
|
||||
Backend for the Polaroid Digital Microscope Camera. See <B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B>.
|
||||
Backend for the Polaroid Digital Microscope Camera. See <B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B>.
|
||||
|
||||
<B>gphoto2</B>
|
||||
Backend for digital cameras supported by the gphoto2 library package.
|
||||
(See <I>http://www.gphoto.org</I> for more information and a list of sup-
|
||||
ported cameras.) Gphoto2 supports over 140 different camera models.
|
||||
However, please note that more development and testing is needed
|
||||
before all of these cameras will be supported by <B>SANE</B> backend. See
|
||||
<B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>.
|
||||
(See <I>http://www.gphoto.org</I> for more information and a list of
|
||||
supported cameras.) Gphoto2 supports over 140 different camera mod-
|
||||
els. 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
|
||||
Also, have a look at the backend information page at
|
||||
<I>http://www.sane-project.org/sane-supported-devices.html</I> and the list of
|
||||
projects in <I>/usr/local/doc/sane-1.0.13/PROJECTS</I>.
|
||||
projects in <I>/usr/local/doc/sane-1.0.14-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
|
||||
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
|
||||
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-
|
||||
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
|
||||
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
|
||||
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
|
||||
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
|
||||
Also, have a look at the backend information page at
|
||||
<I>http://www.sane-project.org/sane-supported-devices.html</I> and the list of
|
||||
projects in <I>/usr/local/doc/sane-1.0.13/PROJECTS</I>.
|
||||
projects in <I>/usr/local/doc/sane-1.0.14-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
|
||||
By default, all <B>SANE</B> backends (drivers) are loaded dynamically by the
|
||||
<B>sane-dll</B> meta backend. If you have any questions about the dynamic
|
||||
loading, read <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>. <B>SANE</B> frontend can also be linked to other
|
||||
backends directly by copying or linking a backend to <B>libsane.so</B> in
|
||||
<I>/usr/local/lib/sane</I>.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>DEVELOPER'S DOCUMENTATION</H2><PRE>
|
||||
It's not hard to write a <B>SANE</B> backend. It can take some time, however.
|
||||
You should have basic knowledge of C and enough patience to work
|
||||
It's not hard to write a <B>SANE</B> backend. It can take some time, however.
|
||||
You should have basic knowledge of C and enough patience to work
|
||||
through the documentation and find out how your scanner works. Appended
|
||||
is a list of some documents that help to write backends and frontends.
|
||||
is a list of some documents that help to write backends and frontends.
|
||||
|
||||
The <B>SANE</B> standard defines the application programming interface (API)
|
||||
that is used to communicate between frontends and backends. It can be
|
||||
found at <I>/usr/local/doc/sane-1.0.13/sane.ps</I> (if latex is installed on
|
||||
your system) and on the <B>SANE</B> website: <I>http://www.sane-project.org/html/</I>
|
||||
(HTML), or <I>http://www.sane-project.org/sane.ps</I> (Postscript).
|
||||
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.14-cvs/sane.ps</I> (if latex is installed
|
||||
on your system) and on the <B>SANE</B> website:
|
||||
<I>http://www.sane-project.org/html/</I> (HTML), or
|
||||
<I>http://www.sane-project.org/sane.ps</I> (Postscript).
|
||||
|
||||
There is some more information for programmers in
|
||||
<I>/usr/local/doc/sane-1.0.13/backend-writing.txt</I>. Most of the internal
|
||||
<B>SANE</B> routines (<B>sanei</B>) are documented using doxygen: <I>http://www.sane-</I>
|
||||
<I>project.org/sanei/</I>. Before a new backend or frontend project is
|
||||
started, have a look at <I>/usr/local/doc/sane-1.0.13/PROJECTS</I> for
|
||||
projects that are planned or not yet included into the <B>SANE</B> distribu-
|
||||
tion and at our bug-tracking system:
|
||||
<I>http://www.http://www.sane-project.org/bugs.html</I>.
|
||||
<I>/usr/local/doc/sane-1.0.14-cvs/backend-writing.txt</I>. Most of the inter-
|
||||
nal <B>SANE</B> routines (<B>sanei</B>) are documented using doxygen:
|
||||
<I>http://www.sane-project.org/sanei/</I>. Before a new backend or frontend
|
||||
project is started, have a look at
|
||||
<I>/usr/local/doc/sane-1.0.14-cvs/PROJECTS</I> for projects that are planned
|
||||
or not yet included into the <B>SANE</B> distribution and at our bug-tracking
|
||||
system: <I>http://www.http://www.sane-project.org/bugs.html</I>.
|
||||
|
||||
There are some links on how to find out about the protocol of a scan-
|
||||
ner: <I>http://www.meier-geinitz.de/sane/misc/develop.html</I>.
|
||||
|
|
@ -455,7 +451,7 @@
|
|||
The shared libraries implementing the backends (present on sys-
|
||||
tems that support dynamic loading).
|
||||
|
||||
<I>/usr/local/doc/sane-1.0.13/*</I>
|
||||
<I>/usr/local/doc/sane-1.0.14-cvs/*</I>
|
||||
<B>SANE</B> documentation: The standard, READMEs, text files for back-
|
||||
ends etc.
|
||||
|
||||
|
|
@ -545,7 +541,7 @@
|
|||
For reporting bugs or requesting new features, please use our bug-
|
||||
tracking system: <I>http://www.sane-project.org/bugs.html</I>. You can also
|
||||
contact the author of your backend directly. Usually the email address
|
||||
can be found in the <I>/usr/local/doc/sane-1.0.13/AUTHORS</I> file or the
|
||||
can be found in the <I>/usr/local/doc/sane-1.0.14-cvs/AUTHORS</I> file or the
|
||||
backend's manpage. For general discussion about SANE, please use the
|
||||
<B>SANE</B> mailing list sane-devel (see <I>http://www.sane-project.org/mail-</I>
|
||||
<I>ing-lists.html</I> for details).
|
||||
|
|
@ -560,26 +556,26 @@
|
|||
<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_pp_ccd.5.html">sane-mustek_pp_ccd(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-plustek_pp.5.html">sane-plustek_pp(5)</A></B>, <B><A HREF="sane-pnm.5.html">sane-pnm(5)</A></B>, <B><A HREF="sane-qcam.5.html">sane-qcam(5)</A></B>, <B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B>,
|
||||
<B><A HREF="sane-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>
|
||||
<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><A HREF="sane-matsushita.5.html">sane-matsushita(5)</A></B>, <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B>, <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B>,
|
||||
<B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>, <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B><A HREF="sane-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>sane-plus-</B>
|
||||
<B><A HREF="tek_pp.5.html">tek_pp(5)</A></B>, <B><A HREF="sane-pnm.5.html">sane-pnm(5)</A></B>, <B><A HREF="sane-qcam.5.html">sane-qcam(5)</A></B>, <B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B>, <B><A HREF="sane-s9036.5.html">sane-s9036(5)</A></B>,
|
||||
<B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B>, <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B>,
|
||||
<B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B>, <B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B>, <B><A HREF="sane-st400.5.html">sane-st400(5)</A></B>, <B><A HREF="sane-tamarack.5.html">sane-tamarack(5)</A></B>,
|
||||
<B><A HREF="sane-teco1.5.html">sane-teco1(5)</A></B>, <B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B>, <B><A HREF="sane-teco3.5.html">sane-teco3(5)</A></B>, <B><A HREF="sane-test.5.html">sane-test(5)</A></B>, <B><A HREF="sane-u12.5.html">sane-u12(5)</A></B>,
|
||||
<B><A HREF="sane-umax1220u.5.html">sane-umax1220u(5)</A></B>, <B><A HREF="sane-umax.5.html">sane-umax(5)</A></B>, <B><A HREF="sane-umax_pp.5.html">sane-umax_pp(5)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>,
|
||||
<B><A HREF="sane-v4l.5.html">sane-v4l(5)</A></B>
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>AUTHOR</H2><PRE>
|
||||
David Mosberger-Tang and many many more (see
|
||||
<I>/usr/local/doc/sane-1.0.13/AUTHORS</I> for details). This man page was
|
||||
<I>/usr/local/doc/sane-1.0.14-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.13 3 Oct 2003 <B><A HREF="sane.7.html">sane(7)</A></B>
|
||||
sane-backends 1.0.14-cvs 06 Jan 2004 <B><A HREF="sane.7.html">sane(7)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -175,7 +175,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
David Mosberger
|
||||
|
||||
sane-backends 1.0.13 29 Oct 2003 <B><A HREF="saned.1.html">saned(1)</A></B>
|
||||
sane-backends 1.0.14-cvs 29 Oct 2003 <B><A HREF="saned.1.html">saned(1)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -109,7 +109,9 @@
|
|||
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.
|
||||
increment to 2. <B>--batch-prompt</B> will ask for pressing RETURN before
|
||||
scanning a page. This can be used for scanning multiple pages without
|
||||
an automatic document feeder.
|
||||
|
||||
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
|
||||
|
|
@ -142,8 +144,8 @@
|
|||
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:
|
||||
To see the options for a device named <I>dev</I>, invoke <B>scanimage</B> via a
|
||||
command-line of the form:
|
||||
|
||||
<B>scanimage</B> <B>--help</B> <B>--device-name</B> <I>dev</I>
|
||||
|
||||
|
|
@ -272,7 +274,7 @@
|
|||
For vector options, the help output currently has no indication as to
|
||||
how many elements a vector-value should have.
|
||||
|
||||
sane-backends 1.0.13 15 Apr 2003 <B><A HREF="scanimage.1.html">scanimage(1)</A></B>
|
||||
sane-backends 1.0.14-cvs 22 Feb 2004 <B><A HREF="scanimage.1.html">scanimage(1)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
Ładowanie…
Reference in New Issue