kopia lustrzana https://gitlab.com/sane-project/website
Updated SANE standard and HTML pages from CVS. Mostly link updates to new
homepage www.sane-project.org and spelling fixes.merge-requests/1/head
Henning Geinitz
rodzic
f732f175af
commit
546d3007e9
|
|
@ -376,7 +376,7 @@ will be expanded as need arises):
|
|||
<td colspan=1 align=left nowrap> <tt>Noname</tt> </td></tr>
|
||||
<tr valign=top>
|
||||
<td colspan=1 align=left nowrap>
|
||||
<tt>Microtek</tt> </td></tr>
|
||||
<tt>Microtek</tt> </td></tr>
|
||||
<tr valign=top>
|
||||
<td colspan=1 align=left nowrap> </td>
|
||||
<td colspan=1 align=left nowrap> </td></tr>
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ Anybody with email access to the Internet can automatically join and
|
|||
leave the discussion group by sending mail to the following address.
|
||||
<blockquote><a name="i151">
|
||||
<pre>
|
||||
sane-devel-request@mostang.com
|
||||
sane-devel-request@lists.alioth.debian.org
|
||||
</pre>
|
||||
</blockquote>
|
||||
To subscribe, send a mail with the body ``<tt>subscribe sane-devel</tt>'' to the
|
||||
|
|
@ -25,7 +25,7 @@ mail with a subject of ``<tt>help</tt>'' to the above address. The
|
|||
mailing list is archived and available through the SANE home page at
|
||||
URL:
|
||||
<blockquote>
|
||||
http://www.mostang.com/sane/
|
||||
http://www.sane-project.org/
|
||||
</blockquote>
|
||||
|
||||
<p>
|
||||
|
|
|
|||
|
|
@ -25,10 +25,10 @@
|
|||
|
||||
If you own a Abaton scanner other than the ones listed above that works
|
||||
with this backend, or if you own an Abaton scanner that does not work
|
||||
with this backend, please contact <I>sane-devel@mostang.com</I> with the model
|
||||
number, so that arrangements can be made to include support for it.
|
||||
Have a look at http://www.mostang.com/sane/mail.html concerning sub-
|
||||
scription to sane-devel.
|
||||
with this backend, please contact <I>sane-devel@lists.alioth.debian.org</I>
|
||||
with the model number, so that arrangements can be made to include sup-
|
||||
port for it. Have a look at http://www.sane-project.org/mail-
|
||||
ing-lists.html concerning subscription to sane-devel.
|
||||
|
||||
Abaton is out of business, and these scanners are not supported by
|
||||
Everex (the parent company of Abaton), nor is there any programming
|
||||
|
|
@ -119,7 +119,7 @@
|
|||
If you have found something that you think is a bug, please attempt to
|
||||
recreate it with the SANE_DEBUG_ABATON environment variable set to 255,
|
||||
and send a report detailing the conditions surrounding the bug to
|
||||
<I>sane-devel@mostang.com</I>.
|
||||
<I>sane-devel@lists.alioth.debian.org</I>.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
|
|||
|
|
@ -34,9 +34,9 @@
|
|||
|
||||
If you own a scanner other than the ones listed above that works with
|
||||
this backend, please let us know by sending the scanner's model name,
|
||||
SCSI id, and firmware revision to <I>sane-devel@mostang.com</I>. Have a look
|
||||
at http://www.mostang.com/sane/mail.html concerning subscription to
|
||||
sane-devel.
|
||||
SCSI id, and firmware revision to <I>sane-devel@lists.alioth.debian.org</I>.
|
||||
Have a look at http://www.sane-project.org/mailing-lists.html concern-
|
||||
ing subscription to sane-devel.
|
||||
|
||||
All of these scanners are pre-SCSI-2, and do not even report properly
|
||||
to SCSI Inquiry. This is typically evident in SCSI bus scans, where
|
||||
|
|
|
|||
|
|
@ -28,9 +28,10 @@
|
|||
|
||||
If you own a Apple scanner other than the ones listed above that works
|
||||
with this backend, please let us know by sending the scanner's model
|
||||
name, SCSI id, and firmware revision to <I>sane-devel@mostang.com</I>. See
|
||||
http://www.mostang.com/sane/mail.html for details on how to subscribe
|
||||
to sane-devel.
|
||||
name, SCSI id, and firmware revision to
|
||||
<I>sane-devel@lists.alioth.debian.org</I>. See
|
||||
http://www.sane-project.org/mailing-lists.html for details on how to
|
||||
subscribe to sane-devel.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -39,39 +40,39 @@
|
|||
|
||||
<I>special</I>
|
||||
|
||||
Where <I>special</I> is either the path-name for the special device that cor-
|
||||
responds to a SCSI scanner. For SCSI scanners, the special device name
|
||||
must be a generic SCSI device or a symlink to such a device. Under
|
||||
Linux, such a device name could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example.
|
||||
Where <I>special</I> is either the path-name for the special device that cor-
|
||||
responds to a SCSI scanner. For SCSI scanners, the special device name
|
||||
must be a generic SCSI device or a symlink to such a device. Under
|
||||
Linux, such a device name could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example.
|
||||
See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONFIGURATION</H2><PRE>
|
||||
The contents of the <I>apple.conf</I> file is a list of options and device
|
||||
names that correspond to Apple scanners. Empty lines and lines start-
|
||||
ing with a hash mark (#) are ignored. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> on details of
|
||||
The contents of the <I>apple.conf</I> file is a list of options and device
|
||||
names that correspond to Apple scanners. Empty lines and lines start-
|
||||
ing with a hash mark (#) are ignored. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> on details of
|
||||
what constitutes a valid device name.
|
||||
|
||||
Options come in two flavors: global and positional ones. Global
|
||||
options apply to all devices managed by the backend whereas positional
|
||||
options apply just to the most recently mentioned device. Note that
|
||||
Options come in two flavors: global and positional ones. Global
|
||||
options apply to all devices managed by the backend whereas positional
|
||||
options apply just to the most recently mentioned device. Note that
|
||||
this means that the order in which the options appear matters!
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>SCSI ADAPTER TIPS</H2><PRE>
|
||||
SCSI scanners are typically delivered with an ISA SCSI adapter. Unfor-
|
||||
tunately, that adapter is not worth much since it is not interrupt
|
||||
driven. It is (sometimes) possible to get the supplied card to work,
|
||||
but without interrupt line, scanning will put so much load on the sys-
|
||||
tunately, that adapter is not worth much since it is not interrupt
|
||||
driven. It is (sometimes) possible to get the supplied card to work,
|
||||
but without interrupt line, scanning will put so much load on the sys-
|
||||
tem, that it becomes almost unusable for other tasks.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>FILES</H2><PRE>
|
||||
<I>/usr/local/etc/sane.d/apple.conf</I>
|
||||
The backend configuration file (see also description of
|
||||
The backend configuration file (see also description of
|
||||
<B>SANE_CONFIG_DIR</B> below).
|
||||
|
||||
<I>/usr/local/lib/sane/libsane-apple.a</I>
|
||||
|
|
@ -87,34 +88,34 @@
|
|||
<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_APPLE</B>
|
||||
If the library was compiled with debug support enabled, this
|
||||
environment variable controls the debug level for this backend.
|
||||
E.g., a value of 255 requests all debug output to be printed.
|
||||
If the library was compiled with debug support enabled, this
|
||||
environment variable controls the debug level for this backend.
|
||||
E.g., a value of 255 requests all debug output to be printed.
|
||||
Smaller levels reduce verbosity.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CURRENT STATUS</H2><PRE>
|
||||
The apple backend is now in version 0.3 (Tue Jul 21 1998). Since I only
|
||||
have the AppleScanner and not the other models (OneScanner, ColorOneS-
|
||||
have the AppleScanner and not the other models (OneScanner, ColorOneS-
|
||||
canner) I can only develop/test for the AppleScanner effectively. How-
|
||||
ever with this release I almost complete the gui part of all scanners.
|
||||
Most of the functionality is there. At least OneScanner should scan at
|
||||
the AppleScanner's compatible modes (LineArt, HalfTone, Gray16). My
|
||||
ever with this release I almost complete the gui part of all scanners.
|
||||
Most of the functionality is there. At least OneScanner should scan at
|
||||
the AppleScanner's compatible modes (LineArt, HalfTone, Gray16). My
|
||||
personal belief is that with a slight touch of debugging the OneScanner
|
||||
could be actually usable. The ColorOneScanner needs more work. AppleS-
|
||||
could be actually usable. The ColorOneScanner needs more work. AppleS-
|
||||
canner is of course almost fully supported.
|
||||
|
||||
|
||||
|
|
@ -130,44 +131,44 @@
|
|||
|
||||
<B>ColorOneScanner</B>
|
||||
Cannot up/download halftone pattern, calibration vectors, custom
|
||||
Color Correction Table (CCT) and of course custom gamma tables.
|
||||
Color Correction Table (CCT) and of course custom gamma tables.
|
||||
|
||||
<B>Park/UnPark</B> <B>(OneScanner,</B> <B>ColorOneScanner)</B>
|
||||
|
||||
The above functionalities are not only missing because I don't actually
|
||||
have the hardware to experiment on it. Another reason is the lack of
|
||||
have the hardware to experiment on it. Another reason is the lack of
|
||||
understanding of how SANE API could provide enaugh means to me to actu-
|
||||
ally describe other array types than the gamma one.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>UNSUPPORTED FEATURES.</H2><PRE>
|
||||
The following "features" will never be supported. At least as I am
|
||||
The following "features" will never be supported. At least as I am
|
||||
maintaining the sane-apple backend.
|
||||
|
||||
<B>NoHome</B> <B>(AppleScanner)</B>
|
||||
The scanner lamp stays on and the carriage assembly remains
|
||||
The scanner lamp stays on and the carriage assembly remains
|
||||
where it stops at the end of the scan. After two minutes, if the
|
||||
scanner does not receive another SCAN command the lamp goes off
|
||||
scanner does not receive another SCAN command the lamp goes off
|
||||
and the carriage returns to the home position.
|
||||
|
||||
<B>Compression</B> <B>(AppleScanner)</B>
|
||||
The Scanner can compress data with CCITT Group III, one dimen-
|
||||
The Scanner can compress data with CCITT Group III, one dimen-
|
||||
sional algorithm (fax), and the Skip White Line algorithm.
|
||||
|
||||
<B>Multiple</B> <B>Windows</B> <B>(AppleScanner)</B>
|
||||
AppleScanner may support multiple windows. It would be a cool
|
||||
feature and a challenge for me to code it if you could intermix
|
||||
different options for different windows (scan areas). This way
|
||||
you could scan a document in LineArt mode but the figures in it
|
||||
on Gray and in a different resolution. Unfortunately this is
|
||||
AppleScanner may support multiple windows. It would be a cool
|
||||
feature and a challenge for me to code it if you could intermix
|
||||
different options for different windows (scan areas). This way
|
||||
you could scan a document in LineArt mode but the figures in it
|
||||
on Gray and in a different resolution. Unfortunately this is
|
||||
impossible.
|
||||
|
||||
<B>Scan</B> <B>Direction</B> <B>(OneScanner)</B>
|
||||
It controls the scan direction. (?)
|
||||
|
||||
<B>Status/Reset</B> <B>Button</B> <B>(OneScanner)</B>
|
||||
This option controls the status of the button in OneScanner
|
||||
This option controls the status of the button in OneScanner
|
||||
model. You can also reset the button status by software.
|
||||
|
||||
|
||||
|
|
@ -176,37 +177,37 @@
|
|||
The bugs in a sane backend are divided in two classes. We have <B>GUI</B> bugs
|
||||
and <B>scanner</B> <B>specific</B> bugs.
|
||||
|
||||
We know we have a GUI bug when a parameter is not showing up itself
|
||||
We know we have a GUI bug when a parameter is not showing up itself
|
||||
when it should (active) or vice versa. To find out which parameters are
|
||||
active accross various Apple modes and models from the documentation
|
||||
active accross various Apple modes and models from the documentation
|
||||
<B>ftp://ftpdev.info.apple.com/devworld/Technical_Documentation/Peripher-</B>
|
||||
<B>als_Documentation/</B> is an interesting exercise. I may missed some depen-
|
||||
dancies. For example for the threshold parameter the Apple Scanners
|
||||
Programming guide says nothing. I had to assume that is valid only in
|
||||
dancies. For example for the threshold parameter the Apple Scanners
|
||||
Programming guide says nothing. I had to assume that is valid only in
|
||||
LineArt mode.
|
||||
|
||||
Scanner specific bugs are mostly due to mandatory round offs in order
|
||||
to scan. In the documentation in some place states that the width of
|
||||
the scan area should be a byte multiple. In an other place says that
|
||||
the width of the scan area should be an even byte multiple. Go fig-
|
||||
Scanner specific bugs are mostly due to mandatory round offs in order
|
||||
to scan. In the documentation in some place states that the width of
|
||||
the scan area should be a byte multiple. In an other place says that
|
||||
the width of the scan area should be an even byte multiple. Go fig-
|
||||
ure...
|
||||
|
||||
Other source of bugs are due to scsi communcation, scsi connects and
|
||||
disconnects. However the classical bugs are still there. So you may
|
||||
Other source of bugs are due to scsi communcation, scsi connects and
|
||||
disconnects. However the classical bugs are still there. So you may
|
||||
encouter buffer overruns, null pointers, memory corruption and <B>SANE</B> API
|
||||
violations.
|
||||
|
||||
<B>SIGSEGV</B> <B>on</B> <B>SliceBars</B>
|
||||
When you try to modify the scan area from the slice bar you have
|
||||
a nice little cute core dump. I don't know why. If you select
|
||||
a nice little cute core dump. I don't know why. If you select
|
||||
the scan are from the preview window, or by hand typing the num-
|
||||
bers everything is fine. The SIGSEGV happens deep in gtk library
|
||||
(gdk). I really cannot debug it.
|
||||
|
||||
<B>Options</B> <B>too</B> <B>much</B>
|
||||
It is possible, especially for the ColorOneScanner, that the
|
||||
backend's options panel to exceed from your screen. It happens
|
||||
with mine and I am running at 1024x768 my X Server. What can I
|
||||
It is possible, especially for the ColorOneScanner, that the
|
||||
backend's options panel to exceed from your screen. It happens
|
||||
with mine and I am running at 1024x768 my X Server. What can I
|
||||
say? Try smaller fonts in the X server, or virtual screens.
|
||||
|
||||
<B>Weird</B> <B>SCSI</B> <B>behaviour.</B>
|
||||
|
|
@ -222,13 +223,13 @@
|
|||
>the Adaptec 2940UW to a dual-channel Symbios 786 chipset. When
|
||||
I started up
|
||||
|
||||
>SANE with your driver, I managed to scan line art drawings
|
||||
>SANE with your driver, I managed to scan line art drawings
|
||||
okay, but Gray16
|
||||
|
||||
>scans led to a stream of SCSI error messages on the console,
|
||||
>scans led to a stream of SCSI error messages on the console,
|
||||
ultimately
|
||||
|
||||
>hanging with a message saying the scanner wasn't releasing the
|
||||
>hanging with a message saying the scanner wasn't releasing the
|
||||
SCSI bus.
|
||||
|
||||
>This may be that the Symbios is simply less tolerant of ancient
|
||||
|
|
@ -238,32 +239,32 @@
|
|||
|
||||
</PRE>
|
||||
<H2>DEBUG</H2><PRE>
|
||||
If you encounter a GUI bug please set the environment variable
|
||||
If you encounter a GUI bug please set the environment variable
|
||||
SANE_DEBUG_APPLE to 255 and rerun the excact sequence of keystrokes and
|
||||
menu selections to reproduce it. Then send me a report with the log
|
||||
menu selections to reproduce it. Then send me a report with the log
|
||||
attached.
|
||||
|
||||
It would be very helpfull if you have handy an Apple machine (I am not
|
||||
It would be very helpfull if you have handy an Apple machine (I am not
|
||||
sure how Mackintoshs are spelled) with the AppleScanners driver
|
||||
installed and check what option are grayed out (inactive) in what modes
|
||||
and report back to me.
|
||||
|
||||
If you want to offer some help but you don't have a scanner or you
|
||||
don't have the model you would like to offer some help, or you are a
|
||||
sane developer and you just want to take a look at how the apple back-
|
||||
end looks like. Goto to apple.h and #define the NEUTRALIZE_BACKEND
|
||||
macro. You can select the scanner model through the APPLE_MODEL_SELECT
|
||||
If you want to offer some help but you don't have a scanner or you
|
||||
don't have the model you would like to offer some help, or you are a
|
||||
sane developer and you just want to take a look at how the apple back-
|
||||
end looks like. Goto to apple.h and #define the NEUTRALIZE_BACKEND
|
||||
macro. You can select the scanner model through the APPLE_MODEL_SELECT
|
||||
macro. Available options are APPLESCANNER, ONESCANNER, COLORONESCANNER.
|
||||
|
||||
If you encounter a SCSI bus error or trimmed and/or displaced images
|
||||
please also set the environment variable SANE_DEBUG_SANEI_SCSI to 255
|
||||
If you encounter a SCSI bus error or trimmed and/or displaced images
|
||||
please also set the environment variable SANE_DEBUG_SANEI_SCSI to 255
|
||||
before sendme the report.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>TODO</H2><PRE>
|
||||
<B>Non</B> <B>Blocking</B> <B>Support</B>
|
||||
Make sane-apple a non blocking backend. Properly support for
|
||||
Make sane-apple a non blocking backend. Properly support for
|
||||
<B>sane_set_io_mode</B> and <B>sane_get_select_fd</B>
|
||||
|
||||
<B>Scan</B> Make scan possible for all models in all supported modes.
|
||||
|
|
@ -278,8 +279,8 @@
|
|||
|
||||
</PRE>
|
||||
<H2>AUTHOR</H2><PRE>
|
||||
The sane-apple backend was written not entirely from scratch by Milon
|
||||
Firikis. It is mostly based on the mustek backend from David Mosberger
|
||||
The sane-apple backend was written not entirely from scratch by Milon
|
||||
Firikis. It is mostly based on the mustek backend from David Mosberger
|
||||
and Andreas Czechanowski
|
||||
|
||||
sane-backends 1.0.12-cvs 13 May 1998 <B><A HREF="sane-apple.5.html">sane-apple(5)</A></B>
|
||||
|
|
|
|||
|
|
@ -33,11 +33,11 @@
|
|||
COPISCAN II 3338(A) Simplex Scanner (with ACE)
|
||||
|
||||
If you have a Bell+Howell scanner and are able to test it with this
|
||||
backend, please contact <I>sane-devel@mostang.com</I> with the model number
|
||||
and testing results. Have a look at
|
||||
http://www.mostang.com/sane/mail.html concerning subscription to sane-
|
||||
devel. Additionally, the author is curious as to the likelihood of
|
||||
using this backend with the newer 4000 and 8000 series scanners. If
|
||||
backend, please contact <I>sane-devel@lists.alioth.debian.org</I> with the
|
||||
model number and testing results. Have a look at
|
||||
http://www.sane-project.org/mailing-lists.html concerning subscription
|
||||
to sane-devel. Additionally, the author is curious as to the likelihood
|
||||
of using this backend with the newer 4000 and 8000 series scanners. If
|
||||
you have such a beast, please let me know.
|
||||
|
||||
The Bell+Howell Copiscan II series document scanners are high volume,
|
||||
|
|
@ -487,7 +487,7 @@
|
|||
If you have found something that you think is a bug, please attempt to
|
||||
recreate it with the SANE_DEBUG_BH environment variable set to 255, and
|
||||
send a report detailing the conditions surrounding the bug to
|
||||
<I>sane-devel@mostang.com</I>.
|
||||
<I>sane-devel@lists.alioth.debian.org</I>.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
|
|||
|
|
@ -119,9 +119,9 @@
|
|||
|
||||
More general comments, suggestions, and inquiries about frontends or
|
||||
SANE should go to the SANE Developers mailing list (see
|
||||
http://www.mostang.com/sane/mail.html for details). You must be sub-
|
||||
scribed to the list, otherwise your mail won't be sent to the sub-
|
||||
scribers.
|
||||
http://www.sane-project.org/mailing-lists.html for details). You must
|
||||
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>
|
||||
</PRE>
|
||||
|
|
|
|||
|
|
@ -122,9 +122,9 @@
|
|||
|
||||
More general comments, suggestions, and inquiries about frontends or
|
||||
SANE should go to the SANE Developers mailing list (see
|
||||
http://www.mostang.com/sane/mail.html for details). You must be sub-
|
||||
scribed to the list, otherwise your mail won't be sent to the sub-
|
||||
scribers.
|
||||
http://www.sane-project.org/mailing-lists.html for details). You must
|
||||
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>
|
||||
</PRE>
|
||||
|
|
|
|||
|
|
@ -112,9 +112,9 @@
|
|||
|
||||
More general comments, suggestions, and inquiries about frontends or
|
||||
SANE should go to the SANE Developers mailing list (see
|
||||
http://www.mostang.com/sane/mail.html for details). You must be sub-
|
||||
scribed to the list, otherwise your mail won't be sent to the sub-
|
||||
scribers.
|
||||
http://www.sane-project.org/mailing-lists.html for details). You must
|
||||
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>
|
||||
</PRE>
|
||||
|
|
|
|||
|
|
@ -127,9 +127,9 @@
|
|||
|
||||
More general comments, suggestions, and inquiries about frontends or
|
||||
SANE should go to the SANE Developers mailing list (see
|
||||
http://www.mostang.com/sane/mail.html for details). You must be sub-
|
||||
scribed to the list, otherwise your mail won't be sent to the sub-
|
||||
scribers.
|
||||
http://www.sane-project.org/mailing-lists.html for details). You must
|
||||
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>
|
||||
</PRE>
|
||||
|
|
|
|||
|
|
@ -59,9 +59,9 @@
|
|||
Because Hewlett-Packard does no longer produce scanners that support
|
||||
SCL (beside the OfficeJets), the above list of supported scanners is
|
||||
complete. Other HP scanners are not supported by the "hp" backend, but
|
||||
might be supported by another one. See <I>http://www.mostang.com/sane</I>.
|
||||
might be supported by another one. See <I>http://www.sane-project.org/</I>.
|
||||
You can also watch the sane-devel mailinglist at
|
||||
<I>http://www.mostang.com/sane/mail.html</I>.
|
||||
<I>http://www.sane-project.org/mailing-lists.html</I>.
|
||||
|
||||
More details about the hp backend can be found on its homepage
|
||||
<I>http://www.kirchgessner.net/sane.html</I>.
|
||||
|
|
|
|||
|
|
@ -162,9 +162,9 @@
|
|||
setenv SANE_DEBUG_MICROTEK 128
|
||||
|
||||
More general comments, suggestions, and inquiries about frontends or
|
||||
SANE should go to <B>sane-devel@mostang.com</B>, the SANE Developers mailing
|
||||
list. Have a look at http://www.mostang.com/sane/mail.html concerning
|
||||
subscription to sane-devel.
|
||||
SANE should go to <B>sane-devel@lists.alioth.debian.org</B>, the SANE Develop-
|
||||
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>
|
||||
</PRE>
|
||||
|
|
|
|||
|
|
@ -59,7 +59,7 @@
|
|||
Scanport SQ4836 SCSI
|
||||
Scanpaq SQ2030 Parport
|
||||
|
||||
Additional information can be found at <B>http://www.mostang.com/sane/</B> <B>.</B>
|
||||
Additional information can be found at <B>http://www.sane-project.org/</B> <B>.</B>
|
||||
|
||||
If you own a Microtek scanner other than the ones listed above, it may
|
||||
or may not work with SANE! Because equal scanners are sold under dif-
|
||||
|
|
|
|||
|
|
@ -72,12 +72,12 @@
|
|||
If you own a Mustek (or Trust) scanner other than the ones listed above
|
||||
that works with this backend, please let us know by sending the scan-
|
||||
ner's exact model name (look at the front and back of the scanner) and
|
||||
a debug output to <I>sane-devel@mostang.com</I>. You can get the debug output
|
||||
by setting the environment variable <B>SANE_DEBUG_MUSTEK</B> to 5 and showing
|
||||
the list of available scanners with scanimage -L . Please send all of
|
||||
it to the mailing list. You must be subscribed to sane-devel before you
|
||||
can send mail to the list. See <I>http://www.mostang.com/sane/mail.html</I>
|
||||
for details.
|
||||
a debug output to <I>sane-devel@lists.alioth.debian.org</I>. You can get the
|
||||
debug output by setting the environment variable <B>SANE_DEBUG_MUSTEK</B> to 5
|
||||
and showing the list of available scanners with scanimage -L . Please
|
||||
send all of it to the mailing list. You must be subscribed to sane-
|
||||
devel before you can send mail to the list. See
|
||||
<I>http://www.sane-project.org/mailing-lists.html</I> for details.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
|
|||
|
|
@ -318,9 +318,10 @@
|
|||
|
||||
</PRE>
|
||||
<H2>BUGS</H2><PRE>
|
||||
Too many... please send bug reports to <I>sane-devel@mostang.com</I> (note
|
||||
that you have to subscribe first to the list before you can send
|
||||
emails... see http://www.mostang.com/sane/mail.html)
|
||||
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
|
||||
* 1505 support isn't even present
|
||||
|
|
@ -329,29 +330,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>
|
||||
|
|
|
|||
|
|
@ -31,9 +31,9 @@
|
|||
If have successfully used the PINT driver with your scanner, but it
|
||||
does not work using this SANE backend, please let us know. To do this,
|
||||
send a mail with the relevant information for your scanner to
|
||||
<I>sane-devel@mostang.com</I>. Have a look at
|
||||
http://www.mostang.com/sane/mail.html concerning subscription to sane-
|
||||
devel.
|
||||
<I>sane-devel@lists.alioth.debian.org</I>. Have a look at
|
||||
http://www.sane-project.org/mailing-lists.html concerning subscription
|
||||
to sane-devel.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
|
|||
|
|
@ -19,92 +19,19 @@
|
|||
</PRE>
|
||||
<H2>DESCRIPTION</H2><PRE>
|
||||
The <B>sane-plustek</B> library implements a SANE (Scanner Access Now Easy)
|
||||
backend that provides access to Plustek parallel port and USB flatbed
|
||||
scanners. The USB support is part of the SANE package but for usage
|
||||
with parallel port scanners you will need a kernel module, called
|
||||
pt_drv which currently can be downloaded from
|
||||
<B>http://www.gjaeger.de/scanner/plustek.html</B>
|
||||
|
||||
<B>!!!Please</B> <B>note</B> <B>that</B> <B>you</B> <B>need</B> <B>the</B> <B>kernel</B> <B>module</B> <B>only</B> <B>for</B> <B>parallel</B> <B>port</B>
|
||||
<B>scanners!!!</B>
|
||||
backend that provides access to USB flatbed scanners based on National
|
||||
Semiconductor Merlin chipsets (LM9831, 9832 and 9833). If you're look-
|
||||
ing for parallel-port support for Plustek scanner please refer to the
|
||||
<B>sane-plustek_pp</B> backend.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>PARALLEL PORT SUPPORT</H2><PRE>
|
||||
At present, the following scanners should work with this backend and
|
||||
the corresponding kernel module:
|
||||
|
||||
<B>PLUSTEK</B> <B>SCANNERS</B>
|
||||
|
||||
Parallelport Model: ASIC: Properties:
|
||||
---------------------- ----- ------------------------
|
||||
OpticPro PT12 98003 600x1200 dpi 36bit 512Kb
|
||||
OpticPro P12 98003 600x1200 dpi 36bit 512Kb
|
||||
OpticPro 9636T/12000T 98001 600x1200 dpi 36bit 512Kb
|
||||
OpticPro 12000P Turbo 98001 600x1200 dpi 36bit 512Kb
|
||||
OpticPro 9636P+/Turbo 98001 600x1200 dpi 36bit 512Kb
|
||||
OpticPro 9636P 96003 600x1200 dpi 36bit 128Kb
|
||||
OpticPro 12000P/96000P 96003 600x1200 dpi 36bit 128Kb
|
||||
OpticPro 1236P 96003 600x1200 dpi 30bit 128Kb
|
||||
OpticPro 9600P 96003 600x1200 dpi 30bit 128Kb
|
||||
OpticPro 9630P/FBIV 96003 600x1200 dpi 30bit 128Kb
|
||||
OpticPro 9630PL (14") 96003 600x1200 dpi 30bit 128Kb
|
||||
OpticPro A3I 96003 400x800 dpi 36bit 128Kb
|
||||
OpticPro 600P/6000P 96003 300x600 dpi 30bit 32Kb
|
||||
OpticPro 4831P 96003 300x600 dpi 30bit 32Kb
|
||||
OpticPro 4830P/FBIII 96003 300x600 dpi 30bit 32Kb
|
||||
OpticPro 4800P/FBII 96001 300x600 dpi 24bit 32Kb
|
||||
|
||||
<B>PRIMAX</B> <B>SCANNERS</B>
|
||||
|
||||
There are some scanners sold by Primax, but they are in fact Plustek
|
||||
devices. These scanners are also supported. The following table will
|
||||
show the relationship:
|
||||
|
||||
Model: Plustek Model: Remarks:
|
||||
--------------------------- -------------- ------------
|
||||
Colorado 4800 OpticPro 4800 not tested
|
||||
Compact 4800 Direct OpticPro 600 mov=2
|
||||
Compact 4800 Direct 30bit OpticPro 4830 mov=7
|
||||
Compact 9600 Direct 30bit OpticPro 9630 works
|
||||
|
||||
<B>GENIUS</B> <B>SCANNERS</B>
|
||||
|
||||
The following devices are sold as Genius Scanners, but are in fact
|
||||
Plustek devices. The table will show the relationship:
|
||||
|
||||
Model: Remarks:
|
||||
--------------------------- ----------------------------
|
||||
Colorpage Vivid III V2 Like P12 but has two buttons
|
||||
and Wolfson DAC
|
||||
|
||||
<B>ARIES</B> <B>SCANNERS</B>
|
||||
|
||||
There's one scanner sold as Aries Scanner, but is in fact a Plustek
|
||||
device. The following table will show the relationship:
|
||||
|
||||
Model: Plustek Model: Remarks:
|
||||
--------------------------- -------------- ------------
|
||||
Scan-It 4800 OpticPro 600 mov=2
|
||||
|
||||
<B>BrightScan</B> <B>SCANNERS</B>
|
||||
|
||||
There's one scanner sold as BrightScan OpticPro Scanner, this is also
|
||||
rebadged Plustek device. The following table will show the relation-
|
||||
ship:
|
||||
|
||||
Model: Remarks:
|
||||
--------------------------- ----------------------------
|
||||
BrightScan OpticPro OpticPro P12
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>USB SUPPORT</H2><PRE>
|
||||
<H2>SUPPORTED DEVICES</H2><PRE>
|
||||
The Backend is able to support USB scanner based on the National Semi-
|
||||
conductor chipset LM9831, LM9832 and LM9833. The following tables show
|
||||
conductor chipsets LM9831, LM9832 and LM9833. The following tables show
|
||||
various devices which are currently reported to work. If your Plustek
|
||||
scanner has another Product ID, then the device is <B>NOT</B> supported, as it
|
||||
contains unsupported ASICs inside.
|
||||
contains an unsupported ASIC inside.
|
||||
|
||||
Vendor Plustek - ID: 0x07B3
|
||||
----------------------------------------------------------
|
||||
|
|
@ -177,10 +104,11 @@
|
|||
|
||||
</PRE>
|
||||
<H2>OTHER PLUSTEK SCANNERS</H2><PRE>
|
||||
For parallelport device support see the <B>plustek_pp</B> backend.
|
||||
The SCSI scanner OpticPro 19200S is a rebadged Artec AM12S scanner and
|
||||
is supported by the <B>Artec</B> backend.
|
||||
Only the National Semiconductor LM9831/2 based devices of Plustek are
|
||||
supported by this driver. Older versions of the U12, the UT12, the
|
||||
Only the National Semiconductor LM983[1/2/] based devices of Plustek
|
||||
are supported by this driver. Older versions of the U12, the UT12, the
|
||||
U1212 and U1248 (GrandTech chipset) are not supported.
|
||||
|
||||
Model Chipset backend
|
||||
|
|
@ -189,150 +117,18 @@
|
|||
UT16B GrandTech gt68xx
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>DEVICE NAMES</H2><PRE>
|
||||
This backend expects a default device called:
|
||||
|
||||
<I>/dev/pt</I><B>_</B><I>drv</I>
|
||||
|
||||
This default device will be used, if no configuration file can be
|
||||
found.
|
||||
|
||||
The device-driver is currently not part of the SANE distribution. It
|
||||
has to be downloaded from:
|
||||
<B>http://www.gjaeger.de/scanner/plustek.html</B>
|
||||
See the INSTALL file there for a proper setup. Currently only Linux is
|
||||
supported by this driver (Kernel 2.2.x and higher).
|
||||
|
||||
As the backend and the driver support up to four devices per system, it
|
||||
is possible to specify them in the configuration file
|
||||
|
||||
<I>/usr/local/etc/sane.d/plustek.conf</I>
|
||||
|
||||
See the plustek.conf file for examples.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONFIGURATION</H2><PRE>
|
||||
The configuration of this backend can be divided into two sections:
|
||||
|
||||
<B>CONFIGURATION</B> <B>-</B> <B>parallel</B> <B>port</B> <B>scanner</B>
|
||||
|
||||
<B>CONFIGURATION</B> <B>-</B> <B>USB</B> <B>scanner</B>
|
||||
|
||||
Please make sure, that the configuration matches the real world, namely
|
||||
your configuration. And note again, .I pt_drv is only needed
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONFIGURATION - PARALLEL PORT SCANNER</H2><PRE>
|
||||
Beside the kernel-module options, which are described below, you need
|
||||
to enable the parallel port device in the configuration file
|
||||
|
||||
<I>/usr/local/etc/sane.d/plustek.conf</I>
|
||||
|
||||
For a proper setup, you will need at least two entries:
|
||||
|
||||
<I>[parport]</I>
|
||||
|
||||
<I>device</I> <I>/dev/pt</I><B>_</B><I>drv</I>
|
||||
|
||||
<I>parport</I> tells the backend, that the following devicename (here
|
||||
<I>/dev/pt</I><B>_</B><I>drv</I> ) has to be interpreted as parallel port scanner device.
|
||||
|
||||
To have this device, you will need to setup the kernel module. As the
|
||||
driver is a loadable kernel module, it is configured by invoking insmod
|
||||
with the appropriate parameters or appending the options to the file
|
||||
<B>/etc/conf.modules</B>
|
||||
|
||||
<B>The</B> <B>Options:</B>
|
||||
lampoff=lll
|
||||
The value <I>lll</I> tells the driver, after how many seconds to
|
||||
switch-off the lamp(s). The default value is 180. 0 will dis-
|
||||
able this feature.
|
||||
<B>HINT:</B> Do not use a value that is too small, because often
|
||||
switching on/off the lamps will reduce their lifetime.
|
||||
|
||||
port=ppp
|
||||
<I>ppp</I> specifies the port base address, where the scanner is con-
|
||||
nected to. The default value is 0x378 which normaly is standard.
|
||||
|
||||
warmup=www
|
||||
<I>www</I> specifies the time in seconds, how long a lamp has to be on,
|
||||
until the driver will start to scan. The default value is 30.
|
||||
|
||||
lOffonEnd=e
|
||||
<I>e</I> specifies the behaviour when unloading the driver, 1 -->
|
||||
switch lamps off, 0 --> do not change lamp status
|
||||
|
||||
slowIO=s
|
||||
<I>s</I> specifies which I/O functions the driver should use, 1 --> use
|
||||
delayed functions, 0 --> use the non-delayed ones
|
||||
|
||||
forceMode=fm
|
||||
<I>fm</I> specifies port mode which should be used, 0 --> autodetec-
|
||||
tion, 1 --> use SPP mode and 2 --> use EPP mode
|
||||
|
||||
mov=m
|
||||
<I>m</I> =0 - default: no override
|
||||
<I>m</I> =1 - OpticPro 9630PL override (works if OP9630
|
||||
has been detected) forces legal size (14")
|
||||
<I>m</I> =2 - Primax 4800Direct override (works if OP600
|
||||
has been detected) swaps red/green color
|
||||
<I>m</I> =3 - OpticPro 9636 override (works if OP9636 has
|
||||
been detected) disables backends
|
||||
transparency/negativ capabilities
|
||||
<I>m</I> =4 - OpticPro 9636P override (works if OP9636 has
|
||||
been detected) disables backends
|
||||
transparency/negativ capabilities
|
||||
<I>m</I> =5 - OpticPro A3I override (works if OP12000 has
|
||||
been detected) enables A3 scanning
|
||||
<I>m</I> =6 - OpticPro 4800P override (works if OP600
|
||||
has been detected) swaps red/green color
|
||||
<I>m</I> =7 - Primax 4800Direct 30bit override (works if OP4830
|
||||
has been detected)
|
||||
|
||||
Sample entry for file <B>/etc/modules.conf</B> :
|
||||
<I>alias</I> <I>char-major-40</I> <I>pt</I><B>_</B><I>drv</I>
|
||||
<I>pre-install</I> <I>pt</I><B>_</B><I>drv</I> <I>modprobe</I> <I>-k</I> <I>parport</I>
|
||||
<I>options</I> <I>pt</I><B>_</B><I>drv</I> <I>lampoff=180</I> <I>warmup=15</I> <I>port=0x378</I> <I>lOffonEnd=0</I> <I>mov=0</I>
|
||||
<I>slowIO=0</I> <I>forceMode=0</I>
|
||||
|
||||
For multidevice support, simply add values separated by commas to the
|
||||
different options
|
||||
<I>options</I> <I>pt</I><B>_</B><I>drv</I> <I>port=0x378,0x278</I> <I>mov=0,4</I> <I>slowIO=0,1</I> <I>forceMode=0,1</I>
|
||||
|
||||
Remember to call depmod after changing /etc/conf.modules.
|
||||
|
||||
<B>PARALLEL</B> <B>PORT</B> <B>MODES</B>
|
||||
|
||||
The current driver works best, when the parallel port has been set to
|
||||
EPP-mode. When detecting any other mode such as ECP or PS/2 the driver
|
||||
tries to set to a faster, supported mode. If this fails, it will use
|
||||
the SPP mode, as this mode should work with all Linux supported paral-
|
||||
lel ports.
|
||||
|
||||
Former Plustek scanner models (4830, 9630) supplied a ISA parallel port
|
||||
adapter card. This card is <B>not</B> supported by the driver.
|
||||
|
||||
The ASIC 96001/3 based models have sometimes trouble with high resolu-
|
||||
tion modes. If you encounter sporadic corrupted images (parts dupli-
|
||||
cated or shifted horizontally) kill all other applications before scan-
|
||||
ning and (if sufficient memory available) disable swapping.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONFIGURATION - USB SCANNER</H2><PRE>
|
||||
To use the USB device with this backend, you need at least two entries
|
||||
in the configuration file
|
||||
To use your scanner with this backend, you need at least two entries in
|
||||
the configuration file
|
||||
<I>/usr/local/etc/sane.d/plustek.conf</I>
|
||||
|
||||
<I>[usb]</I> <I>vendor-id</I> <I>product-id</I>
|
||||
<I>[merlin-device]</I> <I>vendor-id</I> <I>product-id</I>
|
||||
|
||||
<I>device</I> <I>/dev/usbscanner</I>
|
||||
|
||||
<I>usb</I> tells the backend, that the following devicename (here
|
||||
<I>/dev/usbscanner</I> ) has to be interpreted as USB scanner device. If ven-
|
||||
<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>
|
||||
then the next matching device is used.
|
||||
|
|
@ -343,7 +139,7 @@
|
|||
<I>t</I> specifies the warmup period in seconds
|
||||
|
||||
option lampOff t
|
||||
<I>t</I> is the time in seconds for switching off the lamps in standby
|
||||
<I>t</I> is the time in seconds for switching off the lamps in standby
|
||||
mode
|
||||
|
||||
option lOffonEnd b
|
||||
|
|
@ -351,15 +147,32 @@
|
|||
lamps off, 0 --> do not change lamp status
|
||||
|
||||
option invertNegatives b
|
||||
<I>b</I> 0 --> do not invert the picture during negativ scans, 1 -->
|
||||
<I>b</I> 0 --> do not invert the picture during negativ scans, 1 -->
|
||||
invert picture
|
||||
|
||||
option cacheCalData b
|
||||
<I>b</I> 0 --> do not save coarse calibration results, 1 --> save
|
||||
results of coarse calibration in ~/.sane/ directory
|
||||
|
||||
option altCalibrate b
|
||||
<I>b</I> 0 --> use standard calibration routines, 1 --> use alternate
|
||||
calibration (only non Plustek
|
||||
devices, standard for CIS devices)
|
||||
|
||||
option skipFine b
|
||||
<I>b</I> 0 --> perform fine calibration, 1 --> skip fine calibration
|
||||
(only non Plustek devices)
|
||||
|
||||
option skipFineWhite b
|
||||
<I>b</I> 0 --> perform white fine calibration, 1 --> skip white fine
|
||||
calibration (only non Plustek devices)
|
||||
|
||||
option skipCalibration b
|
||||
<I>b</I> 0 --> perform calibration, 1 --> skip calibration (only non
|
||||
<I>b</I> 0 --> perform calibration, 1 --> skip calibration (only non
|
||||
Plustek devices)
|
||||
|
||||
option enableTPA b
|
||||
<I>b</I> 0 --> default behaviour, specified by the internal tables, 1
|
||||
<I>b</I> 0 --> default behaviour, specified by the internal tables, 1
|
||||
--> override internal tables and allow TPA mode (EPSON only)
|
||||
|
||||
option posOffX x
|
||||
|
|
@ -368,14 +181,14 @@
|
|||
option tpaOffY y
|
||||
option negOffX x
|
||||
option negOffY y
|
||||
<I>x</I> <I>y</I> By using this settings, the user can adjust the given image
|
||||
<I>x</I> <I>y</I> By using this settings, the user can adjust the given image
|
||||
positions. <B>Please</B> <B>note,</B> <B>that</B> <B>there's</B> <B>no</B> <B>internal</B> <B>range</B> <B>checking</B>
|
||||
<B>for</B> <B>this</B> <B>feature.</B>
|
||||
|
||||
option posShadingY p
|
||||
option tpaShadingY p
|
||||
option negShadingY p
|
||||
<I>p</I> overrides the internal shading position. The values are in
|
||||
<I>p</I> overrides the internal shading position. The values are in
|
||||
steps. <B>Please</B> <B>note,</B> <B>that</B> <B>there's</B> <B>no</B> <B>internal</B> <B>range</B> <B>checking</B> <B>for</B>
|
||||
<B>this</B> <B>feature.</B>
|
||||
|
||||
|
|
@ -391,22 +204,27 @@
|
|||
option green_gain g
|
||||
option blue_gain b
|
||||
<I>r</I> <I>g</I> <I>b</I> These values can be used to adjust the internally detected
|
||||
gain values of the AFE for each channel. The range is between 0
|
||||
gain values of the AFE for each channel. The range is between 0
|
||||
and 63.
|
||||
|
||||
|
||||
See the plustek.conf file for examples.
|
||||
|
||||
<B>Note:</B>
|
||||
You have to make sure, that the USB subsystem is loaded correctly and
|
||||
the module <I>scanner</I> has been loaded too. To make this module recognize
|
||||
your scanner, you might have to add the following line to your
|
||||
You have to make sure, that the USB subsystem is loaded correctly and
|
||||
the module <I>scanner</I> has been loaded too. To make this module recognize
|
||||
your scanner, you might have to add the following line to your
|
||||
<B>/etc/modules.conf</B> :
|
||||
<I>options</I> <I>scanner</I> <I>vendor=0x7b3</I> <I>product=0x17</I>
|
||||
|
||||
If you're not sure about the vendor and product id of your device, sim-
|
||||
ply load the USB subsystem and plug in your scanner. Then do a <I>cat</I>
|
||||
ply load the USB subsystem and plug in your scanner. Then do a <I>cat</I>
|
||||
<I>/proc/bus/usb/devices</I> and look for the scanner.
|
||||
Alternatively, the backend is able to access your scanner via libusb.
|
||||
You might use <B>sane-find-scanner</B> to check that you have access to your
|
||||
device.
|
||||
|
||||
<B>Note:</B>
|
||||
If there's no configuration file, the backend defaults to <B>device</B> <B>auto</B>
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -421,9 +239,6 @@
|
|||
The shared library implementing this backend (present on systems
|
||||
that support dynamic loading).
|
||||
|
||||
<I>/lib/modules/<Kernel-Version>/misc/pt</I><B>_</B><I>drv.o</I>
|
||||
The Linux Kernelmodule.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONTACT AND BUG-REPORTS</H2><PRE>
|
||||
|
|
@ -439,24 +254,19 @@
|
|||
or directly from the projects' homepage at:
|
||||
<B>http://www.gjaeger.de/scanner/plustek.html</B>
|
||||
|
||||
To obtain debug messages from the backend, please set the environment-
|
||||
variable <I>SANE</I><B>_</B><I>DEBUG</I><B>_</B><I>PLUSTEK</I> before calling your favorite scan-frontend
|
||||
To obtain debug messages from the backend, please set the environment-
|
||||
variable <I>SANE</I><B>_</B><I>DEBUG</I><B>_</B><I>PLUSTEK</I> before calling your favorite scan-frontend
|
||||
(i.e. xscanimage).
|
||||
<B>i.e.:</B> <B>export</B> <B>SANE_DEBUG_PLUSTEK=20</B> <B>;</B> <B>xscanimage</B>
|
||||
|
||||
The value controls the verbosity of the backend. Please note, that val-
|
||||
ues greater than 19 force the backend to output raw data files, which
|
||||
could be rather large. The ending of these files is ".raw". For prob-
|
||||
ues greater than 19 force the backend to output raw data files, which
|
||||
could be rather large. The ending of these files is ".raw". For prob-
|
||||
lem reports it should be enough the set the verbosity to 13.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>KNOWN BUGS & RESTRICTIONS</H2><PRE>
|
||||
* The Halftoning works, but the quality is poor
|
||||
* Printers (especially HP models) will start to
|
||||
print during scanning. This in fact is a problem
|
||||
to other printers too, using bidirectional protocol
|
||||
(see www.plustek.com (TAIWAN) page for further details)
|
||||
* The driver does not support these manic scalings up
|
||||
to 16 times the physical resolution. The only scaling
|
||||
is done on resolutions between the physical resolution
|
||||
|
|
@ -464,33 +274,15 @@
|
|||
600x1200 dpi scanner and you are scanning using 800dpi,
|
||||
so scaling is necesary, because the sensor only delivers
|
||||
600dpi but the motor is capable to perform 800dpi steps.
|
||||
* On some devices, the pictures seems to be bluished
|
||||
|
||||
ASIC 98001 based models:
|
||||
* The 300dpi transparency and negative mode does not work
|
||||
correctly.
|
||||
* There is currently no way to distinguish a model with
|
||||
and without transpareny unit.
|
||||
* The scanned images seem to be too dark (P9636T)
|
||||
|
||||
ASIC 96003/1 based models:
|
||||
* 30bit mode is currently not supported.
|
||||
* On low-end systems and under heavy system load, the
|
||||
driver will loosing data, this might causes the sensor
|
||||
to hit the scan-bed and/or the picture is corrupted.
|
||||
* The scanspeed on 600x1200 dpi models is slow.
|
||||
* The scanquality of the A3I is poor
|
||||
|
||||
USB models:
|
||||
* Plusteks' model policy is somewhat inconsistent. This
|
||||
means, they sell technical different devices under the
|
||||
same product name. Therefore it is possible that some
|
||||
devices like the UT12 or U12 won't work - please check
|
||||
the model list above and compare the product-id to
|
||||
the one your device has.
|
||||
* Negative scanning quality is poor.
|
||||
* Negative/Slide scanning quality is poor.
|
||||
|
||||
sane-backends 1.0.12-cvs 17 September 2003 <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
|
||||
sane-backends 1.0.12-cvs 24 September 2003 <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -7,32 +7,29 @@
|
|||
<HR>
|
||||
<PRE>
|
||||
<!-- Manpage converted by man2html 3.0.1 -->
|
||||
<B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
|
||||
<B><A HREF="sane-plustek_pp.5.html">sane-plustek_pp(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-plustek_pp.5.html">sane-plustek_pp(5)</A></B>
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>NAME</H2><PRE>
|
||||
sane-plustek - SANE backend for Plustek parallel port and LM983[1/2/3]
|
||||
based USB flatbed scanners
|
||||
sane-plustek_pp - SANE backend for Plustek parallel port flatbed scan-
|
||||
ners
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>DESCRIPTION</H2><PRE>
|
||||
The <B>sane-plustek</B> library implements a SANE (Scanner Access Now Easy)
|
||||
backend that provides access to Plustek parallel port and USB flatbed
|
||||
scanners. The USB support is part of the SANE package but for usage
|
||||
with parallel port scanners you will need a kernel module, called
|
||||
pt_drv which currently can be downloaded from
|
||||
<B>http://www.gjaeger.de/scanner/plustek.html</B>
|
||||
|
||||
<B>!!!Please</B> <B>note</B> <B>that</B> <B>you</B> <B>need</B> <B>the</B> <B>kernel</B> <B>module</B> <B>only</B> <B>for</B> <B>parallel</B> <B>port</B>
|
||||
<B>scanners!!!</B>
|
||||
The <B>sane-plustek_pp</B> library implements a SANE (Scanner Access Now Easy)
|
||||
backend that provides access to Plustek ASIC 9600[1/3] and P9800[1/3]
|
||||
based parallel port flatbed scanners. The access of the scanner is
|
||||
either done directly by the backend or via kernel module, called pt_drv
|
||||
which can be created out of the plustek_pp backend code - see also sec-
|
||||
tion <B>BUILDING</B> <B>THE</B> <B>KERNEL</B> <B>MODULE</B> for further information.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>PARALLEL PORT SUPPORT</H2><PRE>
|
||||
At present, the following scanners should work with this backend and
|
||||
the corresponding kernel module:
|
||||
<H2>SUPPORTED DEVICES</H2><PRE>
|
||||
At present, the following scanners should work with this backend and/or
|
||||
the kernel module:
|
||||
|
||||
<B>PLUSTEK</B> <B>SCANNERS</B>
|
||||
|
||||
|
|
@ -89,7 +86,7 @@
|
|||
|
||||
<B>BrightScan</B> <B>SCANNERS</B>
|
||||
|
||||
There's one scanner sold as BrightScan OpticPro Scanner, this is also
|
||||
There's one scanner sold as BrightScan OpticPro Scanner, this is also a
|
||||
rebadged Plustek device. The following table will show the relation-
|
||||
ship:
|
||||
|
||||
|
|
@ -98,146 +95,47 @@
|
|||
BrightScan OpticPro OpticPro P12
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>USB SUPPORT</H2><PRE>
|
||||
The Backend is able to support USB scanner based on the National Semi-
|
||||
conductor chipset LM9831, LM9832 and LM9833. The following tables show
|
||||
various devices which are currently reported to work. If your Plustek
|
||||
scanner has another Product ID, then the device is <B>NOT</B> supported, as it
|
||||
contains unsupported ASICs inside.
|
||||
|
||||
Vendor Plustek - ID: 0x07B3
|
||||
----------------------------------------------------------
|
||||
USB Model: ASIC: Properties: Prod-ID
|
||||
----------------------------------------------------------
|
||||
OpticPro U12 LM9831 600x1200dpi 42bit 512Kb 0x0010
|
||||
OpticPro UT12 LM9831 600x1200dpi 42bit 512Kb 0x0013
|
||||
OpticPro UT12 LM9832 600x1200dpi 42bit 512Kb 0x0017
|
||||
OpticPro UT16 LM9832 600x1200dpi 42bit 512Kb 0x0017
|
||||
OpticPro U24 LM9831 1200x2400dpi 42bit 2Mb 0x0011
|
||||
OpticPro U24 LM9832 1200x2400dpi 42bit 2Mb 0x0015
|
||||
OpticPro UT24 LM9832 1200x2400dpi 42bit 2Mb 0x0017
|
||||
|
||||
Vendor KYE/Genius - ID: 0x0458
|
||||
----------------------------------------------------------
|
||||
USB Model: ASIC: Properties: Prod-ID
|
||||
----------------------------------------------------------
|
||||
Colorpage HR6 V2 LM9832 600x1200dpi 42bit 512Kb 0x2007
|
||||
Colorpage HR6 V2 LM9832 600x1200dpi 42bit 512Kb 0x2008
|
||||
Colorpage HR6A LM9832 600x1200dpi 42bit 512Kb 0x2009
|
||||
Colorpage HR7 LM9832 600x1200dpi 42bit 512Kb 0x2013
|
||||
Colorpage HR7LE LM9832 600x1200dpi 42bit 512Kb 0x2015
|
||||
Colorpage HR6X LM9832 600x1200dpi 42bit 512Kb 0x2016
|
||||
|
||||
Vendor Hewlett-Packard - ID: 0x03F0
|
||||
----------------------------------------------------------
|
||||
USB Model: ASIC: Properties: Prod-ID
|
||||
----------------------------------------------------------
|
||||
ScanJet 2100C LM9831 600x1200dpi 42bit 512Kb 0x0505
|
||||
ScanJet 2200C LM9832 600x1200dpi 42bit 512Kb 0x0605
|
||||
|
||||
Vendor Mustek - ID: 0x0400
|
||||
----------------------------------------------------------
|
||||
USB Model: ASIC: Properties: Prod-ID
|
||||
----------------------------------------------------------
|
||||
BearPaw 1200 LM9831 600x1200dpi 42bit 512Kb 0x1000
|
||||
BearPaw 2400 LM9832 1200x2400dpi 42bit 2Mb 0x1001
|
||||
|
||||
Vendor UMAX - ID: 0x1606
|
||||
----------------------------------------------------------
|
||||
USB Model: ASIC: Properties: Prod-ID
|
||||
----------------------------------------------------------
|
||||
UMAX 3400/3450 LM9832 600x1200dpi 42bit 512Kb 0x0060
|
||||
UMAX 5400 LM9832 1200x2400dpi 42bit 512Kb 0x0160
|
||||
|
||||
Vendor COMPAQ - ID: 0x049F
|
||||
----------------------------------------------------------
|
||||
USB Model: ASIC: Properties: Prod-ID
|
||||
----------------------------------------------------------
|
||||
S4-100 LM9832 600x1200dpi 42bit 512Kb 0x001A
|
||||
|
||||
Vendor Epson - ID: 0x04B8
|
||||
----------------------------------------------------------
|
||||
USB Model: ASIC: Properties: Prod-ID
|
||||
----------------------------------------------------------
|
||||
Perfection 1250 LM9832 1200x2400dpi 42bit 512Kb 0x010F
|
||||
Perfection 1260 LM9832 1200x2400dpi 42bit 512Kb 0x011D
|
||||
|
||||
Vendor CANON - ID: 0x04A9
|
||||
----------------------------------------------------------
|
||||
USB Model: ASIC: Properties: Prod-ID
|
||||
----------------------------------------------------------
|
||||
CanoScan N650/656U LM9832 600x1200dpi 42bit 512Kb 0x2206
|
||||
CanoScan N1220U LM9832 1200x2400dpi 42bit 512Kb 0x2207
|
||||
CanoScan N670/676U LM9833 600x1200dpi 48bit 512Kb 0x220D
|
||||
CanoScan N1240U LM9833 1200x2400dpi 48bit 512Kb 0x220E
|
||||
CanoScan LIDE20 LM9833 600x1200dpi 48bit 512Kb 0x220D
|
||||
CanoScan LIDE30 LM9833 1200x2400dpi 48bit 512Kb 0x220E
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>OTHER PLUSTEK SCANNERS</H2><PRE>
|
||||
The SCSI scanner OpticPro 19200S is a rebadged Artec AM12S scanner and
|
||||
is supported by the <B>Artec</B> backend.
|
||||
Only the National Semiconductor LM9831/2 based devices of Plustek are
|
||||
supported by this driver. Older versions of the U12, the UT12, the
|
||||
U1212 and U1248 (GrandTech chipset) are not supported.
|
||||
|
||||
Model Chipset backend
|
||||
---------------------------
|
||||
U1248 GrandTech gt68xx
|
||||
UT16B GrandTech gt68xx
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>DEVICE NAMES</H2><PRE>
|
||||
This backend expects a default device called:
|
||||
This backend works in two modes, the so called "direct-mode" and the
|
||||
"kernel-mode". In direct-mode, the user-space backend is used, in ker-
|
||||
nel-mode, you should have a kernel-module named pt_drv loaded. This
|
||||
backends default device is:
|
||||
|
||||
<I>/dev/pt</I><B>_</B><I>drv</I>
|
||||
<I>0x378</I>
|
||||
|
||||
This default device will be used, if no configuration file can be
|
||||
found.
|
||||
This "default device" will be used, if no configuration file can be
|
||||
found. It is rather the base address of the parallel port on i386
|
||||
machines.
|
||||
|
||||
The device-driver is currently not part of the SANE distribution. It
|
||||
has to be downloaded from:
|
||||
<B>http://www.gjaeger.de/scanner/plustek.html</B>
|
||||
See the INSTALL file there for a proper setup. Currently only Linux is
|
||||
supported by this driver (Kernel 2.2.x and higher).
|
||||
As the backend supports up to four devices, it is possible to specify
|
||||
them in the configuration file
|
||||
|
||||
As the backend and the driver support up to four devices per system, it
|
||||
is possible to specify them in the configuration file
|
||||
<I>/usr/local/etc/sane.d/plustek</I><B>_</B><I>pp.conf</I>
|
||||
|
||||
<I>/usr/local/etc/sane.d/plustek.conf</I>
|
||||
|
||||
See the plustek.conf file for examples.
|
||||
See the plustek_pp.conf file for examples.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONFIGURATION</H2><PRE>
|
||||
The configuration of this backend can be divided into two sections:
|
||||
|
||||
<B>CONFIGURATION</B> <B>-</B> <B>parallel</B> <B>port</B> <B>scanner</B>
|
||||
|
||||
<B>CONFIGURATION</B> <B>-</B> <B>USB</B> <B>scanner</B>
|
||||
|
||||
Please make sure, that the configuration matches the real world, namely
|
||||
your configuration. And note again, .I pt_drv is only needed
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONFIGURATION - PARALLEL PORT SCANNER</H2><PRE>
|
||||
Beside the kernel-module options, which are described below, you need
|
||||
to enable the parallel port device in the configuration file
|
||||
|
||||
<I>/usr/local/etc/sane.d/plustek.conf</I>
|
||||
<I>/usr/local/etc/sane.d/plustek</I><B>_</B><I>pp.conf</I>
|
||||
|
||||
For a proper setup, you will need at least two entries:
|
||||
|
||||
<I>[parport]</I>
|
||||
<I>[direct]</I>
|
||||
|
||||
<I>device</I> <I>0x378</I>
|
||||
|
||||
or
|
||||
|
||||
<I>[kernel]</I>
|
||||
|
||||
<I>device</I> <I>/dev/pt</I><B>_</B><I>drv</I>
|
||||
|
||||
<I>parport</I> tells the backend, that the following devicename (here
|
||||
<I>direct</I> tells the backend, that the following devicename (here
|
||||
<I>/dev/pt</I><B>_</B><I>drv</I> ) has to be interpreted as parallel port scanner device.
|
||||
|
||||
To have this device, you will need to setup the kernel module. As the
|
||||
|
|
@ -320,104 +218,24 @@
|
|||
cated or shifted horizontally) kill all other applications before scan-
|
||||
ning and (if sufficient memory available) disable swapping.
|
||||
|
||||
See the plustek_pp.conf file for examples.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONFIGURATION - USB SCANNER</H2><PRE>
|
||||
To use the USB device with this backend, you need at least two entries
|
||||
in the configuration file
|
||||
<I>/usr/local/etc/sane.d/plustek.conf</I>
|
||||
|
||||
<I>[usb]</I> <I>vendor-id</I> <I>product-id</I>
|
||||
|
||||
<I>device</I> <I>/dev/usbscanner</I>
|
||||
|
||||
<I>usb</I> tells the backend, that the following devicename (here
|
||||
<I>/dev/usbscanner</I> ) has to be interpreted as USB scanner device. If ven-
|
||||
dor- and product-id has not been specified, the backend tries to detect
|
||||
this by its own. If device ist set to <I>auto</I>
|
||||
then the next matching device is used.
|
||||
|
||||
<B>The</B> <B>Options:</B>
|
||||
|
||||
option warmup t
|
||||
<I>t</I> specifies the warmup period in seconds
|
||||
|
||||
option lampOff t
|
||||
<I>t</I> is the time in seconds for switching off the lamps in standby
|
||||
mode
|
||||
|
||||
option lOffonEnd b
|
||||
<I>b</I> specifies the behaviour when closing the backend, 1 --> switch
|
||||
lamps off, 0 --> do not change lamp status
|
||||
|
||||
option invertNegatives b
|
||||
<I>b</I> 0 --> do not invert the picture during negativ scans, 1 -->
|
||||
invert picture
|
||||
|
||||
option skipCalibration b
|
||||
<I>b</I> 0 --> perform calibration, 1 --> skip calibration (only non
|
||||
Plustek devices)
|
||||
|
||||
option enableTPA b
|
||||
<I>b</I> 0 --> default behaviour, specified by the internal tables, 1
|
||||
--> override internal tables and allow TPA mode (EPSON only)
|
||||
|
||||
option posOffX x
|
||||
option posOffY y
|
||||
option tpaOffX x
|
||||
option tpaOffY y
|
||||
option negOffX x
|
||||
option negOffY y
|
||||
<I>x</I> <I>y</I> By using this settings, the user can adjust the given image
|
||||
positions. <B>Please</B> <B>note,</B> <B>that</B> <B>there's</B> <B>no</B> <B>internal</B> <B>range</B> <B>checking</B>
|
||||
<B>for</B> <B>this</B> <B>feature.</B>
|
||||
|
||||
option posShadingY p
|
||||
option tpaShadingY p
|
||||
option negShadingY p
|
||||
<I>p</I> overrides the internal shading position. The values are in
|
||||
steps. <B>Please</B> <B>note,</B> <B>that</B> <B>there's</B> <B>no</B> <B>internal</B> <B>range</B> <B>checking</B> <B>for</B>
|
||||
<B>this</B> <B>feature.</B>
|
||||
|
||||
option redGamma r
|
||||
option greenGamma g
|
||||
option blueGamma b
|
||||
option grayGamma gr
|
||||
<I>r</I> <I>g</I> <I>b</I> <I>gr</I>
|
||||
By using these values, the internal linear gamma table (r,g,b,gr = 1.0)
|
||||
can be adjusted.
|
||||
|
||||
option red_gain r
|
||||
option green_gain g
|
||||
option blue_gain b
|
||||
<I>r</I> <I>g</I> <I>b</I> These values can be used to adjust the internally detected
|
||||
gain values of the AFE for each channel. The range is between 0
|
||||
and 63.
|
||||
|
||||
|
||||
See the plustek.conf file for examples.
|
||||
|
||||
<B>Note:</B>
|
||||
You have to make sure, that the USB subsystem is loaded correctly and
|
||||
the module <I>scanner</I> has been loaded too. To make this module recognize
|
||||
your scanner, you might have to add the following line to your
|
||||
<B>/etc/modules.conf</B> :
|
||||
<I>options</I> <I>scanner</I> <I>vendor=0x7b3</I> <I>product=0x17</I>
|
||||
|
||||
If you're not sure about the vendor and product id of your device, sim-
|
||||
ply load the USB subsystem and plug in your scanner. Then do a <I>cat</I>
|
||||
<I>/proc/bus/usb/devices</I> and look for the scanner.
|
||||
<H2>BUILDING THE KERNEL MODULE</H2><PRE>
|
||||
As mentioned before, the plustek_pp backend code can also be compiled
|
||||
and installed as linux kernel module...
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>FILES</H2><PRE>
|
||||
<I>/usr/local/etc/sane.d/plustek.conf</I>
|
||||
<I>/usr/local/etc/sane.d/plustek</I><B>_</B><I>pp.conf</I>
|
||||
The backend configuration file
|
||||
|
||||
<I>/usr/local/lib/sane/libsane-plustek.a</I>
|
||||
<I>/usr/local/lib/sane/libsane-plustek</I><B>_</B><I>pp.a</I>
|
||||
The static library implementing this backend.
|
||||
|
||||
<I>/usr/local/lib/sane/libsane-plustek.so</I>
|
||||
<I>/usr/local/lib/sane/libsane-plustek</I><B>_</B><I>pp.so</I>
|
||||
The shared library implementing this backend (present on systems
|
||||
that support dynamic loading).
|
||||
|
||||
|
|
@ -442,12 +260,9 @@
|
|||
To obtain debug messages from the backend, please set the environment-
|
||||
variable <I>SANE</I><B>_</B><I>DEBUG</I><B>_</B><I>PLUSTEK</I> before calling your favorite scan-frontend
|
||||
(i.e. xscanimage).
|
||||
<B>i.e.:</B> <B>export</B> <B>SANE_DEBUG_PLUSTEK=20</B> <B>;</B> <B>xscanimage</B>
|
||||
<B>i.e.:</B> <B>export</B> <B>SANE_DEBUG_PLUSTEK_PP=20</B> <B>;</B> <B>xscanimage</B>
|
||||
|
||||
The value controls the verbosity of the backend. Please note, that val-
|
||||
ues greater than 19 force the backend to output raw data files, which
|
||||
could be rather large. The ending of these files is ".raw". For prob-
|
||||
lem reports it should be enough the set the verbosity to 13.
|
||||
The value controls the verbosity of the backend.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -476,21 +291,12 @@
|
|||
ASIC 96003/1 based models:
|
||||
* 30bit mode is currently not supported.
|
||||
* On low-end systems and under heavy system load, the
|
||||
driver will loosing data, this might causes the sensor
|
||||
driver will loose data, this might causes the sensor
|
||||
to hit the scan-bed and/or the picture is corrupted.
|
||||
* The scanspeed on 600x1200 dpi models is slow.
|
||||
* The scanquality of the A3I is poor
|
||||
|
||||
USB models:
|
||||
* Plusteks' model policy is somewhat inconsistent. This
|
||||
means, they sell technical different devices under the
|
||||
same product name. Therefore it is possible that some
|
||||
devices like the UT12 or U12 won't work - please check
|
||||
the model list above and compare the product-id to
|
||||
the one your device has.
|
||||
* Negative scanning quality is poor.
|
||||
|
||||
sane-backends 1.0.12-cvs 17 September 2003 <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
|
||||
sane-backends 1.0.12-cvs 24 September 2003 <B><A HREF="sane-plustek_pp.5.html">sane-plustek_pp(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -31,9 +31,9 @@
|
|||
ST300 and ST600. If you own one of these scanners, or a scanner other
|
||||
than the ones listed above that works with this backend, please let us
|
||||
know by sending the scanner's model name, SCSI ID, and firmware revi-
|
||||
sion to <I>sane-devel@mostang.com</I>. Have a look at
|
||||
http://www.mostang.com/sane/mail.html concerning subscription to sane-
|
||||
devel.
|
||||
sion to <I>sane-devel@lists.alioth.debian.org</I>. Have a look at
|
||||
http://www.sane-project.org/mailing-lists.html concerning subscription
|
||||
to sane-devel.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
|
|||
|
|
@ -156,7 +156,7 @@
|
|||
sane-find-scanner is able to detect any USB scanner, actual scanning
|
||||
will only work if the scanner is supported by a SANE backend. Informa-
|
||||
tion on the level of support can be found on the SANE webpage
|
||||
(<I>http://www.mostang.com/sane/</I>), and the individual backend manpages.
|
||||
(<I>http://www.sane-project.org/</I>), and the individual backend manpages.
|
||||
|
||||
Most backends can detect USB scanners automatically using "usb" config-
|
||||
uration file lines. This method allows to identify scanners by the USB
|
||||
|
|
|
|||
|
|
@ -95,9 +95,10 @@
|
|||
<H2>BUGS:</H2><PRE>
|
||||
If more than one video card is present, a crash may occur. Frequency
|
||||
and geometry selection is missing.
|
||||
Send bug reports to the SANE mailing list: sane-devel@mostang.com. You
|
||||
must be subscribed to the list to send mail. See
|
||||
http://www.mostang.com/sane/mail.html for details.
|
||||
Send bug reports to the SANE mailing list:
|
||||
sane-devel@lists.alioth.debian.org. You must be subscribed to the list
|
||||
to send mail. See http://www.sane-project.org/mailing-lists.html for
|
||||
details.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
|
|||
176
man/sane.7.html
176
man/sane.7.html
|
|
@ -48,9 +48,9 @@
|
|||
frontend `<B>scanimage</B>'. The frontends `<B>xscanimage</B>', `<B>xcam</B>', and
|
||||
`<B>scanadf</B>' are included in the package `<B>sane-frontends</B>'. Both packages
|
||||
can be downloaded from the <B>SANE</B> homepage
|
||||
(<I>http://www.mostang.com/sane/</I>). Information about other frontends and
|
||||
(<I>http://www.sane-project.org/</I>). Information about other frontends and
|
||||
backends can be found on the frontend page
|
||||
(<I>http://www.mostang.com/sane/frontends.html</I>).
|
||||
(<I>http://www.sane-project.org/sane-frontends.html</I>).
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -67,7 +67,7 @@
|
|||
<B>SANE</B> <B>homepage</B>
|
||||
Information on all aspects of SANE including a tutorial and a link to
|
||||
the SANE FAQ can be found on the SANE homepage:
|
||||
<I>http://www.mostang.com/sane/</I>.
|
||||
<I>http://www.sane-project.org/</I>.
|
||||
|
||||
<B>SANE</B> <B>device</B> <B>lists</B>
|
||||
The <B>SANE</B> device lists contain information about the status of <B>SANE</B>
|
||||
|
|
@ -75,7 +75,7 @@
|
|||
(either supported or unsupported), please contact us. See section HOW
|
||||
CAN YOU HELP SANE for details. There are lists for specific releases
|
||||
of SANE, for the current development version and a search engine:
|
||||
<I>http://www.mostang.com/sane/sane-supported-devices.html</I>. The lists
|
||||
<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/.
|
||||
|
||||
<B>SANE</B> <B>mailing</B> <B>list</B>
|
||||
|
|
@ -84,8 +84,8 @@
|
|||
is not only intended for developers, but also for users. Since this
|
||||
is currently the only mailing list devoted to SANE, it's perfectly OK
|
||||
to ask questions that are not strictly related to SANE development.
|
||||
How to subscribe and unsubscribe:
|
||||
<I>http://www.mostang.com/sane/mail.html</I>.
|
||||
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
|
||||
|
|
@ -121,7 +121,7 @@
|
|||
|
||||
Also, have a look at the <B>sane-frontends</B> package (including <B>xscanimage</B>,
|
||||
<B>xcam</B>, and <B>scanadf</B>) and the frontend information page at
|
||||
<I>http://www.mostang.com/sane/sane-frontends.html</I>.
|
||||
<I>http://www.sane-project.org/sane-frontends.html</I>.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -260,10 +260,17 @@
|
|||
and Devcom SCSI flatbed scanners. See <B><A HREF="sane-pie.5.html">sane-pie(5)</A></B> for details.
|
||||
|
||||
<B>plustek</B>
|
||||
The SANE plustek backend supports Plustek parallel port and
|
||||
LM983[1/2/3] based USB flatbed scanners. Scanners using the LM983x
|
||||
chips include some models from Plustek, KYE/Genius, Hewlett-Packard,
|
||||
Mustek, Umax, Epson, and Canon. See <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B> for details.
|
||||
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>
|
||||
for details.
|
||||
|
||||
<B>plustek_pp</B>
|
||||
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
|
||||
<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
|
||||
|
|
@ -321,7 +328,7 @@
|
|||
<B><A HREF="sane-umax1220u.5.html">sane-umax1220u(5)</A></B> for details.
|
||||
|
||||
Also, have a look at the backend information page at
|
||||
<I>http://www.mostang.com/sane/sane-supported-devices.html</I> and the list of
|
||||
<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>.
|
||||
|
||||
|
||||
|
|
@ -341,17 +348,17 @@
|
|||
|
||||
<B>gphoto2</B>
|
||||
Backend for digital cameras supported by the gphoto2 library package.
|
||||
(See <I>http://www.gphoto.org</I> for more information and a list of sup-
|
||||
ported cameras.) Gphoto2 supports over 140 different camera models.
|
||||
However, please note that more development and testing is needed
|
||||
before all of these cameras will be supported by <B>SANE</B> backend. See
|
||||
<B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>.
|
||||
(See <I>http://www.gphoto.org</I> for more information and a list of
|
||||
supported cameras.) Gphoto2 supports over 140 different camera mod-
|
||||
els. However, please note that more development and testing is
|
||||
needed before all of these cameras will be supported by <B>SANE</B> backend.
|
||||
See <B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>.
|
||||
|
||||
<B>qcam</B>
|
||||
Backend for Connectix QuickCam cameras. See <B><A HREF="sane-qcam.5.html">sane-qcam(5)</A></B>.
|
||||
|
||||
Also, have a look at the backend information page at
|
||||
<I>http://www.mostang.com/sane/sane-supported-devices.html</I> and the list of
|
||||
<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>.
|
||||
|
||||
|
||||
|
|
@ -388,7 +395,7 @@
|
|||
for Linux) API. See <B><A HREF="sane-v4l.5.html">sane-v4l(5)</A></B><B>.</B>
|
||||
|
||||
Also, have a look at the backend information page at
|
||||
<I>http://www.mostang.com/sane/sane-supported-devices.html</I> and the list of
|
||||
<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>.
|
||||
|
||||
|
||||
|
|
@ -404,7 +411,7 @@
|
|||
</PRE>
|
||||
<H2>DEVELOPER'S DOCUMENTATION</H2><PRE>
|
||||
It's not hard to write a <B>SANE</B> backend. It can take some time, however.
|
||||
You should have basic knowledege of C and enough patience to work
|
||||
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.
|
||||
|
||||
|
|
@ -412,8 +419,8 @@
|
|||
that is used to communicate between frontends and backends. It can be
|
||||
found at <I>/usr/local/doc/sane-1.0.12-cvs/sane.ps</I> (if latex is installed
|
||||
on your system) and on the <B>SANE</B> website:
|
||||
<I>http://www.mostang.com/sane/html/</I> (HTML), or
|
||||
<I>http://www.mostang.com/sane/sane.ps</I> (Postscript).
|
||||
<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-
|
||||
|
|
@ -421,8 +428,8 @@
|
|||
<I>http://sanei.meier-geinitz.de/</I>. Before a new backend or frontend
|
||||
project is started, have a look at
|
||||
<I>/usr/local/doc/sane-1.0.12-cvs/PROJECTS</I> for projects that are planned
|
||||
or not yet included into the <B>SANE</B> distribution and at the todo list:
|
||||
<I>/usr/local/doc/sane-1.0.12-cvs/TODO</I>.
|
||||
or not yet included into the <B>SANE</B> distribution and at our bug-tracking
|
||||
system: <I>http://www.http://www.sane-project.org/bugs.html</I>.
|
||||
|
||||
There are some links on how to find out about the protocol of a scan-
|
||||
ner: <I>http://www.meier-geinitz.de/sane/misc/develop.html</I>.
|
||||
|
|
@ -474,7 +481,7 @@
|
|||
build instructions in the <B>README</B> file and the individual manual pages
|
||||
of the backends.
|
||||
|
||||
Another reason for not beeing detected by <B>scanimage</B> <B>-L</B> may be a missing
|
||||
Another reason for not being detected by <B>scanimage</B> <B>-L</B> may be a missing
|
||||
or wrong configuration in the backend's configuration file. While <B>SANE</B>
|
||||
tries to automatically find most scanners, some can't be setup cor-
|
||||
rectly without the intervention of the administrator. Also on some
|
||||
|
|
@ -499,7 +506,7 @@
|
|||
<B>scanimage</B> <B>--help</B>. If scanning aborts with an error message, turn on
|
||||
debugging as mentioned above. Maybe the configuration file needs some
|
||||
tuning, e.g. to setup the path to a firmware that is needed by some
|
||||
scanners. See the backend's maunal page for details. If you can't find
|
||||
scanners. See the backend's manual page for details. If you can't find
|
||||
out what's wrong, contact sane-devel.
|
||||
|
||||
To check that the <B>SANE</B> libraries are installed correctly you can use
|
||||
|
|
@ -525,103 +532,40 @@
|
|||
|
||||
</PRE>
|
||||
<H2>HOW CAN YOU HELP SANE</H2><PRE>
|
||||
We appreciate any help we can get. Here are some topics on which you
|
||||
can work:
|
||||
|
||||
<B>Writing</B> <B>backends</B>
|
||||
Without a backend, a scanner doesn't work. So it's crucial we
|
||||
have backends for as much devices as possible. It's not neces-
|
||||
sary to be an experienced programmer to start writing a backend.
|
||||
If you have an unsupported scanner, writing a backend yourself
|
||||
is probably the only way to get it supported. See DEVELOPER'S
|
||||
DOCUMENTATION for details. But first make sure that you get any
|
||||
information about your scanner that is available (see below),
|
||||
and check if your scanner can be supported by an already exist-
|
||||
ing backend with only small modifications.
|
||||
|
||||
<B>Writing</B> <B>frontends</B>
|
||||
There are already some very capable frontends. So helping with
|
||||
improving the existing frontends may make more sense than to
|
||||
write yet another one. On the other hand there may be reasons to
|
||||
start writing a completely new frontend, like support for a spe-
|
||||
cific widget set, a programming language or a special type of
|
||||
devices (e.g. cameras, slide scanners). In any case, keep the
|
||||
sane-devel mailinglist informed of your plans.
|
||||
|
||||
<B>Reporting</B> <B>unsupported</B> <B>scanners</B>
|
||||
Even if you can't write a backend for your unsupported scanner,
|
||||
please send us all the information you have about it. We need
|
||||
the make and the model name of your scanner. Also provide an
|
||||
output of <B>sane-find-scanner</B> <B>-v</B> <B>-v</B>. For Linux: If it's a SCSI
|
||||
scanner, show us the output of <B>cat</B> <B>/proc/scsi/scsi</B>, for a USB
|
||||
scanner: <B>cat</B> <B>/proc/bus/usb/devices</B> (if the file is not there, do
|
||||
<B>mount</B> <B>-t</B> <B>usbdevfs</B> <B>/proc/bus/usb</B> <B>/proc/bus/usb</B>). See CONTACT
|
||||
section.
|
||||
|
||||
<B>Reporting</B> <B>bugs</B> <B>and</B> <B>missing</B> <B>features</B>
|
||||
If you think something in <B>SANE</B> isn't working as it should,
|
||||
please don't hesiate to contact us (see COTACT scetion). Please
|
||||
provide as many details as possible. Describe which software you
|
||||
are using (operating system + version, distribution, version of
|
||||
sane-backends and of the frontend you use). Explain exactly what
|
||||
doesn't work, is wrong or missing.
|
||||
|
||||
<B>Adding</B> <B>and</B> <B>fixing</B> <B>documentation</B>
|
||||
If you found a bug in any documentation (man pages, web site,
|
||||
READMEs), please contact us (see CONTACT section). Also write us
|
||||
if you think some documentation is missing. Please include a
|
||||
patch in this case, if possible. Don't hesitate to send spelling
|
||||
and grammar mistakes.
|
||||
|
||||
<B>Translations</B>
|
||||
The options of the backends can be translated. For some lan-
|
||||
guages, the translations are almost complete, but some are lack-
|
||||
ing a lot of words and for most languages there is no transla-
|
||||
tion at all. If you want to help to translate the options to
|
||||
your native language (or a language you speak fluently), contact
|
||||
the sane-devel mailing list and have a look at the <I>po/</I> directory
|
||||
in the source code.
|
||||
|
||||
<B>Success</B> <B>reports</B>
|
||||
If you had success using <B>SANE</B> we want to know about that, too.
|
||||
Especially if your scanner is not in the lists yet or is marked
|
||||
"untested".
|
||||
We appreciate any help we can get. Please have alook at our web page
|
||||
about contributing to <B>SANE</B>: <I>http://www.sane-project.org/contrib.html</I>
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CONTACT</H2><PRE>
|
||||
If you want to comment on a backend-specific problem, contact the
|
||||
author of your backend. Usually the email address can be found in the
|
||||
<I>/usr/local/doc/sane-1.0.12-cvs/AUTHORS</I> file or the backend's manpage.
|
||||
If the author isn't marked as `active maintainer' or doesn't answer,
|
||||
you can also contact the <B>SANE</B> mailing list sane-devel (see
|
||||
<I>http://www.mostang.com/sane/mail.html</I> for details). You must be sub-
|
||||
scribed to the list, otherwise your mail won't be sent to the sub-
|
||||
scribers.
|
||||
|
||||
If you want to report bugs concerning security, compilation, installa-
|
||||
tion, porting, and documentation of <B>SANE</B>, you can also contact the
|
||||
author of this manual page: <henning@meier-geinitz.de>.
|
||||
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
|
||||
backend's manpage. For general discussion about SANE, please use the
|
||||
<B>SANE</B> mailing list sane-devel (see <I>http://www.sane-project.org/mail-</I>
|
||||
<I>ing-lists.html</I> for details).
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="saned.1.html">saned(1)</A></B>, <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="sane-abaton.5.html">sane-abaton(5)</A></B>,
|
||||
<B><A HREF="sane-agfafocus.5.html">sane-agfafocus(5)</A></B>, <B><A HREF="sane-apple.5.html">sane-apple(5)</A></B>, <B><A HREF="sane-artec.5.html">sane-artec(5)</A></B>,
|
||||
<B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B>, <B><A HREF="sane-as6e.5.html">sane-as6e(5)</A></B>, <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B>, <B><A HREF="sane-bh.5.html">sane-bh(5)</A></B>,
|
||||
<B><A HREF="sane-canon.5.html">sane-canon(5)</A></B>, <B><A HREF="sane-canon630u.5.html">sane-canon630u(5)</A></B>, <B><A HREF="sane-canon_pp.5.html">sane-canon_pp(5)</A></B>, <B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B>,
|
||||
<B><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B>, <B><A HREF="sane-dc210.5.html">sane-dc210(5)</A></B>, <B><A HREF="sane-dc240.5.html">sane-dc240(5)</A></B>, <B><A HREF="sane-dc25.5.html">sane-dc25(5)</A></B>,
|
||||
<B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>, <B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B>, <B><A HREF="sane-epson.5.html">sane-epson(5)</A></B>, <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>,
|
||||
<B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>, <B><A HREF="sane-hp.5.html">sane-hp(5)</A></B>, <B><A HREF="sane-hpsj5s.5.html">sane-hpsj5s(5)</A></B>,
|
||||
<B><A HREF="sane-hp5400.5.html">sane-hp5400(5)</A></B> <B><A HREF="sane-ibm.5.html">sane-ibm(5)</A></B>, <B><A HREF="sane-leo.5.html">sane-leo(5)</A></B>, <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>, <B>sane-mat-</B>
|
||||
<B><A HREF="sushita.5.html">sushita(5)</A></B>, <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B>, <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>,
|
||||
<B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>, <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B><A HREF="sane-nec.5.html">sane-nec(5)</A></B>, <B><A HREF="sane-net.5.html">sane-net(5)</A></B>,
|
||||
<B><A HREF="sane-pie.5.html">sane-pie(5)</A></B>, <B><A HREF="sane-pint.5.html">sane-pint(5)</A></B>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>, <B><A HREF="sane-pnm.5.html">sane-pnm(5)</A></B>, <B><A HREF="sane-qcam.5.html">sane-qcam(5)</A></B>,
|
||||
<B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B>, <B><A HREF="sane-s9036.5.html">sane-s9036(5)</A></B>, <B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>,
|
||||
<B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B>, <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B>, <B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B>, <B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B>,
|
||||
<B><A HREF="sane-st400.5.html">sane-st400(5)</A></B>, <B><A HREF="sane-tamarack.5.html">sane-tamarack(5)</A></B>, <B><A HREF="sane-teco1.5.html">sane-teco1(5)</A></B>, <B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B>,
|
||||
<B><A HREF="sane-teco3.5.html">sane-teco3(5)</A></B>, <B><A HREF="sane-test.5.html">sane-test(5)</A></B>, <B><A HREF="sane-umax1220u.5.html">sane-umax1220u(5)</A></B>, <B><A HREF="sane-umax.5.html">sane-umax(5)</A></B>,
|
||||
<B><A HREF="sane-umax_pp.5.html">sane-umax_pp(5)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-v4l.5.html">sane-v4l(5)</A></B>
|
||||
<B><A HREF="saned.1.html">saned(1)</A></B>, <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="sane-abaton.5.html">sane-abaton(5)</A></B>,
|
||||
<B><A HREF="sane-agfafocus.5.html">sane-agfafocus(5)</A></B>, <B><A HREF="sane-apple.5.html">sane-apple(5)</A></B>, <B><A HREF="sane-artec.5.html">sane-artec(5)</A></B>,
|
||||
<B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B>, <B><A HREF="sane-as6e.5.html">sane-as6e(5)</A></B>, <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B>, <B><A HREF="sane-bh.5.html">sane-bh(5)</A></B>,
|
||||
<B><A HREF="sane-canon.5.html">sane-canon(5)</A></B>, <B><A HREF="sane-canon630u.5.html">sane-canon630u(5)</A></B>, <B><A HREF="sane-canon_pp.5.html">sane-canon_pp(5)</A></B>, <B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B>,
|
||||
<B><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B>, <B><A HREF="sane-dc210.5.html">sane-dc210(5)</A></B>, <B><A HREF="sane-dc240.5.html">sane-dc240(5)</A></B>, <B><A HREF="sane-dc25.5.html">sane-dc25(5)</A></B>,
|
||||
<B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>, <B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B>, <B><A HREF="sane-epson.5.html">sane-epson(5)</A></B>, <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>,
|
||||
<B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>, <B><A HREF="sane-hp.5.html">sane-hp(5)</A></B>, <B><A HREF="sane-hpsj5s.5.html">sane-hpsj5s(5)</A></B>,
|
||||
<B><A HREF="sane-hp5400.5.html">sane-hp5400(5)</A></B> <B><A HREF="sane-ibm.5.html">sane-ibm(5)</A></B>, <B><A HREF="sane-leo.5.html">sane-leo(5)</A></B>, <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>,
|
||||
<B><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>
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -631,7 +575,7 @@
|
|||
written by Henning Meier-Geinitz. Quite a lot of text was taken from
|
||||
the <B>SANE</B> standard, several man pages, and README files.
|
||||
|
||||
sane-backends 1.0.12-cvs 19 Apr 2003 <B><A HREF="sane.7.html">sane(7)</A></B>
|
||||
sane-backends 1.0.12-cvs 24 Sept 2003 <B><A HREF="sane.7.html">sane(7)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
22
sane.ps
22
sane.ps
|
|
@ -10,7 +10,7 @@
|
|||
%DVIPSWebPage: (www.radicaleye.com)
|
||||
%DVIPSCommandLine: /usr/bin/dvips sane.dvi -o sane.ps
|
||||
%DVIPSParameters: dpi=600, compressed
|
||||
%DVIPSSource: TeX output 2003.09.23:1836
|
||||
%DVIPSSource: TeX output 2003.09.24:1735
|
||||
%%BeginProcSet: texc.pro
|
||||
%!
|
||||
/TeXDict 300 dict def TeXDict begin/N{def}def/B{bind def}N/S{exch}N/X{S
|
||||
|
|
@ -4672,16 +4672,16 @@ b(SANE)e(standard)28 b(is)d(discussed)j(and)f(e)n(v)n(olv)o(ed)g(via)e
|
|||
(a)h(mailing)g(list.)35 b(An)o(ybody)27 b(with)e(email)h(access)h(to)e
|
||||
(the)h(Internet)0 1895 y(can)e(automatically)j(join)d(and)g(lea)n(v)o
|
||||
(e)g(the)g(discussion)i(group)f(by)f(sending)h(mail)f(to)f(the)h(follo)
|
||||
n(wing)h(address.)227 2141 y Fp(sane-devel-requ)o(est)o(@m)o(os)o(ta)o
|
||||
(ng)o(.co)o(m)0 2387 y Fq(T)-7 b(o)22 b(subscribe,)k(send)f(a)e(mail)g
|
||||
(with)g(the)h(body)h(\223)p Fp(subscribe)51 b(sane-devel)p
|
||||
Fq(\224)18 b(to)24 b(the)f(abo)o(v)o(e)i(address.)0 2559
|
||||
y(A)e(complete)j(list)e(of)g(commands)i(supported)h(can)d(be)h
|
||||
(obtained)h(by)e(sending)j(a)c(mail)i(with)f(a)f(subject)j(of)e(\223)p
|
||||
Fp(help)p Fq(\224)f(to)h(the)0 2672 y(abo)o(v)o(e)g(address.)31
|
||||
b(The)23 b(mailing)h(list)g(is)g(archi)n(v)o(ed)h(and)f(a)n(v)n
|
||||
(ailable)h(through)h(the)e(SANE)d(home)j(page)g(at)f(URL:)227
|
||||
2918 y Fp(http://www.most)o(ang)o(.c)o(om)o(/s)o(an)o(e/)1905
|
||||
n(wing)h(address.)227 2141 y Fp(sane-devel-requ)o(est)o(@l)o(is)o(ts)o
|
||||
(.a)o(lio)o(th)o(.d)o(eb)o(ia)o(n.o)o(rg)0 2387 y Fq(T)-7
|
||||
b(o)22 b(subscribe,)k(send)f(a)e(mail)g(with)g(the)h(body)h(\223)p
|
||||
Fp(subscribe)51 b(sane-devel)p Fq(\224)18 b(to)24 b(the)f(abo)o(v)o(e)i
|
||||
(address.)0 2559 y(A)e(complete)j(list)e(of)g(commands)i(supported)h
|
||||
(can)d(be)h(obtained)h(by)e(sending)j(a)c(mail)i(with)f(a)f(subject)j
|
||||
(of)e(\223)p Fp(help)p Fq(\224)f(to)h(the)0 2672 y(abo)o(v)o(e)g
|
||||
(address.)31 b(The)23 b(mailing)h(list)g(is)g(archi)n(v)o(ed)h(and)f(a)
|
||||
n(v)n(ailable)h(through)h(the)e(SANE)d(home)j(page)g(at)f(URL:)227
|
||||
2918 y Fp(http://www.sane)o(-pr)o(oj)o(ec)o(t.)o(or)o(g/)1905
|
||||
5381 y Fq(45)p eop end
|
||||
%%Page: 46 47
|
||||
TeXDict begin 46 46 bop 0 586 a Fs(Index)0 1012 y Fq(array)-6
|
||||
|
|
|
|||
Ładowanie…
Reference in New Issue