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

Updated website for release of sane-backends 1.0.13.

merge-requests/1/head
Henning Geinitz 2003-11-23 12:03:17 +00:00
rodzic b3afa424d7
commit 033604abdf
74 zmienionych plików z 10690 dodań i 3874 usunięć
Pokaż statystyki Ściągnij plik aktualizacji Ściągnij plik porównania Expand all files Collapse all files

85
index.html
Wyświetl plik

@ -37,67 +37,42 @@
<h3>Latest News</h3>
<p>
<strong>2003-11-17:</strong> The <a
href="ftp://ftp.mostang.com/pub/sane/sane-backends-1.0.13-pre3.tar.gz">third
pre-release of sane-backends 1.0.13</a> is now available. Please
test and send any bug reports to our <a href="bugs.html">bug
tracking system</a>.
</p>
<p>
<strong>2003-10-10:</strong> This is the timetable for the next
release of sane-backends (1.0.13):<br>
2003-10-25 backend freeze<br>
2003-11-01 feature freeze<br>
2003-11-15 code freeze<br>
2003-11-22 release
</p>
<p>
<strong>2003-09-23:</strong> The new <a href="/">SANE homepage</a> at
http://www.sane-project.org is online
</p>
<p>
<strong>2003-09-19:</strong> There is a <a href="bugs.html">bug
tracking system</a> for SANE now. Please use it for reporting
any bug in SANE or the web pages.
</p>
<p>
<strong>2003-09-18:</strong> A new <a href="cvs.html">development CVS server</a> is
available. Also the <a href="mailing-lists.html">sane-devel mailing list</a> was moved
and two more lists have been created.
</p>
<p>
<strong>2003-05-25:</strong> <a href="source.html">SANE-Backends-1.0.12</a> has been
<strong>2003-11-23:</strong> <a href="source.html">SANE-Backends-1.0.13</a> has been
released
</p>
<ul>
<li>Documentation updates</li>
<li>Updated backends: apple, artec_eplus48u, as6e, avision, canon,
canon630u, dc210, dc240, dll, epson, fujitsu (fi4220), gphoto2, gt68xx,
hp, mustek, mustek_pp, mustek_usb, net, pie, plustek, snapscan,
teco2, test, umax, umax_pp</li>
<li>New backends: hp5400, ibm, ma1509</li>
<li>Added IPv6 support for saned and net backend</li>
<li>Added SCSI support for MacOS X</li>
<li>Build system improvements</li>
<li>USB access improvements</li>
<li>Portability fixes</li>
<li>Translation updates and new translations: nl, no</li>
<li>Bugfixes</li>
<li>
New backends: mustek_pp_ccd and plustek_pp (both splitted from
existing backends)
</li>
<li>
Updated backends: avision, canon630u, coolscan, epson, fujitsu,
gphoto2, gt68xx, hp, hp5400, mustek, mustek_pp, pie, plustek,
snapscan, teco2, test, umax, umax_pp.
</li>
<li>
Build system improvements
</li>
<li>
Portability updates including port to MS Windows (Cygwin)
</li>
<li>
Networking (IPv6, subnetting) updates
</li>
<li>
Translation updates and new translations: Bulgarian, Czech and Italian
</li>
<li>
Documentation updates
</li>
<li>
Bugfixes
</li>
</ul>
<p>
<strong>2003-05-24:</strong> Frank Zago is working on <a
href="http://www.zago.net/sane/windows/sane_on_windows.html">sane-backends
for MS Windows</a> for SCSI scanners.
</p>
<p>
<strong>2003-05-11:</strong>
<a href="http://www.xsane.org">XSane-0.91</a> released.
</p>
<p>
<strong>2003-04-26:</strong> <a href="source.html">SANE-Frontends-1.0.11</a> has been
released
<strong>2003-09-23:</strong> The new <a href="/">SANE homepage</a> at
http://www.sane-project.org is online
</p>
</td>

2
man/gamma4scanimage.1.html
Wyświetl plik

@ -71,7 +71,7 @@
<H2>EMAIL-CONTACT</H2><PRE>
Oliver.Rauch@Rauch-Domain.DE
sane-backends 1.0.12-cvs 11 Sep 2002 <B><A HREF="gamma4scanimage.1.html">gamma4scanimage(1)</A></B>
sane-backends 1.0.13 11 Sep 2002 <B><A HREF="gamma4scanimage.1.html">gamma4scanimage(1)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -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.12-cvs 19 Nov 1998 <B><A HREF="sane-abaton.5.html">sane-abaton(5)</A></B>
sane-backends 1.0.13 19 Nov 1998 <B><A HREF="sane-abaton.5.html">sane-abaton(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -178,7 +178,7 @@
<H2>AUTHOR</H2><PRE>
Ingo Schneider and Karl Anders Øygard.
sane-backends 1.0.12-cvs 17 Oct 1998 <B><A HREF="sane-agfafocus.5.html">sane-agfafocus(5)</A></B>
sane-backends 1.0.13 17 Oct 1998 <B><A HREF="sane-agfafocus.5.html">sane-agfafocus(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -283,7 +283,7 @@
Firikis. It is mostly based on the mustek backend from David Mosberger
and Andreas Czechanowski
sane-backends 1.0.12-cvs 13 May 1998 <B><A HREF="sane-apple.5.html">sane-apple(5)</A></B>
sane-backends 1.0.13 13 May 1998 <B><A HREF="sane-apple.5.html">sane-apple(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -170,9 +170,9 @@
</PRE>
<H2>AUTHOR</H2><PRE>
Chris Pinkham (cpinkham@infi.net) (does not exist anymore?)
Chris Pinkham (cpinkham@corp.infi.net)
sane-backends 1.0.12-cvs 24 Jan 2000 <B><A HREF="sane-artec.5.html">sane-artec(5)</A></B>
sane-backends 1.0.13 24 Jan 2000 <B><A HREF="sane-artec.5.html">sane-artec(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -187,7 +187,7 @@
<I>http://www.angelfire.com/linux/crapsite</I>. Please contact me if you find
a bug or missing feature: &lt;crapsite@gmx.net&gt;
sane-backends 1.0.12-cvs 19 Nov 2002 <B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B>
sane-backends 1.0.13 19 Nov 2002 <B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -50,7 +50,7 @@
<H2>EMAIL-CONTACT</H2><PRE>
yossarian@users.sourceforge.net
sane-backends 1.0.12-cvs Apr 2nd, 2003 <B><A HREF="sane-as6e.5.html">sane-as6e(5)</A></B>
sane-backends 1.0.13 Apr 2nd, 2003 <B><A HREF="sane-as6e.5.html">sane-as6e(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -13,20 +13,25 @@
</PRE>
<H2>NAME</H2><PRE>
sane-avision - SANE backend for original Avision and Avision OEM scan-
ners (HP, Minolta, Mitsubishi, UMAX and possibly more) flatbed scanners
ners (HP, Minolta, Mitsubishi, UMAX and possibly more) flatbed scan-
ners.
</PRE>
<H2>ABOUT THIS FILE</H2><PRE>
This file only is a short descripton of the avision-backend for sane!
This file is a short descripton for the avision-backend shipped with
SANE.
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-avision</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to various Avision scanners and the Avi-
The <B>sane-avision</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to various Avision scanners and the Avi-
sion OEM scanners labelled by HP, Minolta, Mitsubishi or Fujitsu.
<B>I</B> <B>suggest</B> <B>you</B> <B>hold</B> <B>one</B> <B>hand</B> <B>on</B> <B>the</B> <B>power-button</B> <B>of</B> <B>the</B> <B>scanner</B> <B>while</B>
<B>you</B> <B>try</B> the first scans!
</PRE>
<H2>CONFIGURATION</H2><PRE>
@ -38,9 +43,6 @@
starting with a hash mark (#) are ignored. A sample configuration file
is shown below:
<B>I</B> <B>suggest</B> <B>you</B> <B>hold</B> <B>one</B> <B>hand</B> <B>on</B> <B>the</B> <B>power-button</B> <B>of</B> <B>the</B> <B>scanner</B> <B>while</B>
<B>you</B> <B>try</B> the first scans!
# this is a comment
option force-a4
@ -96,29 +98,38 @@
<H2>DEVICE NAMES</H2><PRE>
This backend expects device names of the form:
<I>scsi</I> <I>special</I> <I>usb</I> <I>special</I>
<I>scsi</I> <I>scsi-spec</I>
Where <I>special</I> is the path-name for the device that corresponds to a
SCSI scanner or the USB vendor/product ID pair corresponding to the USB
scanner. The special device name must be a generic SCSI device or a
symlink to such a device. The program <I>sane-find-scanner</I> helps to find
out the correct device. Under Linux, such a device name could be
<I>/dev/sg0</I> or <I>/dev/sga</I>, for example. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details.
<I>usb</I> <I>usb-sec</I>
Where <I>scsi-spec</I> is the path-name to a special device or a device ID for
the device that corresponds to a SCSI scanner. The special device name
must be a generic SCSI device or a symlink to such a device, for exam-
ple on Linux "/dev/sga" or "/dev/sg0". The device ID is the ID returned
by the scanner, for example "HP" or "AVISION". See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for
details.
Note: Since the backend now includes native USB access,
it is no longer needed - even considered obsolete -
to access the scanner via the SCSI emulation (named
to access USB scanner via the SCSI emulation (named
hpusbscsi on Linux) for Avision USB devices such as
the HP 53xx, HP 74xx or Minolta film-scanners.
A list with supported devices is built into the avision backend so
normally specifying an ID should not be necessary.
<I>usb-spec</I> is the USB device name, the vendor/product ID pair or the name
used by libusb corresponding to the USB scanner. For example "0x03f0
0x0701" or "libusb:002:003". See <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B> for details.
The program <I>sane-find-scanner</I> helps to find out the correct scsi or usb
device name.
A list with supported devices is built into the avision backend so nor-
mally specifying an ID should not be necessary.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/avision.conf</I>
The backend configuration file (see also description of
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-avision.a</I>
@ -134,22 +145,22 @@
<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_AVISION</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output. The
debug level 7 is the author's prefered value to debug backend
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output. The
debug level 7 is the author's prefered value to debug backend
problems.
Example: export SANE_DEBUG_AVISION=7
@ -157,15 +168,15 @@
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>
http://drocklinux.dyndns.org/rene/avision/index.html
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>
http://www.rocklinux-consulting.de/oss/avision/
</PRE>
<H2>AUTHOR</H2><PRE>
René Rebe and Meino Christian Cramer
sane-backends 1.0.12-cvs 04 Mar 2003 <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B>
sane-backends 1.0.13 04 Mar 2003 <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -502,7 +502,7 @@
Reifschneider of tummy.com ltd. Some 8000 enhancements added by Mark
Temple.
sane-backends 1.0.12-cvs 15 Sep 1999 <B><A HREF="sane-bh.5.html">sane-bh(5)</A></B>
sane-backends 1.0.13 15 Sep 1999 <B><A HREF="sane-bh.5.html">sane-bh(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -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.12-cvs 03 May 2001 <B><A HREF="sane-canon.5.html">sane-canon(5)</A></B>
sane-backends 1.0.13 03 May 2001 <B><A HREF="sane-canon.5.html">sane-canon(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -124,7 +124,7 @@
<H2>AUTHOR</H2><PRE>
Nathan Rutman
sane-backends 1.0.12-cvs 06 Apr 2002 <B><A HREF="sane-canon630u.5.html">sane-canon630u(5)</A></B>
sane-backends 1.0.13 06 Apr 2002 <B><A HREF="sane-canon630u.5.html">sane-canon630u(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -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.12-cvs 1 October 2002 <B><A HREF="sane-canon_pp.5.html">sane-canon_pp(5)</A></B>
sane-backends 1.0.13 1 October 2002 <B><A HREF="sane-canon_pp.5.html">sane-canon_pp(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -68,7 +68,7 @@
This manual page was written by Julien BLACHE &lt;jblache@debian.org&gt;, for
the Debian GNU/Linux system (but may be used by others).
sane-backends 1.0.12-cvs 15 October 2002 <B><A HREF="sane-config.1.html">sane-config(1)</A></B>
sane-backends 1.0.13 15 October 2002 <B><A HREF="sane-config.1.html">sane-config(1)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -122,7 +122,7 @@
<H2>EMAIL-CONTACT</H2><PRE>
andreas.rick@free.fr
sane-backends 1.0.12-cvs 4 July 2000 <B><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B>
sane-backends 1.0.13 4 July 2000 <B><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -192,7 +192,7 @@
The backend is written and maintained by András Major
(andras@users.sourceforge.net).
sane-backends 1.0.12-cvs 22/08/2002 <B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B>
sane-backends 1.0.13 22/08/2002 <B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -123,7 +123,7 @@
be subscribed to the list, otherwise your mail won't be sent to the
subscribers.
sane-backends 1.0.12-cvs 15 July 2000 <B><A HREF="sane-dc210.5.html">sane-dc210(5)</A></B>
sane-backends 1.0.13 15 July 2000 <B><A HREF="sane-dc210.5.html">sane-dc210(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -126,7 +126,7 @@
be subscribed to the list, otherwise your mail won't be sent to the
subscribers.
sane-backends 1.0.12-cvs 23 March 2001 <B><A HREF="sane-dc240.5.html">sane-dc240(5)</A></B>
sane-backends 1.0.13 23 March 2001 <B><A HREF="sane-dc240.5.html">sane-dc240(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -116,7 +116,7 @@
be subscribed to the list, otherwise your mail won't be sent to the
subscribers.
sane-backends 1.0.12-cvs 12 April 1999 <B><A HREF="sane-dc25.5.html">sane-dc25(5)</A></B>
sane-backends 1.0.13 12 April 1999 <B><A HREF="sane-dc25.5.html">sane-dc25(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -148,7 +148,7 @@
<H2>AUTHOR</H2><PRE>
David Mosberger
sane-backends 1.0.12-cvs 4 Dec 2002 <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>
sane-backends 1.0.13 4 Dec 2002 <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -159,7 +159,7 @@
The backend is derived from <B>sane-hp</B> by David Mosberger
sane-backends 1.0.12-cvs 13 May 1998 <B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B>
sane-backends 1.0.13 13 May 1998 <B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -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.12-cvs 27-Dec-2000 <B><A HREF="sane-epson.5.html">sane-epson(5)</A></B>
sane-backends 1.0.13 27-Dec-2000 <B><A HREF="sane-epson.5.html">sane-epson(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -106,7 +106,7 @@
Detection of USB chipsets is limited to GrandTech 6801 and 6816, Mustek
chips and National Semiconductor lm983x chips.
sane-backends 1.0.12-cvs 18 Jul 2003 <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>
sane-backends 1.0.13 18 Jul 2003 <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -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.12-cvs 17 Apr 2002 <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>
sane-backends 1.0.13 17 Apr 2002 <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -131,7 +131,7 @@
be subscribed to the list, otherwise your mail won't be sent to the
subscribers.
sane-backends 1.0.12-cvs 04 September 2001 <B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>
sane-backends 1.0.13 04 September 2001 <B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -197,7 +197,7 @@
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B> <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>,
<B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>, <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>
<I>/usr/local/doc/sane-1.0.12-cvs/gt68xx/gt68xx.CHANGES</I>
<I>/usr/local/doc/sane-1.0.13/gt68xx/gt68xx.CHANGES</I>
<I>http://www.meier-geinitz.de/sane/gt68xx</I>
@ -228,7 +228,7 @@
a debug log if your scanner isn't detected correctly (see
SANE_DEBUG_GT68XX above).
sane-backends 1.0.12-cvs 30 Sept 2003 <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>
sane-backends 1.0.13 30 Sept 2003 <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -242,7 +242,7 @@
The sane-hp backend was written by Geoffrey T. Dairiki. HP PhotoSmart
PhotoScanner support by Peter Kirchgessner.
sane-backends 1.0.12-cvs 09 Oct 2003 <B><A HREF="sane-hp.5.html">sane-hp(5)</A></B>
sane-backends 1.0.13 09 Oct 2003 <B><A HREF="sane-hp.5.html">sane-hp(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -110,7 +110,7 @@
other operating systems and especially on big-endian platforms. The
scanner may get wrong data.
sane-backends 1.0.12-cvs 17 Apr 2003 <B><A HREF="sane-hp5400.5.html">sane-hp5400(5)</A></B>
sane-backends 1.0.13 17 Apr 2003 <B><A HREF="sane-hp5400.5.html">sane-hp5400(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -111,7 +111,7 @@
Max Vorobiev
Man page mostly based on canon.man
sane-backends 1.0.12-cvs 24 Feb 2002 <B><A HREF="sane-hpsj5s.5.html">sane-hpsj5s(5)</A></B>
sane-backends 1.0.13 24 Feb 2002 <B><A HREF="sane-hpsj5s.5.html">sane-hpsj5s(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -94,7 +94,7 @@
mf &lt;massifr@tiscalinet.it&gt;
Maintained by Henning Meier-Geinitz &lt;henning@meier-geinitz.de&gt;
sane-backends 1.0.12-cvs 15 Apr 2003 <B><A HREF="sane-ibm.5.html">sane-ibm(5)</A></B>
sane-backends 1.0.13 15 Apr 2003 <B><A HREF="sane-ibm.5.html">sane-ibm(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -132,9 +132,9 @@
</PRE>
<H2>AUTHOR</H2><PRE>
The package is actively maintained by Frank Zago.
http://fz.eryx.net/sane/#leo
http://www.zago.net/sane/#leo
sane-backends 1.0.12-cvs 16 April 2002 <B><A HREF="sane-leo.5.html">sane-leo(5)</A></B>
sane-backends 1.0.13 16 April 2002 <B><A HREF="sane-leo.5.html">sane-leo(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -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.12-cvs 24 Feb 2003 <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>
sane-backends 1.0.13 24 Feb 2003 <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -173,9 +173,9 @@
</PRE>
<H2>AUTHOR</H2><PRE>
The package is actively maintained by Frank Zago.
http://fz.eryx.net/sane/#matsushita
http://www.zago.net/sane/#matsushita
sane-backends 1.0.12-cvs April 21s, 2002 <B><A HREF="sane-matsushita.5.html">sane-matsushita(5)</A></B>
sane-backends 1.0.13 April 21s, 2002 <B><A HREF="sane-matsushita.5.html">sane-matsushita(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -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.12-cvs February 8, 2000 <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B>
sane-backends 1.0.13 February 8, 2000 <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -283,7 +283,7 @@
Karsten Festag karsten.festag@gmx.de
sane-backends 1.0.12-cvs 28 Jan 2002 <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B>
sane-backends 1.0.13 28 Jan 2002 <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -67,7 +67,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.12-cvs/PROBLEMS</I> file.
the <I>/usr/local/doc/sane-1.0.13/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-
@ -314,7 +314,7 @@
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B>sane-</B>
<B><A HREF="gt68xx.5.html">gt68xx(5)</A></B>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>
<I>/usr/local/doc/sane-1.0.12-cvs/mustek/mustek.CHANGES</I>
<I>/usr/local/doc/sane-1.0.13/mustek/mustek.CHANGES</I>
<I>http://www.meier-geinitz.de/sane/mustek-backend/</I>
@ -337,7 +337,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.12-cvs 5 Dec 2002 <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>
sane-backends 1.0.13 5 Dec 2002 <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -106,25 +106,30 @@
A device can be defined as follows:
<I>scanner</I> <I>&lt;name&gt;</I> <I>&lt;address&gt;</I> <I>&lt;driver&gt;</I>
<I>scanner</I> <I>&lt;name&gt;</I> <I>&lt;port</I> <I>name&gt;</I> <I>&lt;driver&gt;</I>
where
<B>&lt;name&gt;</B> is an arbitrary name for the device, optionally enclosed by dou-
ble quotes, for instance "LifeTec 9350".
<B>&lt;address&gt;</B> is the port address of the parallel port to which the device
is connected. Known ports are <B>0x378,</B> <B>0x278,</B> and <B>0x3BC</B>. The
mapping of parallel ports (lp0, lp1, and lp2) to these addresses
can be different for different Linux kernel versions. For
instance, if you are using a Kernel 2.2.x or better and you have
only one parallel port, this port is named lp0 regardless of the
base address. However, this backend requires the base address of
your port. If you are not sure which port your scanner is con-
nected to, have a look at your /etc/conf.modules, /etc/mod-
ules.conf and/or /proc/ioports.
<B>&lt;port</B> <B>name&gt;</B> is the name of the parallel port to which the device is
connected. In case libieee1284 is used for communication with
the port <I>(default</I> <I>setup)</I>, valid port names are <B>parport0</B>, <B>par-</B>
<B>port1</B>, and <B>parport2</B>.
<B>&lt;driver&gt;</B> is the driver to use for this device. Currently available
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
your scanner is connected to, have a look at your /etc/conf.mod-
ules, /etc/modules.conf and/or /proc/ioports.
<B>&lt;driver&gt;</B> is the driver to use for this device. Currently available
drivers are:
<B>cis600</B> : for 600 CP, 96 CP &amp; OEM versions
@ -133,16 +138,16 @@
<B>Choosing</B> <B>the</B> <B>wrong</B> <B>driver</B> <B>can</B> <B>damage</B> <B>your</B> <B>scanner!</B>
Especially, using the 1200CP settings on a 600CP can be harmful.
If the scanner starts making a loud noice, turn it off
immediately !!!
If the scanner starts making a loud noice, turn it off immedi-
ately !!!
Using the cis600 driver on a 1200CP or a 1200CP+ is probably not
dangerous. The cis1200+ driver also works for the 1200CP, and
using the cis1200 driver on a 1200CP+ will typically result in
scans that cover only half of the width of the scan area (also
dangerous. The cis1200+ driver also works for the 1200CP, and
using the cis1200 driver on a 1200CP+ will typically result in
scans that cover only half of the width of the scan area (also
not dangerous).
If unsure about the exact model of your OEM version, check the
optical resolution in the manual or on the box: the 600CP has a
maximum optical resolution of 300x600 DPI, whereas the 1200CP
If unsure about the exact model of your OEM version, check the
optical resolution in the manual or on the box: the 600CP has a
maximum optical resolution of 300x600 DPI, whereas the 1200CP
and 1200CP+ have a maximum optical resolution of 600x1200 DPI.
Examples:
@ -156,20 +161,20 @@
<H2>CONFIGURATION</H2><PRE>
The contents of the <B>mustek_pp.conf</B> file is a list of device definitions
and device options that correspond to Mustek scanners. Empty lines and
lines starting with a hash mark (#) are ignored. Options have the fol-
lines starting with a hash mark (#) are ignored. Options have the fol-
lowing format:
<I>option</I> <I>&lt;name&gt;</I> <I>[&lt;value&gt;]</I>
Depending on the nature of the option, a value may or may not be
present. Options always apply to the scanner definition that preceeds
them. There are no global options. Options are also driver-specific:
Depending on the nature of the option, a value may or may not be
present. Options always apply to the scanner definition that preceeds
them. There are no global options. Options are also driver-specific:
not all drivers support all possible options.
<B>Common</B> <B>options</B>
<B>bw</B> <B>&lt;value&gt;</B> Black/white discrimination value to be used during lin-
eart scanning. Pixel values below this value are assumed to
<B>bw</B> <B>&lt;value&gt;</B> Black/white discrimination value to be used during lin-
eart scanning. Pixel values below this value are assumed to
be black, values above are assumed to be white.
Default value: 127
Minimum: 0
@ -179,12 +184,12 @@
<B>CIS</B> <B>driver</B> <B>options</B>
<B>top_adjust</B> <B>&lt;value&gt;</B> Vertical adjustment of the origin, expressed in
millimeter (floating point). This option can be used to
<B>top_adjust</B> <B>&lt;value&gt;</B> Vertical adjustment of the origin, expressed in
millimeter (floating point). This option can be used to
calibrate the position of the origin, within certain limits.
Note that CIS scanners are probably temperature sensitive,
and that a certain inaccuracy may be hard to avoid. Differ-
ences in offset between runs in the order of 1 to 2 mm are
Note that CIS scanners are probably temperature sensitive,
and that a certain inaccuracy may be hard to avoid. Differ-
ences in offset between runs in the order of 1 to 2 mm are
not unusual.
Default value: 0.0
Minimum: -5.0
@ -192,14 +197,14 @@
Example: option top_skip -2.5
<B>slow_skip</B> Turns fast skipping to the start of the scan region off.
When the region to scan does not start at the origin, the
driver will try to move the scanhead to the start of the
scan area at the fastest possible speed. On some models,
this may not work, resulting in large inaccuracies (up to
centimeters). By setting this option, the driver is forced
to use normal speed during skipping, which can circumvent
the accuracy problems. Currently, there are no models for
<B>slow_skip</B> Turns fast skipping to the start of the scan region off.
When the region to scan does not start at the origin, the
driver will try to move the scanhead to the start of the
scan area at the fastest possible speed. On some models,
this may not work, resulting in large inaccuracies (up to
centimeters). By setting this option, the driver is forced
to use normal speed during skipping, which can circumvent
the accuracy problems. Currently, there are no models for
which these inaccuracy problems are known to occur.
By default, fast skipping is used.
@ -242,7 +247,7 @@
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/mustek</I><B>_</B><I>pp.conf</I>
The backend configuration file (see also description of
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-mustek</I><B>_</B><I>pp.a</I>
@ -258,21 +263,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
by a semi-colon (`;'). If this variable is not set, the
configuration file is searched in two default directories:
first, the current working directory (".") and then in
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
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_MUSTEK_PP</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend.
E.g., a value of 128 requests all debug output to be printed.
If the library was compiled with debug support enabled, this
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
@ -286,8 +291,8 @@
6 special debug information
<B>SANE_DEBUG_SANEI_PA4S2</B>
This variable sets the debug level for the SANE interface for
the Mustek chipset A4S2. Note that enabling this will spam your
This variable sets the debug level for the SANE interface for
the Mustek chipset A4S2. Note that enabling this will spam your
terminal with some million lines of debug output.
level debug output
@ -320,9 +325,9 @@
</PRE>
<H2>BUGS</H2><PRE>
Too many... please send bug reports to
<I>sane-devel@lists.alioth.debian.org</I> (note that you have to subscribe
first to the list before you can send emails... see
Too many... please send bug reports to
<I>sane-devel@lists.alioth.debian.org</I> (note that you have to subscribe
first to the list before you can send emails... see
http://www.sane-project.org/mailing-lists.html)
* 1013 support isn't bullet proofed
@ -332,29 +337,29 @@
</PRE>
<H2>BUG REPORTS</H2><PRE>
If something doesn't work, please contact us (Jochen for the CCD scan-
ners, Eddy for the CIS scanners). But we need some information about
If something doesn't work, please contact us (Jochen for the CCD scan-
ners, Eddy for the CIS scanners). But we need some information about
your scanner to be able to help you...
<I>SANE</I> <I>version</I>
run "scanimage -V" to determine this
<I>the</I> <I>backend</I> <I>version</I> <I>and</I> <I>your</I> <I>scanner</I> <I>hardware</I>
run "SANE_DEBUG_MUSTEK_PP=128 scanimage -L" as root. If you
don't get any output from the mustek_pp backend, make sure a
line "mustek_pp" is included into your
run "SANE_DEBUG_MUSTEK_PP=128 scanimage -L" as root. If you
don't get any output from the mustek_pp backend, make sure a
line "mustek_pp" is included into your
/usr/local/etc/sane.d/dll.conf. If your scanner isn't detected,
make sure you've defined the right port address in your
mustek_pp.conf.
<I>the</I> <I>name</I> <I>of</I> <I>your</I> <I>scanner/vendor</I>
also a worthy information. Please also include the optical reso-
lution and lamp type of your scanner, both can be found in the
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.
<I>some</I> <I>nice</I> <I>greetings</I>

2
man/sane-mustek_pp_ccd.5.html
Wyświetl plik

@ -337,7 +337,7 @@
<I>some</I> <I>nice</I> <I>greetings</I>
sane-backends 1.0.12-cvs 3 Oct 2003 <B><A HREF="sane-mustek_pp_ccd.5.html">sane-mustek_pp_ccd(5)</A></B>
sane-backends 1.0.13 3 Oct 2003 <B><A HREF="sane-mustek_pp_ccd.5.html">sane-mustek_pp_ccd(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -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.12-cvs/mustek</I><B>_</B><I>usb/mustek</I><B>_</B><I>usb.CHANGES</I>,
<I>/usr/local/doc/sane-1.0.12-cvs/mustek</I><B>_</B><I>usb/mustek</I><B>_</B><I>usb.TODO</I>
<I>/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>http://www.meier-geinitz.de/sane/mustek</I><B>_</B><I>usb-backend/</I>
@ -170,12 +170,14 @@
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.
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.
More detailed bug information is available at the Mustek backend home-
page <I>http://www.meier-geinitz.de/sane/mustek</I><B>_</B><I>usb-backend/</I>.
sane-backends 1.0.12-cvs 09 Jan 2003 <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>
sane-backends 1.0.13 21 Oct 2003 <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -67,7 +67,7 @@
<H2>AUTHORS</H2><PRE>
Kazuya Fukuda
sane-backends 1.0.12-cvs 17 Feb 2000 <B><A HREF="sane-nec.5.html">sane-nec(5)</A></B>
sane-backends 1.0.13 17 Feb 2000 <B><A HREF="sane-nec.5.html">sane-nec(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -131,7 +131,7 @@
<H2>AUTHOR</H2><PRE>
David Mosberger and Andreas Beck
sane-backends 1.0.12-cvs 8 Oct 2002 <B><A HREF="sane-net.5.html">sane-net(5)</A></B>
sane-backends 1.0.13 8 Oct 2002 <B><A HREF="sane-net.5.html">sane-net(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -66,7 +66,7 @@
Please send any information and bug-reports to:
<B>Simon</B> <B>Munton</B> <B>&lt;simon@munton.demon.co.uk&gt;</B>
sane-backends 1.0.12-cvs 7 Sept 2000 <B><A HREF="sane-pie.5.html">sane-pie(5)</A></B>
sane-backends 1.0.13 7 Sept 2000 <B><A HREF="sane-pie.5.html">sane-pie(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -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.12-cvs 13 May 1998 <B><A HREF="sane-pint.5.html">sane-pint(5)</A></B>
sane-backends 1.0.13 13 May 1998 <B><A HREF="sane-pint.5.html">sane-pint(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -123,14 +123,14 @@
the configuration file
<I>/usr/local/etc/sane.d/plustek.conf</I>
<I>[merlin-device]</I> <I>vendor-id</I> <I>product-id</I>
<I>[usb]</I> <I>vendor-id</I> <I>product-id</I>
<I>device</I> <I>/dev/usbscanner</I>
<I>merlin-device</I> tells the backend, that the following devicename (here
<I>/dev/usbscanner</I> ) has to be interpreted as USB scanner device. If ven-
dor- and product-id has not been specified, the backend tries to detect
this by its own. If device ist set to <I>auto</I>
<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>
@ -282,7 +282,7 @@
the one your device has.
* Negative/Slide scanning quality is poor.
sane-backends 1.0.12-cvs 28 September 2003 <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
sane-backends 1.0.13 27 October 2003 <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -296,7 +296,7 @@
* The scanspeed on 600x1200 dpi models is slow.
* The scanquality of the A3I is poor
sane-backends 1.0.12-cvs 24 September 2003 <B><A HREF="sane-plustek_pp.5.html">sane-plustek_pp(5)</A></B>
sane-backends 1.0.13 24 September 2003 <B><A HREF="sane-plustek_pp.5.html">sane-plustek_pp(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -74,7 +74,7 @@
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>
sane-backends 1.0.12-cvs 22 April 2001 <B><A HREF="sane-pnm.5.html">sane-pnm(5)</A></B>
sane-backends 1.0.13 22 April 2001 <B><A HREF="sane-pnm.5.html">sane-pnm(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -109,7 +109,7 @@
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>
sane-backends 1.0.12-cvs 25 October 1997 <B><A HREF="sane-qcam.5.html">sane-qcam(5)</A></B>
sane-backends 1.0.13 25 October 1997 <B><A HREF="sane-qcam.5.html">sane-qcam(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -85,7 +85,7 @@
<H2>AUTHOR</H2><PRE>
Feico W. Dillema
sane-backends 1.0.12-cvs 24 Jun 2000 <B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B>
sane-backends 1.0.13 24 Jun 2000 <B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -83,7 +83,7 @@
Ingo Schneider
sane-backends 1.0.12-cvs 24 Jun 2000 <B><A HREF="sane-s9036.5.html">sane-s9036(5)</A></B>
sane-backends 1.0.13 24 Jun 2000 <B><A HREF="sane-s9036.5.html">sane-s9036(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -145,9 +145,9 @@
</PRE>
<H2>AUTHOR</H2><PRE>
The package is actively maintained by Frank Zago.
http://fz.eryx.net/sane/#sceptre
http://www.zago.net/sane/#sceptre
sane-backends 1.0.12-cvs April 21st, 2002 <B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B>
sane-backends 1.0.13 April 21st, 2002 <B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -109,157 +109,159 @@
</PRE>
<H2>FREEBSD INFO</H2><PRE>
Auto-configuration using the "scsi *" lines in the config files doesn't
seem to work. Set a link <I>/dev/scanner</I> to the appropriate /dev/uk
device.
Auto-configuration using the "scsi *" lines in the config files only
works if the user running the frontend has read/write acces to
/dev/xpt0. Instead, you can also set a link <I>/dev/scanner</I> to the appro-
priate /dev/uk device.
Adaptec AHA1542CF
Reported to work fine under FreeBSD 2.2.2R with the <B>aha</B>
Reported to work fine under FreeBSD 2.2.2R with the <B>aha</B>
driver.
Adaptec 2940
Reported to work fine under FreeBSD 2.2.2.
Adaptec 1522
The scanner probes ok but any attempt to access it <I>hangs</I>
the entire system. It looks like something is disabling
The scanner probes ok but any attempt to access it <I>hangs</I>
the entire system. It looks like something is disabling
interrupts and then not reenabling them, so it looks like
a bug in the FreeBSD <B>aic</B> driver.
Adaptec 1505
Works on FreeBSD 2.2.5R and 3.0 using the <B>aic</B> driver,
provided that Plug-and-Play support is disabled on the
Works on FreeBSD 2.2.5R and 3.0 using the <B>aic</B> driver,
provided that Plug-and-Play support is disabled on the
card. If there are no <I>uk</I> devices, just do a ``sh MAKEDEV
uk0'' in the <B>/dev</B> directory. The scanner should then be
uk0'' in the <B>/dev</B> directory. The scanner should then be
accessible as <B>/dev/uk0</B> <B>if</B> <B>it</B> <B>was</B> <B>probed</B> during boot.
Tekram DC390
Reported to work fine under FreeBSD 2.2.2R with the <B>amd</B>
Reported to work fine under FreeBSD 2.2.2R with the <B>amd</B>
driver.
</PRE>
<H2>LINUX INFO</H2><PRE>
First, make sure your kernel has SCSI generic support enabled. In
First, make sure your kernel has SCSI generic support enabled. In
``make xconfig'', this shows up under ``SCSI support-&gt;SCSI generic sup-
port''.
To keep scanning times to a minimum, it is strongly recommended to use
To keep scanning times to a minimum, it is strongly recommended to use
a large buffer size for the generic SCSI driver. From SG driver version
2.0 on, the maximum buffer size can be changed at program run time, and
there is no restriction in size. This driver version is part of the
Linux kernels from version 2.2.7 on. If the new SG driver is available
some backends (e.g. sane-umax, sane-mustek, sane-sharp) automatically
request larger scsi buffers. If a backend does not automatically
request a larger scsi buffer, set the environment variable
<B>SANE_SG_BUFFERSIZE</B> to the desired buffer size in bytes. It is not rec-
ommended to use more than 1 MB, because for large values the probabil-
there is no restriction in size. This driver version is part of the
Linux kernels from version 2.2.7 on. If the new SG driver is available
some backends (e.g. sane-umax, sane-mustek, sane-sharp) automatically
request larger scsi buffers. If a backend does not automatically
request a larger scsi buffer, set the environment variable
<B>SANE_SG_BUFFERSIZE</B> to the desired buffer size in bytes. It is not rec-
ommended to use more than 1 MB, because for large values the probabil-
ity increases that the SG driver cannot allocate the necessary
buffer(s). For ISA cards, even 1 MB might be a too large value. For a
detailed discussion of memory issues of the SG driver, see
buffer(s). For ISA cards, even 1 MB might be a too large value. For a
detailed discussion of memory issues of the SG driver, see
http://www.torque.net/sg.
For Linux kernels before version 2.2.7 the size of the buffer is only
32KB. This works, but for many cheaper scanners this causes scanning
For Linux kernels before version 2.2.7 the size of the buffer is only
32KB. This works, but for many cheaper scanners this causes scanning
to be slower by about a factor of four than when using a size of 127KB.
Linux defines the size of this buffer by macro <B>SG_BIG_BUFF</B> in header
file <I>/usr/include/scsi/sg.h</I>. Unless a system is seriously short on
memory, it is recommended to increase this value to the maximum legal
value of 128*1024-512=130560 bytes. After changing this value, it is
Linux defines the size of this buffer by macro <B>SG_BIG_BUFF</B> in header
file <I>/usr/include/scsi/sg.h</I>. Unless a system is seriously short on
memory, it is recommended to increase this value to the maximum legal
value of 128*1024-512=130560 bytes. After changing this value, it is
necessary to recompile both the kernel (or the SCSI generic module) and
the SCSI backends. Keep in mind that this is only necessary with older
the SCSI backends. Keep in mind that this is only necessary with older
Linux kernels.
A common issue with SCSI scanners is what to do when you booted the
system while the scanner was turned off? In such a case, the scanner
won't be recognized by the kernel and SANE won't be able to access it.
Fortunately, Linux provides a simple mechanism to probe a SCSI device
on demand. Suppose you have a scanner connected to SCSI bus 2 and the
scanner has a SCSI id of 5. When the system is up and running and the
A common issue with SCSI scanners is what to do when you booted the
system while the scanner was turned off? In such a case, the scanner
won't be recognized by the kernel and SANE won't be able to access it.
Fortunately, Linux provides a simple mechanism to probe a SCSI device
on demand. Suppose you have a scanner connected to SCSI bus 2 and the
scanner has a SCSI id of 5. When the system is up and running and the
scanner is turned on, you can issue the command:
echo "scsi add-single-device 2 0 5 0" &gt; /proc/scsi/scsi
and the kernel will probe and recognize your scanner (this needs to be
done as root). It's also possible to dynamically remove a SCSI device
by using the ``remove-single-device'' command. For details, please
and the kernel will probe and recognize your scanner (this needs to be
done as root). It's also possible to dynamically remove a SCSI device
by using the ``remove-single-device'' command. For details, please
refer to to the SCSI-2.4-HOWTO.
Scanners are known to work with the following SCSI adapters under
Linux. This list isn't complete, usually any SCSI adapter supported by
Scanners are known to work with the following SCSI adapters under
Linux. This list isn't complete, usually any SCSI adapter supported by
Linux should work.
Acard/Advance SCSI adapters
Some old versions of the kernel driver (atp870u.c) cut
the inquiry information. Therefore the scanner couldn't
Some old versions of the kernel driver (atp870u.c) cut
the inquiry information. Therefore the scanner couldn't
be detected correctly. Use a current kernel.
Adaptec AHA-1505/AHA-1542/AHA-2940
Reported to work fine with Linux since v2.0. If you
encounter kernel freezes or other unexpected behaviour
get the latest Linux kernel (2.2.17 seems to work) or
Reported to work fine with Linux since v2.0. If you
encounter kernel freezes or other unexpected behaviour
get the latest Linux kernel (2.2.17 seems to work) or
reduce SCSI buffer size to 32 kB.
ASUS SC200
Reported to work fine with Linux v2.0.
BusLogic BT958
To configure the BusLogic card, you may need to follow
To configure the BusLogic card, you may need to follow
these instructions (contributed by Jeremy
&lt;jeremy@xxedgexx.com&gt;): During boot, when your BusLogic
adapter is being initialized, press Ctrl-B to enter your
BusLogic adapter setup. Choose the address which your
&lt;jeremy@xxedgexx.com&gt;): During boot, when your BusLogic
adapter is being initialized, press Ctrl-B to enter your
BusLogic adapter setup. Choose the address which your
BusLogic containing your scanner is located. Choose
``SCSI Device Configuration''. Choose ``Scan SCSI Bus''.
Choose whatever SCSI id that contains your scanner and
then choose ``View/Modify SCSI configuration''. Change
Choose whatever SCSI id that contains your scanner and
then choose ``View/Modify SCSI configuration''. Change
``Negotiation'' to ``async'' and change ``Disconnect'' to
``off''. Press Esc, save, and Esc again until you are
``off''. Press Esc, save, and Esc again until you are
asked to reboot.
NCR/Symbios 53c400/53c400a or Domex DTC3181E/L/LE (DTCT436/436P)
ISA SCSI card
This card is supplied by Mustek (and other vendors). It's
supported since Linux 2.2. The SCSI cards are supported
supported since Linux 2.2. The SCSI cards are supported
by the module g_NCR5380. It's necessary to tell the ker-
nel the io port and type of card. Example for a 53c400a:
``modprobe g_NCR5380 ncr_addr=0x280 ncr_53c400a=1''.
Once the kernel detects the card, it should work all
``modprobe g_NCR5380 ncr_addr=0x280 ncr_53c400a=1''.
Once the kernel detects the card, it should work all
right. However, while it should work, do not expect good
performance out of this card---it has no interrupt line
and therefore while a scan is in progress, the system
becomes almost unusable. You may change the values of
performance out of this card---it has no interrupt line
and therefore while a scan is in progress, the system
becomes almost unusable. You may change the values of
the USLEEP macros in drivers/scsi/g_NCR5380.c. Some doc-
umentation is in this file and NCR5380.c.
NCR/Symbios 810
For some scanners it may be necssary to disable discon-
nect/reconnect. To achieve this use the option
For some scanners it may be necssary to disable discon-
nect/reconnect. To achieve this use the option
ncr53c8xx="disc:n". Some people reported that their scan-
ner only worked with the 53c7,8xx driver, not the
ncr53c8xx. Try both if you have trouble.
For Linux kernels before 2.0.33 it may be necessary to
increase the SCSI timeout. The default timeout for the
Linux kernels before 2.0.33 is 10 seconds, which is way
For Linux kernels before 2.0.33 it may be necessary to
increase the SCSI timeout. The default timeout for the
Linux kernels before 2.0.33 is 10 seconds, which is way
too low when scanning large area. If you get messages of
the form ``restart (ncr dead ?)'' in your /var/log/mes-
sages file or on the system console, it's an indication
that the timeout is too short. In this case, find the
line ``if (np-&gt;latetime&gt;10)'' in file ncr53c8xx.c (nor-
mally in directory /usr/src/linux/drivers/scsi) and
change the constant 10 to, say, 60 (one minute). Then
the form ``restart (ncr dead ?)'' in your /var/log/mes-
sages file or on the system console, it's an indication
that the timeout is too short. In this case, find the
line ``if (np-&gt;latetime&gt;10)'' in file ncr53c8xx.c (nor-
mally in directory /usr/src/linux/drivers/scsi) and
change the constant 10 to, say, 60 (one minute). Then
rebuild the kernel/module and try again.
Tekram DC315
The driver can be downloaded from
http://www.garloff.de/kurt/linux/dc395/. For some older
scanners it may be necessary to disable all the more
The driver can be downloaded from
http://www.garloff.de/kurt/linux/dc395/. For some older
scanners it may be necessary to disable all the more
advanced features by using e.g. modprobe dc395x_trm
dc395x_trm=7,5,1,32.
Tekram DC390
Version 1.11 of the Tekram driver seems to work fine
mostly, except that the scan does not terminate properly
Version 1.11 of the Tekram driver seems to work fine
mostly, except that the scan does not terminate properly
(it causes a SCSI timeout after 10 minutes). The generic
AM53C974 also seems to work fine and does not suffer from
the timeout problems.
@ -267,10 +269,10 @@
</PRE>
<H2>SOLARIS, OPENSTEP AND NEXTSTEP INFO</H2><PRE>
Under Solaris, OpenStep and NeXTStep, the generic SCSI device name
refers to a SCSI bus, not to an individual device. For example,
<B>/dev/sg0</B> refers to the first SCSI bus. To tell SANE which device to
use, append the character 'a'+target-id to the special device name.
Under Solaris, OpenStep and NeXTStep, the generic SCSI device name
refers to a SCSI bus, not to an individual device. For example,
<B>/dev/sg0</B> refers to the first SCSI bus. To tell SANE which device to
use, append the character 'a'+target-id to the special device name.
For example, the SCSI device connected to the first SCSI controller and
with target-id 0 would be called <B>/dev/sg0a</B>, and the device with target-
id 1 on that same bus would be called <B>/dev/sg0b,</B> and so on.
@ -279,16 +281,16 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_SANEI_SCSI</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for the generic
SCSI I/O subsystem. E.g., a value of 128 requests all debug
output to be printed by the backend. A value of 255 also prints
kernel messages from the SCSI subsystem (where available).
If the library was compiled with debug support enabled, this
environment variable controls the debug level for the generic
SCSI I/O subsystem. E.g., a value of 128 requests all debug
output to be printed by the backend. A value of 255 also prints
kernel messages from the SCSI subsystem (where available).
Smaller levels reduce verbosity.
<B>SANE_SCSICMD_TIMEOUT</B>
sets the timeout value for SCSI commands in seconds. Overriding
the default value of 120 seconds should only be necessary for
sets the timeout value for SCSI commands in seconds. Overriding
the default value of 120 seconds should only be necessary for
very slow scanners.
@ -301,7 +303,7 @@
<H2>AUTHOR</H2><PRE>
David Mosberger
sane-backends 1.0.12-cvs 07 Dec 2002 <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>
sane-backends 1.0.13 28 Oct 2003 <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -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.12-cvs 21 Nov 2000 <B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B>
sane-backends 1.0.13 21 Nov 2000 <B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -110,7 +110,7 @@
Marian Eichholz (eichholz@computer.org)
Glenn Ramsey (glenn@componic.com)
sane-backends 1.0.12-cvs 10.02.2002 <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B>
sane-backends 1.0.13 10.02.2002 <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -114,7 +114,7 @@
Man page by Henning Meier-Geinitz (mostly based on the web pages and
source code).
sane-backends 1.0.12-cvs 26 May 2001 <B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B>
sane-backends 1.0.13 26 May 2001 <B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -78,7 +78,7 @@
working first driver. Watch this space for changes.
sane-backends 1.0.12-cvs 17 Apr 2002 <B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B>
sane-backends 1.0.13 17 Apr 2002 <B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -153,7 +153,7 @@
<H2>AUTHOR</H2><PRE>
Ingo Wilken &lt;Ingo.Wilken@informatik.uni-oldenburg.de&gt;
sane-backends 1.0.12-cvs 08 Mar 1999 <B><A HREF="sane-st400.5.html">sane-st400(5)</A></B>
sane-backends 1.0.13 08 Mar 1999 <B><A HREF="sane-st400.5.html">sane-st400(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -87,7 +87,7 @@
<H2>AUTHOR</H2><PRE>
Roger Wolff
sane-backends 1.0.12-cvs 24 Jun 2000 <B><A HREF="sane-tamarack.5.html">sane-tamarack(5)</A></B>
sane-backends 1.0.13 24 Jun 2000 <B><A HREF="sane-tamarack.5.html">sane-tamarack(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -158,7 +158,7 @@
</PRE>
<H2>AUTHOR</H2><PRE>
The package is actively maintained by Frank Zago.
http://fz.eryx.net/sane/#teco
http://www.zago.net/sane/#teco
</PRE>
@ -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.12-cvs August 30th, 2002 <B><A HREF="sane-teco1.5.html">sane-teco1(5)</A></B>
sane-backends 1.0.13 August 30th, 2002 <B><A HREF="sane-teco1.5.html">sane-teco1(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -20,14 +20,15 @@
The <B>sane-teco2</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to some TECO SCSI flatbed scanners. This
backend should be considered <B>beta-quality</B> software! TECO scanners are
sold under various brands like Relisys, Piotech, TRUST. This backend
may or may not support yours.
sold under various brands like Mustek, Relisys, Piotech, Primax, TRUST.
This backend may or may not support yours.
The scanners that should work with this backend are:
Vendor Model TECO model status
---------------------- -------------- -----------
Mustek ScanMagic 4830S VM3575 untested
Primax Jewel 4800 VM356A tested
Primax Profi 9600 VM6575 tested
Primax Profi 19200 VM6586 tested
@ -53,7 +54,7 @@
The options the backend supports can either be selected through command
line options to programs like scanimage or through GUI elements in
xscanimage or xsane.
xscanimage, xsane, quiteinsane or kooka.
If you have any success with a scanner not listed here, or if you have
any strange behavior, please report to the backend maintainer or to the
@ -70,8 +71,12 @@
els of gray (8 bits). Color will produce a 24 bits color image.
<B>--resolution</B>
selects the resolution for a scan. The scanner can do all reso-
lutions between 1 and 600, in increments of 1.
Black @ White and Grayscale selects the resolution for a scan.
The scanner can do all resolutions between 1 and 600, in
increments of 1.
Color selects the resolution for a scan. The scanner can do only
the resolutions listed.
<B>Geometry</B> <B>options</B>
@ -83,7 +88,7 @@
<B>Enhancement</B> <B>options</B>
<B>--custom-gamma</B>
<B>--custom-gamma</B> <B>(no</B> <B>custom</B> <B>gamma</B> <B>option</B> <B>for</B> <B>the</B> <B>VM3564</B> <B>and</B> <B>VM356A)</B>
(color mode only) allows the user to specify a gamma table (see
the next 3 parameters).
@ -99,6 +104,11 @@
(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>--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
@ -132,13 +142,14 @@
<B>SANE_TECO2_CAL_ALGO</B>
Either 0 or 1. Selects the algorithm for the calibration. A
value of 1 seems to give better scans on the VM3575. Feedback on
it is welcome.
it is welcome. For VM356A and VM3575 default 1. For other sup-
ported types default 0.
</PRE>
<H2>LIMITATIONS</H2><PRE>
The windows TWAIN driver has many more options than this SANE backend.
However they are only software adjustments. This backend only imple-
The windows TWAIN driver has many more options than this SANE backend.
However they are only software adjustments. This backend only imple-
ments what the scanner can support.
@ -154,8 +165,9 @@
</PRE>
<H2>AUTHORS</H2><PRE>
The package is actively maintained by Frank Zago.
http://fz.eryx.net/sane/#teco2
The package is actively maintained by Frank Zago, Gerard Klaver.
http://www.zago.net/sane/#teco2
http://gkall.hobby.nl/index.html
Gerard Klaver contributed a patch to support the VM3564 and VM356A.
@ -168,15 +180,18 @@
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.
sane-backends 1.0.12-cvs 19 March 2002 <B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B>
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>
</PRE>
<HR>
<ADDRESS>

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

@ -137,9 +137,9 @@
</PRE>
<H2>AUTHOR</H2><PRE>
The package is actively maintained by Frank Zago.
http://fz.eryx.net/sane/#teco3
http://www.zago.net/sane/#teco3
sane-backends 1.0.12-cvs 25 July 2002 <B><A HREF="sane-teco3.5.html">sane-teco3(5)</A></B>
sane-backends 1.0.13 25 July 2002 <B><A HREF="sane-teco3.5.html">sane-teco3(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -279,7 +279,7 @@
<H2>BUGS</H2><PRE>
- config file values aren't tested for correctness
sane-backends 1.0.12-cvs 24 Jul 2002 <B><A HREF="sane-test.5.html">sane-test(5)</A></B>
sane-backends 1.0.13 24 Jul 2002 <B><A HREF="sane-test.5.html">sane-test(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -268,7 +268,7 @@
<H2>EMAIL-CONTACT</H2><PRE>
Oliver.Rauch@Rauch-Domain.DE
sane-backends 1.0.12-cvs 29 november 2002 <B><A HREF="sane-umax.5.html">sane-umax(5)</A></B>
sane-backends 1.0.13 29 november 2002 <B><A HREF="sane-umax.5.html">sane-umax(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -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.12-cvs 6 Jan 2002 <B><A HREF="sane-umax1220u.5.html">sane-umax1220u(5)</A></B>
sane-backends 1.0.13 6 Jan 2002 <B><A HREF="sane-umax1220u.5.html">sane-umax1220u(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -64,26 +64,32 @@
<I>port</I> <I>value</I>
Where <B>value</B> is the base address, or the ppdev device name of the port
your scanner is attached to. Known ports are <B>0x378</B>, <B>0x278</B> and <B>0x3BC</B> .
Or the name of the parallel port character device user interface, such
as /dev/parport0 for the linux ppdev, or /dev/ppi0 for FreeBSD ppi.
Under linux, if you are not sure which port your scanner is connected
to, may have a look at your /etc/modules.conf. Also typing dmesg|grep
parport in a command shell should show you a line like:
parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COM-
PAT,ECP,DMA]
telling you about port address and mode.
Where <B>value</B> is :
If you are using the linux ppdev character device, you will have to
specify the device name, which is /dev/parport0 for the first parallel
port. Check the permissions on /dev/paraport0, many linux distributions
restrict them for root only access. Get sure they are like:
crw-rw-rw- 1 root root 99, 0 mai 20 2002 /dev/parport0
crw-rw-rw- 1 root root 99, 1 mai 20 2002 /dev/parport1
crw-rw-rw- 1 root root 99, 2 mai 20 2002 /dev/parport2
crw-rw-rw- 1 root root 99, 3 mai 20 2002 /dev/parport3
The same apply with the /dev/ppi0 character device under FreeBSD.
value description.br
------------- ---------------------------------------------
auto autodetect all parallel ports and probe
them for scanner
safe-auto autodetect all parallel ports and probe
them for scanner, but does not try direct
hardware access
/dev/ppi0 uses *BSD ppi device, depending on the
number of available parallel port, you
have to use /dev/ppi1, /dev/ppi2, ...
/dev/parport0 uses linux ppdev device, depending on the
number of available parallel port, you
have to use /dev/parport1, /dev/parport2, ...
0x378 does direct hardware access on the given
address. Usual values are 0x378, 0x278, 0x3BC
In this case, you have to run the scanner as
root (*BSD and linux), or with 'IOPL=yes' on
OS/2
<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*
devices.
You can rename any device using the
@ -123,20 +129,19 @@
autodetection fails to detect properly your scanner model. If your
scanner work properly but is reported wrongly, let it be that way. The
only valid case to change the model is when your scanner produces
'black' or
'inverted' scans. In this case you can put the model. Be aware that
it will prevent autodetection.
'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 progress status reporting in the
frontend, but will stall the scan more often.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/umax</I><B>_</B><I>pp.conf</I>
The backend configuration file (see also description of
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>
@ -152,21 +157,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
@ -180,8 +185,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
@ -194,19 +199,18 @@
255 everything
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-net.5.html">sane-net(5)</A></B>, <B><A HREF="saned.1.html">saned(1)</A></B>
For latest bug fixes and information see
<I>http://umax1220p.sourceforge.net/</I>
</PRE>
<H2>AUTHOR</H2><PRE>
Stéphane VOLTZ &lt;svoltz@wanadoo.fr&gt;, man page derived from mustek_pp man
page by Jochen Eisinger &lt;jochen.eisinger@gmx.net&gt;
Stéphane VOLTZ &lt;svoltz@wanadoo.fr&gt;
</PRE>
@ -218,7 +222,7 @@
run "scanimage -V" to determine this
<I>the</I> <I>backend</I> <I>version</I> <I>and</I> <I>your</I> <I>scanner</I> <I>hardware</I>
run "SANE_DEBUG_UMAX=255 scanimage -L 2&gt;log" as root. If you
run "SANE_DEBUG_UMAX_PP=255 scanimage -L 2&gt;log" as root. If you
don't get any output from the umax_pp backend, make sure a line
"umax_pp" is included into your /usr/local/etc/sane.d/dll.conf.
If your scanner isn't detected, make sure you've defined the
@ -234,7 +238,7 @@
better), or you think I should know something, please include
it.
sane-backends 1.0.12-cvs 16 September 2003 <B><A HREF="sane-umax_pp.5.html">sane-umax_pp(5)</A></B>
sane-backends 1.0.13 16 September 2003 <B><A HREF="sane-umax_pp.5.html">sane-umax_pp(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -64,7 +64,7 @@
nel, libsub), NetBSD (libusb), OpenBSD (kernel, libusb) and MacOS X
(libusb). Testing on MacOS X is very limited and not all scanners seem
to work reliably with the BSDs. For installation issues, also check the
/usr/local/doc/sane-1.0.12-cvs/README.platform files.
/usr/local/doc/sane-1.0.13/README.platform files.
Generally speaking, if your scanner works with one method, there is no
need to switch to the other one.
@ -141,8 +141,8 @@
message concerning "only 2 or three endpoints" in syslog.
For OpenBSD the kernel may need to be recompiled. For details look at
/usr/local/doc/sane-1.0.12-cvs/README.openbsd. Similar approaches
should be used for the other BSDs.
/usr/local/doc/sane-1.0.13/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
@ -216,7 +216,7 @@
<H2>AUTHOR</H2><PRE>
Henning Meier-Geinitz
sane-backends 1.0.12-cvs 27 Nov 2002 <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>
sane-backends 1.0.13 27 Nov 2002 <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -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.12-cvs 28 Aug 2002 <B><A HREF="sane-v4l.5.html">sane-v4l(5)</A></B>
sane-backends 1.0.13 28 Aug 2002 <B><A HREF="sane-v4l.5.html">sane-v4l(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -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.12-cvs/sane.tex</I>' are references to text files
that were copied to the <B>SANE</B> documentation directory
(<I>/usr/local/doc/sane-1.0.12-cvs/</I>) during installation. Everything else
is a URL to a resource on the web.
`<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.
<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.12-cvs/.
are also installed on your system at /usr/local/doc/sane-1.0.13/.
<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.12-cvs/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.13/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,143 +193,148 @@
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-
The SANE mustek backend supports most Mustek SCSI flatbed scanners
including the Paragon and ScanExpress series and the 600 II N (non-
SCSI). Some Trust scanners are also supported. See <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B> for
details.
<B>mustek_pp</B>
The mustek_pp backend provides access to Mustek parallel port flatbed
scanners. See <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B> for details.
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.
<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.12-cvs/PROJECTS</I>.
projects in <I>/usr/local/doc/sane-1.0.13/PROJECTS</I>.
</PRE>
@ -344,92 +349,91 @@
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
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>.
(See <I>http://www.gphoto.org</I> for more information and a list of sup-
ported cameras.) Gphoto2 supports over 140 different camera models.
However, please note that more development and testing is needed
before all of these cameras will be supported by <B>SANE</B> backend. See
<B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>.
<B>qcam</B>
Backend for Connectix QuickCam cameras. See <B><A HREF="sane-qcam.5.html">sane-qcam(5)</A></B>.
Also, have a look at the backend information page at
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.12-cvs/PROJECTS</I>.
projects in <I>/usr/local/doc/sane-1.0.13/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.12-cvs/PROJECTS</I>.
projects in <I>/usr/local/doc/sane-1.0.13/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.12-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).
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).
There is some more information for programmers in
<I>/usr/local/doc/sane-1.0.12-cvs/backend-writing.txt</I>. Most of the inter-
nal <B>SANE</B> routines (<B>sanei</B>) are documented using doxygen:
<I>http://sanei.meier-geinitz.de/</I>. Before a new backend or frontend
project is started, have a look at
<I>/usr/local/doc/sane-1.0.12-cvs/PROJECTS</I> for projects that are planned
or not yet included into the <B>SANE</B> distribution and at our bug-tracking
system: <I>http://www.http://www.sane-project.org/bugs.html</I>.
<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>.
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>.
@ -451,7 +455,7 @@
The shared libraries implementing the backends (present on sys-
tems that support dynamic loading).
<I>/usr/local/doc/sane-1.0.12-cvs/*</I>
<I>/usr/local/doc/sane-1.0.13/*</I>
<B>SANE</B> documentation: The standard, READMEs, text files for back-
ends etc.
@ -541,7 +545,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.12-cvs/AUTHORS</I> file or the
can be found in the <I>/usr/local/doc/sane-1.0.13/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).
@ -556,26 +560,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><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-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>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>
</PRE>
<H2>AUTHOR</H2><PRE>
David Mosberger-Tang and many many more (see
<I>/usr/local/doc/sane-1.0.12-cvs/AUTHORS</I> for details). This man page was
<I>/usr/local/doc/sane-1.0.13/AUTHORS</I> for details). This man page was
written by Henning Meier-Geinitz. Quite a lot of text was taken from
the <B>SANE</B> standard, several man pages, and README files.
sane-backends 1.0.12-cvs 24 Sept 2003 <B><A HREF="sane.7.html">sane(7)</A></B>
sane-backends 1.0.13 3 Oct 2003 <B><A HREF="sane.7.html">sane(7)</A></B>
</PRE>
<HR>
<ADDRESS>

75
man/saned.1.html
Wyświetl plik

@ -49,23 +49,26 @@
authentification. Don't run <B>saned</B> as root if it's not necessary. And do
<B>not</B> install <B>saned</B> as setuid root.
The contents of the <I>saned.conf</I> file is a list of host names or IP
addresses that are permitted to use local SANE devices. Connections
from localhost are always permitted. Empty lines and lines starting
with a hash mark (#) are ignored. A line containing the single charac-
ter ``+'' is interpreted to match any hostname. This allows any remote
machine to use your scanner and may present a security risk, so this
shouldn't be used unless you know what you're doing. A sample configu-
ration file is shown below:
The contents of the <I>saned.conf</I> file is a list of host names, IP
addresses or IP subnets (CIDR notation) that are permitted to use local
SANE devices. IPv6 addresses must be enclosed in brackets, and should
always be specified in their compressed form. Connections from local-
host are always permitted. Empty lines and lines starting with a hash
mark (#) are ignored. A line containing the single character ``+'' is
interpreted to match any hostname. This allows any remote machine to
use your scanner and may present a security risk, so this shouldn't be
used unless you know what you're doing. A sample configuration file is
shown below:
scan-client.somedomain.firm
# this is a comment
192.168.0.1
::1
192.168.2.12/29
[::1]
[2001:7a8:185e::42:12]/64
The case of the host names does not matter, so AHost.COM is considered
identical to ahost.com. IPv6 addresses should always be specified in
their compressed form.
identical to ahost.com.
For <B>saned</B> to work properly, it is also necessary to add a configuration
line to <I>/etc/inetd.conf</I>. Note that your inetd must support IPv6 if you
@ -77,20 +80,20 @@
sane stream tcp nowait saned.saned /usr/local/sbin/saned saned
However, if your system uses <B><A HREF="tcpd.8.html">tcpd(8)</A></B> for additional security screening,
you may want to disable saned access control by putting ``+'' in
<I>saned.conf</I> and use a line of the following form in <I>/etc/inetd.conf</I>
you may want to disable saned access control by putting ``+'' in
<I>saned.conf</I> and use a line of the following form in <I>/etc/inetd.conf</I>
instead:
sane stream tcp nowait saned.saned /usr/sbin/tcpd
/usr/local/sbin/saned
Note that both examples assume that there is a <B>saned</B> group and a <B>saned</B>
user. If you follow this example, please make sure that the access
permissions on the special device are set such that <B>saned</B> can access
Note that both examples assume that there is a <B>saned</B> group and a <B>saned</B>
user. If you follow this example, please make sure that the access
permissions on the special device are set such that <B>saned</B> can access
the scanner (the program generally needs read and write access to scan-
ner devices).
If xinetd is installed on your system instead of inetd the following
If xinetd is installed on your system instead of inetd the following
example for xinetd.conf may be helpful:
# default: off
@ -107,7 +110,7 @@
server = /usr/local/sbin/saned
}
Finally, it is also necessary to add a line of the following form to
Finally, it is also necessary to add a line of the following form to
<I>/etc/services</I>:
sane 6566/tcp # SANE network scanner daemon
@ -115,21 +118,23 @@
</PRE>
<H2>RESTRICTIONS</H2><PRE>
In addition to the control connection (port 6566) saned also uses a
data connection. The port of this socket is selected by the operating
system and can't be specified by the user currently. This may be a
problem if the connection must go through a firewall (packet filter).
In addition to the control connection (port 6566) saned also uses a
data connection. The port of this socket is selected by the operating
system and can't be specified by the user currently. This may be a
problem if the connection must go through a firewall (packet filter).
If you must use a packet filter, make sure that all ports &gt; 1024 are
open on the server for connections from the client.
</PRE>
<H2>FILES</H2><PRE>
<I>/etc/hosts.equiv</I>
The hosts listed in this file are permitted to access all local
SANE devices. Caveat: this file imposes serious security risks
The hosts listed in this file are permitted to access all local
SANE devices. Caveat: this file imposes serious security risks
and its use is not recommended.
<I>/usr/local/etc/sane.d/saned.conf</I>
Contains a list of hosts permitted to access local SANE devices
Contains a list of hosts permitted to access local SANE devices
(see also description of <B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/etc/sane.d/saned.users</I>
@ -137,8 +142,8 @@
user:password:backend
access to the listed backends is restricted. A backend may be
listed multiple times for different user/password combinations.
access to the listed backends is restricted. A backend may be
listed multiple times for different user/password combinations.
The server uses MD5 encryption if supported by the client.
@ -147,21 +152,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).
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, <B><A HREF="xcam.1.html">xcam(1)</A></B>, <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>, <B>sane-</B>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, <B><A HREF="xcam.1.html">xcam(1)</A></B>, <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>, <B>sane-</B>
<B><A HREF="net.5.html">net(5)</A></B>, <B>sane-"backendname"</B>(5)
<I>http://www.penguin-breeder.org/?page=sane-net</I>
@ -170,7 +175,7 @@
<H2>AUTHOR</H2><PRE>
David Mosberger
sane-backends 1.0.12-cvs 9 Feb 2003 <B><A HREF="saned.1.html">saned(1)</A></B>
sane-backends 1.0.13 29 Oct 2003 <B><A HREF="saned.1.html">saned(1)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -272,7 +272,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.12-cvs 15 Apr 2003 <B><A HREF="scanimage.1.html">scanimage(1)</A></B>
sane-backends 1.0.13 15 Apr 2003 <B><A HREF="scanimage.1.html">scanimage(1)</A></B>
</PRE>
<HR>
<ADDRESS>

5318
sane-backends-1.0.12.html 100644
Wyświetl plik

Plik diff jest za duży Load Diff

2784
sane-backends.html
Wyświetl plik

Plik diff jest za duży Load Diff

5348
sane-mfgs.html
Wyświetl plik

Plik diff jest za duży Load Diff

27
sane-support.html
Wyświetl plik

@ -90,7 +90,7 @@
<tr>
<td align="left"><a href="http://www.freebsd.org/">FreeBSD Alpha v4.8</a></td>
<td align="center">1.0.12</td>
<td align="center">1.0.13</td>
<td align="center">gcc 2.95.4</td>
<td align="center"><font color="#a08000">???</font></td>
<td align="center"><font color="#a08000">???</font></td>
@ -146,8 +146,8 @@
<tr>
<td align="left"><a href="http://www.alphalinux.org/">Linux Alpha v2.4</a></td>
<td align="center">1.0.12</td>
<td align="center">gcc 2.95.4</td>
<td align="center">1.0.13</td>
<td align="center">gcc 3.3.1</td>
<td align="center"><font color="#a08000">???</font> </td>
<td align="center"><font color="#008000">yes(?)</font></td>
<td align="center"><font color="#008000">yes</font></td>
@ -168,7 +168,7 @@
<tr>
<td align="left"><a href="http://www.linuxia64.org/">Linux ia64 v2.4</a></td>
<td align="center">1.0.10</td>
<td align="center">1.0.13</td>
<td align="center">gcc 3.0</td>
<td align="center"><font color="#008000">yes(?)</font></td>
<td align="center"><font color="#008000">yes(?)</font></td>
@ -191,8 +191,19 @@
<tr>
<td align="left"><a href="http://www.linux.org/">Linux ix86 v2.4</a></td>
<td align="center">1.0.12</td>
<td align="center">gcc 3.2.3</td>
<td align="center">1.0.13</td>
<td align="center">gcc 3.3.2</td>
<td align="center"><font color="#008000">yes</font></td>
<td align="center"><font color="#008000">yes</font></td>
<td align="center"><font color="#008000">yes</font></td>
<td align="center"><font color="#008000">yes</font></td>
<td align="center"><font color="#008000">yes</font></td>
</tr>
<tr>
<td align="left"><a href="http://www.linux.org/">Linux ix86 v2.6</a></td>
<td align="center">1.0.13</td>
<td align="center">gcc 3.3.2</td>
<td align="center"><font color="#008000">yes</font></td>
<td align="center"><font color="#008000">yes</font></td>
<td align="center"><font color="#008000">yes</font></td>
@ -213,7 +224,7 @@
<tr>
<td align="left"><a href="http://www.linux.org/">Linux Parisc64 v2.4</a></td>
<td align="center">1.0.12</td>
<td align="center">1.0.13</td>
<td align="center">gcc 3.0.4</td>
<td align="center"><font color="#a08000">???</font></td>
<td align="center"><font color="#a08000">???</font></td>
@ -360,7 +371,7 @@
<tr>
<td align="left"><a href="http://www.tru64unix.compaq.com/">Tru64 5.1 Alpha</a></td>
<td align="center">1.0.12</td>
<td align="center">1.0.13</td>
<td align="center">cc</td>
<td align="center"><font color="#a08000">???</font></td>
<td align="center"><font color="#FF0000">no</font></td>

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

@ -104,7 +104,9 @@
supported by that version, these lists are for you.
</p>
<p>
SANE version: <a href="sane-backends-1.0.10.html">1.0.11 and 1.0.10</a>,
SANE version:
<a href="sane-backends-1.0.12.html">1.0.12</a>,
<a href="sane-backends-1.0.10.html">1.0.11 and 1.0.10</a>,
<a href="sane-backends-1.0.9.html">1.0.9</a>,
<a href="sane-backends-1.0.8.html">1.0.8</a>,
<a href="sane-backends-1.0.7.html">1.0.7</a>,