diff --git a/man/gamma4scanimage.1.html b/man/gamma4scanimage.1.html
new file mode 100644
index 00000000..95224334
--- /dev/null
+++ b/man/gamma4scanimage.1.html
@@ -0,0 +1,82 @@
+
+
+gamma4scanimage.1
+
+
+gamma4scanimage.1
+
+
+
+gamma4scanimage(1) SANE Scanner Access Now Easy gamma4scanimage(1)
+
+
+
+NAME
+ gamma4scanimage - create a gamma table for scanimage
+
+
+
+SYNOPSIS
+ gamma4scanimage gamma [shadow [highlight [maxin [maxout]]]]
+
+
+
+DESCRIPTION
+ The tool gamma4scanimage creates a gamma table in the format expected
+ by scanimage. You can define a gamma, a shadow and a highlight value.
+ You also can specify the size (maxin) and maximum output value (maxout)
+ of the gamma table.
+
+ gamma is a floating point value, neutral value is 1.0, if the value is
+ larger than 1.0 then the image gets brighter.
+
+ shadow defines the minmum input value that is necessary to create an
+ output value larger than zero. shadow has to be in the range
+ [0..maxin]. Its default value is 0.
+
+ highlight defines the maximum input value that produces an output value
+ smaller than maxout. highlight has to be in the range [0..maxin],
+ highlight has to be larger than shadow. Its default value is the same
+ as maxin (16383 if not set).
+
+ maxin defines the size of the gamma table. The size depends on the
+ scanner/backend. If the scanner uses 8 bits gamma input then maxin has
+ to be set to 255, for 10 bits 1023, for 12 bits 4095, for 14 bits
+ 16383. The default is 16383. To find out what value maxin has to be
+ call scanimage with a very large gamma table [0]0-[99999]255 then scan-
+ image prints an error message with the needed size of the gamma table.
+
+ maxout defines the maximum output value. Take a look at the output of
+ scanimage -h to find out what maxout has to be. The default value is
+ 255.
+
+
+
+EXAMPLE
+ scanimage --custom-gamma=yes --gamma-table `gamma4scanimage 1.8 0 11500
+ 16383 255` >image.pnm
+
+
+
+SEE ALSO
+ scanimage(7)
+
+
+
+AUTHOR
+ Oliver Rauch
+
+
+
+EMAIL-CONTACT
+ Oliver.Rauch@Rauch-Domain.DE
+
+sane-backends 1.0.12-cvs 11 Sep 2002 gamma4scanimage(1)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-abaton.5.html b/man/sane-abaton.5.html
new file mode 100644
index 00000000..d8424507
--- /dev/null
+++ b/man/sane-abaton.5.html
@@ -0,0 +1,153 @@
+
+
+sane-abaton.5
+
+
+sane-abaton.5
+
+
+
+sane-abaton(5) SANE Scanner Access Now Easy sane-abaton(5)
+
+
+
+NAME
+ sane-abaton - SANE backend for Abaton flatbed scanners
+
+
+
+DESCRIPTION
+ The sane-abaton library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to Abaton flatbed scanners. At present,
+ only the Scan 300/GS (8bit, 256 levels of gray) is fully supported, due
+ to the absence of programming information. The Scan 300/S (black and
+ white) is recognized, but support for it is untested.
+
+ If you own a Abaton scanner other than the ones listed above that works
+ with this backend, or if you own an Abaton scanner that does not work
+ with this backend, please contact sane-devel@mostang.com with the model
+ number, so that arrangements can be made to include support for it.
+ Have a look at http://www.mostang.com/sane/mail.html concerning sub-
+ scription to sane-devel.
+
+ Abaton is out of business, and these scanners are not supported by
+ Everex (the parent company of Abaton), nor is there any programming
+ information to be found. This driver is therefore based on information
+ obtained by running Abaton's scanning desk accessory under MacsBug and
+ tracing the MacOS SCSI Manager calls it made during image acquisition.
+
+ However, the protocol is very similar to, though not compatible with,
+ the one used by the Apple scanners, therefore, if this backend is ever
+ extended to support the other Abaton models (they also made a color
+ flatbed scanner), it may be possible to fill in some "missing pieces"
+ from the (quite detailed) Apple scanner documentation.
+
+
+
+DEVICE NAMES
+ This backend expects device names of the form:
+
+ special
+
+ Where special is the path-name for the special device that corresponds
+ to a SCSI scanner. For SCSI scanners, the special device name must be a
+ generic SCSI device or a symlink to such a device. Under Linux, such a
+ device name takes a format such as /dev/sga or /dev/sg0, for example.
+ See sane-scsi(5) for details.
+
+
+
+CONFIGURATION
+ The contents of the abaton.conf file is a list of device names that
+ correspond to Abaton scanners. Empty lines and lines starting with a
+ hash mark (#) are ignored. See sane-scsi(5) on details of what consti-
+ tutes a valid device name.
+
+
+
+FILES
+ /usr/local/etc/sane.d/abaton.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-abaton.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-abaton.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_ABATON
+ 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.
+
+
+
+BUGS
+ There are a few known ones, and definitely some unknown ones.
+
+ Scan area miscalculations
+ For the sake of programmer efficiency, this backend handles all
+ measurements in millimetres, and floors (rather than rounds)
+ values to avoid possible damage to the scanner mechanism.
+ Therefore, it may not be possible to scan to the extreme right
+ or bottom edges of the page.
+
+ Cancelling the scan
+ This might not work correctly, or it might abort the frontend.
+ The former is more likely than the latter.
+
+ If you have found something that you think is a bug, please attempt to
+ recreate it with the SANE_DEBUG_ABATON environment variable set to 255,
+ and send a report detailing the conditions surrounding the bug to
+ sane-devel@mostang.com.
+
+
+
+TODO
+ Implement non-blocking support
+
+ Finish reverse-engineering the MacOS driver
+ This will allow me to add support for other models with reason-
+ able confidence that it will work, as well as to fully exploit
+ the information returned by the INQUIRY command.
+
+
+
+SEE ALSO
+ sane(7), sane-scsi(5), scanimage(1)
+
+
+
+AUTHOR
+ 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 sane-abaton(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-agfafocus.5.html b/man/sane-agfafocus.5.html
new file mode 100644
index 00000000..e0807ce8
--- /dev/null
+++ b/man/sane-agfafocus.5.html
@@ -0,0 +1,189 @@
+
+
+sane-agfafocus.5
+
+
+sane-agfafocus.5
+
+
+
+sane-agfafocus(5) SANE Scanner Access Now Easy sane-agfafocus(5)
+
+
+
+NAME
+ sane-agfafocus - SANE backend for AGFA Focus flatbed scanners
+
+
+
+DESCRIPTION
+ The sane-agfafocus library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to AGFA Focus flatbed scanners. At
+ present, the following scanners are supported from this backend:
+
+ AGFA Focus GS Scanner (6 bit gray scale) (untested)
+ AGFA Focus Lineart Scanner (lineart) (untested)
+ AGFA Focus II (8 bit gray scale) (untested)
+ AGFA Focus Color (24 bit color 3-pass)
+ AGFA Focus Color Plus (24 bit color 3-pass)
+
+ Siemens S9036 (8 bit gray scale) (untested)
+
+ The driver supports line art, 6bpp and 8bpp gray, 18bpp and 24bpp color
+ scans.
+
+ If you own a scanner other than the ones listed above that works with
+ this backend, please let us know by sending the scanner's model name,
+ SCSI id, and firmware revision to sane-devel@mostang.com. Have a look
+ at http://www.mostang.com/sane/mail.html concerning subscription to
+ sane-devel.
+
+ All of these scanners are pre-SCSI-2, and do not even report properly
+ to SCSI Inquiry. This is typically evident in SCSI bus scans, where
+ the scanner will come up with only garbage as vendor and models
+ strings.
+
+
+
+DEVICE NAMES
+ This backend expects device names of the form:
+
+ special
+
+ Where special 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 /dev/sga or /dev/sge, for example.
+ See sane-scsi(5) for details.
+
+
+
+CONFIGURATION
+ The contents of the agfafocus.conf file is a list of device names that
+ correspond to AGFA Focus scanners. Empty lines and lines starting with
+ a hash mark (#) are ignored. A sample configuration file is shown
+ below:
+
+ /dev/scanner
+ # this is a comment
+ /dev/sge
+
+
+
+FILES
+ /etc/sane.d/agfafocus.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/lib/libsane-agfafocus.a
+ The static library implementing this backend.
+
+ /usr/lib/libsane-agfafocus.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in /etc/sane.d. If the
+ value of the environment variable ends with the directory sepa-
+ rator character, then the default directories are searched after
+ the explicitly specified directories. For example, setting
+ SANE_CONFIG_DIR to "/tmp/config:" would result in directories
+ "tmp/config", ".", and "/etc/sane.d" being searched (in this
+ order).
+
+ SANE_DEBUG_AGFAFOCUS
+ If the library was compiled with debug support enabled, this
+ environment variable controls the debug level for this backend.
+ E.g., a value of 128 requests all debug output to be printed.
+ Smaller levels reduce verbosity. SANE_DEBUG_AGFAFOCUS values:
+
+ Number Remark
+
+ 0 print important errors (printed each time)
+ 1 print errors
+ 2 print sense
+ 3 print warnings
+ 4 print scanner-inquiry
+ 5 print informations
+ 6 print less important informations
+ 7 print called procedures
+ 8 print reader_process messages
+ 10 print called sane-init-routines
+ 11 print called sane-procedures
+ 12 print sane infos
+ 13 print sane option-control messages
+
+
+
+MISSING FUNCTIONALITY
+ Uploading of dither matrices and tonecurves has been implemented, but
+ so far has not proven to be useful for anything. For this reason these
+ options have been disabled.
+
+
+
+BUGS
+ The scanners that do not support disconnect have problems with SCSI
+ timeouts if the SCSI bus gets loaded, eg. if you do a kernel build at
+ the same time as scanning. To see if your scanner supports disconnect,
+ run "SANE_DEBUG_AGFAFOCUS=128 scanimage -L" in sh and look for the
+ "disconnect:" line)
+
+
+
+DEBUG
+ If you have problems with SANE not detecting your scanner, make sure
+ the Artec backend is disabled. Somehow, this backend causes at least
+ my scanner not to respond correctly to SCSI inquiry commands.
+
+ If you encounter a bug please set the environment variable
+ SANE_DEBUG_AGFAFOCUS to 128 and try to regenerate the problem. Then
+ send me a report with the log attached.
+
+ If you encounter a SCSI bus error or trimmed and/or displaced images
+ please also set the environment variable SANE_DEBUG_SANEI_SCSI to 128
+ before sending me the report.
+
+
+
+TODO
+ More scanners?
+
+ The AGFA ACS and ARCUS scanners are similar to the FOCUS scan-
+ ners. The driver could probably be extended to support these
+ scanners without too many changes. I do not have access to such
+ scanners, and cannot add support for it. However, if you are in
+ possession of such a scanner, I could be helpful in adding sup-
+ port for these scanners.
+
+ The AGFA HORIZON scanners are SCSI-2 scanners, and it would
+ probably be easier to support these scanners in a SCSI-2 compli-
+ ant backend.
+
+
+
+SEE ALSO
+ sane(7), sane-scsi(5)
+
+
+
+AUTHOR
+ Ingo Schneider and Karl Anders ?ygard.
+
+sane-backends 1.0.12-cvs 17 Oct 1998 sane-agfafocus(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-apple.5.html b/man/sane-apple.5.html
new file mode 100644
index 00000000..552ddfb7
--- /dev/null
+++ b/man/sane-apple.5.html
@@ -0,0 +1,293 @@
+
+
+sane-apple.5
+
+
+sane-apple.5
+
+
+
+sane-apple(5) SANE Scanner Access Now Easy sane-apple(5)
+
+
+
+NAME
+ sane-apple - SANE backend for Apple flatbed scanners
+
+
+
+DESCRIPTION
+ The sane-apple library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to Apple flatbed scanners. At present, the
+ following scanners are supported from this backend:
+
+ --------------- ----- ------------------ ------
+ AppleScanner 4bit 16 Shades of Gray
+ OneScanner 8bit 256 Shades of Gray
+ ColorOneScanner 24bit RGB color 3-pass
+
+ If you own a Apple scanner other than the ones listed above that works
+ with this backend, please let us know by sending the scanner's model
+ name, SCSI id, and firmware revision to sane-devel@mostang.com. See
+ http://www.mostang.com/sane/mail.html for details on how to subscribe
+ to sane-devel.
+
+
+
+DEVICE NAMES
+ This backend expects device names of the form:
+
+ special
+
+ Where special 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 /dev/sga or /dev/sge, for example.
+ See sane-scsi(5) for details.
+
+
+
+CONFIGURATION
+ The contents of the apple.conf 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 sane-scsi(5) on details of
+ what constitutes a valid device name.
+
+ Options come in two flavors: global and positional ones. Global
+ options apply to all devices managed by the backend whereas positional
+ options apply just to the most recently mentioned device. Note that
+ this means that the order in which the options appear matters!
+
+
+
+SCSI ADAPTER TIPS
+ SCSI scanners are typically delivered with an ISA SCSI adapter. Unfor-
+ tunately, that adapter is not worth much since it is not interrupt
+ driven. It is (sometimes) possible to get the supplied card to work,
+ but without interrupt line, scanning will put so much load on the sys-
+ tem, that it becomes almost unusable for other tasks.
+
+
+
+FILES
+ /usr/local/etc/sane.d/apple.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-apple.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-apple.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_APPLE
+ 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.
+
+
+
+CURRENT STATUS
+ The apple backend is now in version 0.3 (Tue Jul 21 1998). Since I only
+ have the AppleScanner and not the other models (OneScanner, ColorOneS-
+ canner) I can only develop/test for the AppleScanner effectively. How-
+ ever with this release I almost complete the gui part of all scanners.
+ Most of the functionality is there. At least OneScanner should scan at
+ the AppleScanner's compatible modes (LineArt, HalfTone, Gray16). My
+ personal belief is that with a slight touch of debugging the OneScanner
+ could be actually usable. The ColorOneScanner needs more work. AppleS-
+ canner is of course almost fully supported.
+
+
+
+MISSING FUNCTIONALITY
+ Currently all 3 models are lacking upload/dowload support.
+
+ AppleScanner
+ Cannot up/download a halftone pattern.
+
+ OneScanner
+ Cannot up/download halftone pattern and calibration vector.
+
+ ColorOneScanner
+ Cannot up/download halftone pattern, calibration vectors, custom
+ Color Correction Table (CCT) and of course custom gamma tables.
+
+ Park/UnPark (OneScanner, ColorOneScanner)
+
+ The above functionalities are not only missing because I don't actually
+ have the hardware to experiment on it. Another reason is the lack of
+ understanding of how SANE API could provide enaugh means to me to actu-
+ ally describe other array types than the gamma one.
+
+
+
+UNSUPPORTED FEATURES.
+ The following "features" will never be supported. At least as I am
+ maintaining the sane-apple backend.
+
+ NoHome (AppleScanner)
+ The scanner lamp stays on and the carriage assembly remains
+ where it stops at the end of the scan. After two minutes, if the
+ scanner does not receive another SCAN command the lamp goes off
+ and the carriage returns to the home position.
+
+ Compression (AppleScanner)
+ The Scanner can compress data with CCITT Group III, one dimen-
+ sional algorithm (fax), and the Skip White Line algorithm.
+
+ Multiple Windows (AppleScanner)
+ 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.
+
+ Scan Direction (OneScanner)
+ It controls the scan direction. (?)
+
+ Status/Reset Button (OneScanner)
+ This option controls the status of the button in OneScanner
+ model. You can also reset the button status by software.
+
+
+
+BUGS
+ The bugs in a sane backend are divided in two classes. We have GUI bugs
+ and scanner specific bugs.
+
+ We know we have a GUI bug when a parameter is not showing up itself
+ when it should (active) or vice versa. To find out which parameters are
+ active accross various Apple modes and models from the documentation
+ ftp://ftpdev.info.apple.com/devworld/Technical_Documentation/Peripher-
+ als_Documentation/ is an interesting exercise. I may missed some depen-
+ dancies. For example for the threshold parameter the Apple Scanners
+ Programming guide says nothing. I had to assume that is valid only in
+ LineArt mode.
+
+ Scanner specific bugs are mostly due to mandatory round offs in order
+ to scan. In the documentation in some place states that the width of
+ the scan area should be a byte multiple. In an other place says that
+ the width of the scan area should be an even byte multiple. Go fig-
+ ure...
+
+ Other source of bugs are due to scsi communcation, scsi connects and
+ disconnects. However the classical bugs are still there. So you may
+ encouter buffer overruns, null pointers, memory corruption and SANE API
+ violations.
+
+ SIGSEGV on SliceBars
+ When you try to modify the scan area from the slice bar you have
+ a nice little cute core dump. I don't know why. If you select
+ the scan are from the preview window, or by hand typing the num-
+ bers everything is fine. The SIGSEGV happens deep in gtk library
+ (gdk). I really cannot debug it.
+
+ Options too much
+ 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.
+
+ Weird SCSI behaviour.
+ I am quoting David Myers Here...
+
+ >> OS: FreeBSD 2.2.6
+
+ >> CC: egcs-1.02
+
+ >Just wanted to follow up on this... I recently changed my SCSI
+ card from
+
+ >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
+ okay, but Gray16
+
+ >scans led to a stream of SCSI error messages on the console,
+ ultimately
+
+ >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
+
+ >hardware, or may be bugs in your driver or in SANE itself...
+
+
+
+DEBUG
+ If you encounter a GUI bug please set the environment variable
+ SANE_DEBUG_APPLE to 255 and rerun the excact sequence of keystrokes and
+ menu selections to reproduce it. Then send me a report with the log
+ attached.
+
+ It would be very helpfull if you have handy an Apple machine (I am not
+ sure how Mackintoshs are spelled) with the AppleScanners driver
+ installed and check what option are grayed out (inactive) in what modes
+ and report back to me.
+
+ If you want to offer some help but you don't have a scanner or you
+ don't have the model you would like to offer some help, or you are a
+ sane developer and you just want to take a look at how the apple back-
+ end looks like. Goto to apple.h and #define the NEUTRALIZE_BACKEND
+ macro. You can select the scanner model through the APPLE_MODEL_SELECT
+ macro. Available options are APPLESCANNER, ONESCANNER, COLORONESCANNER.
+
+ If you encounter a SCSI bus error or trimmed and/or displaced images
+ please also set the environment variable SANE_DEBUG_SANEI_SCSI to 255
+ before sendme the report.
+
+
+
+TODO
+ Non Blocking Support
+ Make sane-apple a non blocking backend. Properly support for
+ sane_set_io_mode and sane_get_select_fd
+
+ Scan Make scan possible for all models in all supported modes.
+
+ Missing Functionality.
+
+
+
+SEE ALSO
+ sane(7), sane-scsi(5)
+
+
+
+AUTHOR
+ 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 sane-apple(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-artec.5.html b/man/sane-artec.5.html
new file mode 100644
index 00000000..7190f14f
--- /dev/null
+++ b/man/sane-artec.5.html
@@ -0,0 +1,183 @@
+
+
+sane-artec.5
+
+
+sane-artec.5
+
+
+
+sane-artec(5) SANE Scanner Access Now Easy sane-artec(5)
+
+
+
+NAME
+ sane-artec - SANE backend for Artec flatbed scanners
+
+
+
+DESCRIPTION
+ The sane-artec library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to Artec/Ultima SCSI flatbed scanners. At
+ present, the following scanners are known to work at least partially
+ with this backend:
+
+ Artec A6000C
+ Artec A6000C PLUS
+ Artec ViewStation AT3
+ BlackWidow BW4800SP (rebadged Artec AT3)
+ Artec ViewStation AT6
+ Artec ViewStation AT12
+ Artec AM12S
+ Plustek 19200S (rebadged Artec AM12S)
+
+ Although this manual page is generally updated with each release, up-
+ to-date information on new releases and extraneous helpful hints are
+ available from the backend homepage:
+ http://www4.infi.net/~cpinkham/sane/
+
+
+
+DOCUMENTATION
+
+
+CONFIGURATION
+ The contents of the artec.conf file are a list of device names that
+ correspond to Artec scanners. Empty lines and lines starting with a
+ hash mark (#) are ignored. See sane-scsi(5) on details of what consti-
+ tutes a valid device name.
+ Sample file:
+ # artec.conf
+ #
+ # this is a comment.
+ #
+ # this line says search for any SCSI devices which are scanners and
+ have
+ # a vendor string of 'ULTIMA'
+ scsi ULTIMA
+ #
+ # the next line forces the backend to assume the next scanner found has
+ # the specified vendor string (useful for testing rebadged models).
+ vendor ULTIMA
+ #
+ # the next line forces the backend to assume the next scanner found has
+ # the specified model string (useful for testing rebadged models).
+ model AT3
+ #
+ # now a line that actually specifies a device. The backend is going to
+ # assume this is an Artec/Ultima AT3 because we forced the vendor
+ and
+ # model above.
+ /dev/scanner
+ #
+ # once we hit a scanner device line, the forced vendor and model
+ # string are
+ # 'forgotten', so the vendor and model for this next device will be
+ # determined from the result of a SCSI inquiry.
+ /dev/sge
+ #
+
+
+
+
+SCSI ADAPTER TIPS
+ Some Artec scanners come with an included SCSI adapter. If your scan-
+ ner came with a DTC ISA scsi cards, you can probably use it with recent
+ (>= 2.2.0) kernels using the generic NCR5380 support. You must pass
+ the following boot argument to the kernel: "dtc3181e=0x2c0,0"
+ I do not have any information on the PCI SCSI adapter included with
+ some newer Artec scanners.
+
+
+
+FILES
+ /usr/local/etc/sane.d/artec.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-artec.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-artec.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi- colon (`;'). If this variable is not set, the con-
+ figuration file is searched in two default directories: first,
+ the current working direc- tory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_ARTEC
+ If the library was compiled with debug support enabled, this
+ environment variable controls the debug level for this backend.
+ E.g., a value of 128 requests all debug output to be printed.
+ Smaller levels reduce verbosity: SANE_DEBUG_ARTEC values
+
+ Number Remark
+ 0 print important errors
+ 1 print errors
+ 2 print sense
+ 3 print warnings
+ 4 print scanner-inquiry
+ 5 print informations
+ 6 print less important informations
+ 7 print major called procedures
+ 8 print all called procedures
+ 9 print procedure info/data messages
+ 10 print called sane-init-routines
+ 11 print called sane-procedures
+ 12 print sane infos
+ 13 print sane option-control messages
+
+ 50 print verbose data/debug messages
+
+ == 100 print software RGB calibration data
+ == 101 print raw data from scanner to artec.data.raw file
+
+ == 128 print out all messages
+
+ Example:
+ export SANE_DEBUG_ARTEC=13
+
+
+
+BUGS
+ Known bugs in this release: A6000C+ users with firmware v1.92 or ear-
+ lier have problems with the backend, the cause has not been determined.
+ Sometimes the backend is not particularly robust, you can possibly lock
+ up the SCSI bus (and/or machine) by not having patience enough when
+ scanning. 3-channel gamma correction is not implemented and single-
+ channel gamma correction is not totally working on models other than
+ the AT3.
+
+
+
+SEE ALSO
+ sane(7), sane-scsi(5)
+
+
+
+AUTHOR
+ Chris Pinkham (cpinkham@infi.net) (does not exist anymore?)
+
+sane-backends 1.0.12-cvs 24 Jan 2000 sane-artec(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-artec_eplus48u.5.html b/man/sane-artec_eplus48u.5.html
new file mode 100644
index 00000000..d4c1631d
--- /dev/null
+++ b/man/sane-artec_eplus48u.5.html
@@ -0,0 +1,198 @@
+
+
+sane-artec_eplus48u.5
+
+
+sane-artec_eplus48u.5
+
+
+
+sane-artec_eplus48u(5) SANE sane-artec_eplus48u(5)
+
+
+
+NAME
+ sane-artec_eplus48u - SANE backend for the scanner Artec E+ 48U and re-
+ badged models
+
+
+
+DESCRIPTION
+ The sane-artec_eplus48u library implements a SANE (Scanner Access Now
+ Easy) backend that at present provides access to the USB flatbed scan-
+ ners
+
+ Artec E+ 48U,
+ Tevion MD 9693,
+ Medion MD 9693,
+ Medion MD 9705 and
+ Trust Easy Webscan 19200.
+
+ These scanners have a contact image sensor (CIS) and an USB interface.
+
+ VendorID: 0x05d8
+ ProductID: 0x4003
+
+ The Trust Easy Webscan 19200 is an exception. It's ProductID is 0x4006
+ .
+
+ More details can be found on http://www.angelfire.com/linux/crapsite/.
+
+ This is ALPHA software. Especially if you test new or untested scan-
+ ners, keep your hand at the scanner's plug and unplug it, if the head
+ bumps at the end of the scan area.
+
+ If you own a scanner other than the ones listed above that works with
+ this backend, please let me know this by sending the scanner's exact
+ model name and the USB vendor and product ids (e.g. from
+ /proc/bus/usb/devices, sane-find-scanner or syslog) to me. Even if the
+ scanner's name is only slightly different from the models mentioned
+ above, please let me know.
+
+
+
+KERNEL ISSUES
+ If libusb-0.1.6 or later is installed, this section can be skipped. The
+ scanner should be found by sane-find-scanner without further actions.
+ For setting permissions and general USB information look at sane-
+ usb(5).
+
+ When you are using the scanner module, a Linux kernel 2.4.12 or newer
+ is required.
+
+
+
+FIRMWARE FILE
+ You need a firmware file for your scanner. That's a small file contain-
+ ing software that will be uploaded to the scanner's memory. For the
+ scanners mentioned above, it's usually named Artec48.usb. You can find
+ it on the installation CD that was provided by the manufacturer, nor-
+ mally in the directory Win98, WinMe or similar. If the Windows-driver
+ is installed on your computer, then you can also find the firmware file
+ under c:\windows\system32\drivers.
+
+
+
+CONFIGURATION
+ The contents of the artec_eplus48u.conf file is a list of usb lines
+ containing vendor and product ids that correspond to USB scanners. The
+ file can also contain option lines. Empty lines and lines starting
+ with a hash mark (#) are ignored. The scanners are autodetected by usb
+ vendor_id product_id statements which are already included into
+ artec_eplus48u.conf . "vendor_id" and "product_id" are hexadecimal
+ numbers that identify the scanner.
+
+ Every usb section can have additional options
+
+ artecFirmwareFile <path>/Artec48.usb
+ The path to the firmware file. This option is required.
+
+ redGamma 1.0
+
+ greenGamma 1.0
+
+ blueGamma 1.0
+
+ masterGamma 1.9
+ These are the default gamma values. If you set the "Defaults"
+ option with a frontend, then the gamma options are reset to the
+ values specified here.
+
+ redOffset 0x28
+
+ greenOffset 0x2f
+
+ blueOffset 0x2f
+
+ redExposure 0xa7
+
+ greenExposure 0x116
+
+ blueExposure 0xdc
+ These are the default values for offset and exposure time. You
+ can e.g. change them to speed up calibration, if you don't want
+ to save the calibration data to disk.
+
+ vendorString Artec
+
+ modelString E+ 48U
+ By default, the scanner is reported as "Artec E+ 48U". If you
+ don't like this, e.g. because you have an Tevion MD 9693, then
+ change the options accordingly.
+
+
+
+FILES
+ /usr/local/etc/sane.d/artec_eplus48u.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-artec_eplus48u.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-artec_eplus48u.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_ARTEC_EPLUS48U
+ If the library was compiled with debug support enabled, this
+ environment variable controls the debug level for this backend.
+ Higher debug levels increase the verbosity of the output.
+
+ Example: export SANE_DEBUG_ARTEC_EPLUS48U=3
+
+
+
+SEE ALSO
+ sane(7), sane-usb(5)
+
+
+
+AUTHOR
+ Michael Herder <crapsite@gmx.net>
+ This backend is based on the gt68xx test-program written by Sergey
+ Vlasov, Andreas Nowack, and David Stevenson. Thanks to everyone who
+ tested the backend or reported bugs.
+ This man page is based on man sane-gt68xx, written by Henning Meier-
+ Geinitz.
+
+
+
+BUGS
+ This backend has been tested on Linux only. If you are using it on a
+ different platform, please contact me.
+
+ Interpolation with 1200 dpi is weak.
+
+ Support for buttons is missing due to missing support in SANE.
+
+ More detailed bug information is available at
+ http://www.angelfire.com/linux/crapsite. Please contact me if you find
+ a bug or missing feature: <crapsite@gmx.net>
+
+sane-backends 1.0.12-cvs 19 Nov 2002 sane-artec_eplus48u(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-as6e.5.html b/man/sane-as6e.5.html
new file mode 100644
index 00000000..4882d9cd
--- /dev/null
+++ b/man/sane-as6e.5.html
@@ -0,0 +1,61 @@
+
+
+sane-as6e.5
+
+
+sane-as6e.5
+
+
+
+sane-as6e(5) SANE Scanner Access Now Easy sane-as6e(5)
+
+
+
+NAME
+ sane-as6e - SANE backend for using the Artec AS6E parallel port inter-
+ face scanner.
+
+
+
+DESCRIPTION
+ The sane-as6e library implements a SANE (Scanner Access Now Easy) back-
+ end that provides access to Artec AS6E flatbed scanner. It requires
+ the as6edriver program in order to operate. The as6edriver program is
+ not included with the SANE package. It can be found at
+ http://as6edriver.sourceforge.net. See the as6edriver documentation
+ for technical information.
+
+ The as6edriver program must be in the path for executables ($PATH).
+ Especially if you run saned (the SANE network scanning daemon), take
+ care to setup the path for inetd or xinetd correctly or place the pro-
+ gram in a directory that is in the path.
+
+
+
+FILES
+ as6edriver - driver program that controls the scanner.
+
+
+
+SEE ALSO
+ sane(7), as6edriver(5), saned(1), http://as6edriver.sourceforge.net
+
+
+
+AUTHOR
+ Eugene S. Weiss
+
+
+
+EMAIL-CONTACT
+ yossarian@users.sourceforge.net
+
+sane-backends 1.0.12-cvs Apr 2nd, 2003 sane-as6e(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-avision.5.html b/man/sane-avision.5.html
new file mode 100644
index 00000000..759d694c
--- /dev/null
+++ b/man/sane-avision.5.html
@@ -0,0 +1,176 @@
+
+
+sane-avision.5
+
+
+sane-avision.5
+
+
+
+sane-avision(5) SANE Scanner Access Now Easy sane-avision(5)
+
+
+
+NAME
+ sane-avision - SANE backend for original Avision and Avision OEM scan-
+ ners (HP, Minolta, Mitsubishi, UMAX and possibly more) flatbed scanners
+
+
+
+ABOUT THIS FILE
+ This file only is a short descripton of the avision-backend for sane!
+
+
+
+DESCRIPTION
+ The sane-avision 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.
+
+
+
+CONFIGURATION
+ The configuration file for this backend resides in
+ /usr/local/etc/sane.d/avision.conf.
+
+ Its contents is a list of device names that correspond to Avision and
+ Avision compatible scanners and backend-options. Empty lines and lines
+ starting with a hash mark (#) are ignored. A sample configuration file
+ is shown below:
+
+ I suggest you hold one hand on the power-button of the scanner while
+ you try the first scans!
+
+ # this is a comment
+
+ option force-a4
+ option disable-gamma-table
+ option disable-calibration
+ option one-calib-only
+ option old-calibration
+
+ #scsi Vendor Model Type Bus Channel ID LUN
+ scsi AVISION
+ scsi HP
+ scsi /dev/scanner
+ usb 0x03f0 0x0701
+
+ - force-a4:
+ Forces the backend to overwrite the scanable area
+ returned by the scanner. This might be needed for
+ the AV 630 which returns no area - or newer scanners
+ which retun the area in a unkown format our backend
+ doesn't recongize yet.
+
+ - disable-gamma-table:
+ Disables the usage of the scanner's gamma-table. You
+ might try this if your scans hang or only produces
+ random garbage.
+
+ - disable-calibration:
+ Disables the scanner's color calibration. You
+ might try this if your scans hang or only produces
+ random garbage.
+
+ - one-calib-only:
+ When this option is enabled, the backend will only
+ perform a calibration when the backend is initialized
+ and not before each scan. This might extend the life
+ of the CCD, but does not work reliable with the newer
+ USB scanners (they hang sometimes or return garbage
+ image data). So this option should be used with care.
+
+ - old-calibration:
+ This enables the use of the old calibration code for
+ testing purposes.
+
+ Note: Any option above modifies the default code-flow
+ for your scanner. The options should only be used
+ when you encounter problems with the default be-
+ haviour of the backend. Please report the need of
+ options to the backend-author so the backend can
+ be fixed as soon as possible.
+
+
+
+DEVICE NAMES
+ This backend expects device names of the form:
+
+ scsi special usb special
+
+ Where special 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 sane-find-scanner helps to find
+ out the correct device. Under Linux, such a device name could be
+ /dev/sg0 or /dev/sga, for example. See sane-scsi(5) for details.
+
+ Note: Since the backend now includes native USB access,
+ it is no longer needed - even considered obsolete -
+ to access the scanner via the SCSI emulation (named
+ hpusbscsi on Linux) for Avision USB devices such as
+ the HP 53xx, HP 74xx or Minolta film-scanners.
+
+ A list with supported devices is built into the avision backend so
+ normally specifying an ID should not be necessary.
+
+
+
+FILES
+ /usr/local/etc/sane.d/avision.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-avision.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-avision.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_AVISION
+ 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
+
+
+
+SEE ALSO
+ sane(7), sane-scsi(5)
+ http://drocklinux.dyndns.org/rene/avision/index.html
+
+
+
+AUTHOR
+ Ren? Rebe and Meino Christian Cramer
+
+sane-backends 1.0.12-cvs 04 Mar 2003 sane-avision(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-bh.5.html b/man/sane-bh.5.html
new file mode 100644
index 00000000..59d4099f
--- /dev/null
+++ b/man/sane-bh.5.html
@@ -0,0 +1,513 @@
+
+
+sane-bh.5
+
+
+sane-bh.5
+
+
+
+sane-bh(5) SANE Scanner Access Now Easy sane-bh(5)
+
+
+
+NAME
+ sane-bh - SANE backend for Bell+Howell Copiscan II series document
+ scanners
+
+
+
+DESCRIPTION
+ The sane-bh library implements a SANE (Scanner Access Now Easy) backend
+ that provides access to Bell+Howell Copiscan II series document scan-
+ ners. The Copiscan II 6338 has been the primary scanner model used
+ during development and testing, but since the programming interface for
+ the entire series is consistent the backend should work for the follow-
+ ing scanner models.
+
+ COPISCAN II 6338 Duplex Scanner with ACE
+ COPISCAN II 2135 Simplex Scanner
+ COPISCAN II 2137(A) Simplex Scanner (with ACE)
+ COPISCAN II 2138A Simplex Scanner with ACE
+ COPISCAN II 3238 Simplex Scanner
+ COPISCAN II 3338(A) Simplex Scanner (with ACE)
+
+ If you have a Bell+Howell scanner and are able to test it with this
+ backend, please contact sane-devel@mostang.com with the model number
+ and testing results. Have a look at
+ http://www.mostang.com/sane/mail.html concerning subscription to sane-
+ devel. Additionally, the author is curious as to the likelihood of
+ using this backend with the newer 4000 and 8000 series scanners. If
+ you have such a beast, please let me know.
+
+ The Bell+Howell Copiscan II series document scanners are high volume,
+ high throughput scanners designed for document scanning applications.
+ As such, they are lineart/grayscale scanners supporting a fixed number
+ of fairly low resolutions (e.g. 200/240/300dpi). However, they do have
+ a number of interesting and useful features suited to needs of document
+ imaging applications. This backend attempts to support as many of
+ these features as possible.
+
+ The main technical reference used in writing this backend is the Bell
+ and Howell Copiscan II Remote SCSI Controller (RSC) OEM Technical Man-
+ ual Version 1.5. The Linux SCSI programming HOWTO, the SANE API docu-
+ mentation, and SANE source code were also extremely valuable resources.
+
+ The latest backend release, additional information and helpful hints
+ are available from the backend homepage:
+ http://www.martoneconsulting.com/sane-bh.html
+
+
+
+DEVICE NAMES
+ This backend expects device names of the form:
+
+ special
+
+ Where special is the path-name for the special device that corresponds
+ to a SCSI scanner. For SCSI scanners, the special device name must be a
+ generic SCSI device or a symlink to such a device. Under Linux, such a
+ device name takes a format such as /dev/sga or /dev/sg0, for example.
+ See sane-scsi(5) for details.
+
+
+
+CONFIGURATION
+ The contents of the bh.conf file is a list of device names that corre-
+ spond to Bell+Howell scanners. See sane-scsi(5) on details of what
+ constitutes a valid device name. Additionally, options can be speci-
+ fied; these lines begin with the word "option". Each option is
+ described in detail below. Empty lines and lines starting with a hash
+ mark (#) are ignored.
+
+
+
+OPTIONS
+ The following options can be specified in the bh.conf file.
+
+ disable-optional-frames
+ This option prevents the backend from sending any optional
+ frames. This option may be useful when dealing with frontends
+ which do not support these optional frames. When this option is
+ in effect, the data is sent in a SANE_FRAME_GRAY frame. The
+ optional frames sent by this backend are: SANE_FRAME_G31D,
+ SANE_FRAME_G32D, SANE_FRAME_G42D and SANE_FRAME_TEXT. These
+ frames are generated based on the compression and barcode
+ options. These frames are never sent in preview mode.
+
+ fake-inquiry
+ This option is used for debugging purposes and its use is not
+ encouraged. Essentially, it allows the backend to initialize in
+ the absence of a scanner. This is useful for development and
+ not much else. This option must be specified earlier in the
+ configuration file than the devices which are to be "faked".
+
+
+
+FILES
+ /usr/local/etc/sane.d/bh.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-bh.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-bh.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_BH
+ 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.
+
+
+
+SUPPORTED FEATURES
+ ADF support
+ With document scanners, automatic document feeder (ADF) support
+ is a key feature. The backend supports the ADF by default and
+ returns SANE_STATUS_NO_DOCS when the out-of-paper condition is
+ detected. The SANE frontend scanadf is a command line frontend
+ that supports multi-page scans. It has been used successfully
+ with this backend. The SANE frontend xsane is an improved GUI
+ frontend by Oliver Rauch. Support for multi-page scans is
+ included in xsane version 0.35 and above.
+
+ Duplex scanning
+ Some models, such as the COPISCAN II 6338, support duplex scan-
+ ning. That is, they scan both sides of the document during a
+ single pass through the scanner (the scanner has two cameras).
+ This backend supports duplex scanning (with the --duplex
+ option). The front and back page images are delivered consecu-
+ tively as if they were separately scanned pages.
+
+ Hardware compression
+ The scanner is capable of compressing the data into several
+ industry standard formats (CCITT G3, CCITT G3-2D, CCITT G4).
+ This results in increased performance as less data is passed
+ from the scanner to the host over the SCSI bus. The backend
+ supports these compression formats via the --g31d, --g32d,
+ --g42d options, respectively. Many SANE frontends are not
+ equipped to deal with these formats, however. The SANE frontend
+ scanadf supports these optional frame formats. The compressed
+ image data is written directly to a file and can then be pro-
+ cessed by a scan-script using the --scan-script option. Exam-
+ ples of this are given on the scanadf homepage.
+
+ Automatic Border Detection
+ The scanner can automatically detect the paper size and adjust
+ the scanning window geometry appropriately. The backend sup-
+ ports this useful feature with the --autoborder option. It is
+ enabled by default.
+
+ Batch Mode Scanning
+ The batch scan mode allows for maximum throughput. The Set Win-
+ dow parameters must remain constant during the entire batch.
+
+ Icon Generation
+ The Icon function generates a thumbnail of the full page image,
+ that can be transferred as if it were a separate page. This
+ allows the host to quickly display a thumbnail representation
+ during the scanning operation. Perhaps this would be a great
+ way of implementing a preview scan, but since a normal scan is
+ so quick, it might not be worth the trouble.
+
+ Multiple Sections
+ Multiple sections (scanning sub-windows) can be defined for the
+ front and back pages. Each section can have different charac-
+ teristics (e.g. geometry, compression). The sections are
+ returned as if they were separately scanned images. Addition-
+ ally sections can be used to greatly enhance the accuracy and
+ efficiency of the barcode/patchcode decoding process by limiting
+ the search area to a small subset of the page. Most Copiscan II
+ series scanners support up to 8 user-defined sections.
+
+ Support Barcode/Patchcode Decoding
+ The RSC unit can recognize Bar and Patch Codes of various types
+ embedded in the scanned image. The codes are decoded and the
+ data is returned to the frontend as a text frame. The text is
+ encoded in xml and contains a great deal of information about
+ the decoded data such as the location where it was found, its
+ orientation, and the time it took to find. Further information
+ on the content of this text frame as well as some barcode decod-
+ ing examples can be found on the backend homepage.
+
+
+
+LIMITATIONS
+ Decoding a single barcode type per scan
+ The RSC unit can search for up to six different barcode types at
+ a time. While the code generally supports this as well, the
+ --barcode-search-bar option only allows the user to specify a
+ single barcode type. Perhaps another option which allows a
+ comma separated list of barcode type codes could be added to
+ address this.
+
+ Scanning a fixed number of pages in batch mode
+ The separation of front and back end functionality in SANE
+ presents a problem in supporting the 'cancel batch' functional-
+ ity in the scanner. In batch mode, the scanner is always a page
+ ahead of the host. The host, knowing ahead of time which page
+ will be the last, can cancel batch mode prior to initiating the
+ last scan command. Currently, there is no mechanism available
+ for the frontend to pass this knowledge to the backend. If
+ batch mode is enabled and the --end-count terminates a scanadf
+ session, an extra page will be pulled through the scanner, but
+ is niether read nor delivered to the frontend. The issue can be
+ avoided by specifying --batch=no when scanning a fixed number of
+ pages.
+
+ Revision 1.2 Patch detector
+ There is an enhanced patchcode detection algorithm available in
+ the RSC with revision 1.2 or higher that is faster and more
+ reliable than the standard Bar/Patch code decoder. This is not
+ currently supported.
+
+
+
+OPTIONS
+ Scan Mode Options:
+
+ --preview[=(yes|no)] [no]
+ Request a preview-quality scan. When preview is set to yes
+ image compression is disabled and the image is delivered in a
+ SANE_FRAME_GRAY frame.
+
+ --mode lineart|halftone [lineart]
+ Selects the scan mode (e.g., lineart,monochrome, or color).
+
+ --resolution 200|240|300dpi [200]
+ Sets the resolution of the scanned image. Each scanner model
+ supports a list of standard resolutions; only these resolutions
+ can be used.
+
+ --compression none|g31d|g32d|g42d [none]
+ Sets the compression mode of the scanner. Determines the type
+ of data returned from the scanner. Values are:
+ none - uncompressed data - delivered in a SANE_FRAME_GRAY frame
+ g31d - CCITT G3 1 dimension (MH) - delivered in a
+ SANE_FRAME_G31D frame
+ g32d - CCITT G3 2 dimensions (MR, K=4) - delivered in a
+ SANE_FRAME_G32D frame
+ g42d - CCITT G4 (MMR) - delivered in a SANE_FRAME_G42D frame
+ NOTE: The use of g31d, g32d, and g42d compression values causes
+ the backend to generate optional frame formats which may not be
+ supported by all SANE frontends.
+
+ Geometry Options:
+
+ --autoborder[=(yes|no)] [yes]
+ Enable/Disable automatic image border detection. When enabled,
+ the RSC unit automatically detects the image area and sets the
+ window geometry to match.
+
+ --paper-size Custom|Letter|Legal|A3|A4|A5|A6|B4|B5 [Custom]
+ Specify the scan window geometry by specifying the paper size of
+ the documents to be scanned.
+
+ --tl-x 0..297.18mm [0]
+ Top-left x position of scan area.
+
+ --tl-y 0..431.8mm [0]
+ Top-left y position of scan area.
+
+ --br-x 0..297.18mm [297.18]
+ Bottom-right x position of scan area.
+
+ --br-y 0..431.8mm [431.8]
+ Bottom-right y position of scan area.
+
+ Feeder Options:
+
+ --source Automatic Document Feeder|Manual Feed Tray [Automatic Document
+ Feeder]
+ Selects the scan source (such as a document feeder). This
+ option is provided to allow multiple image scans with xsane; it
+ has no other purpose.
+
+ --batch[=(yes|no)] [no]
+ Enable/disable batch mode scanning. Batch mode allows scanning
+ at maximum throughput by buffering within the RSC unit. This
+ option is recommended when performing multiple pages scans until
+ the feeder is emptied.
+
+ --duplex[=(yes|no)] [no]
+ Enable duplex (dual-sided) scanning. The scanner takes an image
+ of each side of the document during a single pass through the
+ scanner. The front page is delivered followed by the back page.
+ Most options, such as compression, affect both the front and
+ back pages.
+
+ --timeout-adf 0..255 [0]
+ Sets the timeout in seconds for the automatic document feeder
+ (ADF). The value 0 specifies the hardware default value which
+ varies based on the scanner model.
+
+ --timeout-manual 0..255 [0]
+ Sets the timeout in seconds for semi-automatic feeder. The
+ value 0 specifies the hardware default value which varies based
+ on the scanner model.
+
+ --check-adf[=(yes|no)] [no]
+ Check ADF Status prior to starting scan using the OBJECT POSI-
+ TION command. Note that this feature requires RSC firmware
+ level 1.5 or higher and dip switch 4 must be in the on position.
+ NOTE: This option has not been tested extensively and may pro-
+ duce undesireable results.
+
+ Enhancement:
+
+ --control-panel[=(yes|no)] [yes]
+ Enables the scanner's control panel for selecting image enhance-
+ ment parameters. When the option is set to no the following
+ options are used to control image enhancement. See the
+ Bell+Howell scanner users' guide for complete information on ACE
+ functionality.
+
+ --ace-function -4..4 [3]
+ Specify the Automatic Contrast Enhancement (ACE) Function.
+
+ --ace-sensitivity 0..9 [5]
+ Specify the Automatic Contrast Enhancement (ACE) Sensitivity.
+
+ --brightness 0..255 [0]
+ Controls the brightness of the acquired image. Ignored for ACE
+ capable scanners.
+
+ --threshold 0..255 [0]
+ Select minimum-brightness to get a white point. Ignored for ACE
+ capable scanners.
+
+ --contrast 0..255 [inactive]
+ Controls the contrast of the acquired image. This option is not
+ currently used by the scanner (and perhaps never will be).
+
+ --negative[=(yes|no)] [no]
+ Swap black and white, yielding a reverse-video image.
+
+ Icon:
+
+ --icon-width 0..3600pel (in steps of 8) [0]
+ Width of icon (thumbnail) image in pixels.
+
+ --icon-length 0..3600pel (in steps of 8) [0]
+ Length of icon (thumbnail) image in pixels.
+
+ Barcode Options:
+
+ --barcode-search-bar <see list> [none]
+ Specifies the barcode type to search for. If this option is not
+ specified, or specified with a value of none, then the barcode
+ decoding feature is completely disabled. The valid barcode type
+ are:
+ none
+ ean-8
+ ean-13
+ reserved-ean-add
+ code39
+ code2-5-interleaved
+ code2-5-3lines-matrix
+ code2-5-3lines-datalogic
+ code2-5-5lines-industrial
+ patchcode
+ codabar
+ codabar-with-start-stop
+ code39ascii
+ code128
+ code2-5-5lines-iata
+
+ --barcode-search-count 1..7 [3]
+ Number of times that the RSC performs the decoding algorithm.
+ Specify the smallest number possible to increase performance.
+ If you are having trouble recognizing barcodes, it is suggested
+ that you increase this option to its maximum value (7).
+
+ --barcode-search-mode <see list> [horiz-vert]
+ Chooses the orientation of barcodes to be searched. The valid
+ orientations are:
+ horiz-vert
+ horizontal
+ vertical
+ vert-horiz
+
+ --barcode-hmin 0..1660mm [5]
+ Sets the barcode minimum height in millimeters (larger values
+ increase recognition speed). Of course the actual barcodes in
+ the document must be of sufficient size.
+
+ --barcode-search-timeout 20..65535us [10000]
+ Sets the timeout for barcode searching in milliseconds. When
+ the timeout expires, the decoder will stop trying to decode bar-
+ codes.
+
+ --section <string> []
+ Specifies a series of image sections. A section can be used to
+ gather a subset image or to provide a small area for barcode
+ decoding. Each section is specified in the following format
+ (units are in millimeters):
+
+ <width>x<height>+<top-left-x>+<top-left-y>[:functioncode...]
+
+ Multiple sections can be specified by separating them with commas.
+
+ For example 76.2x25.4+50.8+0:frontbar identifies an area 3 inches wide
+ and 1 inch high with a top left corner at the top of the page two
+ inches from the left hand edge of the page. This section will be used
+ for barcode decoding on the front page only.
+
+ For example 50.8x25.4+25.4+0:frontbar:front:g42d identifies an area 2
+ inches wide and 1 inch high with a top left corner at the top of the
+ page one inch from the left hand edge of the page. This section will
+ be used for barcode decoding on the front page as well as generating an
+ image compressed in g42d format.
+
+ Ordinarily barcodes are searched in the entire image. However, when
+ you specify sections all barcode searching is done within the specific
+ sections identified. This can significantly speed up the decoding pro-
+ cess.
+
+ The following functioncodes are available:
+ front - generate an image for the front page section
+ back - generate an image for the back page section
+ frontbar - perform barcode search in front page section
+ backbar - perform barcode search in back page section
+ frontpatch - perform patchcode search in front page section
+ backpatch - perform patchcode search in back page section
+ none - use no image compression
+ g31d - use Group 3 1 dimension image compression
+ g32d - use Group 3 2 dimensions image compression
+ g42d - use Group 4 2 dimensions image compression
+
+ If you omit a compression functioncode, the full page compression set-
+ ting is used. If you specify multiple compression functioncodes, only
+ the last one is used.
+
+ --barcode-relmax 0..255 [0]
+ Specifies the maximum relation from the widest to the smallest
+ bar.
+
+ --barcode-barmin 0..255 [0]
+ Specifies the minimum number of bars in Bar/Patch code.
+
+ --barcode-barmax 0..255 [0]
+ Specifies the maximum number of bars in a Bar/Patch code.
+
+ --barcode-contrast 0..6 [3]
+ Specifies the image contrast used in decoding. Use higher val-
+ ues when there are more white pixels in the code.
+
+ --barcode-patchmode 0..1 [0]
+ Controls Patch Code detection.
+
+
+
+BUGS
+ This is a new backend; detailed bug reports are welcome -- and expected
+ ;)
+
+ If you have found something that you think is a bug, please attempt to
+ recreate it with the SANE_DEBUG_BH environment variable set to 255, and
+ send a report detailing the conditions surrounding the bug to
+ sane-devel@mostang.com.
+
+
+
+SEE ALSO
+ sane(7), sane-scsi(5), scanimage(1), scanadf(1)
+
+
+
+AUTHOR
+ The sane-bh backend was written by Tom Martone, based on the sane-ricoh
+ backend by Feico W. Dillema and the bnhscan program by Sean
+ Reifschneider of tummy.com ltd. Some 8000 enhancements added by Mark
+ Temple.
+
+sane-backends 1.0.12-cvs 15 Sep 1999 sane-bh(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-canon.5.html b/man/sane-canon.5.html
new file mode 100644
index 00000000..fbb6e0ab
--- /dev/null
+++ b/man/sane-canon.5.html
@@ -0,0 +1,119 @@
+
+
+sane-canon.5
+
+
+sane-canon.5
+
+
+
+sane-canon(5) SANE Scanner Access Now Easy sane-canon(5)
+
+
+
+NAME
+ sane-canon - SANE backend for Canon SCSI scanners
+
+
+
+DESCRIPTION
+ The sane-canon library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to the following Canon flatbed and film
+ scanners:
+
+ CanoScan 300
+ CanoScan 600
+ CanoScan FB620S
+ CanoScan FB1200S
+ CanoScan FS2700F
+ CanoScan FS2710S
+
+ Parallel port and USB scanners are not supported by this backend; see
+ the manual pages for sane-canon_pp and sane-canon630u for further
+ information.
+
+ IMPORTANT: This is beta code. We tested the code on the scanners listed
+ above, using the computers and operating systems available to us, but
+ we cannot guarantee that the backend will work smoothly with future
+ operating systems, SCSI adapters, SANE frontend programs, or Canon
+ scanners not contained in the list above. In some cases your computer
+ might even hang. It cannot be excluded (although we consider it
+ extremely unlikely) that your scanner will be damaged.
+
+ That said, TESTERS ARE WELCOME. Send your bug reports and comments to
+ Manuel Panea <mpd@rzg.mpg.de>; for questions concerning the FB620 and
+ FB1200S contact Mitsuru Okaniwa <m-okaniwa@bea.hi-ho.ne.jp>, for the
+ FS2710S Ulrich Deiters <ukd@xenon.pc.uni-koeln.de>.
+
+
+
+TIPS (FS2700F)
+ Scanning either slides or negatives has been found to require rather
+ large gamma corrections of about 2.2 to 2.4 (same value for red, green,
+ and blue). It is recommended to use the automatic exposure controls of
+ the frontend xsane for best results.
+
+ The "Auto Focus" function triggers a special pass to determine the
+ focus value. After that, the real scanning pass takes place.
+
+ Even with "Auto Focus" turned on, the scanned image is often a bit too
+ blurred. Using the GIMP to do a "Filter->Enhance->Sharpen" at about 40
+ to 60 improves the image considerably.
+
+
+
+TIPS (FS2710S)
+ Gamma corrections are done not by the scanner, but by the backend. The
+ scanner is always run in 12-bit mode. In "color" mode the image data
+ are corrected for gamma, shadow point, etc., and then truncated to
+ 8-bit intensities; the default gamma value is 2.0. In "raw" mode the
+ image data are exported without corrections as 16-bit intensities; this
+ mode can be recommended if extensive adjustments have to be made to a
+ picture (and if the frontend can handle 16-bit intensities).
+
+ Negatives are handled by simple color inversion and may require manual
+ removal of blue discoloration.
+
+
+
+FILES
+ /usr/local/lib/sane/libsane-canon.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-canon.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_DEBUG_CANON
+ If the library was compiled with debug support enabled, this
+ environment variable controls the debug level for this backend.
+ Higher debug levels increase the verbosity of the output.
+
+ Example: export SANE_DEBUG_CANON=4
+
+
+
+SEE ALSO
+ sane-scsi(5)
+ http://www.rzg.mpg.de/~mpd/sane/
+ doc/canon.install2700F.txt (installation of a CanoScan 2700F
+
+
+
+AUTHOR
+ Helmut Koeberle, Manuel Panea, and Markus Mertinat; FB620S and FB1200S
+ support by Mitsuru Okaniwa; FS2710S support by Ulrich Deiters
+ Man page by Henning Meier-Geinitz (mostly based on canon.README)
+
+sane-backends 1.0.12-cvs 03 May 2001 sane-canon(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-canon630u.5.html b/man/sane-canon630u.5.html
new file mode 100644
index 00000000..73bce8ed
--- /dev/null
+++ b/man/sane-canon630u.5.html
@@ -0,0 +1,135 @@
+
+
+sane-canon630u.5
+
+
+sane-canon630u.5
+
+
+
+sane-canon630u(5) SANE Scanner Access Now Easy sane-canon630u(5)
+
+
+
+NAME
+ sane-canon630u - SANE backend for the Canon 630u USB flatbed scanner
+
+
+
+DESCRIPTION
+ The sane-canon library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to the following Canon flatbed scanners:
+
+ CanoScan 630u
+ CanoScan 636u (hopefully)
+
+ IMPORTANT: this is alpha code. Although there are no known bugs at
+ this time, this code uses the Linux USB kernel drivers, which are cur-
+ rently in active development. So it may not work, your computer might
+ even hang, and it cannot be excluded (although I consider it extremely
+ unprobable) that your scanner will be damaged.
+
+ That said, TESTERS ARE WELCOME. Send your bug reports and comments to
+ Nathan Rutman <nathan@gordian.com>
+
+
+
+DEVICE NAMES
+ This backend expects device names of the form:
+
+ special
+
+ Where special is the path-name for the special device that corresponds
+ to a USB scanner or a symlink to such a device. The program sane-find-
+ scanner helps to find out the correct device. Under Linux, such a
+ device name could be /dev/usb/scanner0 for example. See sane-usb(5)
+ for details.
+
+
+
+CONFIGURATION
+ The contents of the canon630u.conf file is a list of device names that
+ correspond to Canon USB scanners. Empty lines and lines starting with
+ a hash mark (#) are ignored. Only one device name can be listed in
+ canon630u.conf.
+
+
+
+NOTES
+ Due to Canon's unwillingness to provide scanner documentation, this
+ software was developed by analyzing the USB traffic of the Windows 2000
+ driver. So things like the calibration procedure I kind of made up; it
+ seems to work for my scanner. If you have complaints, let me know.
+
+ This driver requires the ability to send USB Control Messages, avail-
+ able in kernel 2.4.12 or later.
+
+ This scanner may not be recognized (yet) by the USB kernel driver.
+ Check for "Driver=usbscanner" under /proc/bus/usb/devices. If
+ "Driver=(none)", try forcing it with "modprobe scanner vendor=0x04a9
+ product=0x2204"
+
+
+
+FILES
+ /usr/local/etc/sane.d/canon630u.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-canon630u.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-canon630u.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+ /tmp/canon.cal
+ The calibration file used to normalize pixel brightness. This
+ is calculated every time the scanner is first used after it has
+ lost power. It can be forced to recalibrate by simply deleting
+ this file.
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_CANON630U
+ If the library was compiled with debug support enabled, this
+ environment variable controls the debug level for this backend.
+ Higher debug levels increase the verbosity of the output.
+
+ Example: SANE_DEBUG_CANON630U=12 scanimage > /dev/null
+
+
+
+SEE ALSO
+ sane(7), sane-usb(5), sane-find-scanner(1)
+ http://canon-fb630u.sourceforge.net/
+
+
+
+AUTHOR
+ Nathan Rutman
+
+sane-backends 1.0.12-cvs 06 Apr 2002 sane-canon630u(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-canon_pp.5.html b/man/sane-canon_pp.5.html
new file mode 100644
index 00000000..5a7095dc
--- /dev/null
+++ b/man/sane-canon_pp.5.html
@@ -0,0 +1,233 @@
+
+
+sane-canon_pp.5
+
+
+sane-canon_pp.5
+
+
+
+sane-canon_pp(5) SANE Scanner Access Now Easy sane-canon_pp(5)
+
+
+
+NAME
+ sane-canon_pp - SANE backend for Canon CanoScan Parallel Port flatbed
+ scanners
+
+
+
+DESCRIPTION
+ The sane-canon_pp library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to the following Canon flatbed scanners:
+
+ CanoScan FB320P
+ CanoScan FB620P
+ CanoScan FB330P
+ CanoScan FB630P
+ CanoScan N340P
+ CanoScan N640P
+ CanoScan N640P ex
+
+ No USB scanners are supported and there are no plans to support them in
+ the future. Other projects are working on support for USB scanners.
+ See the PROJECTS file for more detail. The FB310P and FB610P are re-
+ badged Avision scanners which use a different command set, so are
+ unlikely to be supported by this backend in the future.
+
+ IMPORTANT: this is alpha code. While we have made every effort to make
+ it as reliable as possible, it will not always work as expected. Feed-
+ back is still appreciated. Please send any bug reports to the main-
+ tainers as listed on the web page (listed in SEE ALSO below).
+
+
+
+DEVICE NAMES
+ This backend expects device names of the form presented by libieee1284.
+ These names are highly dependent on operating system and version.
+
+ On Linux 2.4 kernels this will be of the form parport0 or older (2.2
+ and before) kernels may produce names like 0x378 (the base address of
+ your port) or simply 0 depending on your module configuration. Check
+ the contents of /proc/parport if it exists. If you don't want to spec-
+ ify a default port (or don't know its name), the backend should be able
+ to detect which port your scanner is on.
+
+
+
+CONFIGURATION
+ The contents of the canon_pp.conf file is a list of options for the
+ driver to use. Empty lines and lines starting with a hash mark (#) are
+ ignored.
+
+ The supported options are currently ieee1284, calibrate, init_mode, and
+ force_nibble
+
+ Option ieee1284 port-name defines which port to use. The format of
+ port-name is OS dependent, based on the names presented by libieee1284.
+ Please only have one of these lines, or all but one will be ignored.
+
+ Option calibrate cal-file [port-name] defines which calibration file to
+ use on a per-port basis. If you only have one parport, the port-name
+ argument may be omitted - but be careful as this will cause problems on
+ multi-scanner systems. You may have as many of these lines as you
+ like, as long as each has a unique port name. The tilde (`~') charac-
+ ter is acceptable and will be expanded to the value of the HOME envi-
+ ronment.
+
+ Option init_mode <AUTO|FB620P|FB630P> [portname] defines which
+ initialisation (wake-up) mode to use on a per-port basis. If you only
+ have one parport, the portname argument may be omitted - but be careful
+ as this may cause problems on multi-scanner systems. You may have as
+ many of these lines as you like, as long as each has a unique port
+ name. The valid initialisation modes are FB620P (which strobes
+ 10101010 and 01010101 on the data pins), FB630P (which strobes 11001100
+ and 00110011 on the data pins) and AUTO, which will try FB630P mode
+ first then FB620P mode second. The FB620P mode is also used by the
+ FB320P. The FB630P mode is used by the FB330P, N340P, and N640P.
+
+ Option force_nibble forces the driver to use nibble mode even if ECP
+ mode is reported to work by libieee1284. This works-around the rare
+ issue of ECP mode being reported to work by the library, then not work-
+ ing.
+
+
+
+TIPS
+ Hit the "Calibrate" button before scanning. It vastly improves the
+ quality of scans.
+
+ To enable automatic detection of your scanner, uncomment the "canon_pp"
+ line from /usr/local/etc/sane.d/dll.conf
+
+
+
+FILES
+ /usr/local/etc/sane.d/canon_pp.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-canon_pp.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-canon_pp.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_CANON_PP
+ If the library was compiled with debug support enabled, this
+ environment variable controls the debug level for this backend.
+ Higher debug levels increase the verbosity of the output.
+
+ Example: export SANE_DEBUG_CANON_PP=4
+
+
+
+NOTES
+ Features available in the Windows interface
+
+ Brightness and Contrast
+ These are not implemented, and probably never will be. These
+ appear to be implemented entirely in software. Use GIMP or a
+ similar program if you need these features.
+
+ Descreen Mode
+ This appears on our first analysis to be just oversampling with
+ an anti-aliasing filter. Again, it seems to be implemented
+ entirely in software, so GIMP is your best bet for now.
+
+ Gamma Tables
+ This is under investigation, but for now only a simple gamma
+ profile (ie: the one returned during calibration) will be
+ loaded.
+
+ Communication Problems
+
+ ECP mode in libieee1284 doesn't always work properly, even with new
+ hardware. We believe that this is a ppdev problem. If you change the
+ configuration file to include force_nibble , the problem will go away,
+ but you will only be able to scan in nibble mode.
+
+ Sometimes the scanner can be left in a state where our code cannot
+ revive it. If the backend reports no scanner present, try unplugging
+ the power and plugging it back in. Also try unplugging printers from
+ the pass-through port.
+
+ The scanner will not respond correctly to our commands when you first
+ plug in the power. You may find if you try a scan very soon after
+ plugging in the power that the backend will incorrectly report that you
+ have no scanner present. To avoid this, give it about 10 seconds to
+ reset itself before attempting any scans.
+
+ Repeated Lines
+
+ Sometimes at high resolutions (ie. 600dpi) you will notice lines which
+ appear twice. These lines correspond to points where the scanner head
+ has stopped during the scan (it stops every time the internal 64kb
+ buffer is full). Basically it's a mechanical problem inside the scan-
+ ner, that the tolerance of movement for a start/stop event is greater
+ than 1/600 inches. I've never tried the windows driver so I'm not sure
+ how (or if) it works around this problem, but as we don't know how to
+ rewind the scanner head to do these bits again, there's currently no
+ nice way to deal with the problem.
+
+ Grey-scale Scans
+
+ Be aware that the scanner uses the green LEDs to read grey-scale scans,
+ meaning green coloured things will appear lighter than normal, and red
+ and blue coloured items will appear darker than normal. For high-accu-
+ racy grey-scale scans of colour items, it's best just to scan in colour
+ and convert to grey-scale in graphics software such as the GIMP.
+
+ FB620P/FB320P Caveats
+
+ These models can not be reset in the same way as the others. The win-
+ dows driver doesn't know how to reset them either - when left with an
+ inconsistent scanner, it will start scanning half way down the page!
+
+ Aborting is known to work correctly on the FB*30P models, and is known
+ to be broken on the FB*20P models. The FB620P which I tested on simply
+ returns garbage after a scan has been aborted using the method we know.
+ Aborting is able to leave the scanner in a state where it can be shut
+ down, but not where another scan can be made.
+
+
+
+SEE ALSO
+ sane(7), sane-dll(5) http://canon-fb330p.sourceforge.net/
+
+
+
+AUTHOR
+ This backend is primarily the work of Simon Krix (Reverse Engineering),
+ and Matthew Duggan (SANE interface).
+
+ Many thanks to Kevin Easton for his comments and help, and Kent A. Sig-
+ norini for his help with the N340P.
+
+sane-backends 1.0.12-cvs 1 October 2002 sane-canon_pp(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-config.1.html b/man/sane-config.1.html
new file mode 100644
index 00000000..295a6293
--- /dev/null
+++ b/man/sane-config.1.html
@@ -0,0 +1,79 @@
+
+
+sane-config.1
+
+
+sane-config.1
+
+
+
+sane-config(1) SANE Scanner Access Now Easy sane-config(1)
+
+
+
+NAME
+ sane-config - get information about the installed version of libsane
+
+
+
+SYNOPSIS
+ sane-config [--prefix] [--exec-prefix] [--libs] [--cflags] [--ldflags]
+ [--version] [--help [OPTION]]
+
+
+
+DESCRIPTION
+ sane-config is a tool that is used to determine the compiler and linker
+ flags that should be used to compile and link SANE frontends to a SANE
+ backend library (libsane).
+
+
+
+OPTIONS
+ sane-config accepts the following options:
+
+ --version
+ Print the currently installed version of libsane on the stan-
+ dard output.
+
+ --help OPTION
+ Print a short usage message. If OPTION is specified, help for
+ that option (e.g. --libs) is printed (if available).
+
+ --libs Print the additional libraries that are necessary to link a
+ SANE frontend to libsane.
+
+ --ldflags
+ Print the linker flags that are necessary to link a SANE fron-
+ tend to libsane.
+
+ --cflags
+ Print the compiler flags that are necessary to compile a SANE
+ frontend.
+
+ --prefix
+ Print the prefix used during compilation of libsane.
+
+ --exec-prefix
+ Print the exec-prefix used during compilation of libsane.
+
+
+
+SEE ALSO
+ sane(7)
+
+
+
+AUTHOR
+ This manual page was written by Julien BLACHE <jblache@debian.org>, for
+ the Debian GNU/Linux system (but may be used by others).
+
+sane-backends 1.0.12-cvs 15 October 2002 sane-config(1)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-coolscan.5.html b/man/sane-coolscan.5.html
new file mode 100644
index 00000000..93a6570f
--- /dev/null
+++ b/man/sane-coolscan.5.html
@@ -0,0 +1,133 @@
+
+
+sane-coolscan.5
+
+
+sane-coolscan.5
+
+
+
+sane-coolscan(5) SANE Scanner Access Now Easy sane-coolscan(5)
+
+
+
+NAME
+ sane-coolscan - SANE backend for Nikon film-scanners
+
+
+
+ABOUT THIS FILE
+ This file is a short descripton of the coolscan-backend for sane!
+
+
+
+DESCRIPTION
+ The sane-coolscan library implements a SANE backend that provides the
+ interface to the following Nikon Coolscan Film scanners: Nikon LS20,
+ LS30, LS1000, LS2000.
+
+ Even though the backend has worked for a number of people, there are
+ still some problems, especially in combination with some SCSI
+ card/drivers (AHA-1505/aha152x.o) and the autofocus command. You should
+ consider this backend 'alpha' and be carefull when using it the first
+ time.
+
+
+
+CONFIGURATION
+ The configuration file for this backend resides in
+ /usr/local/etc/sane.d/coolscan.conf.
+
+ Its contents is a list of device names that correspond to Nikon
+ Coolscan scanners. Empty lines and lines starting with a hash mark (#)
+ are ignored. A sample configuration file is shown below:
+
+ #scsi Vendor Model Type
+ scsi Nikon * Scanner
+ /dev/scanner
+
+ The special device name must be a generic SCSI device or a symlink to
+ such a device. To find out to which device your scanner is assigned
+ and how you have to set the permissions of that device, have a look at
+ sane-scsi.
+
+
+
+SCSI ADAPTER TIPS
+ Some SCSI-adapters and low-level SCSI drivers do not work correctly
+ with this backend and the Coolscan scanners. These systems hang when
+ the autofocus command is send to the Scanner. To see a list of which
+ card/driver combinations work or dont work have a look at:
+ http://andreas.rick.free.fr/sane/autofocus.html.
+
+
+
+FILES
+ The backend configuration file:
+ /usr/local/etc/sane.d/coolscan.conf.
+
+ The static library implementing this backend:
+ /usr/local/lib/sane/libsane-coolscan.a
+
+ The shared library implementing this backend:
+ /usr/local/lib/sane/libsane-coolscan.so
+ (present on systems that support dynamic loading)
+
+
+
+ENVIRONMENT
+ SANE_DEBUG_COOLSCAN
+ If the library was compiled with debug support enabled, this
+ environment variable controls the debug level for this backend. E.g., a
+ value of 128 requests all debug output to be printed. Smaller levels
+ reduce verbosity: SANE_DEBUG_COOLSCAN values
+
+ Examples:
+ on bash:
+ export SANE_DEBUG_COOLSCAN=8
+ on csh
+ setenv SANE_DEBUG_COOLSCAN 8
+
+
+
+BUGS
+ The autofocus command does not work with some SCSI card/driver combi-
+ nations
+ The gamma table is not implemented for the LS1000 yet.
+ The dust-removal is not working yet
+
+
+
+SEE ALSO
+ http://andreas.rick.free.fr/sane/ The homepage of this backend
+ http://www.sema.be/coolscan/ The original version of the coolscan
+ backend by Didier
+ sane(7), sane-scsi(5)
+
+
+
+THANKS TO
+ Didier Carlier - For writing the original Coolscan backend (without it
+ I would not have started this)
+ Oliver.Rauch - For adapting xsane so quickly to the infrared stuff.
+ All the other people working on SANE.
+
+
+
+AUTHOR
+ Andreas Rick
+
+
+
+EMAIL-CONTACT
+ andreas.rick@free.fr
+
+sane-backends 1.0.12-cvs 4 July 2000 sane-coolscan(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-coolscan2.5.html b/man/sane-coolscan2.5.html
new file mode 100644
index 00000000..a5f0b1fc
--- /dev/null
+++ b/man/sane-coolscan2.5.html
@@ -0,0 +1,203 @@
+
+
+sane-coolscan2.5
+
+
+sane-coolscan2.5
+
+
+
+sane-coolscan2(5) SANE Scanner Access Now Easy sane-coolscan2(5)
+
+
+
+NAME
+ sane-coolscan2 - SANE backend for Nikon Coolscan film scanners
+
+
+
+DESCRIPTION
+ The library implements a SANE (Scanner Access Now Easy) backend that
+ provides access to Nikon Coolscan film scanners. Some functions of
+ this backend should be considered beta-quality software. Most functions
+ have been stable for a long time, but of course new development can not
+ and will not function properly from the very first day. Please report
+ any strange behaviour to the maintainer of the backend.
+
+ At present, the following scanners are known to work with this backend:
+
+ Model: Connection Type
+ --------------------------- -------------------
+ LS-30 (Coolscan III) SCSI
+ LS-2000 SCSI
+ LS-40 ED (Coolscan IV) USB
+ LS-4000 ED IEEE 1394
+ LS-8000 ED IEEE 1394
+
+ Please send mail to the backend author (andras@users.sourceforge.net)
+ to report successes or failures.
+
+
+
+OPTIONS
+ The options the backend supports can either be selected through command
+ line options to programs like scanimage or through GUI elements in
+ xscanimage or xsane.
+
+ Valid command line options and their syntax can be listed by using
+ scanimage --help -d coolscan2:<interface>:<device>
+ where <interface> and <device> specify the device in question, as in
+ the configuration file (see next section). The "-d" parameter and its
+ argument can be omitted to obtain information on the first scanner
+ identified. Use the command
+ scanimage -L
+ to list all devices recognized by your SANE installation.
+
+ The options should be fully described by the description or tooltips
+ given by frontend. Here is a description of some of the most important
+ options, in the syntax with which they must be supplied to scanimage:
+
+ --frame <n>
+ This option specifies which frame to operate on, if a motorized
+ film strip feeder or APS adapter are used. The frame number <n>
+ ranges from 1 to the number of frames available, which is sensed
+ each time the backend is initialized (usually each time you
+ start the frontend).
+
+ --subframe <x>
+ This option shifts the scan window by the specified amount
+ (default unit is mm).
+
+ --infrared=yes/no
+ If set to "yes", the scanner will read the infrared channel,
+ thus allowing defect removal in software. The infrared image is
+ read during a second scan, with no options altered. The backend
+ must not be restarted between the scans. If you use scanimage,
+ perform a batch scan with batch-count=2 to obtain the IR infor-
+ mation.
+
+ --depth <n>
+ Here <n> can either be 8 or the maximum number of bits supported
+ by the scanner (10, 12, or 14). It specifies whether or not the
+ scanner reduces the scanned data to 8 bits before sending it to
+ the backend. If 8 bits are used, some information and thus image
+ quality is lost, but the amount of data is smaller compared to
+ higher depths. Also, many imaging programs and image formats
+ cannot handle depths greater than 8 bits.
+
+ --autofocus
+ Perform autofocus operation. Unless otherwise specified by the
+ other options ( --focus-on-centre and friends), focusing is per-
+ formed on the centre of the selected scan area.
+
+ --ae-wb
+
+ --ae Perform a pre-scan to calculate exposure values automatically.
+ --ae-wb will maintain the white balance, while --ae will adjust
+ each channel separately.
+
+ --exposure
+ Multiply all exposure times with this value. This allows expo-
+ sure correction without modifying white balance.
+
+ --load Load the next slide when using the slide loader.
+
+ --eject
+ Eject the film strip or mounted slide when using the slide
+ loader.
+
+ --reset
+ Reset scanner. The scanner will perform the same action as when
+ power is turned on: it will eject the film strip and calibrate
+ itself. Use this whenever the scanner refuses to load a film
+ strip properly, as a result of which --eject does not work.
+
+
+
+CONFIGURATION FILE
+ The configuration file /usr/local/etc/sane.d/coolscan2.conf specifies
+ the device(s) that the backend will use. Owing to the nature of the
+ supported connection types SCSI, USB, and IEEE 1394, the default con-
+ figuration file supplied with the SANE distribution should work without
+ being edited.
+
+ Each line in the configuration file is either of the following, where
+ all entries are case-sensitive:
+
+ blank or starting with a '#' character
+ These lines are ignored, thus '#' can be used to include com-
+ ments.
+
+ containing only the word "auto"
+ This instructs the backend to probe for a scanner by scanning
+ the buses for devices with know identifiers. This is the action
+ taken when no configuration file is present.
+
+ a line of the form <interface>:<device>
+ Here <interface> can be one of "scsi" or "usb", and <device> is
+ the device file of the scanner. Note that IEEE 1394 devices are
+ handled by the SBP-2 module in the kernel and appear to SANE as
+ SCSI devices.
+
+
+
+FILES
+ /usr/local/lib/sane/libsane-coolscan2.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-coolscan2.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+ /usr/local/etc/sane.d/coolscan2.conf
+ Configuration file for this backend, read each time the backend
+ is initialized.
+
+
+
+ENVIRONMENT
+ SANE_DEBUG_COOLSCAN2
+ 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.
+
+
+
+SEE ALSO
+ sane-scsi(5), sane-usb(5), scanimage(1), xscanimage(1), xsane(1)
+
+
+
+BUGS
+ Currently, the SANE protocol does not allow automatically updating
+ options whenever the hardware changes. Thus the number of choices for
+ the --frame option will be fixed when the backend is initialized (usu-
+ ally when the user runs the frontend). In particular, if there is no
+ film strip in the automatic film strip feeder when the backend is ini-
+ tialized, the frame option will not appear at all. Also, restarting the
+ frontend after swapping film adapters is strongly recommended.
+
+ Linux kernels prior to 2.4.19 had a patch that truncated INQUIRY data
+ from IEEE 1394 scanners to 36 bytes, discarding vital information about
+ the scanner. The IEEE 1394 models therefore only work with 2.4.19 or
+ later.
+
+ No real bugs currently known, please report any to the backend main-
+ tainer or the SANE developers' email list.
+
+
+
+AUTHORS
+ The backend is written and maintained by Andr?s Major
+ (andras@users.sourceforge.net).
+
+sane-backends 1.0.12-cvs 22/08/2002 sane-coolscan2(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-dc210.5.html b/man/sane-dc210.5.html
new file mode 100644
index 00000000..c3c2df6e
--- /dev/null
+++ b/man/sane-dc210.5.html
@@ -0,0 +1,134 @@
+
+
+sane-dc210.5
+
+
+sane-dc210.5
+
+
+
+sane-dc210(5) SANE Scanner Access Now Easy sane-dc210(5)
+
+
+
+NAME
+ sane-dc210 - SANE backend for Kodak DC210 Digital Camera
+
+
+
+DESCRIPTION
+ The sane-dc210 library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to the Kodak DC210 camera. THIS IS
+ EXTREMELY ALPHA CODE! USE AT YOUR OWN RISK!!
+
+
+
+DEVICE NAMES
+ The current version of the backend only allows one camera to be con-
+ nected. The device name is always "0".
+
+
+
+CONFIGURATION
+ The contents of the dc210.conf specify the serial port and baud rate to
+ use. The baud rate specifies the maximum rate to use while downloading
+ pictures. (The camera is always initialized using 9600 baud, then
+ switches to the higher rate). On my 90MHz Pentium, I usually have no
+ problems downloading at 115200 baud as long as the system is not exces-
+ sively busy and the "interrupt-unmask flag" is set in the IDE driver
+ (hdparm -u1). Supported baud rates are: 9600, 19200, 38400, 57600, and
+ 115200.
+
+ The dumpinquiry line causes some information about the camera to be
+ printed.
+
+ cmdrespause specifies how many usec (1,000,000ths of a) between writing
+ the command and reading the result should be used. 125000 seems to be
+ the lowest I could go reliably.
+
+ breakpause is the time in 1,000,000ths of a usec between sending the
+ "back to default" break sending commands.
+
+ Empty lines and lines starting with a hash mark (#) are ignored. A
+ sample configuration file is shown below:
+
+ port=/dev/ttyS0
+ # this is a comment
+ baud=115200
+ dumpinquiry
+ cmdrespause=125000
+ breakpause=1000000
+
+
+
+FILES
+ /usr/local/etc/sane.d/dc210.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-dc210.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-dc210.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the
+ configuration file is searched in two default directories:
+ first, the current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_DC210
+ If the library was compiled with debugging support enabled, this
+ environment variable controls the debug level for this backend.
+ A value of 128 requests maximally copious debug output; smaller
+ levels reduce verbosity.
+
+
+
+SEE ALSO
+ sane(7)
+
+
+
+AUTHOR
+ Brian J. Murrell
+
+ This backend is based somewhat on the dc25 backend included in this
+ package by Peter Fales.
+
+ The manpage was copied from the dc25 backend and somewhat edited by
+ Henning Meier-Geinitz.
+
+
+
+BUGS
+ Known bugs/limitations are: ?
+
+ More general comments, suggestions, and inquiries about frontends or
+ SANE should go to the SANE Developers mailing list (see
+ http://www.mostang.com/sane/mail.html for details). You must be sub-
+ scribed to the list, otherwise your mail won't be sent to the sub-
+ scribers.
+
+sane-backends 1.0.12-cvs 15 July 2000 sane-dc210(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-dc240.5.html b/man/sane-dc240.5.html
new file mode 100644
index 00000000..59055993
--- /dev/null
+++ b/man/sane-dc240.5.html
@@ -0,0 +1,137 @@
+
+
+sane-dc240.5
+
+
+sane-dc240.5
+
+
+
+sane-dc240(5) SANE Scanner Access Now Easy sane-dc240(5)
+
+
+
+NAME
+ sane-dc240 - SANE backend for Kodak DC240 Digital Camera
+
+
+
+DESCRIPTION
+ The sane-dc240 library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to the Kodak DC240 camera. THIS IS
+ EXTREMELY ALPHA CODE! USE AT YOUR OWN RISK!!
+
+
+
+DEVICE NAMES
+ The current version of the backend only allows one camera to be con-
+ nected. The device name is always "0".
+
+
+
+CONFIGURATION
+ The contents of the dc240.conf specify the serial port and baud rate to
+ use. The baud rate specifies the maximum rate to use while downloading
+ pictures. (The camera is always initialized using 9600 baud, then
+ switches to the higher rate). On a 450MHz Pentium, I usually have no
+ problems downloading at 115200 baud, though the camera sometimes has to
+ resend packets due to lost characters. Results are better when the
+ "interrupt-unmask flag" is set in the IDE driver (hdparm -u1). Sup-
+ ported baud rates are: 9600, 19200, 38400, 57600, and 115200.
+
+ The dumpinquiry line causes some information about the camera to be
+ printed.
+
+ cmdrespause specifies how many usec (1,000,000ths of a) between writing
+ the command and reading the result should be used. 125000 seems to be
+ the lowest I could go reliably.
+
+ breakpause is the time in 1,000,000ths of a usec between sending the
+ "back to default" break sending commands.
+
+ Empty lines and lines starting with a hash mark (#) are ignored. A
+ sample configuration file is shown below:
+
+ port=/dev/ttyS0
+ # this is a comment
+ baud=115200
+ dumpinquiry
+ cmdrespause=125000
+ breakpause=1000000
+
+
+
+FILES
+ /usr/local/etc/sane.d/dc240.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-dc240.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-dc240.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the
+ configuration file is searched in two default directories:
+ first, the current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_DC240
+ If the library was compiled with debugging support enabled, this
+ environment variable controls the debug level for this backend.
+ A value of 128 requests maximally copious debug output; smaller
+ levels reduce verbosity.
+
+
+
+SEE ALSO
+ sane(7)
+
+
+
+AUTHOR
+ Peter S. Fales
+
+ This backend borrows heavily from the dc210 backend by Brian J. Murrell
+ which is based somewhat on the dc25 backend by Peter Fales.
+
+ The manpage was largeley copied from the dc210 manpage.
+
+
+
+BUGS
+ The major limitation that I know of is that the backend assumes the
+ directory in the camera is 100dc240. Once the camera has taken more
+ than 9999 pictures, the directory will increment to 101dc240. Not only
+ should we check for the additional directory, but pictures may actually
+ be found in multiple directories.
+
+ More general comments, suggestions, and inquiries about frontends or
+ SANE should go to the SANE Developers mailing list (see
+ http://www.mostang.com/sane/mail.html for details). You must be sub-
+ scribed to the list, otherwise your mail won't be sent to the sub-
+ scribers.
+
+sane-backends 1.0.12-cvs 23 March 2001 sane-dc240(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-dc25.5.html b/man/sane-dc25.5.html
new file mode 100644
index 00000000..9e20c888
--- /dev/null
+++ b/man/sane-dc25.5.html
@@ -0,0 +1,127 @@
+
+
+sane-dc25.5
+
+
+sane-dc25.5
+
+
+
+sane-dc25(5) SANE Scanner Access Now Easy sane-dc25(5)
+
+
+
+NAME
+ sane-dc25 - SANE backend for Kodak DC20/DC25 Digital Cameras
+
+
+
+DESCRIPTION
+ The sane-dc25 library implements a SANE (Scanner Access Now Easy) back-
+ end that provides access to Kodak DC20 and DC25 cameras. At present,
+ only the DC25 has been tested, but since the code is based on a DC20
+ interface program, it is likely to work for that model also.
+
+
+
+DEVICE NAMES
+ The current version of the backend only allows one camera to be con-
+ nected. The device name is always "0".
+
+
+
+CONFIGURATION
+ The contents of the dc25.conf specify the serial port and baud rate to
+ use. The baud rate specifies the maximum rate to use while downloading
+ pictures. (The camera is always initialized using 9600 baud, then
+ switches to the higher rate). On my 90MHz Pentium, I usually have no
+ problems downloading at 115200 baud as long as the system is not exces-
+ sively busy and the "interrupt-unmask flag" is set in the IDE driver
+ (hdparm -u1). Supported baud rates are: 9600, 19200, 38400, 57600, and
+ 115200.
+
+ The dumpinquiry line causes some information about the camera to be
+ printed to stderr during startup. Note: This is not compatible with
+ saned, so make sure you don't have any dumpinquiry lines if you are
+ using saned (i.e. scanning on a remote machine using a network).
+
+ Empty lines and lines starting with a hash mark (#) are ignored. A
+ sample configuration file is shown below:
+
+ port=/dev/ttyS0
+ # this is a comment
+ baud=115200
+ dumpinquiry
+
+
+
+FILES
+ /usr/local/etc/sane.d/dc25.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-dc25.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-dc25.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_DC25
+ If the library was compiled with debugging support enabled, this
+ environment variable controls the debug level for this backend.
+ A value of 128 requests maximally copious debug output; smaller
+ levels reduce verbosity.
+
+
+
+SEE ALSO
+ sane(7)
+
+
+
+AUTHOR
+ Peter Fales, dc25-devel@fales-lorenz.net
+
+
+
+BUGS
+ Known bugs/limitations are:
+
+ I haven't figured out how to trigger an option reload following a
+ "scan." This causes problems when a new picture is snapped for exam-
+ ple, the slider that is used to select the picture from the camera may
+ not be updated immediately.
+
+ More general comments, suggestions, and inquiries about frontends or
+ SANE should go to the SANE Developers mailing list (see
+ http://www.mostang.com/sane/mail.html for details). You must be sub-
+ scribed to the list, otherwise your mail won't be sent to the sub-
+ scribers.
+
+sane-backends 1.0.12-cvs 12 April 1999 sane-dc25(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-dll.5.html b/man/sane-dll.5.html
new file mode 100644
index 00000000..20ad1c38
--- /dev/null
+++ b/man/sane-dll.5.html
@@ -0,0 +1,159 @@
+
+
+sane-dll.5
+
+
+sane-dll.5
+
+
+
+sane-dll(5) SANE Scanner Access Now Easy sane-dll(5)
+
+
+
+NAME
+ sane-dll - SANE dynamic backend loader
+
+
+
+DESCRIPTION
+ The sane-dll library implements a SANE (Scanner Access Now Easy) back-
+ end that provides access to an arbitrary number of other SANE backends.
+ These backends may either be pre-loaded at the time the sane-dll
+ library is built or, on systems that support dynamic loading of shared
+ libraries, the backends may be loaded at runtime. In the latter case,
+ adding support for a new backend simply involves installing the rele-
+ vant library in /usr/local/lib/sane and adding an entry to the dll.conf
+ configuration file. In other words, no applications need to be modi-
+ fied or recompiled to add support for new devices.
+
+
+
+DEVICE NAMES
+ This backend expects device names of the form:
+
+ backend:device
+
+ Where backend is the name of the backend and device is the name of the
+ device in this backend that should be addressed. If the device name
+ does not contain a colon (:), then the entire string is treated as the
+ device string for the default backend. The default backend is the
+ backend listed last in the configuration file (see below) or the first
+ pre-loaded backend (if any).
+
+
+
+CONFIGURATION
+ The contents of the dll.conf file is a list of backend names that may
+ be loaded dynamically upon demand. Empty lines are ignored, also
+ everything after a hash mark (#). A sample configuration file is shown
+ below:
+
+ net
+ # this is a comment
+ pnm
+ mustek
+
+ Note that backends that were pre-loaded when building this library do
+ not have to be listed in this configuration file. That is, if a back-
+ end was preloaded, then that backend will always be present, regardless
+ of whether it's listed in the configuration file or not.
+
+ The list of preloaded backends is determined by macro PRELOADABLE_BACK-
+ ENDS in file backend/Makefile.in of the SANE source code distribution.
+ After changing the value of this macro, it is necessary to reconfigure,
+ rebuild, and reinstall SANE for the change to take effect.
+
+ Aliases are defined in the config file dll.aliases. It can contain
+ entries of the form
+
+ alias SomeName SaneDeviceName
+ alias "Some Name" SaneDeviceName
+ hide SaneDeviceName
+
+ For example:
+
+ alias Epson net:somehost:epson:/dev/sgX
+ alias "Siemens ST400" st400:/dev/sgY
+ hide net:somehost:pnm:0
+ hide net:somehost:pnm:1
+ alias "Read from file" pnm:0
+ hide pnm:1
+
+ Aliased device names are automatically hidden.
+
+ The idea is that users don't have to deal with complicated device names
+ (especially for networked devices), and to hide other exported devices
+ which might confuse them. Note that a hidden device can still be
+ accessed if the device name is known, it just doesn't appear on the
+ list.
+
+
+
+FILES
+ /usr/local/etc/sane.d/dll.aliases
+ The list of aliased or hidden backends.
+
+ /usr/local/etc/sane.d/dll.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-dll.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-dll.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_DLL
+ If the library was compiled with debug support enabled, this
+ environment variable controls the debug level for this backend.
+ E.g., a value of 128 requests all debug output to be printed.
+ Smaller levels reduce verbosity.
+
+ Value Description
+ 0 print severe errors only
+ 1 print normal errors and important messages
+ 2 print normal messages
+ 3 print debugging messages
+ 4 print everything
+
+ Example:
+ export SANE_DEBUG_DLL=3
+
+
+
+SEE ALSO
+ sane(7), scanimage(1), sane-"backendname"(5)
+
+
+
+AUTHOR
+ David Mosberger
+
+sane-backends 1.0.12-cvs 4 Dec 2002 sane-dll(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-dmc.5.html b/man/sane-dmc.5.html
new file mode 100644
index 00000000..293fc969
--- /dev/null
+++ b/man/sane-dmc.5.html
@@ -0,0 +1,170 @@
+
+
+sane-dmc.5
+
+
+sane-dmc.5
+
+
+
+sane-dmc(5) SANE Scanner Access Now Easy sane-dmc(5)
+
+
+
+NAME
+ sane-dmc - SANE backend for the Polaroid Digital Microscope Camera
+
+
+
+DESCRIPTION
+ The sane-dmc library implements a SANE (Scanner Access Now Easy) back-
+ end that provides access to the Polaroid Digital Microscope Camera.
+
+
+
+DEVICE NAMES
+ This backend expects device names of the form:
+
+ special
+
+ Where special is the UNIX path-name for the special device that corre-
+ sponds to the scanner. The special device name must be a generic SCSI
+ device or a symlink to such a device. Under Linux, such a device name
+ could be /dev/sga or /dev/sge, for example.
+
+
+
+IMAGING MODES
+ The Polaroid DMC supports a number of imaging modes. This driver sup-
+ ports five of the imaging modes:
+
+ Full Frame
+ This mode corresponds to the 801-by-600 pixel full-color full-
+ frame image.
+
+ Viewfinder
+ This mode corresponds to the 270-by-201 pixel grey-scale
+ viewfinder image. This image is acquired very quickly.
+
+ Raw This mode corresponds to the 1599-by-600 pixel "raw" image from
+ the CCD. It is grey-scale, with pixels alternating horizontally
+ between red, green and blue stripes. The pixels are twice as
+ high as they are wide, so the image is distorted.
+
+ Thumbnail
+ This mode corresponds to the 80-by-60 pixel full-color thumbnail
+ image.
+
+ Super Resolution
+ This image is a 1599-by-1200 pixel full-color image constructed
+ by filtering and interpolating the "raw" image. The filtering
+ and interpolation is done in software, so this mode is very
+ slow. Also, this mode places restrictions on how the image is
+ read which means that the "preview" mode of xscanimage does not
+ work in Super Resolution mode. (xcam and the non-preview modes
+ of scanimage and xscanimage work fine, however.)
+
+
+
+OTHER SETTINGS
+ ASA Setting
+ This setting adjusts the camera's sensitivity. You can choose
+ one of 25, 50, or 100 "equivalent" ASA.
+
+ Shutter Speed
+ You can select a shutter speed from 8 to 1000 milliseconds. The
+ shutter speed is quantized in units of 32 microseconds.
+
+ White Balance
+ You can choose one of "Daylight", "Incandescent" or "Fluores-
+ cent" white balances. This setting more-or-less corresponds to
+ the "Color Temperature" settings on Polaroid's Windows and Mac
+ software.
+
+
+
+CONFIGURATION
+ The contents of the dmc.conf file is a list of device names that corre-
+ spond to DMC scanners. Empty lines and lines starting with a hash mark
+ (#) are ignored. A sample configuration file is shown below:
+
+ /dev/scanner
+ # this is a comment
+ /dev/sge
+
+
+
+FILES
+ /usr/local/etc/sane.d/dmc.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-dmc.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-dmc.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_DMC
+ 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.
+
+
+
+BUGS
+ In the "Full Frame" and "Raw" modes, images must be read in units of
+ entire lines. The driver performs no buffering in these modes; if you
+ ask sane_read to read a non-integral number of lines, it may read less
+ than you ask for. If you ask sane_read to read less than a single
+ line, it returns SANE_STATUS_INVAL.
+
+ In the "Super Resolution" mode, images must be read in units of two
+ lines (3198 pixels or 9594 bytes.) If you try to read less than two
+ lines, you get SANE_STATUS_INVAL. The Super Resolution mode is very
+ slow.
+
+ In the "Viewfinder" and "Thumbnail" modes, the entire image must be
+ read in one SCSI transfer. In this case, the driver performs buffering
+ and you can read the image in as small an increment as you like.
+
+
+
+SEE ALSO
+ sane(7), sane-scsi(5)
+
+
+
+AUTHOR
+ David F. Skoll
+
+ The backend is derived from sane-hp by David Mosberger
+
+sane-backends 1.0.12-cvs 13 May 1998 sane-dmc(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-epson.5.html b/man/sane-epson.5.html
new file mode 100644
index 00000000..d94c35d8
--- /dev/null
+++ b/man/sane-epson.5.html
@@ -0,0 +1,295 @@
+
+
+sane-epson.5
+
+
+sane-epson.5
+
+
+
+sane-epson(5) SANE Scanner Access Now Easy sane-epson(5)
+
+
+
+NAME
+ sane-epson - SANE backend for EPSON scanners
+
+
+
+DESCRIPTION
+ The sane-epson library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to Epson flatbed scanners. Some functions
+ of this backend should be considered beta-quality software! Most func-
+ tions have been stable for a long time, but of course new development
+ can not and often times will not function properly from the very first
+ day. Please report any strange behavior to the maintainer of the back-
+ end.
+
+ At present, the following scanners are known to work with this backend:
+
+ Model: Connection Type
+ --------------------------- -------------------
+ GT-5000 parallel
+ GT-6000 parallel
+ ActionScanner II parallel
+ GT-7000 SCSI
+ Perfection 636 SCSI
+ Perfection 636U USB
+ Perfection 610 USB
+ Perfection 640 USB
+ Perfection 1200S SCSI
+ Perfection 1200U USB
+ Perfection 1240 USB, SCSI
+ Perfection 1640 USB, SCSI
+ Perfection 1650 USB
+ Perfection 1660 USB
+ Perfection 2400 USB
+ Perfection 2450 USB, IEEE-1394
+ Expression 636 / GT-9500 SCSI
+ Expression 1600 USB, SCSI, IEEE-1394
+ Expression 1680 USB, SCSI, IEEE-1394
+ CX-3200 USB
+ CX-5200 USB
+
+ For other scanners the software may or may not work. Please send mail
+ to the backend author (khk@khk.net) to report success with scanners not
+ on the list or problems with scanners that are listed.
+
+
+
+OPTIONS
+ The options the backend supports can either be selected through command
+ line options to programs like scanimage or through GUI elements in pro-
+ grams like xscanimage or xsane.
+
+ Valid command line options and their syntax can be listed by using
+ scanimage --help -d epson
+ Not all devices support all options.
+
+ Scan Mode
+ The --mode switch selects the basic mode of operation of the
+ scanner. Valid choices are Binary, Gray and Color. The Binary
+ mode is black and white only, Gray will produce 256 levels of
+ gray or more depending on the scanner and Color means 24 bit
+ color mode or more depending on the scanner. Some scanners will
+ internally use 36 bit color, their external interface however
+ may only support 24 bits.
+
+ The --depth option selects the bit depth the scanner is using.
+ This option is only available for scanners that support more
+ than one bit depth. Older scanners will always transfer the
+ image in 8bit mode. Newer scanners allow to select either 8
+ bits, 12 or 14 bits per color channel. For a color scan this
+ means an effective color depth of 36 or 42 bits over all three
+ channels. The valid choices depend on the scanner model.
+
+ The --halftoning switch selects the mode that is used in Binary
+ mode. Valid options are "None", "Halftone A (Hard Tone)",
+ "Halftone B (Soft Tone)", "Halftone C (Net Screen)", "Dither A
+ (4x4 Bayer)", "Dither B (4x4 Spiral)", "Dither C (4x4 Net
+ Screen)", "Dither D (8x4 Net Screen)", "Text Enhanced Technol-
+ ogy", "Download pattern A", and "Download pattern B".
+
+ The --dropout switch selects the so called dropout color. Vald
+ options are None, Red, Green and Blue. The default is None. The
+ dropout color is used for monochrome scanning and selects the
+ color that is not scanned. This can be used to e.g. scan an
+ original with a colored background.
+
+ The --brightness switch controls the brightness of the scan.
+ Valid options are integer values from -3 to 3. The default is 0.
+ The larger the brightness value, the brighter the image gets. If
+ a user defined table for the gamma correction is selected, the
+ brightness parameter is not available.
+
+ The --sharpness switch sets the sharpness of the image data.
+ Valid options are integer values from -2 to 2, with -2 meaning
+ "Defocus", -1 "Defocus slightly", 0 "Normal", 1 "Sharpen
+ slighly" and 2 "Sharpen".
+
+ The --gamma-correction switch controls the scanner's internal
+ gamma correction. Valid options are "Default", "User defined",
+ "High density printing" "Low density printing" and "High con-
+ trast printing".
+
+ The --color-correction switch controls the scanner's internal
+ color correction function. Valid options are "No Correction",
+ "Impact-dot printers", "Thermal printers", "Ink-jet printers"
+ and "CRT monitors". The default is "CRT monitors".
+
+ The --resolution switch selects the resolution for a scan. Some
+ EPSON scanners will scan in any resulution between the lowest
+ and highest possible value. The list reported by the scanner can
+ be displayed using the "--help -d epson" parameters to scanim-
+ age.
+
+ The --mirror option controls the way the image is scanned. By
+ reading the image data from right to left the image is mirored.
+ Valid options are "yes" and "no". The default is "no".
+
+ The --speed option can improve the scan speed in monochrome
+ mode. Valid options are "yes" or "no", the "yes" option will
+ speed up the scan if this option is supported.
+
+ The --auto-area-segmentation switch activates the automatic area
+ segmentation for monochrome scans. The scanner will try to
+ determine which areas are text and which contain images. The
+ image areas will be halftoned, and the text will be impoved.
+ Valid options are "yes" and "no". The default is "yes".
+
+ The --gamma-table parameter can be used to download a user
+ defined gamma table. The option takes 256 values from the range
+ 0-255. In color mode this option equally affects the red, green,
+ and blue channel.
+
+ The --red-gamma-table parameter can be used to download a user
+ defined gamma table for the red channel. The valid options are
+ the same as for --gamma-table.
+
+ The --green-gamma-table parameter can be used to download a user
+ defined gamma table for the green channel. The valid options are
+ the same as for --gamma-table.
+
+ The --blue-gamma-table parameter can be used to download a user
+ defined gamma table for the blue channel. The valid options are
+ the same as for --gamma-table.
+
+ The color correction coefficients --cct-1 --cct-2 --cct-3 ...
+ --cct-9 will install color correction coefficients for the user
+ defined color correction. Values are specified as integers in
+ the range -127..127.
+
+ The --preview option requests a preview scan. The frontend soft-
+ ware automatically selects a low resolution. Valid options are
+ "yes" and "no". The default is "no".
+
+ The --preview-speed options will increase the scan speed if this
+ is supported by the scanner. Valid options are "yes" and "no",
+ the default is "no".
+
+ The geometry options -l -t -x -y control the scan area: -l sets
+ the top left x coordinate, -t the top left y coordinate, -x
+ selects the width and -y the height of the scan aea. All parame-
+ ters are specified in milimeters.
+
+ The --quick-format option lets the user select a scan area with
+ predefined sizes. Valid parameters are "CD", "A5 portrait", "A5
+ landscape", "Letter", "A4" and "max". The default is "max",
+ which selects the largest possible area.
+
+ The --source option selects the scan source. Valid options
+ depend on the installed options. The default is "Flatbed".
+
+ The --auto-eject option will eject a page after scanning from
+ the document feeder.
+
+ The --film-type option will select the film type for scans with
+ the transparency unit. This option is only activated if the TPU
+ is selected as scan source. Valid options are "Negative Film"
+ and "Positive Film".
+
+ The --focus-position option selects the focus position for all
+ scans. Valid options are "Focus 2.5mm above glass" and "Focus on
+ glass". The focus on the 2.5mm point above the glass is neces-
+ sary for scans with the transparency unit, so that the scanner
+ can focus on the film if one of the film holders is used. This
+ option is only functional for selected scanners, all other scan-
+ ners will ignore this option.
+
+
+
+CONFIGURATION FILE
+ The configuration file /usr/local/etc/sane.d/epson.conf specifies the
+ device(s) that the backend will use. Possible connection types are:
+
+ SCSI This is the default, and if nothing else is specified the back-
+ end software will open a given path as SCSI device. More infor-
+ mation about valid syntax for SCSI devices can be found in sane-
+ scsi(5).
+
+ PIO - Parallel Interface
+ The parallel interface can be configured in two ways: An integer
+ value starting at the beginning of a line will be interpreted as
+ the IO address of the parallel port. To make it clearer that a
+ configured IO address is a parallel port the port address can be
+ preceded by the string "PIO". The PIO connection does not use a
+ special device file in the /dev directory. The IO address can be
+ specified in hex mode (prefixed with "0x").
+
+ USB A device file that is preceded by the string "USB" is treated as
+ a scanner connected via the Universal Serial Bus. The correct
+ special device file has to be created prior to using it with
+ Sane. See the USB documentation for more information about how
+ to set up the USB subsystem and the required device files.
+
+
+
+FILES
+ /usr/local/lib/sane/libsane-epson.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-epson.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_DEBUG_EPSON
+ If the library was compiled with debug support enabled, this
+ environment variable controls the debug level for this backend.
+ E.g., a value of 128 requests all debug output to be printed.
+ Smaller levels reduce verbosity.
+
+ SANE_EPSON_CMD_LVL
+ This allows to override the function or command level that the
+ backend uses to communicate with the scanner. The function level
+ a scanner supports is determined during the initialization of
+ the device. If the backend does not recognize the function level
+ reported by the scanner it will default to function level B5.
+ Valid function levels are A1, A2, B1, B2, B3, B4, B5, B6, B7,
+ B8, D1 and F5. Use this feature only if you know what you are
+ doing!
+
+
+
+SEE ALSO
+ sane-scsi(5), scanimage(1), xscanimage(1), xsane(1)
+
+
+
+BUGS
+ None :-) At least none are currently known.
+
+
+
+UNSUPPORTED DEVICES
+ The backend may be used with Epson scanners that are not yet listed
+ under the list of supported devices. A scanner that is not recognized
+ may default to the function level B3, which means that not all func-
+ tions that the scanner may be capable of are accessible.
+
+ If the scanner is not even recognized as an Epson scanner this is prob-
+ ably because the device name reported by the scanner is not in the cor-
+ rect format. Please send this information to the backend maintainer
+ (email address is in the AUTHOR section of this man page or in the
+ AUTHORS file of the SANE distribution).
+
+ The Perfection 600, Perfection 650, Perfection 660, Perfection 1250 and
+ Perfection 1260 are not supported by this backend.
+
+
+
+AUTHOR
+ 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 sane-epson(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-find-scanner.1.html b/man/sane-find-scanner.1.html
new file mode 100644
index 00000000..ab3ae758
--- /dev/null
+++ b/man/sane-find-scanner.1.html
@@ -0,0 +1,117 @@
+
+
+sane-find-scanner.1
+
+
+sane-find-scanner.1
+
+
+
+sane-find-scanner(1) SANE Scanner Access Now Easy sane-find-scanner(1)
+
+
+
+NAME
+ sane-find-scanner - find SCSI and USB scanners and their device files
+
+
+
+SYNOPSIS
+ sane-find-scanner [-h|-?] [-v] [-q] [-f] [devname]
+
+
+
+DESCRIPTION
+ sane-find-scanner is a command-line tool to find SCSI and USB scanners
+ and determine their Unix device files. Its primary aim is to make sure
+ that scanners can be detected by SANE backends.
+
+ For SCSI scanners, it checks the default generic SCSI device files
+ (e.g., /dev/sg0) and /dev/scanner. The test is done by sending a SCSI
+ inquiry command and looking for a device type of "scanner" or "proces-
+ sor" (some old HP scanners seem to send "processor"). So sane-find-
+ scanner will find any SCSI scanner connected to those default device
+ files even if it isn't supported by any SANE backend.
+
+ For USB scanners, first the USB kernel scanner device files (e.g.
+ /dev/usb/scanner0), /dev/usb/scanner, and /dev/usbscanner) are tested.
+ The files are opened and the vendor and device ids are determined, if
+ the operating system supports this feature. Currently USB scanners are
+ only found this way if they are supported by the Linux scanner module
+ or the FreeBSD or OpenBSD uscanner driver. After that test, sane-find-
+ scanner tries to scan for USB devices found by the USB library libusb
+ (if available). There is no special USB class for scanners, so the
+ heuristics used to distinguish scanners from other USB devices is not
+ perfect. sane-find-scanner also tries to find out the type of USB chip
+ used in the scanner. If detected, it will be printed after the vendor
+ and product ids. sane-find-scanner will even find USB scanners, that
+ are not supported by any SANE backend.
+
+ sane-find-scanner won't find parallel port scanners, or scanners con-
+ nected to proprietary ports.
+
+
+
+OPTIONS
+ -h, -? Prints a short usage message.
+
+ -v Verbose output. If used once, sane-find-scanner shows every
+ device name and the test result. If used twice, SCSI inquiry
+ information and the USB device descriptors are also printed.
+
+ -q Be quiet. Print only the devices, no comments.
+
+ -f Force opening all explicitely given devices as SCSI and USB
+ devices. That's useful if sane-find-scanner is wrong in
+ determing the device type.
+
+ devname Test device file "devname". No other devices are checked if
+ devname is given.
+
+
+
+EXAMPLE
+ sane-find-scanner -v
+ Check all SCSI and USB devices for available scanners and print a line
+ for every device file.
+
+ sane-find-scanner /dev/scanner
+ Look for a (SCSI) scanner only at /dev/scanner and print the result.
+
+
+
+SEE ALSO
+ sane(7), sane-scsi(5), sane-usb(5), scanimage(1), xscanimage(1),
+ xsane(1), sane-"backendname"(5)
+
+
+
+AUTHOR
+ Oliver Rauch, Henning Meier-Geinitz and others
+
+
+
+SUPPORTED PLATFORMS
+ USB support is limited to Linux (kernel, libusb), FreeBSD (kernel,
+ libusb), NetBSD (libusb), OpenBSD (kernel, libusb). Detecting the ven-
+ dor and device ids only works with Linux or libusb.
+
+ SCSI support is available on Irix, EMX, Linux, Next, AIX, Solaris,
+ FreeBSD, NetBSD, OpenBSD, and HP-UX.
+
+
+
+BUGS
+ No support for parallel port scanners yet.
+ Detection of USB chipsets is limited to GrandTech 6801 and 6816, Mustek
+ chips and National Semiconductor lm983x chips.
+
+sane-backends 1.0.12-cvs 18 Jul 2003 sane-find-scanner(1)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-fujitsu.5.html b/man/sane-fujitsu.5.html
new file mode 100644
index 00000000..7150d700
--- /dev/null
+++ b/man/sane-fujitsu.5.html
@@ -0,0 +1,168 @@
+
+
+sane-fujitsu.5
+
+
+sane-fujitsu.5
+
+
+
+sane-fujitsu(5) SANE Scanner Access Now Easy sane-fujitsu(5)
+
+
+
+NAME
+ sane-fujitsu - SANE backend for Fujitsu flatbed and ADF scanners
+
+
+
+DESCRIPTION
+ The sane-fujitsu library implements a SANE (Scanner Access Now Easy)
+ backend which provides access to Fujitsu flatbed and ADF scanners. At
+ present, the following scanners are known to work with this backend:
+
+ Vendor: Model: Rev:
+ -------- ---------------- -----
+ FUJITSU M3096Gm 02
+ FUJITSU M3093GX
+ FUJITSU M3093GD
+ FUJITSU M4097
+ FUJITSU fi-4220C
+ FUJITSU fi-4340C
+ FUJITSU M3091DCd BF21
+ FUJITSU M3092DCd
+
+ The driver supports lineart, halftone, grayscale, and color (3091 and
+ 3092) scanning depending on hardware capabiliites.
+
+ The "Fujitsu" driver is a first attempt at integrating support for all
+ Fujitsu scanners - previously available as different single drivers -
+ in one driver. At present, the M3091DCd is working (lineart, halftone,
+ 8-bit grayscale and 24-bit color, simplex and duplex), and the driver
+ should also support the M3096 as the M3096g driver code has been incor-
+ porated. This driver supersedes the old "m3091"/"fujitsu" drivers and
+ the old "m3096g" driver.
+
+ Other scanners in these families may work. The ScanPartner 15C seems
+ to be a repackaging of the ScanPartner 600C, but I don't know if it
+ works. Look at the sp15c backend for this scanner. Perusal of the
+ M3096GX/M3093GX/M3093DG manual suggests the M3096G driver offers access
+ to a subset of the new scanners. People are encouraged to try these
+ driver with the other scanners and to contact the author with test
+ results.
+
+
+
+DUPLEX MODE
+ The M3091 driver supports duplex scanning. To the front-end, a duplex
+ scan looks very much like scanning two separate pages from the document
+ feeder, i.e. the SANE front-end receives two images instead of one.
+ Front-ends which are not capable of dealing with that - e.g. the com-
+ mand-line tool scanimage - cannot be used for duplex scanning. If you
+ want to do duplex scans from the command line, get Tom Martone's
+ scanadf program from http://www.martoneconsulting.com/sane-
+ scanadf.html.
+
+
+
+CONFIGURATION
+ A modest effort has been made to expose the standard options to the
+ API. This allows frontends such as xscanimage to set scanning region,
+ resolution, bit-depth (and color), and enable the automatic document
+ feeder.
+ The "Fujitsu" driver supports the following options:
+ mode m
+ m may be one of "Color", "Lineart", "Halftone", or "Gray",
+ dependent on the scanner model. It is advisable to specify this
+ option first when using command line tools, as the validity of
+ some of the other options depends on the mode setting.
+
+ x, y
+ Scan width and height
+
+ pagewidth, pageheight
+ Page size; when using the ADF, the driver will assume that a
+ page of the given width is centered
+
+ resolution, y-resolution
+ Controls scan resolution. Permissible values dependent on model
+ and scan mode; setting --resolution also sets --y-resolution but
+ not vice versa. This makes it possible to set the 3091's maximum
+ resolution of 300x600dpi.
+
+ brightness b
+ Only supported for M3096
+
+ treshold t
+ Only supported for M3096
+
+ duplex d
+ d may be "front", "back", or "both" and denotes which sides of
+ the page are to be scanned (duplex scanner only for example
+ 3091, 3093Gd).
+
+ lampcolor c
+ c may be "red", "green", "blue", or "default" - the lamp color
+ to be used when doing graysacale or b/w scans on the M3091.
+
+ blueoffset, greenoffset
+ Color justification options for the M3091; anything other than
+ +1/-1 will probably distort the image. Should be left alone
+ unless your scanner is buggy.
+
+ swapfile
+ boolean option for the M3091. Only affects duplex scans. If set,
+ a swap file will be used for storing the rear side of a document
+ as it is scanned; otherwise the whole page will be kept in mem-
+ ory.
+
+ You may specify the line "forceModel=xxx" in the configuration file to
+ make the driver treat your scanner as an "xxx" scanner (currently sup-
+ ported: 3096, 3091). Use this if you have another scanner that is not
+ automatically detected as being compatible.
+
+ The only other configuration option supported is "scsi-buf-size=xxx",
+ allowing you to set the SCSI buffer size to something other than the
+ compiled-in default. Especially with the M3091 scanner, some users had
+ the problem that the scanner would "hang" mid-page, and this can often
+ be alleviated by using "scsi-buf-size=32768".
+
+
+
+SEE ALSO
+ sane(7), sane-scsi(5), sane-sp15c(5) sane-usb(5),
+ Fujitsu ScanPartner 15C OEM Manual, Doc. No. 250-0081-0
+ Fujitsu M3096G OEM Manual, part number 50FH5028E-05
+ Fujitsu M3096GX/M3093GX/M3093DG OEM Manual, part number C150-E015...03
+
+
+
+AUTHOR
+ 3096/SP15 drivers: Randolph Bentson <bentson@holmsjoen.com>, with
+ credit to the unnamed author of the coolscan driver
+ 3091 driver: Frederik Ramm <frederik@remote.org> 3093GD,fi-4340C, ipc
+ and cmp options: Oliver Schirrmeister <oschirr@abm.de> 3092 patch:
+ Mario Goppold <mgoppold@tbzpariv.tcc-chemnitz.de> fi-4220C patch and
+ USB support: Ronald B. Cemer <ron@roncemer.com>
+
+
+
+LIMITATIONS
+ Only tested with Linux 2.4
+
+
+
+BUGS
+ I'm sure there are plenty, and not too well hidden, but I haven't seen
+ them yet. I don't know if the ScanPartner 15C still works, because I'm
+ not able to test it. 3091/3092 don't support halftone
+
+sane-backends 1.0.12-cvs 17 Apr 2002 sane-fujitsu(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-gphoto2.5.html b/man/sane-gphoto2.5.html
new file mode 100644
index 00000000..b192911a
--- /dev/null
+++ b/man/sane-gphoto2.5.html
@@ -0,0 +1,142 @@
+
+
+sane-gphoto2.5
+
+
+sane-gphoto2.5
+
+
+
+sane-gphoto2(5) SANE Scanner Access Now Easy sane-gphoto2(5)
+
+
+
+NAME
+ sane-gphoto2 - SANE backend for gphoto2 supported cameras
+
+
+
+DESCRIPTION
+ The sane-gphoto2 library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to the digital cameras supported by
+ gphoto2. This backend has only been tested with a handful of cameras
+ so far. Patches to support other models are welcome.
+
+ Because of the limited testing of this backend, it is commented out in
+ /usr/local/etc/sane.d/dll.conf by default. Either the comment charac-
+ ter must be removed or the backend must be called explicitly. E.g.
+ `scanimage -d gphoto2' or `xscanimage gphoto2'.
+
+
+
+DEVICE NAMES
+ The current version of the backend only allows one camera to be con-
+ nected. The device name is always "0".
+
+
+
+CONFIGURATION
+ The contents of the gphoto2.conf specify the characteristics of the
+ camera to be used. Resolutions (high resolution, low resolution, and
+ thumbnail size) are required since they are needed by the sane fron-
+ tends, but can't be obtained through the gphoto2 interface. Valid
+ ports and cameras can be obtained by "gphoto2 --list-cameras" and
+ "gphoto2 --list-ports".
+
+ The dumpinquiry line causes some information about the camera to be
+ printed.
+
+ Empty lines and lines starting with a hash mark (#) are ignored. A
+ sample configuration file is shown below:
+
+ The "topfolder" line specifies the "fixed" part of the file path. For
+ example, on the Kodak DC-240, files are stored in the directory
+ /DCIM/100DC240. The /DCIM portion is constant, but 100DC240 will
+ change and must be read from the camers. In this case, the line would
+ read "topfolder=/DCIM"
+
+ Some cameras don't implement a file structure and store all pictures in
+ the "/" directory. This is indicated by setting "subdirs=0" with "top-
+ folder=/"
+ port=usb:
+ camera=Kodak DC240
+ # this is a comment
+ high_resolution=1280x960
+ low_resolution=640x480
+ thumb_resolution=160x120
+ dumpinquiry
+
+
+
+FILES
+ /usr/local/etc/sane.d/gphoto2.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-gphoto2.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-gphoto2.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_GPHOTO2
+ If the library was compiled with debugging support enabled, this
+ environment variable controls the debug level for this backend.
+ A value of 128 requests maximally copious debug output; smaller
+ levels reduce verbosity.
+
+ GP_DEBUG
+ Set to 1, 2, or 3, to enable various levels of debugging within
+ the gphoto2 libraries.
+
+
+
+SEE ALSO
+ sane(7)
+
+
+
+AUTHOR
+ Peter S. Fales
+
+ The manpage was largeley copied from the dc210 manpage.
+
+
+
+BUGS
+ Many, no doubt.
+
+ More general comments, suggestions, and inquiries about frontends or
+ SANE should go to the SANE Developers mailing list (see
+ http://www.mostang.com/sane/mail.html for details). You must be sub-
+ scribed to the list, otherwise your mail won't be sent to the sub-
+ scribers.
+
+sane-backends 1.0.12-cvs 04 September 2001 sane-gphoto2(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-gt68xx.5.html b/man/sane-gt68xx.5.html
new file mode 100644
index 00000000..2050b55e
--- /dev/null
+++ b/man/sane-gt68xx.5.html
@@ -0,0 +1,238 @@
+
+
+sane-gt68xx.5
+
+
+sane-gt68xx.5
+
+
+
+sane-gt68xx(5) SANE Scanner Access Now Easy sane-gt68xx(5)
+
+
+
+NAME
+ sane-gt68xx - SANE backend for GT-68XX based USB flatbed scanners
+
+
+
+DESCRIPTION
+ The sane-gt68xx library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to USB flatbed scanners based on the
+ Grandtech GT-6801 and GT-6816 chips. At present, the following scan-
+ ners are known to work with this backend:
+
+ Artec Ultima 2000 (only product 0x4002)
+ Artec Ultima 2000 e+
+ Boeder SmartScan Slim Edition
+ Fujitsu 1200CUS
+ Genius Colorpage Vivid3x
+ Genius Colorpage Vivid3xe
+ Lexmark X70
+ Lexmark X73
+ Medion/Lifetec/Tevion MD 4395
+ Medion/Lifetec/Tevion/Cytron MD/LT 9385
+ Medion/Lifetec/Tevion LT 9452
+ Medion/Lifetec/Tevion MD 9458
+ Mustek BearPaw 1200 CS
+ Mustek BearPaw 1200 CU (Plus)
+ Mustek BearPaw 1200 TA
+ Mustek BearPaw 2400 CS (Plus)
+ Mustek BearPaw 2400 CU (Plus)
+ Mustek BearPaw 2400 TA (Plus)
+ Mustek ScanExpress A3 USB
+ Mustek ScanExpress 1200 UB Plus
+ Mustek ScanExpress 2400 USB
+ Mustek ScanMagic 1200 UB Plus
+ Packard Bell Diamond 1200 (Plus)
+ Plustek OpticPro 1248U
+ RevScan 19200i
+ Trust Compact Scan USB 19200
+ Trust Flat Scan USB 19200
+
+ More details can be found on the gt68xx backend homepage
+ http://www.meier-geinitz.de/sane/gt68xx/.
+
+ The Artec E+ 48U and its clones are supported by the artec_eplus48u
+ backend, see sane-artec_eplus48u(5) for details.
+
+ This is BETA software. Especially if you test new or untested scanners,
+ keep your hand at the scanner's plug and unplug it, if the head bumps
+ at the end of the scan area.
+
+ If you own a scanner other than the ones listed above that works with
+ this backend, please let me know this by sending the scanner's exact
+ model name and the USB vendor and device ids (e.g. from
+ /proc/bus/usb/devices, sane-find-scanner or syslog) to me. Even if the
+ scanner's name is only slightly different from the models mentioned
+ above, please let me know.
+
+
+
+KERNEL ISSUES
+ If libusb-0.1.6 or later is installed, this section can be skipped. The
+ scanner should be found by sane-find-scanner without further actions.
+ For setting permissions and general USB information looks at
+ sane-usb(5).
+
+ The scanners based on the GT-6816 (Mustek BearPaw TA and BearPaw Plus
+ models, the Packard Bell and the Lexmark scanner) need a Linux kernel
+ 2.4.12 or newer. Recent 2.2 kernels may also work, but I haven't
+ tested them. Older kernels or other operating systems won't work. Use
+ libusb instead.
+
+ The scanners based on the GT-6801 (all other scanners) need Linux ker-
+ nel 2.4.21 or newer. Older kernels will not work.
+
+
+
+FIRMWARE FILE
+ You need a firmware file for your scanner. That's a small file contain-
+ ing software that will be uploaded to the scanner's memory. It's usu-
+ ally named *.usb, e.g. PS1fw.usb. It comes on the installation CD
+ that was provided by the manufacturer, but it may be packaged together
+ with the installation program in an .exe file. For Mustek scanners, the
+ file can be dowloaded from the gt68xx backend homepage. For other scan-
+ ners, check the CD for .usb files. If everything else fails, you must
+ install the Windows driver and get the firmware from there (usually in
+ the windows/system or system32 directories). Put that firmware file
+ into /usr/local/share/sane/gt68xx/.
+
+
+
+CONFIGURATION
+ The contents of the gt68xx.conf file is a list of usb lines containing
+ vendor and product ids that correspond to USB scanners. The file can
+ also contain option lines. Empty lines and lines starting with a hash
+ mark (#) are ignored. The scanners are autodetected by usb vendor_id
+ product_id statements which are already included into gt68xx.conf.
+ "vendor_id" and "product_id" are hexadecimal numbers that identfy the
+ scanner.
+
+ The override, firmware, vendor, model, and afe options must be placed
+ after the usb line they refer to.
+
+ Option override is used to override the default model parameters.
+ That's necessary for some scanners that use the same vendor/product ids
+ but are different. For these scanners there are already commented out
+ override lines in the configuration file. override mustek-scanex-
+ press-1200-ub-plus is necessary for the Mustek Scanexpress 1200 UB
+ Plus, the Medion/Lifetec/Tevion LT 9452, and the Trust Compact Scan USB
+ 19200. override artec-ultima-2000 is used for the Artec Ultima 2000,
+ the Boeder SmartScan Slim Edition, the Medion/ Lifetec/ Tevion/ Cytron
+ MD/LT 9385, the Medion/ Lifetec/ Tevion MD 9458, and the Trust Flat
+ Scan USB 19200. override mustek-bearpaw-2400-cu is necessary for the
+ Mustek BearPaw 2400 CU and the Fujitsu 1200CUS. The override option
+ must be the first one after the usb line.
+
+ Option firmware selects the name and path of the firmware file. It's
+ only necessary if the default (or override) doesn't work. The default
+ firmware directory is /usr/local/share/sane/gt68xx/. You may need to
+ create this directory. If you want to place the firmware files at a
+ different path, use a firmware line.
+
+ The vendor and model options are not absolutely necessary but for con-
+ venience. Quite a lot of scanners from different manufacturers share
+ the same vendor/product ids so you can set the "correct" name here.
+
+ The afe option allows to set custom offset and gain values for the Ana-
+ log FrontEnd of the scanner. This option can be either used to select
+ the AFE values if automatic coarse calibration is disabled, or to make
+ automatic coarse calibration faster. For the latter usage, enable debug
+ level 3 (see below), scan an image and look for debug line string with
+ "afe". Copy this line to gt68xx.conf. The option has six parameters:
+ res offset, red gain, green offset, green gain, blue offset, and blue
+ gain.
+
+ A sample configuration file is shown below:
+
+ usb 0x05d8 0x4002
+ override "mustek-scanexpress-1200-ub-plus"
+ firmware "/opt/gt68xx/SBfw.usb"
+ vendor "Trust"
+ model "Compact Scan USB 19200"
+ afe 0x20 0x02 0x22 0x03 0x1f 0x04
+
+
+
+FILES
+ /usr/local/etc/sane.d/gt68xx.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-gt68xx.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-gt68xx.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_GT68XX
+ If the library was compiled with debug support enabled, this
+ environment variable controls the debug level for this backend.
+ Higher debug levels increase the verbosity of the output.
+
+ Example: export SANE_DEBUG_GT68XX=4
+
+
+
+SEE ALSO
+ sane(7), sane-usb(5), sane-artec_eplus48u(5) sane-plustek(5),
+ sane-ma1509(5), sane-mustek_usb(5), sane-mustek(5), sane-mustek_pp(5)
+ /usr/local/doc/sane-1.0.12-cvs/gt68xx/gt68xx.CHANGES
+ http://www.meier-geinitz.de/sane/gt68xx
+
+
+
+AUTHOR
+ Henning Meier-Geinitz <henning@meier-geinitz.de>
+ The original gt68xx driver was written by Sergey Vlasov, Andreas
+ Nowack, and David Stevenson. Thanks for sending patches and answering
+ questions to them and all the other contributors.
+
+
+
+BUGS
+ Currently scanning seems to only work reliably under Linux. With
+ FreeBSD, NetBSD and OpenBSD scanning works only once. Then the scanner
+ isn't detected anymore and has to be replugged.
+
+ The first few lines of the image are garbage for the 2400 TA Plus.
+
+ Interpolation should be used instead of just copying data, when the X-
+ and Y-resolution differ.
+
+ Support for buttons is missing.
+
+ More detailed bug information is available at the gt68xx backend home-
+ page http://www.meier-geinitz.de/sane/gt68xx. Please contact me if you
+ find a bug or missing feature: <henning@meier-geinitz.de>. Please send
+ a debug log if your scanner isn't detected correctly (see
+ SANE_DEBUG_GT68XX above).
+
+sane-backends 1.0.12-cvs 22 Jul 2003 sane-gt68xx(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-hp.5.html b/man/sane-hp.5.html
new file mode 100644
index 00000000..f59a246b
--- /dev/null
+++ b/man/sane-hp.5.html
@@ -0,0 +1,244 @@
+
+
+sane-hp.5
+
+
+sane-hp.5
+
+
+
+sane-hp(5) SANE Scanner Access Now Easy sane-hp(5)
+
+
+
+NAME
+ sane-hp - SANE backend for HP ScanJet scanners
+
+
+
+DESCRIPTION
+ The sane-hp library implements a SANE (Scanner Access Now Easy) backend
+ that provides access to HP ScanJet scanners which support SCL (Scanner
+ Control Language by HP). The following scanners are known positively
+ to work with this backend:
+
+ Model: Product id: Interface:
+ ---------- ----------- ----------
+ ScanJet Plus C9195A HP Parallel Interface Card
+ ScanJet IIc C1750A 3226 SCSI
+ ScanJet IIcx C2500A 3332 SCSI
+ ScanJet IIp C1790A SCSI
+ ScanJet 3C C2520A 3503 SCSI
+ ScanJet 3P C2570A 3406 SCSI
+ ScanJet 4C C2520A SCSI
+ ScanJet 4P C1130A 3540 SCSI
+ ScanJet 4100C C6290A USB
+ ScanJet 5P C5110A SCSI
+ ScanJet 5100C C5190A parallel port
+ ScanJet 5200C C7190A 3846 parallel port/USB
+ ScanJet 6100C C2520A 3644 SCSI
+ ScanJet 6200C C6270A 3828 SCSI/USB
+ ScanJet 6250C C6270A 3828 SCSI/USB
+ ScanJet 6300C C7670A SCSI/USB
+ ScanJet 6350C C7670A SCSI/USB
+ ScanJet 6390C C7670A SCSI/USB
+ PhotoSmart C5100A R029,R030,R032 SCSI
+
+ Support for models 5100C/5200C connected to the parallel port requires
+ the ppSCSI driver available at http://www.torque.net/par-
+ port/ppscsi.html (under development)
+
+ Support for models 5200C/62X0C/63X0C connected to the USB require the
+ kernel scanner driver or libusb. See sane-usb(5) for more details.
+
+ The "hp" backend no longer supports OfficeJet multi-function peripher-
+ als. For these devices use the external "hpoj" backend in version 0.90
+ and later of the "HP OfficeJet Linux driver", available at
+ http://hpoj.sourceforge.net
+
+ 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 http://www.mostang.com/sane.
+ You can also watch the sane-devel mailinglist at
+ http://www.mostang.com/sane/mail.html.
+
+ More details about the hp backend can be found on its homepage
+ http://www.kirchgessner.net/sane.html.
+
+
+
+DEVICE NAMES
+ This backend expects device names of the form:
+
+ special
+
+ Where special is the UNIX path-name for the special device that corre-
+ sponds to the scanner. For SCSI scanners the special device name must
+ be a generic SCSI device or a symlink to such a device. Under Linux,
+ such a device name could be /dev/sga or /dev/sg2, for example. If the
+ special device name contains "usb", "uscanner" or "ugen", it is assumed
+ that the scanner is connected by USB. For the HP ScanJet Plus the spe-
+ cial device name must be the device that corresponds to the parallel
+ interface card that was shipped with the scanner. That is /dev/hpscan.
+ A special driver is required for this card. See ftp://rvs.ctrl-
+ c.liu.se/pub/wingel/hpscan for details. If the link does not work, try
+ ftp://sunsite.unc.edu/pub/Linux/kernel/patches/scanners.
+
+
+
+CONFIGURATION
+ The contents of the hp.conf file is a list of options and device names
+ that correspond to HP ScanJet scanners. Empty lines and lines starting
+ with a hash mark (#) are ignored. See sane-scsi(5) and sane-usb(5) on
+ details of what constitutes a valid device name.
+
+ Options specified in front of the first line that contains a device
+ name are defaults for all devices. Options specified below a line that
+ contains a device name apply just to the most recently mentioned
+ device.
+
+ Supported options are connect-scsi, connect-device, enable-image-
+ buffering, and dumb-read.
+
+ Option connect-scsi specifies that the scanner is connected to the sys-
+ tem by SCSI. Input/output is performed using SCSI-commands. This is
+ the default. But if your SCSI device name contains "usb", "uscanner"
+ or "ugen", option connect-scsi must be specified. Otherwise it is
+ assumed that the scanner is connected by USB.
+
+ Option connect-device specifies that the scanner is connected to the
+ system by a special device. Input/output is performed by
+ read()/write()-operations on the device. This option must be used for
+ HP ScanJet Plus or scanners connected to USB which are accessed through
+ a named device (e.g. /dev/usb/scanner0). For device names that contain
+ "usb", "uscanner" or "ugen", it is not necessary to specify option con-
+ nect-device.
+
+ Option enable-image-buffering stores the scanned image in memory before
+ passing it to the frontend. Could be used in case of forward/backward
+ moving scanner lamp.
+
+ Option dumb-read can be used to work around problems with "Error during
+ device I/O". These problems may occur with certain SCSI-to-USB conver-
+ tors or Buslogic SCSI cards. The option should not be used for SCSI
+ devices which are working correctly. Otherwise startup of frontends
+ and changing parameters might be slower.
+
+ A sample configuration file is shown below:
+
+ /dev/scanner
+ # this is a comment
+ /dev/hpscan
+ option connect-device
+
+ /dev/scanner is typically a symlink to the actual SCSI scanner device.
+
+
+
+FILES
+ /usr/local/etc/sane.d/hp.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-hp.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-hp.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+ $HOME/.sane/calib-hp:<device>.dat
+ Calibration data for HP PhotoSmart PhotoScanner that is
+ retrieved from the scanner after calibration. The data is
+ uploaded to the scanner at start of the backend if it is in
+ media mode 'print media' or if the media mode is changed to
+ 'print media'.
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_HP
+ 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.
+
+
+
+BUGS
+ HP PhotoSmart PhotoScanner
+ In media mode 'slide' and 'negative', scan resolutions are
+ rounded to multiple of 300 dpi. The scanner does not scale the
+ data correctly on other resolutions. Some newer models (firmware
+ code R030 and later) do not support adjustment of con-
+ trast/intensity level and tone map. The backend will simulate
+ this by software, but only for gray and 24 bit color.
+
+ Automatic Document Feeder (ADF)
+ For use of the ADF with xscanimage(1), first place paper in the
+ ADF and then change option scan source to 'ADF'. Press 'change
+ document' to load a sheet. Then press 'scan' to start a scan.
+ Maybe it is sufficient to press 'scan' without 'change document'
+ for repeated scans. The use of the preview window is not recom-
+ mended when working with the ADF. Setting a window to scan from
+ ADF is not supported with xscanimage(1). Try xsane(1).
+
+ Immediate actions
+ Some actions in xscanimage(1) (i.e. unload, select media, cali-
+ brate) have an immediate effect on the scanner without starting
+ a scan. These options can not be used with scanimage.
+
+
+
+TODO
+ HP PhotoSmart PhotoScanner
+ PhotoScanners with firmware release R030 and up have no firmware
+ support for contrast/brightness/gamma table. In the current
+ backend this is simulated by software on 24 bits data. Simula-
+ tion on 30 bits should give better results.
+
+ Data widths greater than 8 bits
+ Custom gamma table does not work.
+
+ Parallel scanner support
+ Beside the ScanJet Plus which came with its own parallel inter-
+ face card, currently only the HP ScanJet 5100C/5200C are
+ supported. These scanners are using an internal parallel-to-
+ SCSI converter which is supported by the ppSCSI-driver (see
+ above).
+
+
+
+SEE ALSO
+ sane(7), sane-scsi(5), sane-usb(5)
+
+
+
+AUTHOR
+ The sane-hp backend was written by Geoffrey T. Dairiki. HP PhotoSmart
+ PhotoScanner support by Peter Kirchgessner.
+
+sane-backends 1.0.12-cvs 06 Dec 2002 sane-hp(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-hp5400.5.html b/man/sane-hp5400.5.html
new file mode 100644
index 00000000..717e065d
--- /dev/null
+++ b/man/sane-hp5400.5.html
@@ -0,0 +1,121 @@
+
+
+sane-hp5400.5
+
+
+sane-hp5400.5
+
+
+
+sane-hp5400(5) SANE Scanner Access Now Easy sane-hp5400(5)
+
+
+
+NAME
+ sane-hp5400 - SANE backend for Hewlett-Packard 54XX scanners
+
+
+
+DESCRIPTION
+ The sane-hp5400 library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to the following Hewlett-Packard USB
+ flatbed scanners:
+
+ ScanJet 5400C
+ ScanJet 5470C
+ ScanJet 5490C
+
+ More details can be found on the hp5400 backend homepage
+ http://hp5400backend.sourceforge.net/.
+
+ This is ALPHA software. Keep your hand at the scanner's plug and unplug
+ it, if the head bumps at the end of the scan area. See also the BUGS
+ section.
+
+ If you own a scanner other than the ones listed above that works with
+ this backend, please let us know this by sending the scanner's exact
+ model name and the USB vendor and device ids (e.g. from
+ /proc/bus/usb/devices, sane-find-scanner or syslog) to us. Even if the
+ scanner's name is only slightly different from the models mentioned
+ above, please let us know.
+
+
+
+CONFIGURATION
+ The contents of the hp5400.conf file is a list of usb lines containing
+ vendor and product ids that correspond to USB scanners. The file can
+ also contain the names of device files that correspond to an HP 54XX
+ scanner. Empty lines and lines starting with a hash mark (#) are
+ ignored. The scanners are autodetected by usb vendor_id product_id
+ statements which are already included into hp5400.conf. "vendor_id"
+ and "product_id" are hexadecimal numbers that identify the scanner. If
+ autodetection does not work, add the device name of your scanner to the
+ configuration file, e.g. /dev/usb/scanner0.
+
+
+
+FILES
+ /usr/local/etc/sane.d/hp5400.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-hp5400.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-hp5400.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_HP5400
+ If the library was compiled with debug support enabled, this
+ environment variable controls the debug level for this backend.
+ Higher debug levels increase the verbosity of the output.
+
+ Example: export SANE_DEBUG_HP5400=4
+
+
+
+SEE ALSO
+ sane(7), sane-usb(5),
+ http://hp5400backend.sourceforge.net/
+
+
+
+AUTHOR
+ Martijn van Oosterhout <kleptog@svana.org>, Thomas Soumarmon
+ <soumarmt@nerim.net>. Manpage by Henning Meier-Geinitz <henning@meier-
+ geinitz.de>.
+
+
+
+BUGS
+ Scanning is only tested with Linux/ix86/gcc. Be careful when testing on
+ other operating systems and especially on big-endian platforms. The
+ scanner may get wrong data.
+
+sane-backends 1.0.12-cvs 17 Apr 2003 sane-hp5400(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-hpsj5s.5.html b/man/sane-hpsj5s.5.html
new file mode 100644
index 00000000..6e13d6fd
--- /dev/null
+++ b/man/sane-hpsj5s.5.html
@@ -0,0 +1,122 @@
+
+
+sane-hpsj5s.5
+
+
+sane-hpsj5s.5
+
+
+
+sane-hpsj5s(5) SANE Scanner Access Now Easy sane-hpsj5s(5)
+
+
+
+NAME
+ sane-hpsj5s - SANE backend for HP ScanJet 5S sheetfed scanner
+
+
+
+DESCRIPTION
+ The sane-hpsj5s library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to parallel port Hewlett-Packard ScanJet
+ 5S scaner.
+
+ IMPORTANT: this is alpha code. Don't expect this to work correctly.
+ Many functions are missing, others contain errors. In some cases, your
+ computer might even hang. It cannot be excluded (although I consider it
+ extremely unprobable) that your scanner will be damaged.
+
+ LIMITATIONS: For now this backend works only at Linux platform.This
+ limitation is due dependance on libieee1284 library. If your system
+ supports libieee1284 too, this backend should work. If you ported
+ libieee1284 for you platform, please let me know.Your system should
+ support EPP (or EPP+ECP ) mode to operate this scaner. Future versions
+ will support ECP and SPP (Nibble and Byte) modes also. It's planned to
+ support for scaners not only at 0 daisy-chain position, but at any one.
+ Support for multiple scaners could be implemented too.
+
+ Current version implements only gray scale scaning. True Color and B/W
+ modes are not supported for now.
+
+ That said, TESTERS ARE WELCOME. Send your bug reports and comments to
+ Max Vorobiev <pcwizard@yandex.ru>.
+
+
+
+DEVICE NAMES
+ This backend expects device names of the form:
+
+ special
+
+ Where special is the parallel port name in form, libieee1284 expects.
+ It seems to be system dependent. Under Linux it's parport0, parport1,
+ etc.
+
+
+
+CONFIGURATION
+ The contents of the hpsj5s.conf file is a list of parport names that
+ correspond to HP ScanJet 5S scanners. Empty lines and lines starting
+ with a hash mark (#) are ignored. Only one device name can be listed
+ in hpsj5s.conf for this moment. Future versions will support daisy
+ chain selection.
+
+
+
+TIPS
+ It seems that HP ScanJet 5S scaner uses software noise correction. This
+ feature is not implemented for now. So does gamma correction and cali-
+ bration. I'll handle it in future versions. Native resolution for
+ this scaner is 300 DPI. Other modes could be jagged in some ways.
+
+
+
+FILES
+ /usr/local/etc/sane.d/hpsj5s.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-hpsj5s.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-hpsj5s.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SEE ALSO
+ sane(7)
+ http://hpsj5s.sourceforge.net
+ http://cyberelk.net/tim/libieee1284
+
+
+
+AUTHOR
+ Max Vorobiev
+ Man page mostly based on canon.man
+
+sane-backends 1.0.12-cvs 24 Feb 2002 sane-hpsj5s(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-ibm.5.html b/man/sane-ibm.5.html
new file mode 100644
index 00000000..e8ec348f
--- /dev/null
+++ b/man/sane-ibm.5.html
@@ -0,0 +1,105 @@
+
+
+sane-ibm.5
+
+
+sane-ibm.5
+
+
+
+sane-ibm(5) SANE Scanner Access Now Easy sane-ibm(5)
+
+
+
+NAME
+ sane-ibm - SANE backend for IBM and Ricoh SCSI flatbed scanners
+
+
+
+DESCRIPTION
+ The sane-ibm library implements a SANE (Scanner Access Now Easy) back-
+ end that provides access to the IBM 2456 and the Ricoh IS-410, IS-420,
+ and IS-430 flatbed scanners. Support for the IS-410 and IS-430 is
+ untested. Please contact the maintainer or the sane-devel mailing list
+ if you own such a scanner.
+
+ This backend is alpha-quality. It may have bugs and some scanners
+ haven't been tested at all. Be careful and pull the plug if the scanner
+ causes unusual noise.
+
+
+
+DEVICE NAMES
+ This backend expects device names of the form:
+
+ special
+
+ Where special is either the path-name for the special device that cor-
+ responds to a SCSI scanner. The program sane-find-scanner helps to find
+ out the correct device. Under Linux, such a device name could be
+ /dev/sg0 or /dev/sga, for example. See sane-scsi(5) for details.
+
+
+
+CONFIGURATION
+ The contents of the ibm.conf file is a list of device names that corre-
+ spond to SCSI scanners. Empty lines and lines starting with a hash
+ mark (#) are ignored. See sane-scsi(5) on details of what constitutes
+ a valid device name.
+
+
+
+FILES
+ /usr/local/etc/sane.d/ibm.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-ibm.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-ibm.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_IBM
+ 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.
+
+
+
+SEE ALSO
+ sane(7), sane-find-scanner(1), sane-scsi(5),
+
+
+
+AUTHOR
+ mf <massifr@tiscalinet.it>
+ Maintained by Henning Meier-Geinitz <henning@meier-geinitz.de>
+
+sane-backends 1.0.12-cvs 15 Apr 2003 sane-ibm(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-leo.5.html b/man/sane-leo.5.html
new file mode 100644
index 00000000..f6e7f5e4
--- /dev/null
+++ b/man/sane-leo.5.html
@@ -0,0 +1,145 @@
+
+
+sane-leo.5
+
+
+sane-leo.5
+
+
+
+sane-leo(5) SANE Scanner Access Now Easy sane-leo(5)
+
+
+
+NAME
+ sane-leo - SANE backend for LEO Technologies scanners
+
+
+
+DESCRIPTION
+ The sane-leo library implements a SANE (Scanner Access Now Easy) back-
+ end that provides access to some LEO SCSI flatbed scanners. This back-
+ end should be considered beta-quality software! LEO scanners were also
+ sold under the Across Technologies brand.
+
+ The scanners that should work with this backend are:
+
+ Vendor Model status
+ ---------------------- -----------
+ Across FS-1130 tested
+ Leo S3 tested
+
+ The options the backend supports can either be selected through command
+ line options to programs like scanimage or through GUI elements in
+ xscanimage or xsane.
+
+ If you have any strange behavior, please report to the backend main-
+ tainer or to the SANE mailing list.
+
+ Valid command line options and their syntax can be listed by using
+ scanimage --help -d leo
+
+ Scan Mode
+
+ --mode selects the basic mode of operation of the scanner valid choices
+ are Black & White , Grayscale and Color The Black & White mode
+ is black and white only (1 bit). Grayscale will produce 256 lev-
+ els of gray (8 bits). Color will produce a 24 bits color image.
+
+ --resolution
+ selects the resolution for a scan. The scanner can do all reso-
+ lutions between 1 and 300, in increments of 1.
+
+ Geometry options
+
+ -l -t -x -y
+ control the scan area: -l sets the top left x coordinate, -t the
+ top left y coordinate, -x selects the width and -y the height of
+ the scan area. All parameters are specified in millimeters by
+ default.
+
+ Enhancement options
+
+ --custom-gamma
+ (grayscale and color mode only) allows the user to specify a
+ gamma table (see the next 3 parameters).
+
+ --red-gamma-table
+ (color mode only) can be used to download a user defined gamma
+ table for the red channel. The table must be 256 bytes long.
+
+ --green-gamma-table
+ (color mode only) can be used to download a user defined gamma
+ table for the green channel. The table must be 256 bytes long.
+
+ --blue-gamma-table
+ (color mode only) can be used to download a user defined gamma
+ table for the blue channel. The table must be 256 bytes long.
+
+ --halftone
+ (Black & White only) select the halftone mask to use. Possible
+ values are Diamond , 8x8 Coarse Fatting , 8x8 Fine Fatting , 8x8
+ Bayer and 8x8 Vertical Line
+
+ --preview
+ requests a preview scan. The resolution used for that scan is 28
+ dpi and the scan area is the maximum allowed. The scan mode is
+ user selected. The default is "no".
+
+
+
+CONFIGURATION FILE
+ The configuration file /usr/local/etc/sane.d/leo.conf supports only one
+ information: the device name to use (eg /dev/scanner).
+
+
+
+FILES
+ /usr/local/lib/sane/libsane-leo.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-leo.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_DEBUG_LEO
+ 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.
+
+
+
+LIMITATIONS
+ 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.
+
+
+
+BUGS
+ None known.
+
+
+
+SEE ALSO
+ sane-scsi(5), scanimage(1), xscanimage(1), xsane(1), sane(7)
+
+
+
+AUTHOR
+ The package is actively maintained by Frank Zago.
+ http://fz.eryx.net/sane/#leo
+
+sane-backends 1.0.12-cvs 16 April 2002 sane-leo(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-ma1509.5.html b/man/sane-ma1509.5.html
new file mode 100644
index 00000000..044f1fbb
--- /dev/null
+++ b/man/sane-ma1509.5.html
@@ -0,0 +1,138 @@
+
+
+sane-ma1509.5
+
+
+sane-ma1509.5
+
+
+
+sane-ma1509(5) SANE Scanner Access Now Easy sane-ma1509(5)
+
+
+
+NAME
+ sane-ma1509 - SANE backend for Mustek BearPaw 1200F USB scanner
+
+
+
+DESCRIPTION
+ The sane-ma1509 library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to the Mustek BearPaw 1200F USB flatbed
+ scanner. This scanner is based on the MA-1509 chipset. Other scanners
+ that use this chip (if they exist) may also work.
+
+ This backend is ALPHA software. Be careful and remove the power plug
+ immediately if your hear unusual noises.
+
+ More details can be found on the ma1509 backend homepage
+ http://www.meier-geinitz.de/sane/ma1509-backend/.
+
+ Other Mustek USB scanners are supported by the gt68xx, mustek_usb and
+ the plustek backends. See sane-mustek_usb(5), sane-gt68xx(5) and sane-
+ plustek(5) for details.
+
+ This backend can only work with scanners that are already detected by
+ the operating system. See sane-usb(5) for details.
+
+ If you own a scanner other than the Mustek BearPaw 1200F that works
+ with this backend, please let me know this by sending the scanner's
+ exact model name and the USB vendor and device ids (e.g. from
+ /proc/bus/usb/devices or syslog) to me.
+
+
+
+DEVICE NAMES
+ This backend expects device names of the form:
+
+ special
+
+ Where special is a path-name for the special device that corresponds to
+ a USB scanner. With Linux, such a device name could be /dev/usb/scan-
+ ner0 or libusb:001:002, for example.
+
+
+
+CONFIGURATION
+ The contents of the ma1509.conf file is a list of options and device
+ names that correspond to Mustek BearPAw 1200F scanners. Empty lines
+ and lines starting with a hash mark (#) are ignored.
+
+ Instead of using the device name, the scanner can be autodetected by
+ usb vendor_id product_id statements which are already included into
+ ma1509.conf. This is only supported with Linux 2.4.8 and higher and
+ all systems that support libsub. "vendor_id" and "product_id" are hex-
+ adecimal numbers that identfy the scanner. If this doesn't work, a
+ device name must be placed in ma1509.conf as described above.
+
+ To set the time the lamp needs for warm-up, use option warmup-time in
+ ma1509.conf. The time is given in seconds after the option. The
+ default is 30 seconds.
+
+
+
+FILES
+ /usr/local/etc/sane.d/ma1509.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-ma1509.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-ma1509.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_MA1509
+ 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.
+
+
+
+SEE ALSO
+ sane(7), sane-usb(5), sane-gt68xx(5), sane-plustek(5), sane-
+ mustek_usb(5), sane-mustek(5), sane-mustek_pp(5),
+ http://www.meier-geinitz.de/sane/ma1509-backend/
+
+
+
+AUTHOR
+ Henning Meier-Geinitz <henning@meier-geinitz.de>
+
+
+
+BUGS
+ Resolutions higher than 600 dpi don't work
+ Transparency adapter and automatic document feeder is not supported yet
+ No support for "high-speed" mode (jpeg)
+
+ More detailed bug information is available at the MA-1509 backend home-
+ page http://www.meier-geinitz.de/sane/ma1509-backend/.
+
+sane-backends 1.0.12-cvs 24 Feb 2003 sane-ma1509(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-matsushita.5.html b/man/sane-matsushita.5.html
new file mode 100644
index 00000000..7b9e908f
--- /dev/null
+++ b/man/sane-matsushita.5.html
@@ -0,0 +1,186 @@
+
+
+sane-matsushita.5
+
+
+sane-matsushita.5
+
+
+
+sane-matsushita(5) SANE Scanner Access Now Easy sane-matsushita(5)
+
+
+
+NAME
+ sane-matsushita - SANE backend for Panasonic KV-SS high speed scanners
+
+
+
+DESCRIPTION
+ The sane-matsushita library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to some Panasonic KV-SS high speed scan-
+ ners. This backend is stable.
+
+ At present, the following scanners are known to work with this backend:
+
+ Product id
+ --------------
+ KV-SS 25
+ KV-SS 25D
+
+ Other Panasonic high speed scanners may or may not work with that back-
+ end.
+
+ Valid command line options and their syntax can be listed by using
+ scanimage --help -d matsushita
+
+ Scan Mode
+
+ --mode selects the basic mode of operation of the scanner.
+
+ --resolution
+ selects the resolution for a scan. Each model supports all or a
+ subset of these resolutions: 100, 150, 200, 240, 300, 360, 400.
+
+ --duplex
+ indicates whether to scan both side of the sheet.
+
+ --feeder-mode
+ selects the number of pages to scan (one or until the tray is
+ empty).
+
+ Geometry
+
+ --paper-size A4|...|Legal|Letter [A4]
+ options selects the area to scan. It adjust the -l -t -x -y
+ options accordingly. It does not need to be the real size of the
+ paper.
+
+ -l -t -x -y
+ control the scan area: -l sets the top left x coordinate, -t the
+ top left y coordinate, -x selects the width and -y the height of
+ the scan aea. All parameters are specified in milimeters. It is
+ possible to use the option --paper-size instead.
+
+ Enhancement
+
+ --brightness
+ controls the brightness of the acquired image. The value varies
+ from 1 to 255, or less, depending on the scanner model.
+
+ --contrast
+ controls the contrast of the acquired image. Some models do not
+ support that option.
+
+ --automatic-threshold
+ automatically sets brightness, contrast, white level, gamma,
+ noise reduction and image emphasis. These options are not avail-
+ able when automatic-threshold is in use.
+
+ --halftone-pattern
+ option sets the tonal gradation for the halftone mode. Pattern
+ downloading is not implemented by the backend.
+
+ --autoseparation
+ provides automatic separation of text and images.
+
+ --white-level
+ option indicate the source of the white base.
+
+ --noise-reduction
+ reduces the isolated dot noise. This option is not supported by
+ all scanners.
+
+ --image-emphasis
+ option sets the image emphasis. Some selection are not available
+ on all scanners.
+
+ --gamma
+ options set the gamma curve. It is only valid for Gray modes,
+ and is not available on all scanners. Gamma downloading is not
+ implemented by the backend.
+
+
+
+CONFIGURATION FILE
+ The configuration file /usr/local/etc/sane.d/matsushita.conf supports
+ the device name to use (eg /dev/scanner) and the scsi option to autode-
+ tect the scanners supported.
+
+
+
+FILES
+ /usr/local/lib/sane/libsane-matsushita.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-matsushita.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_DEBUG_MATSUSHITA
+ 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.
+
+
+
+LIMITATIONS
+ Memory in the KV-SS 25
+ The KV-SS 25 has not enough internal memory to scan a whole A4
+ page in duplex mode at high densities. The frontend will return
+ a memory error in that case. Apparently, the KV-SS 25D has not
+ that problem.
+
+ Pattern and gamma downloading
+ The scanner, with the proper firmware, can download a halftone
+ pattern and a gamma table. This is not implemented.
+
+ Sub-areas
+ The scanner can support up to 3 sub-areas on each side to define
+ some more precise enhancment options. This is not implemented.
+
+ Duplex mode
+ The backend does not support the setting of different options
+ for each side. The scan will occur with the same options
+ (halftone pattern, brightness, image emphasis) for both sides.
+
+
+
+SCANNING EXAMPLE
+ To date, the only frontend capable of using this scanner at full speed
+ is scanadf.
+
+ A scanadf command line would be:
+
+ scanadf -d matsushita --output-file scan%04d.pbm --start-count 0
+ --duplex --resolution 300 --feeder-mode="All pages" --paper-size="A4"
+
+
+
+BUGS
+ None known.
+
+
+
+SEE ALSO
+ sane-scsi(5), scanimage(1), xscanimage(1), xsane(1), sane(7)
+
+
+
+AUTHOR
+ The package is actively maintained by Frank Zago.
+ http://fz.eryx.net/sane/#matsushita
+
+sane-backends 1.0.12-cvs April 21s, 2002 sane-matsushita(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-microtek.5.html b/man/sane-microtek.5.html
new file mode 100644
index 00000000..1ee0b890
--- /dev/null
+++ b/man/sane-microtek.5.html
@@ -0,0 +1,177 @@
+
+
+sane-microtek.5
+
+
+sane-microtek.5
+
+
+
+sane-microtek(5) SANE Scanner Access Now Easy sane-microtek(5)
+
+
+
+NAME
+ sane-microtek - SANE backend for Microtek scanners
+
+
+
+DESCRIPTION
+ The sane-microtek library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to the "second generation" Microtek scan-
+ ners. At present, the following hardware is known to work with this
+ backend:
+
+ Microtek ScanMaker E2, E3, E6
+ Microtek ScanMaker II, IIG, IIHR, IISP, III
+ Microtek ScanMaker 35t, 35t+, 45t
+ Microtek ScanMaker 600GS, 600ZS (see bug notes)
+ Agfa StudioScan
+ Agfa StudioScan II, StudioScan IIsi
+ Agfa Arcus II (but not the "Arcus")
+ Agfa DuoScan (premliminary)
+ Vobis "Highscreen Realscan"
+ Microtek Color PageWiz (preliminary)
+
+ Transparent Media Adapter
+ Document AutoFeeder
+
+ The driver supports line art, halftone, 8bpp gray, and 24bpp color
+ scans at normal and "expanded" resolutions (i.e. 1200x1200 on an E6),
+ fast scans for color previews, and downloadable gamma tables.
+
+ The supported scanners are all SCSI scanners. However, some parallel
+ port models may work (under Linux), if they use a parport->scsi chip,
+ and if you can find a scsi->parport driver. This is known to be the
+ case for the Color PageWiz.
+
+ The driver does not support the newest Microtek scanners, such as the
+ V330 and V660, which use a new and very different SCSI-II command set.
+ For those, try the alternate microtek2 backend. Most non-SCSI scanners
+ would use the new command set. Most scanners newer than the Scanmaker
+ E6 would use the new command set.
+
+ If you own a Microtek scanner other than the ones listed above, tell us
+ what happens --- see the BUGS section at the end of this document.
+
+ Although this manual page is generally updated with each release, up-
+ to-date information on new releases and extraneous helpful hints are
+ available from the backend homepage:
+ http://www.mir.com/mtek/
+
+
+
+DEVICE NAMES
+ This backend expects device names of the form:
+
+ special
+
+ Where special is the UNIX path-name for the special device that corre-
+ sponds to the scanner. The special device name must be a generic SCSI
+ device or a symlink to such a device. Under Linux, such a device name
+ could be /dev/sga or /dev/sge, for example.
+
+
+
+CONFIGURATION
+ The contents of the microtek.conf file is a list of device names that
+ correspond to Microtek scanners. Empty lines and lines starting with a
+ hash mark (#) are ignored. A sample configuration file is shown below:
+
+ /dev/scanner
+ # this is a comment
+ /dev/sge
+
+ The configuration file may also contain the special tokens norealcal or
+ noprecal. norealcal will disable the use of magic, undocumented scan-
+ ner calibration commands which are known to work on the E6, but may not
+ work with other models. noprecal will disable logic which tries to
+ avoid scanner precalibration. This logic would only have been acti-
+ vated if the magic calibration code was turned off.
+
+
+
+FILES
+ /usr/local/etc/sane.d/microtek.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-microtek.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-microtek.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_MICROTEK
+ If the library was compiled with debugging support enabled, this
+ environment variable controls the debug level for this backend.
+ A value of 128 requests maximally copious debug output; smaller
+ levels reduce verbosity.
+
+
+
+SEE ALSO
+ sane(7), sane-scsi(5)
+
+
+
+AUTHOR
+ Matt Marjanovic
+
+
+
+BUGS
+ Known bugs/limitations are:
+
+ Brightness and contrast broken.
+ The 600GS is grayscale only, and will lock up if you select
+ color. (Unfortunately, the 600GS and 600ZS are indistinguish-
+ able by software.)
+
+ i.e. don't complain about these --- but if brightness and/or contrast
+ do work for you, please tell me.
+
+ If your scanner locks up, try setting the norealcal or noprecal option
+ in the configuration file (first one, then both), and see if it helps.
+ (If it does, report it.)
+
+ Send lengthy bug reports and new scanner information to mtek-
+ bugs@mir.com. All bug reports and new scanner inquiries should include
+ an error log file. You can generate copious stderr output by setting
+ the SANE_DEBUG_MICROTEK environment variable described above. For
+ example:
+
+ setenv SANE_DEBUG_MICROTEK 128
+
+ More general comments, suggestions, and inquiries about frontends or
+ SANE should go to sane-devel@mostang.com, the SANE Developers mailing
+ list. Have a look at http://www.mostang.com/sane/mail.html concerning
+ subscription to sane-devel.
+
+sane-backends 1.0.12-cvs February 8, 2000 sane-microtek(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-microtek2.5.html b/man/sane-microtek2.5.html
new file mode 100644
index 00000000..a0dbe8e2
--- /dev/null
+++ b/man/sane-microtek2.5.html
@@ -0,0 +1,294 @@
+
+
+sane-microtek2.5
+
+
+sane-microtek2.5
+
+
+
+sane-microtek2(5) SANE Scanner Access Now Easy sane-microtek2(5)
+
+
+
+NAME
+ sane-microtek2 - SANE backend for Microtek scanners with SCSI-2 command
+ set
+
+
+
+DESCRIPTION
+ The sane-microtek2 library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to Microtek scanners with a SCSI-2 command
+ set. This backend can be considered alpha to beta. Some scanner models
+ are reported to work well, others not. New development versions of this
+ backend can be obtained from http://karstenfestag.gmxhome.de
+
+ There exists a different backend for Microtek scanners with SCSI-1 com-
+ mand set. Refer to sane-microtek(5) for details.
+
+ And there is work in progress for the ScanMaker 3600. See
+ http://sourceforge.net/projects/sm3600
+
+ At present, the following scanners are known positively to work with
+ this backend:
+
+ Vendor Product id: Remark
+ -------- -------------- -------------
+ Microtek E3+ Parport and SCSI
+ Microtek X6 SCSI
+ Microtek X6EL SCSI
+ Microtek X6USB USB
+ Microtek ScanMaker V300 Parport and SCSI
+ Microtek ScanMaker V310 Parport and SCSI
+ Microtek ScanMaker V600 Parport and SCSI
+ Microtek ScanMaker 330 SCSI
+ Microtek ScanMaker 630 SCSI
+ Microtek ScanMaker 636 SCSI
+ Microtek ScanMaker 9600XL SCSI; only flatbed mode?
+ Microtek Phantom 330CX Parport
+ Microtek SlimScan C3 Parport
+ Microtek SlimScan C6 USB
+ Microtek Phantom 636 SCSI
+ Microtek Phantom 636CX Parport
+ Microtek V6USL SCSI and USB
+ Microtek V6UPL USB; not stable
+ Microtek X12USL SCSI; only 8bit color, work in progress
+ Vobis HighScan SCSI (E3+ based models)
+ Scanport SQ300 Parport?
+ Scanport SQ4836 SCSI
+ Scanpaq SQ2030 Parport
+
+ Additional information can be found at http://www.mostang.com/sane/ .
+
+ If you own a Microtek scanner other than the ones listed above, it may
+ or may not work with SANE! Because equal scanners are sold under dif-
+ ferent names in different countries your model may be equivalent to one
+ of the above.
+
+ The parport scanners work with the ppscsi + onscsi kernel modules. See
+ http://www.torque.net/parport/ppscsi.html
+
+ The USB scanners work with the microtek kernel module. You may have to
+ add the vendor and model codes to microtek.c if they aren't yet listed
+ there.
+
+ Both parport and USB scanners need the generic SCSI support, so check
+ if you have loaded the scsi_mod and sg modules!
+
+ If you try your scanner for the first time keep an eye on it. If it
+ gets commands that it doesn't understand the scanhead may go beyond the
+ scan area. The scanner then makes strange noises. In this case imme-
+ dieately switch off the scanner or disconnect its power cable to pre-
+ vent damages!
+
+ If your scanner is a different one than the models mentioned above and
+ it is working please tell the author about it. It would be nice if you
+ add a logfile to this information (creation of the logfile: see below).
+
+ If your scanner is not working properly you also should create a log-
+ file and send it to the author. He will use the information to improve
+ the backend and possibly make your scanner work.
+
+ How to create the logfile?
+
+ - put the line
+ "option dump 2" into your microtek2.conf
+ file or change the existing "option dump" to "2"
+
+ - in a terminal (bash) type
+ "export SANE_DEBUG_MICROTEK2=30" and then
+ "scanimage -l0 -t0 -x100 -y20 2>scan.log >sout.pnm"
+ You get two files: scan.log contains the logfile and sout.pnm
+ the scanned image (if there was scanned something). Zip them
+ before sending.
+
+
+
+FRONTEND OPTIONS
+ This backend dynamically enables the options for the frontend, that are
+ supported by the scanner in dependence of the scanning-mode and other
+ options. Not supported options are disabled.
+
+ The following options are supported by the Microtek2-driver:
+
+ Color, grayscale, halftone and lineart scans.
+
+ Highlight, midtone, shadow, contrast, brightness, exposure time con-
+ trol, gamma correction, threshold (dependent of the scan mode and the
+ scanner capabilities)
+
+ Transparency media adapter, automatic document feeder
+
+ Additional options can be enabled or disabled in the microtek2.conf
+ file. See the configuration section of this manpage.
+
+
+
+DEVICE NAMES
+ This backend expects device names of the form:
+
+ special
+
+ Where special is the UNIX path-name for the special device that corre-
+ sponds to the scanner. The special device name must be a generic SCSI
+ device or a symlink to such a device. Under Linux, such a device name
+ could be /dev/sga or /dev/sge for example.
+
+
+
+CONFIGURATION
+ The configuration file for this backend resides in
+ /usr/local/etc/sane.d/microtek2.conf Its contents is a list of device
+ names that correspond to Microtek scanners with SCSI-2 interface. Empty
+ lines and lines starting with a hash mark (#) are ignored.
+
+ The configuration file may also contain options. Global options that
+ are valid for all devices are placed above the device names. Device-
+ specific options are placed under the device name. Note that, except
+ for option dump <n> and option strip-height <n>, the entry in the
+ microtek2.conf file only enables the corresponding option for being
+ showed in the frontend. There, in the frontend, you can switch the
+ options on and off. Currently the following options are supported:
+
+ option dump <n>
+ option strip-height <n>
+ option no-backtrack-option <on/off>
+ option lightlid-35 <on/off>
+ option toggle-lamp <on/off>
+ option lineart-autoadjust <on/off>
+ option backend-calibration <on/off>
+ option colorbalance-adjust <on/off>
+
+ option dump <n> enables printing of additional information about the
+ SCSI commands that are sent to the scanner to stderr. This option is
+ primarily useful for debugging purpose. This option has to be a global
+ option and is best placed at the top of the microtek2.conf file.
+
+ If n=1 the contents of the command blocks and the results for the
+ INQUIRY and READ SCANNER ATTRIBUTES command are printed to stderr.
+
+ If n=2 the contents of the command blocks for all other SCSI commands
+ are printed to stderr, too. If n=3 the contents of the gamma table is
+ printed, too. If n=4 all scan data is additionally printed to stderr.
+
+ The default is n=1.
+
+ option strip-height <n> , where <n> is a floating point number, limits
+ the amount of data that is read from the scanner with one read command.
+ The unit is inch and <n> defaults to 1.0, if this option is not set in
+ the configuration file. If less than <n> inch of data fit into the SCSI
+ buffer, then the smaller value is used and this option has no effect.
+
+ If your system has a big SCSI buffer and you want to make use of the
+ whole buffer, increase the value for <n>. For example, if <n> is set to
+ 14.0, no restrictions apply for scanners with a letter, legal or A4
+ sized scan area.
+
+ The following options enable or disable additional frontend options. If
+ an option is set to <on> an appropriate option will appear in the fron-
+ tend.
+
+ option no-backtrack-option <on/off> prevents the scanner head from mov-
+ ing backwards between the read commands. This speeds up scanning. Try
+ it.
+
+ option lightlid-35 <on/off> If you use the LightLid-35 transparency
+ adapter you get an advanced option which switches off the flatbed lamp
+ during the scan.
+
+ option toggle-lamp <on/off> You get a button in the frontend where you
+ can switch on and off the flatbed lamp.
+
+ option lineart-autoadjust <on/off> You can tell the backend to try to
+ determine a good value for the lineart threshold.
+
+ option backend-calibration <on/off> Some scanners (e.g. Phantom 330CX
+ and 636CX) need to have calibrated the data by the backend. Try this
+ option if you see vertical stripes in your pictures.
+
+ option colorbalance-adjust <on/off> Some scanners (e.g. Phantom 330CX
+ and 636CX) need to have corrected the color balance. If this option is
+ enabled you get advanced options where you can balance the colors. And
+ you will have a button to use the values that the firmware of the scan-
+ ner provides.
+
+ A sample configuration file is shown below:
+
+ option dump 1
+ option strip-height 1.0
+ /dev/scanner
+ option no-backtrack-option on
+ # this is a comment
+ /dev/sge
+ option lightlid-35 on
+
+ This backend also supports the new configuration file format which
+ makes it easier to detect scanners under Linux. If you have only one
+ scanner it would be best to use the following configuration file for
+ this backend:
+
+ option dump 1
+ option strip-height 14.0
+ option no-backtrack-option on
+ option backend-calibration on
+ option lightlid-35 on
+ option toggle-lamp on
+ option lineart-autoadjust on
+ option colorbalance-adjust off
+ scsi * * Scanner
+
+ In this case all SCSI-Scanners should be detected automatically because
+ of the
+
+ scsi * * Scanner
+
+ line.
+
+
+
+FILES
+ /usr/local/etc/sane.d/microtek2.conf
+ The backend configuration file.
+
+ /usr/local/lib/sane/libsane-microtek2.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-microtek2.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_DEBUG_MICROTEK2
+ If the library was compiled with debug support enabled, this
+ environment variable controls the debug level for this backend.
+ E.g., a value of 255 requests all debug output to be printed.
+ Smaller levels reduce verbosity. To see error messages on stderr
+ set SANE_DEBUG_MICROTEK2 to 1 (Remark: The whole debugging lev-
+ els should be better revised).
+ E.g. just say:
+ export SANE_DEBUG_MICROTEK2=128
+
+
+
+SEE ALSO
+ sane-scsi(5), sane(7)
+
+
+
+AUTHORS
+ Bernd Schroeder (not active anymore)
+ Karsten Festag karsten.festag@gmx.de
+
+
+sane-backends 1.0.12-cvs 28 Jan 2002 sane-microtek2(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-mustek.5.html b/man/sane-mustek.5.html
new file mode 100644
index 00000000..bc42125e
--- /dev/null
+++ b/man/sane-mustek.5.html
@@ -0,0 +1,348 @@
+
+
+sane-mustek.5
+
+
+sane-mustek.5
+
+
+
+sane-mustek(5) SANE Scanner Access Now Easy sane-mustek(5)
+
+
+
+NAME
+ sane-mustek - SANE backend for Mustek SCSI flatbed scanners
+
+
+
+DESCRIPTION
+ The sane-mustek library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to Mustek (and some relabeled Trust and
+ Primax) SCSI flatbed scanners. At present, the following scanners are
+ known to work more or less with this backend:
+
+ Paragon MFS-6000CX
+ Paragon MFS-12000CX
+ Paragon MFC-600S, 600 II CD, ScanMagic 600 II SP
+ Paragon MFC-800S, 800 II SP
+ Paragon MFS-6000SP
+ Paragon MFS-8000SP
+ Paragon MFS-1200SP, MFS-12000SP
+ ScanExpress 6000SP
+ ScanExpress 12000SP, 12000SP Plus, Paragon 1200 III SP, Scan-
+ Magic 9636S, 9636S Plus
+ Paragon 1200 LS
+ ScanExpress A3 SP
+ Paragon 1200 SP Pro
+ Paragon 1200 A3 Pro
+ Paragon 600 II N
+ Trust Imagery 1200
+ Trust Imagery 1200 SP
+ Trust Imagery 4800 SP
+ Trust SCSI Connect 19200
+ Primax Compact 4800 SCSI
+
+ More details can be found on the Mustek SCSI backend homepage
+ http://www.meier-geinitz.de/sane/mustek-backend/.
+
+ Don't mix up MFS (Paragon), Pro and ScanExpress models! They're com-
+ pletely different. Check the exact model name!
+
+ Note that most of the above scanners come with a SCSI interface. The
+ only non-SCSI scanner that has some support at this point is the 600 II
+ N scanner which comes with its own parallel port adapter (i.e., it does
+ not attach to the printer port). It uses the SCSI protocoll internally,
+ too. More info on how to use the 600 II N can be found below in section
+ PARAGON 600 II N. Other parallel port scanners are not supported by
+ this backend but you may be successful using the Mustek parallel port
+ backend mustek_pp, see sane-mustek_pp(5). USB scanners are also not
+ supported by this backend but the mustek_usb, gt68xx, and plustek back-
+ ends include support for some of them, see sane-mustek_usb(5), sane-
+ gt68xx(5), and sane-plustek(5).
+
+ Mustek scanners have no protection against exceeding the physical scan
+ area height. That is, if a scan is attempted with a height that
+ exceeds the height of the scan surface, the scanner begins making loud
+ noises and the scan mechanism may be damaged. Thus, if you hear such a
+ noise, IMMEDIATELY turn off the scanner. This shouldn't happen if your
+ scanner is in the list of known scanners. There is more information in
+ the /usr/local/doc/sane-1.0.12-cvs/PROBLEMS file.
+
+ If you own a Mustek (or Trust) scanner other than the ones listed above
+ that works with this backend, please let us know by sending the scan-
+ ner's exact model name (look at the front and back of the scanner) and
+ a debug output to sane-devel@mostang.com. You can get the debug output
+ by setting the environment variable SANE_DEBUG_MUSTEK 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 http://www.mostang.com/sane/mail.html
+ for details.
+
+
+
+DEVICE NAMES
+ This backend expects device names of the form:
+
+ special
+
+ Where special is either the path-name for the special device that cor-
+ responds to a SCSI scanner or the port number at which the 600 II N can
+ be found (see section PARAGON 600 II N below). For SCSI scanners, the
+ special device name must be a generic SCSI device or a symlink to such
+ a device. The program sane-find-scanner helps to find out the correct
+ device. Under Linux, such a device name could be /dev/sga or /dev/sge,
+ for example. See sane-scsi(5) for details.
+
+
+
+CONFIGURATION
+ The contents of the mustek.conf file is a list of options and device
+ names that correspond to Mustek scanners. Empty lines and lines start-
+ ing with a hash mark (#) are ignored. See sane-scsi(5) on details of
+ what constitutes a valid device name.
+
+ The supported options are linedistance-fix, lineart-fix, legal-size,
+ buffersize, blocksize, strip-height, disable-double-buffering, disable-
+ backtracking, and force-wait.
+
+ Options come in two flavors: global and positional ones. Global
+ options apply to all devices managed by the backend whereas positional
+ options apply just to the most recently mentioned device. Note that
+ this means that the order in which the options appear matters!
+
+ Option linedistance-fix is positional and works around a problem that
+ occurs with some SCSI controllers (notably the ncr810 controller under
+ Linux). If color scans have horizontal stripes and/or the colors are
+ off, then it's likely that your controller suffers from this problem.
+ Turning on this option usually fixes the problem.
+
+ Option lineart-fix is positional and works around a timing problem that
+ seems to exist with certain MFS-12000SP scanners. The problem mani-
+ fests itself in dropped lines when scanning in lineart mode. Turning
+ on this option should fix the problem but may slow down scanning a bit.
+
+ Option legal-size is positional and sets the size of the scan area to
+ Legal format. Set this option if you own a Paragon 12000 LS. It can't
+ be distinguished by software from a ScanExpress 12000 SP (ISO A4 for-
+ mat).
+
+ Option buffersize is a positional option that overrides the default
+ value set for the size of the SCSI buffer. The buffer size is specified
+ in kilobytes. The default value is 128. Because of double buffering the
+ buffer actually sent to the scanner is half the size of this value. Try
+ to increase this value to achieve higher scan speeds. Note that some
+ ScanExpress scanners don't like buffer sizes above 64 kb (buffersize =
+ 128). If your sg driver can't set SCSI buffer sizes at runtime you may
+ have to change that value, too. See sane-scsi(5) for details.
+
+ Option blocksize is a positional option that overrides the default
+ value set for the maximum amount of data scanned in one block. The
+ buffer size is specified in kilobytes. Some scanners freeze if this
+ value is bigger than 2048. The default value is 1 GB (so effectively no
+ limit) for most scanners. Don't change this value if you don't know
+ exactly what you do.
+
+ Option strip-height is a global option that limits the maximum height
+ of the strip scanned with a single SCSI read command. The height is
+ specified in inches and may contain a fractional part (e.g., 1.5).
+ Setting the strip-height to a small value (one inch, for example)
+ reduces the likelihood of encountering problems with SCSI driver time-
+ outs and/or timeouts with other devices on the same SCSI bus. Unfortu-
+ nately, it also increases scan times. With current SCSI adapters and
+ drivers this option shouldn't be needed any more.
+
+ Option disable-double-buffering is a global option. If set, the backend
+ will only send one buffer at a time to the scanner. Try this option if
+ you have trouble while scanning, e.g. SCSI errors, freezes, or the
+ first few cm are repeated over and over again in your image.
+
+ Option disable-backtracking is a positional option. If set, the scanner
+ will not move back its slider after each SCSI buffer is filled (`back-
+ tracking'). Setting this option will lead to faster scans but may also
+ produce horizontal stripes. This option doesn't work with every scanner
+ (only some of the paragon models can modify backtracking).
+
+ Finally, force-wait is a global option. If set, the backend will wait
+ until the device is ready before sending the inquiry command. Further
+ more the backend will force the scan slider to return to its starting
+ position (not implemented for all scanners). This option may be neces-
+ sary with the 600 II N or when scanimage is used multiple times (e.g.
+ in scripts). The default is off (not set).
+
+ A sample configuration file is shown below:
+
+ # limit strip height of all scanners to 1.5 inches:
+ option strip-height 1.5
+ /dev/scanner # first Mustek scanner
+ # 1 MB buffer for /dev/scanner:
+ option buffersize 1024
+ /dev/sge # second Mustek scanner
+ # turn on fixes for /dev/sge:
+ option lineart-fix
+ option linedistance-fix
+
+
+
+SCSI ADAPTER TIPS
+ You need a SCSI adapter for the SCSI scanners. Even if the connector is
+ the same as that of parallel port scanners, connecting it to the com-
+ puters parallel port will NOT work.
+
+ Mustek SCSI scanners are typically delivered with an ISA SCSI adapter.
+ Unfortunately, that adapter is not worth much since it is not interrupt
+ driven. It is (sometimes) possible to get the supplied card to work,
+ but without interrupt line, scanning will be very slow and put so much
+ load on the system, that it becomes almost unusable for other tasks.
+
+ If you already have a working SCSI controller in your system, you
+ should consider that Mustek scanners do not support the SCSI-2 discon-
+ nect/reconnect protocol and hence tie up the SCSI bus while a scan is
+ in progress. This means that no other SCSI device on the same bus can
+ be accessed while a scan is in progress.
+
+ Because the Mustek-supplied adapter is not worth much and because
+ Mustek scanners do not support the SCSI-2 disconnect/reconnect proto-
+ col, it is recommended to install a separate (cheap) SCSI controller
+ for Mustek scanners. For example, ncr810 based cards are known to work
+ fine and cost as little as fifty US dollars.
+
+ For Mustek scanners, it is typically necessary to configure the low-
+ level SCSI driver to disable synchronous transfers (sync negotiation),
+ tagged command queuing, and target disconnects. See sane-scsi(5) for
+ driver- and platform-specific information.
+
+ The ScanExpress models have sometimes trouble with high resolution
+ color mode. If you encounter sporadic corrupted images (parts dupli-
+ cated or shifted horizontally) kill all other applications before scan-
+ ning and (if sufficient memory is available) disable swapping.
+
+ Details on how to get the Mustek SCSI adapters and other cards running
+ can be found at http://www.meier-geinitz.de/sane/mustek-backend/#SCSI.
+
+
+
+PARAGON 600 II N
+ This backend has support for the Paragon 600 II N parallel port scan-
+ ner. Note that this scanner comes with its own ISA card that imple-
+ ments a funky parallel port (in other words, the scanner does not con-
+ nected to the printer parallel port).
+
+ This scanner can be configured by listing the port number of the
+ adapter in the mustek.conf file. Valid port numbers are 0x26b, 0x2ab,
+ 0x2eb, 0x22b, 0x32b, 0x36b, 0x3ab, 0x3eb. Pick one that doesn't con-
+ flict with the other hardware in your computer. Put only one number on
+ a single line. Example:
+
+ 0x3eb
+
+ Note that for this scanner root privileges are required to access the
+ I/O ports. Thus, either make frontends such as scanimage(1) and xscan-
+ image(1) setuid root (generally not recommended for safety reasons) or,
+ alternatively, access this backend through the network daemon saned(1).
+ On systems which support this feature, the scanner can be accessed
+ through /dev/port. Don't forget to adjust the permissions for
+ /dev/port. At least with recent Linux kernels root privileges are nec-
+ essary for /dev/port access, even with full permissions set for all
+ users..
+
+ If your images have horizontal stripes in color mode, check option
+ linedistance-fix (see above). Apply this option for a scanner with
+ firmware version 2.x and disable it for version 1.x.
+
+ If the Mustek backend blocks while sending the inqiury command to the
+ scanner, add the option force-wait to mustek.conf.
+
+ Also note that after a while of no activity, some scanners themself
+ (not the SANE backend) turns off their CCFL lamps. This shutdown is not
+ always perfect with the result that the lamp sometimes continues to
+ glow dimly at one end. This doesn't appear to be dangerous since as
+ soon as you use the scanner again, the lamp turns back on to the normal
+ high brightness. However, the first image scanned after such a shutdown
+ may have stripes and appear to be over-exposed. When this happens,
+ just take another scan, and the image will be fine.
+
+
+
+FILES
+ /usr/local/etc/sane.d/mustek.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-mustek.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-mustek.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_MUSTEK
+ If the library was compiled with debug support enabled, this
+ environment variable controls the debug level for this backend.
+ Higher debug levels increase the verbosity of the output.
+
+ Value Description
+ 0 no output
+ 1 print fatal errors
+ 2 print important messages
+ 3 print non-fatal errors and less important messages
+ 4 print all but debugging messages
+ 5 print everything
+
+ Example:
+ export SANE_DEBUG_MUSTEK=4
+
+
+
+SEE ALSO
+ sane(7), sane-find-scanner(1), sane-scsi(5), sane-mustek_usb(5), sane-
+ gt68xx(5), sane-plustek(5), sane-mustek_pp(5)
+ /usr/local/doc/sane-1.0.12-cvs/mustek/mustek.CHANGES
+ http://www.meier-geinitz.de/sane/mustek-backend/
+
+
+
+AUTHOR
+ David Mosberger, Andreas Czechanowski, Andreas Bolsch (SE extensions),
+ Henning Meier-Geinitz
+
+
+
+BUGS
+ Scanning with the SCSI adapters supplied by Mustek is very slow at high
+ resolutions and wide scanareas.
+
+ Some scanners (e.g. Paragon 1200 A3 + Pro, SE A3) need more testing.
+
+ The gamma table supports only 256 colors, even if some scanners can do
+ more.
+
+ More detailed bug information is available at the Mustek backend home-
+ page: http://www.meier-geinitz.de/sane/mustek-backend/.
+
+sane-backends 1.0.12-cvs 5 Dec 2002 sane-mustek(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-mustek_pp.5.html b/man/sane-mustek_pp.5.html
new file mode 100644
index 00000000..d7451584
--- /dev/null
+++ b/man/sane-mustek_pp.5.html
@@ -0,0 +1,367 @@
+
+
+sane-mustek_pp.5
+
+
+sane-mustek_pp.5
+
+
+
+sane-mustek_pp(5) sane-mustek_pp(5)
+
+
+
+NAME
+ sane-mustek_pp - SANE backend for Mustek parallel port flatbed scanners
+
+
+
+DESCRIPTION
+ The sane-mustek_pp library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to Mustek parallel port flatbed scanners
+ and OEM versions.
+
+ There are 2 classes of Mustek parallel port scanners: regular CCD (cold
+ cathode device) scanners and CIS (contact image sensor) scanners.
+
+ Previous versions of this backend only supported CCD type scanners.
+ Patches for CIS type scanners were available, but simultaneous support
+ for both types was not possible. The current version of the driver
+ enables both types to co-exist. The CIS drivers have been ported to it
+ already, and work is going on to port the CCD drivers too.
+
+ The following scanners might work with this backend:
+
+ CCD scanners (currently not hooked up yet)
+
+ Model: ASIC ID: CCD Type: works:
+ -------------------- --------- ---------- -------
+ SE 6000 P 1013 00 yes
+ SM 4800 P 1013/1015 04/01 yes
+ SE 1200 ED Plus 1015 01 partly
+ SM 1200 ED Plus 1015 01 partly
+ SE 12000 P 1505 05 no
+ 600 III EP Plus 1013/1015 00/01 yes
+ SE 600 SEP 1013 ?? yes
+ 600 II EP ???? ?? no
+ MD9848 1015 00 yes
+ Gallery 4800 ???? ?? yes
+ Viviscan Compact II 1013 00 yes
+
+ CIS scanners
+
+ Model: ASIC ID: works:
+ --------------------- --------- -------
+ Mustek 600 CP 1015 yes (*)
+ Mustek 1200 CP 1015 yes
+ Mustek 1200 CP+ 1015 yes
+
+ OEM versions Original works
+ --------------------- --------- ----------
+ Medion/LifeTec/Tevion
+ MD/LT 9350/9351 1200 CP yes
+ MD/LT 9850/9851 1200 CP maybe (**)
+ MD/LT 9858 1200 CP probably
+ MD/LT 9890/9891 1200 CP yes
+ Targa
+ Funline TS12EP 1200 CP yes
+ Funline TS6EP 600 CP yes
+ Trust
+ Easy Connect 9600+ 600 CP yes
+
+ (*) Calibration problems existed with earlier version of this
+ driver. They seem to be solved now.
+
+ (**) Problems have been reported in the past for the MD/LT9850 type
+ (striped scans, head moving in wrong direction at some resolu-
+ tions). It is not known whether the current version of the
+ driver still has these problems.
+ IF YOU HEAR LOUD CLICKING NOISES, IMMEDIATELY UNPLUG THE SCANNER
+ ! (This holds for any type of scanner).
+
+ Please note that this backend is still under construction. Certain mod-
+ els are currently not supported and some may never be because the com-
+ munication protocol is still unknown (eg., SE 12000 P).
+
+ Some scanners work faster when EPP/ECP is enabled in the BIOS.
+
+ Note that the backend needs to run as root. To allow user access to the
+ scanner run the backend through the network interface (See saned(1) and
+ sane-net(5)). Note also that the backend does not support parport shar-
+ ing , i.e. if you try printing while scanning, your computer may crash.
+ This backend also conflicts with the sane-musteka4s2 backend. You can
+ only enable one of them in your dll.conf. However, you have to enable
+ the backend explicitly in your dll.conf, just remove the hash mark in
+ the line "mustek_pp".
+
+
+
+DEVICE DEFINITION
+ This backend allows multiple devices being defined and configured via
+ the mustek_pp.conf file (even simultaneously, provided that they are
+ connected to different parallel ports). Please make sure to edit this
+ file before you use the backend.
+
+ A device can be defined as follows:
+
+ scanner <name> <address> <driver>
+
+ where
+
+ <name> is an arbitrary name for the device, optionally enclosed by dou-
+ ble quotes, for instance "LifeTec 9350".
+
+ <address> is the port address of the parallel port to which the device
+ is connected. Known ports are 0x378, 0x278, and 0x3BC. 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.
+
+ <driver> is the driver to use for this device. Currently available
+ drivers are:
+
+ cis600 : for 600 CP & OEM versions
+ cis1200 : for 1200 CP & OEM versions
+ cis1200+ : for 1200 CP+ & OEM versions
+
+ Choosing the wrong driver can damage your scanner!
+ Especially, using the 1200CP settings on a 600CP can be harmful.
+ If the scanner starts making a loud noice, turn it off immedi-
+ ately !!!
+ Using the cis600 driver on a 1200CP or a 1200CP+ is probably not
+ dangerous. The cis1200+ driver also works for the 1200CP, and
+ using the cis1200 driver on a 1200CP+ will typically result in
+ scans that cover only half of the width of the scan area (also
+ not dangerous).
+ If unsure about the exact model of your OEM version, check the
+ optical resolution in the manual or on the box: the 600CP has a
+ maximum optical resolution of 300x600 DPI, whereas the 1200CP
+ and 1200CP+ have a maximum optical resolution of 600x1200 DPI.
+
+ Examples:
+
+ scanner "LifeTec 9350" 0x378 cis1200
+
+ scanner Mustek_600CP 0x378 cis600
+
+
+
+CONFIGURATION
+ The contents of the mustek_pp.conf file is a list of device definitions
+ and device options that correspond to Mustek scanners. Empty lines and
+ lines starting with a hash mark (#) are ignored. Options have the fol-
+ lowing format:
+
+ option <name> [<value>]
+
+ 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.
+
+ Common options
+
+ bw <value> Black/white discrimination value to be used during lin-
+ eart scanning. Pixel values below this value are assumed to
+ be black, values above are assumed to be white.
+ Default value: 127
+ Minimum: 0
+ Maximum: 255
+
+ Example: option bw 150
+
+ CIS driver options
+
+ top_adjust <value> Vertical adjustment of the origin, expressed in
+ millimeter (floating point). This option can be used to
+ calibrate the position of the origin, within certain limits.
+ Note that CIS scanners are probably temperature sensitive,
+ and that a certain inaccuracy may be hard to avoid. Differ-
+ ences in offset between runs in the order of 1 to 2 mm are
+ not unusual.
+ Default value: 0.0
+ Minimum: -5.0
+ Maximum: 5.0
+
+ Example: option top_skip -2.5
+
+ slow_skip Turns fast skipping to the start of the scan region off.
+ When the region to scan does not start at the origin, the
+ driver will try to move the scanhead to the start of the
+ scan area at the fastest possible speed. On some models,
+ this may not work, resulting in large inaccuracies (up to
+ centimeters). By setting this option, the driver is forced
+ to use normal speed during skipping, which can circumvent
+ the accuracy problems. Currently, there are no models for
+ which these inaccuracy problems are known to occur.
+ By default, fast skipping is used.
+
+ Example: option slow_skip
+
+ CCD driver options
+
+ To be defined.
+
+ A sample configuration file is shown below:
+
+ #
+ # LifeTec/Medion 9350 on port 0x378
+ #
+ scanner "LifeTec 9350" 0x378 cis1200
+
+ # Some calibration options (examples!).
+ option bw 127
+ option top_skip -0.8
+
+ #
+ # A Mustek 600CP on port 0x3BC
+ #
+ scanner "Mustek 600CP" 0x3BC cis600
+
+ # Some calibration options (examples!).
+ option bw 120
+ option top_skip 1.2
+
+ #
+ # A Mustek 1200CP+ on port 0x278
+ #
+ scanner "Mustek 1200CP plus" 0x278 cis1200+
+
+ # Some calibration options (examples!).
+ option bw 130
+ option top_skip 0.2
+
+
+
+FILES
+ /usr/local/etc/sane.d/mustek_pp.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-mustek_pp.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-mustek_pp.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_MUSTEK_PP
+ If the library was compiled with debug support enabled, this
+ environment variable controls the debug level for this backend.
+ E.g., a value of 128 requests all debug output to be printed.
+ Smaller levels reduce verbosity.
+
+ level debug output
+ ------- ------------------------------
+ 0 nothing
+ 1 errors
+ 2 warnings & minor errors
+ 3 additional information
+ 4 debug information
+ 5 code flow (not supported yet)
+ 6 special debug information
+
+ SANE_DEBUG_SANEI_PA4S2
+ This variable sets the debug level for the SANE interface for
+ the Mustek chipset A4S2. Note that enabling this will spam your
+ terminal with some million lines of debug output.
+
+ level debug output
+ ------- -------------------------------
+ 0 nothing
+ 1 errors
+ 2 warnings
+ 3 things nice to know
+ 4 code flow
+ 5 detailed code flow
+ 6 everything
+
+
+
+SEE ALSO
+ sane(7), sane-mustek(5), sane-net(5), saned(1)
+
+ For latest bug fixes and information see
+ http://www.penguin-breeder.org/?page=mustek_pp
+
+ For the latest CIS driver versions, see
+ http://home.tiscalinet.be/EddyDeGreef/
+
+
+
+AUTHORS
+ Jochen Eisinger <jochen.eisinger@gmx.net>
+ Eddy De Greef <eddy_de_greef at tiscali dot be>
+
+
+
+BUGS
+ Too many... please send bug reports to sane-devel@mostang.com (note
+ that you have to subscribe first to the list before you can send
+ emails... see http://www.mostang.com/sane/mail.html)
+
+ * 1013 support isn't bullet proofed
+ * 1505 support isn't even present
+ * 1015 only works for CCD type 00 & 01 (01 only bw/grayscale)
+
+
+
+BUG REPORTS
+ 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...
+
+ SANE version
+ run "scanimage -V" to determine this
+
+ the backend version and your scanner hardware
+ 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.
+
+ the name of your scanner/vendor
+ also a worthy information. Please also include the optical reso-
+ lution and lamp type of your scanner, both can be found in the
+ manual of your scanner.
+
+ any further comments
+ if you have comments about the documentation (what could be done
+ better), or you think I should know something, please include
+ it.
+
+ some nice greetings
+
+ February 20 2002 sane-mustek_pp(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-mustek_usb.5.html b/man/sane-mustek_usb.5.html
new file mode 100644
index 00000000..9c65d3b1
--- /dev/null
+++ b/man/sane-mustek_usb.5.html
@@ -0,0 +1,186 @@
+
+
+sane-mustek_usb.5
+
+
+sane-mustek_usb.5
+
+
+
+sane-mustek_usb(5) SANE Scanner Access Now Easy sane-mustek_usb(5)
+
+
+
+NAME
+ sane-mustek_usb - SANE backend for Mustek USB flatbed scanners
+
+
+
+DESCRIPTION
+ The sane-mustek_usb library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to Mustek USB flatbed scanners (including
+ a clone from Trust). At present, the following scanners are known to
+ work more or less with this backend:
+
+ Mustek 600 CU
+ Mustek 1200 UB
+ Mustek 1200 CU
+ Mustek 1200 CU Plus
+ Trust Compact Scan USB 19200
+
+ More details can be found on the Mustek USB backend homepage
+ http://www.meier-geinitz.de/sane/mustek_usb-backend/.
+
+ The Mustek BearPaw 1200 and 2400 scanners are supported by the plustek
+ backend. See sane-plustek(5) for details. The Mustek BearPaw 1200F is
+ supported by the MA-1509 backend. See sane-ma1509(5) for details. Other
+ Mustek USB scanners are supported by the gt68xx backend, see sane-
+ gt68xx(5).
+
+ This backend can only work with scanners that are already detected by
+ the operating system. See sane-usb(5) for details.
+
+ If you own a Mustek (or Trust) scanner other than the ones listed above
+ that works with this backend, please let me know this by sending the
+ scanner's exact model name and the USB vendor and device ids (e.g. from
+ /proc/bus/usb/devices or syslog) to me.
+
+
+
+DEVICE NAMES
+ This backend expects device names of the form:
+
+ special
+
+ Where special is a path-name for the special device that corresponds to
+ a USB scanner. With Linux, such a device name could be /dev/usb/scan-
+ ner0 or /dev/usbscanner1, for example.
+
+ For FreeBSD use /dev/uscanner0.
+
+
+
+CONFIGURATION
+ The contents of the mustek_usb.conf file is a list of options and
+ device names that correspond to Mustek USB scanners. Empty lines and
+ lines starting with a hash mark (#) are ignored. If a device name is
+ placed in mustek_usb.conf, it must be followed by a line containing the
+ keyword option and an option specifying the scanner type. The following
+ options can be used: 600cu, 1200cu, 1200cu_plus, 1200ub. For the Trust
+ Compact Scan USB 19200 use `option 1200ub'.
+
+ Instead of using the device name, the scanner can be autodetected by
+ usb vendor_id product_id statements which are already included into
+ mustek_usb.conf. This is only supported with Linux 2.4.8 and higher
+ and all systems that support libsub. "vendor_id" and "product_id" are
+ hexadecimal numbers that identfy the scanner. If this doesn't work, a
+ device name and the option specifying the scanner type must be placed
+ in mustek_usb.conf as described above.
+
+ The global option max_block_size can be used to limit the amount of
+ data acquired in one turn from the USB system. It may be worth trying,
+ if USB errors occur.
+
+ A sample configuration file is shown below:
+
+ # Comment
+ option max_block_size 1024
+ usb 0x055f 0x0001
+ /dev/usb/scanner0
+ option 600cu
+
+ The first line is ignored. The second line sets the buffer size to a
+ maximum of 1024 bytes. The third line tries to autodetect a scanner
+ with vendor id 0x055f and product id 0x0001 (Mustek 1200 CU). The
+ fourth line tells the backend to attach to /dev/usb/scanner0 and the
+ fifth line specifies that /dev/usb/scanner0 is a Mustek 600 CU.
+
+
+
+FILES
+ /usr/local/etc/sane.d/mustek_usb.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-mustek_usb.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-mustek_usb.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_MUSTEK_USB
+ If the library was compiled with debug support enabled, this
+ environment variable controls the debug level for this backend.
+ Higher debug levels increase the verbosity of the output.
+
+ Value Descsription
+ 0 no output
+ 1 print fatal errors
+ 2 print important messages
+ 3 print non-fatal errors and less important messages
+ 4 print all but debugging messages
+ 5 print high level debugging messages
+ 6 print medium level debugging messages
+ 7 print low level debugging messages
+
+ Example:
+ export SANE_DEBUG_MUSTEK_USB=4
+
+
+
+SEE ALSO
+ sane(7), sane-usb(5), sane-mustek(5), sane-mustek_pp(5), sane-plus-
+ tek(5), sane-gt68xx(5), sane-ma1509(5)
+ /usr/local/doc/sane-1.0.12-cvs/mustek_usb/mustek_usb.CHANGES,
+ /usr/local/doc/sane-1.0.12-cvs/mustek_usb/mustek_usb.TODO
+ http://www.meier-geinitz.de/sane/mustek_usb-backend/
+
+
+
+AUTHOR
+ Henning Meier-Geinitz <henning@meier-geinitz.de>
+ This backend is based on the Mustek 1200ub backend from Mustek, main-
+ tained by Tom Wang.
+
+
+
+BUGS
+ These devices have a hardware bug: Once data is written to them, they
+ can't be resetted (toggle = DATA0). That means, any operation that
+ tries to reset the device will result in running into timeouts.
+
+ That means that this backend will fail when it is loaded the second
+ time in some configurations: E.g. using libusb, (Free|Open|Net)BSD or
+ with Linux if you unload and reload the scanner module. The only choice
+ is to replug the scanner in this case.
+
+ More detailed bug information is available at the Mustek backend home-
+ page http://www.meier-geinitz.de/sane/mustek_usb-backend/.
+
+sane-backends 1.0.12-cvs 09 Jan 2003 sane-mustek_usb(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-nec.5.html b/man/sane-nec.5.html
new file mode 100644
index 00000000..7d127e9d
--- /dev/null
+++ b/man/sane-nec.5.html
@@ -0,0 +1,78 @@
+
+
+sane-nec.5
+
+
+sane-nec.5
+
+
+
+sane-nec(5) SANE Scanner Access Now Easy sane-nec(5)
+
+
+
+NAME
+ sane-nec - SANE backend for NEC scanners
+
+
+
+DESCRIPTION
+ The sane-nec library implements a SANE (Scanner Access Now Easy) back-
+ end that provides access to NEC SCSI scanners. This backend should be
+ considered alpha-quality software! In the current state it is known to
+ work with PC-IN500/4C scanners. Another MultiReader scanner series is
+ not supported. PC-IN 500/4C and MultiReader scanner are only sold in
+ Japan.(except Multi Reader PetiScan.)
+
+ For other scanners, it may or may not work.
+
+ The backend has the following known problems:
+ - ColorLineart mode is not supported.
+ - device name is fixed to /dev/scanner
+
+ At present, the following scanners are known to work with this backend.
+ Vendor Product id
+ ------ -----------
+ NEC PC-IN500/4C
+
+
+
+FILES
+ /usr/local/etc/sane.d/nec.conf
+ The backend configuration file.
+
+ /usr/local/lib/sane/libsane-nec.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-nec.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_DEBUG_NEC
+ 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.
+
+
+
+SEE ALSO
+ sane(7), sane-scsi(5)
+
+
+
+AUTHORS
+ Kazuya Fukuda
+
+sane-backends 1.0.12-cvs 17 Feb 2000 sane-nec(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-net.5.html b/man/sane-net.5.html
new file mode 100644
index 00000000..3b6ca5a7
--- /dev/null
+++ b/man/sane-net.5.html
@@ -0,0 +1,142 @@
+
+
+sane-net.5
+
+
+sane-net.5
+
+
+
+sane-net(5) SANE Scanner Access Now Easy sane-net(5)
+
+
+
+NAME
+ sane-net - SANE network backend
+
+
+
+DESCRIPTION
+ The sane-net library implements a SANE (Scanner Access Now Easy) back-
+ end that provides access to image acquisition devices through a network
+ connection. This makes it possible to control devices attached to a
+ remote host and also provides a means to grant users access to pro-
+ tected resources.
+
+
+
+DEVICE NAMES
+ This backend expects device names of the form:
+
+ host:device
+
+ Where host is the name (or IP address) of the (remote-) host and device
+ is the name of the device on this host that should be addressed. If
+ the device name does not contain a colon (:), then the entire string is
+ treated as the device string for the default host. The default host is
+ the host listed last in the configuration file (see below).
+
+ An IPv6 address can be specified enclosed in square brackets:
+
+ [::1]:device
+
+
+
+CONFIGURATION
+ The contents of the net.conf file is a list of host names (or IP
+ addresses) that should be contacted for scan requests. Empty lines and
+ lines starting with a hash mark (#) are ignored. Note that IPv6
+ addresses in this file do not need to be enclosed in square brackets.
+ A sample configuration file is shown below:
+
+ scan-server.somedomain.firm
+ 192.168.0.1
+ # this is a comment
+ localhost
+ ::1
+
+ The above list of hosts can be extended at run-time using environment
+ variable SANE_NET_HOSTS. This environment variable is a colon-sepa-
+ rated list of hostnames or IP addresses that should be contacted in
+ addition to the hosts mentioned in the configuration file. For exam-
+ ple, a user could set the environment variable to the string:
+
+ new.scanner.com:[::1]:192.168.0.2:scanner.univ.edu
+
+ To request that hosts new.scanner.com , [::1] , 192.168.0.2 and scan-
+ ner.univ.edu are contacted in addition to the hosts listed above.
+
+ For this backend to function properly, it is also necessary to define
+ the sane service in /etc/services. The sane service should be defined
+ using a line of the following form:
+
+ sane 6566/tcp # SANE network scanner daemon
+
+
+
+FILES
+ /usr/local/etc/sane.d/net.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-net.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-net.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_NET_HOSTS
+ A colon-separated list of host names or IP addresses to be con-
+ tacted by this backend.
+
+ SANE_DEBUG_NET
+ 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.
+
+
+
+BUGS
+ If saned has timed out, the net backend may loop with authorization
+ requests.
+
+
+
+SEE ALSO
+ sane(7), saned(1), sane-dll(5), scanimage(1)
+
+ http://www.penguin-breeder.org/?page=sane-net
+
+
+
+AUTHOR
+ David Mosberger and Andreas Beck
+
+sane-backends 1.0.12-cvs 8 Oct 2002 sane-net(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-pie.5.html b/man/sane-pie.5.html
new file mode 100644
index 00000000..7dfcdcfc
--- /dev/null
+++ b/man/sane-pie.5.html
@@ -0,0 +1,77 @@
+
+
+sane-pie.5
+
+
+sane-pie.5
+
+
+
+sane-pie(5) SANE Scanner Access Now Easy sane-pie(5)
+
+
+
+NAME
+ sane-pie - SANE backend for PIE, Devcom and AdLib SCSI flatbed scanners
+
+
+
+DESCRIPTION
+ The sane-pie library implements a SANE (Scanner Access Now Easy) back-
+ end that provides access to PIE, Devcom and AdLib SCSI flatbed scan-
+ ners.
+ At present, the following scanners should work with this backend:
+
+ Model: Status
+ ---------------------- ------
+ Devcom 9636PRO OK
+ Devcom 9636S Untested
+ Devcom 9630S Untested
+ ScanAce 1236S Untested
+ ScanAce 1230S Untested
+ ScanAce II Untested
+ ScanAce III OK
+ ScanAce Plus Untested
+ ScanAce II Plus Untested
+ ScanAce III Plus Untested
+ ScanAce V Untested
+ ScanAce ScanMedia Untested
+ ScanAce ScanMedia II Untested
+ ScanAce 630S Untested
+ ScanAce 636S Untested
+ JetScan 630 OK
+ JetScan 636PRO Untested
+
+
+
+FILES
+ /usr/local/etc/sane.d/pie.conf
+ The backend configuration file
+
+ /usr/local/lib/sane/libsane-pie.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-pie.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+SEE ALSO
+ sane(7)
+
+
+
+CONTACT AND BUG-REPORTS
+ Please send any information and bug-reports to:
+ Simon Munton <simon@munton.demon.co.uk>
+
+sane-backends 1.0.12-cvs 7 Sept 2000 sane-pie(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-pint.5.html b/man/sane-pint.5.html
new file mode 100644
index 00000000..c1f5ccfc
--- /dev/null
+++ b/man/sane-pint.5.html
@@ -0,0 +1,146 @@
+
+
+sane-pint.5
+
+
+sane-pint.5
+
+
+
+sane-pint(5) SANE Scanner Access Now Easy sane-pint(5)
+
+
+
+NAME
+ sane-pint - SANE backend for scanners that use the PINT device driver
+
+
+
+DESCRIPTION
+ The sane-pint library implements a SANE (Scanner Access Now Easy) back-
+ end that provides generic access to hand-held and flatbed scanners
+ using the PINT (PINT Is Not Twain) device driver. The PINT driver is
+ being actively developed on the OpenBSD platform, and has been ported
+ to a few other *nix-like operating systems.
+
+ PINT is designed to provide an ioctl(2) interface to many different
+ scanner types. However, this backend has only been tested with flatbed
+ single-pass scanners, and more work will probably be required to get it
+ to use other scanner types successfully.
+
+ If have successfully used the PINT driver with your scanner, but it
+ does not work using this SANE backend, please let us know. To do this,
+ send a mail with the relevant information for your scanner to
+ sane-devel@mostang.com. Have a look at
+ http://www.mostang.com/sane/mail.html concerning subscription to sane-
+ devel.
+
+
+
+DEVICE NAMES
+ This backend expects device names of the form:
+
+ special
+
+ Where special is the UNIX path-name for the special device that corre-
+ sponds to the scanner. The special device name must be a PINT device
+ or a symlink to such a device. For example, under NetBSD or OpenBSD,
+ such a device name could be /dev/ss0 or /dev/scan0.
+
+
+
+CONFIGURATION
+ The contents of the pint.conf. file is a list of device names that
+ correspond to PINT scanners. Empty lines and lines starting with a
+ hash mark (#) are ignored. A sample configuration file is shown below:
+
+ /dev/scanner
+ # this is a comment
+ /dev/ss1
+
+
+
+FILES
+ /usr/local/etc/sane.d/pint.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-pint.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-pint.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_PINT
+ 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.
+
+
+
+SEE ALSO
+ sane(7)
+
+
+
+AUTHOR
+ Gordon Matzigkeit, adapted from existing backends written by David Mos-
+ berger.
+
+
+
+BUGS
+ There are minor roundoff errors when adjusting the ranges, since PINT
+ uses units of 1/1200 of an inch, and SANE normally uses millimeters.
+ Symptoms of these errors are skewed images. This should really be
+ fixed (no pun intended) as soon as possible, but I just don't know/care
+ enough about fixed-point representation and roundoff errors to do this
+ correctly. Workaround: use inches as the scanning unit, and everything
+ usually works fine.
+
+ The PINT 0.5e interface does not provide a way to determine valid
+ ranges for DPI, modes, and scan sizes. So, the SANE backend queries
+ the PINT device, and dynamically discovers valid ranges by doing a
+ binary search. This means that the driver takes longer to initialize
+ than seems necessary.
+
+ Resetting the scanner does not seem to work (at least not on my HP
+ ScanJet 4p). For that reason, the driver sends a SCIOCRESTART, then
+ gobbles up any remaining input until it hits EOF.
+
+ Not all of the scanners have been identified (i.e. whether they are
+ flatbed or handheld).
+
+ X and Y resolutions are assumed to be the same.
+
+ No testing has been done on three-pass or handheld scanners, or with
+ Automatic Document Feeder support.
+
+sane-backends 1.0.12-cvs 13 May 1998 sane-pint(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-plustek.5.html b/man/sane-plustek.5.html
new file mode 100644
index 00000000..468bfa3f
--- /dev/null
+++ b/man/sane-plustek.5.html
@@ -0,0 +1,501 @@
+
+
+sane-plustek.5
+
+
+sane-plustek.5
+
+
+
+sane-plustek(5) SANE Scanner Access Now Easy sane-plustek(5)
+
+
+
+NAME
+ sane-plustek - SANE backend for Plustek parallel port and LM983[1/2/3]
+ based USB flatbed scanners
+
+
+
+DESCRIPTION
+ The sane-plustek 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
+ http://www.gjaeger.de/scanner/plustek.html
+
+ !!!Please note that you need the kernel module only for parallel port
+ scanners!!!
+
+
+
+PARALLEL PORT SUPPORT
+ At present, the following scanners should work with this backend and
+ the corresponding kernel module:
+
+ PLUSTEK SCANNERS
+
+ 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
+
+ PRIMAX SCANNERS
+
+ 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
+
+ GENIUS SCANNERS
+
+ 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
+
+ ARIES SCANNERS
+
+ 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
+
+ BrightScan SCANNERS
+
+ 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
+
+
+
+USB SUPPORT
+ 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 NOT 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
+
+
+
+OTHER PLUSTEK SCANNERS
+ The SCSI scanner OpticPro 19200S is a rebadged Artec AM12S scanner and
+ is supported by the Artec 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
+
+
+
+DEVICE NAMES
+ This backend expects a default device called:
+
+ /dev/pt_drv
+
+ 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:
+ http://www.gjaeger.de/scanner/plustek.html
+ 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
+
+ /usr/local/etc/sane.d/plustek.conf
+
+ See the plustek.conf file for examples.
+
+
+
+CONFIGURATION
+ The configuration of this backend can be divided into two sections:
+
+ CONFIGURATION - parallel port scanner
+
+ CONFIGURATION - USB scanner
+
+ Please make sure, that the configuration matches the real world, namely
+ your configuration. And note again, .I pt_drv is only needed
+
+
+
+CONFIGURATION - PARALLEL PORT SCANNER
+ Beside the kernel-module options, which are described below, you need
+ to enable the parallel port device in the configuration file
+
+ /usr/local/etc/sane.d/plustek.conf
+
+ For a proper setup, you will need at least two entries:
+
+ [parport]
+
+ device /dev/pt_drv
+
+ parport tells the backend, that the following devicename (here
+ /dev/pt_drv ) 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
+ /etc/conf.modules
+
+ The Options:
+ lampoff=lll
+ The value lll tells the driver, after how many seconds to
+ switch-off the lamp(s). The default value is 180. 0 will dis-
+ able this feature.
+ HINT: Do not use a value that is too small, because often
+ switching on/off the lamps will reduce their lifetime.
+
+ port=ppp
+ ppp specifies the port base address, where the scanner is con-
+ nected to. The default value is 0x378 which normaly is standard.
+
+ warmup=www
+ www 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
+ e specifies the behaviour when unloading the driver, 1 -->
+ switch lamps off, 0 --> do not change lamp status
+
+ slowIO=s
+ s specifies which I/O functions the driver should use, 1 --> use
+ delayed functions, 0 --> use the non-delayed ones
+
+ forceMode=fm
+ fm specifies port mode which should be used, 0 --> autodetec-
+ tion, 1 --> use SPP mode and 2 --> use EPP mode
+
+ mov=m
+ m =0 - default: no override
+ m =1 - OpticPro 9630PL override (works if OP9630
+ has been detected) forces legal size (14")
+ m =2 - Primax 4800Direct override (works if OP600
+ has been detected) swaps red/green color
+ m =3 - OpticPro 9636 override (works if OP9636 has
+ been detected) disables backends
+ transparency/negativ capabilities
+ m =4 - OpticPro 9636P override (works if OP9636 has
+ been detected) disables backends
+ transparency/negativ capabilities
+ m =5 - OpticPro A3I override (works if OP12000 has
+ been detected) enables A3 scanning
+ m =6 - OpticPro 4800P override (works if OP600
+ has been detected) swaps red/green color
+ m =7 - Primax 4800Direct 30bit override (works if OP4830
+ has been detected)
+
+ Sample entry for file /etc/modules.conf :
+ alias char-major-40 pt_drv
+ pre-install pt_drv modprobe -k parport
+ options pt_drv lampoff=180 warmup=15 port=0x378 lOffonEnd=0 mov=0
+ slowIO=0 forceMode=0
+
+ For multidevice support, simply add values separated by commas to the
+ different options
+ options pt_drv port=0x378,0x278 mov=0,4 slowIO=0,1 forceMode=0,1
+
+ Remember to call depmod after changing /etc/conf.modules.
+
+ PARALLEL PORT MODES
+
+ 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 not 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.
+
+
+
+CONFIGURATION - USB SCANNER
+ To use the USB device with this backend, you need at least two entries
+ in the configuration file
+ /usr/local/etc/sane.d/plustek.conf
+
+ [usb] vendor-id product-id
+
+ device /dev/usbscanner
+
+ usb tells the backend, that the following devicename (here
+ /dev/usbscanner ) 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 auto
+ then the next matching device is used.
+
+ The Options:
+
+ option warmup t
+ t specifies the warmup period in seconds
+
+ option lampOff t
+ t is the time in seconds for switching off the lamps in standby
+ mode
+
+ option lOffonEnd b
+ b specifies the behaviour when closing the backend, 1 --> switch
+ lamps off, 0 --> do not change lamp status
+
+ option invertNegatives b
+ b 0 --> do not invert the picture during negativ scans, 1 -->
+ invert picture
+
+ option skipCalibration b
+ b 0 --> perform calibration, 1 --> skip calibration (only non
+ Plustek devices)
+
+ option enableTPA b
+ b 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
+ x y By using this settings, the user can adjust the given image
+ positions. Please note, that there's no internal range checking
+ for this feature.
+
+ option posShadingY p
+ option tpaShadingY p
+ option negShadingY p
+ p overrides the internal shading position. The values are in
+ steps. Please note, that there's no internal range checking for
+ this feature.
+
+ option redGamma r
+ option greenGamma g
+ option blueGamma b
+ option grayGamma gr
+ r g b gr
+ 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
+ r g b 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.
+
+ Note:
+ You have to make sure, that the USB subsystem is loaded correctly and
+ the module scanner has been loaded too. To make this module recognize
+ your scanner, you might have to add the following line to your
+ /etc/modules.conf :
+ options scanner vendor=0x7b3 product=0x17
+
+ 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 cat
+ /proc/bus/usb/devices and look for the scanner.
+
+
+
+FILES
+ /usr/local/etc/sane.d/plustek.conf
+ The backend configuration file
+
+ /usr/local/lib/sane/libsane-plustek.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-plustek.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+ /lib/modules/<Kernel-Version>/misc/pt_drv.o
+ The Linux Kernelmodule.
+
+
+
+CONTACT AND BUG-REPORTS
+ Please send any information and bug-reports to:
+ Plustek Driver Mailing List <plustek@linuxhacker.org>
+ or directly to:
+ Gerhard Jaeger <gerhard@gjaeger.de>
+
+ Additional info and hints can be obtained from our
+ Mailing-List archive at:
+ http://www.linuxhacker.org/cgi-bin/ezmlm-cgi/3
+
+ or directly from the projects' homepage at:
+ http://www.gjaeger.de/scanner/plustek.html
+
+ To obtain debug messages from the backend, please set the environment-
+ variable SANE_DEBUG_PLUSTEK before calling your favorite scan-frontend
+ (i.e. xscanimage).
+ i.e.: export SANE_DEBUG_PLUSTEK=20 ; xscanimage
+
+ 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.
+
+
+
+KNOWN BUGS & RESTRICTIONS
+ * The Halftoning works, but the quality is poor
+ * Printers (especially HP models) will start to
+ print during scanning. This in fact is a problem
+ to other printers too, using bidirectional protocol
+ (see www.plustek.com (TAIWAN) page for further details)
+ * The driver does not support these manic scalings up
+ to 16 times the physical resolution. The only scaling
+ is done on resolutions between the physical resolution
+ of the CDD-sensor and the stepper motor i.e. you have a
+ 600x1200 dpi scanner and you are scanning using 800dpi,
+ so scaling is necesary, because the sensor only delivers
+ 600dpi but the motor is capable to perform 800dpi steps.
+ * On some devices, the pictures seems to be bluished
+
+ ASIC 98001 based models:
+ * The 300dpi transparency and negative mode does not work
+ correctly.
+ * There is currently no way to distinguish a model with
+ and without transpareny unit.
+ * The scanned images seem to be too dark (P9636T)
+
+ ASIC 96003/1 based models:
+ * 30bit mode is currently not supported.
+ * On low-end systems and under heavy system load, the
+ driver will loosing data, this might causes the sensor
+ to hit the scan-bed and/or the picture is corrupted.
+ * The scanspeed on 600x1200 dpi models is slow.
+ * The scanquality of the A3I is poor
+
+ USB models:
+ * Plusteks' model policy is somewhat inconsistent. This
+ means, they sell technical different devices under the
+ same product name. Therefore it is possible that some
+ devices like the UT12 or U12 won't work - please check
+ the model list above and compare the product-id to
+ the one your device has.
+ * Negative scanning quality is poor.
+
+sane-backends 1.0.12-cvs 17 September 2003 sane-plustek(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-plustek_pp.5.html b/man/sane-plustek_pp.5.html
new file mode 100644
index 00000000..99870126
--- /dev/null
+++ b/man/sane-plustek_pp.5.html
@@ -0,0 +1,501 @@
+
+
+sane-plustek_pp.5
+
+
+sane-plustek_pp.5
+
+
+
+sane-plustek(5) SANE Scanner Access Now Easy sane-plustek(5)
+
+
+
+NAME
+ sane-plustek - SANE backend for Plustek parallel port and LM983[1/2/3]
+ based USB flatbed scanners
+
+
+
+DESCRIPTION
+ The sane-plustek 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
+ http://www.gjaeger.de/scanner/plustek.html
+
+ !!!Please note that you need the kernel module only for parallel port
+ scanners!!!
+
+
+
+PARALLEL PORT SUPPORT
+ At present, the following scanners should work with this backend and
+ the corresponding kernel module:
+
+ PLUSTEK SCANNERS
+
+ 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
+
+ PRIMAX SCANNERS
+
+ 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
+
+ GENIUS SCANNERS
+
+ 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
+
+ ARIES SCANNERS
+
+ 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
+
+ BrightScan SCANNERS
+
+ 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
+
+
+
+USB SUPPORT
+ 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 NOT 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
+
+
+
+OTHER PLUSTEK SCANNERS
+ The SCSI scanner OpticPro 19200S is a rebadged Artec AM12S scanner and
+ is supported by the Artec 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
+
+
+
+DEVICE NAMES
+ This backend expects a default device called:
+
+ /dev/pt_drv
+
+ 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:
+ http://www.gjaeger.de/scanner/plustek.html
+ 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
+
+ /usr/local/etc/sane.d/plustek.conf
+
+ See the plustek.conf file for examples.
+
+
+
+CONFIGURATION
+ The configuration of this backend can be divided into two sections:
+
+ CONFIGURATION - parallel port scanner
+
+ CONFIGURATION - USB scanner
+
+ Please make sure, that the configuration matches the real world, namely
+ your configuration. And note again, .I pt_drv is only needed
+
+
+
+CONFIGURATION - PARALLEL PORT SCANNER
+ Beside the kernel-module options, which are described below, you need
+ to enable the parallel port device in the configuration file
+
+ /usr/local/etc/sane.d/plustek.conf
+
+ For a proper setup, you will need at least two entries:
+
+ [parport]
+
+ device /dev/pt_drv
+
+ parport tells the backend, that the following devicename (here
+ /dev/pt_drv ) 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
+ /etc/conf.modules
+
+ The Options:
+ lampoff=lll
+ The value lll tells the driver, after how many seconds to
+ switch-off the lamp(s). The default value is 180. 0 will dis-
+ able this feature.
+ HINT: Do not use a value that is too small, because often
+ switching on/off the lamps will reduce their lifetime.
+
+ port=ppp
+ ppp specifies the port base address, where the scanner is con-
+ nected to. The default value is 0x378 which normaly is standard.
+
+ warmup=www
+ www 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
+ e specifies the behaviour when unloading the driver, 1 -->
+ switch lamps off, 0 --> do not change lamp status
+
+ slowIO=s
+ s specifies which I/O functions the driver should use, 1 --> use
+ delayed functions, 0 --> use the non-delayed ones
+
+ forceMode=fm
+ fm specifies port mode which should be used, 0 --> autodetec-
+ tion, 1 --> use SPP mode and 2 --> use EPP mode
+
+ mov=m
+ m =0 - default: no override
+ m =1 - OpticPro 9630PL override (works if OP9630
+ has been detected) forces legal size (14")
+ m =2 - Primax 4800Direct override (works if OP600
+ has been detected) swaps red/green color
+ m =3 - OpticPro 9636 override (works if OP9636 has
+ been detected) disables backends
+ transparency/negativ capabilities
+ m =4 - OpticPro 9636P override (works if OP9636 has
+ been detected) disables backends
+ transparency/negativ capabilities
+ m =5 - OpticPro A3I override (works if OP12000 has
+ been detected) enables A3 scanning
+ m =6 - OpticPro 4800P override (works if OP600
+ has been detected) swaps red/green color
+ m =7 - Primax 4800Direct 30bit override (works if OP4830
+ has been detected)
+
+ Sample entry for file /etc/modules.conf :
+ alias char-major-40 pt_drv
+ pre-install pt_drv modprobe -k parport
+ options pt_drv lampoff=180 warmup=15 port=0x378 lOffonEnd=0 mov=0
+ slowIO=0 forceMode=0
+
+ For multidevice support, simply add values separated by commas to the
+ different options
+ options pt_drv port=0x378,0x278 mov=0,4 slowIO=0,1 forceMode=0,1
+
+ Remember to call depmod after changing /etc/conf.modules.
+
+ PARALLEL PORT MODES
+
+ 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 not 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.
+
+
+
+CONFIGURATION - USB SCANNER
+ To use the USB device with this backend, you need at least two entries
+ in the configuration file
+ /usr/local/etc/sane.d/plustek.conf
+
+ [usb] vendor-id product-id
+
+ device /dev/usbscanner
+
+ usb tells the backend, that the following devicename (here
+ /dev/usbscanner ) 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 auto
+ then the next matching device is used.
+
+ The Options:
+
+ option warmup t
+ t specifies the warmup period in seconds
+
+ option lampOff t
+ t is the time in seconds for switching off the lamps in standby
+ mode
+
+ option lOffonEnd b
+ b specifies the behaviour when closing the backend, 1 --> switch
+ lamps off, 0 --> do not change lamp status
+
+ option invertNegatives b
+ b 0 --> do not invert the picture during negativ scans, 1 -->
+ invert picture
+
+ option skipCalibration b
+ b 0 --> perform calibration, 1 --> skip calibration (only non
+ Plustek devices)
+
+ option enableTPA b
+ b 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
+ x y By using this settings, the user can adjust the given image
+ positions. Please note, that there's no internal range checking
+ for this feature.
+
+ option posShadingY p
+ option tpaShadingY p
+ option negShadingY p
+ p overrides the internal shading position. The values are in
+ steps. Please note, that there's no internal range checking for
+ this feature.
+
+ option redGamma r
+ option greenGamma g
+ option blueGamma b
+ option grayGamma gr
+ r g b gr
+ 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
+ r g b 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.
+
+ Note:
+ You have to make sure, that the USB subsystem is loaded correctly and
+ the module scanner has been loaded too. To make this module recognize
+ your scanner, you might have to add the following line to your
+ /etc/modules.conf :
+ options scanner vendor=0x7b3 product=0x17
+
+ 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 cat
+ /proc/bus/usb/devices and look for the scanner.
+
+
+
+FILES
+ /usr/local/etc/sane.d/plustek.conf
+ The backend configuration file
+
+ /usr/local/lib/sane/libsane-plustek.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-plustek.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+ /lib/modules/<Kernel-Version>/misc/pt_drv.o
+ The Linux Kernelmodule.
+
+
+
+CONTACT AND BUG-REPORTS
+ Please send any information and bug-reports to:
+ Plustek Driver Mailing List <plustek@linuxhacker.org>
+ or directly to:
+ Gerhard Jaeger <gerhard@gjaeger.de>
+
+ Additional info and hints can be obtained from our
+ Mailing-List archive at:
+ http://www.linuxhacker.org/cgi-bin/ezmlm-cgi/3
+
+ or directly from the projects' homepage at:
+ http://www.gjaeger.de/scanner/plustek.html
+
+ To obtain debug messages from the backend, please set the environment-
+ variable SANE_DEBUG_PLUSTEK before calling your favorite scan-frontend
+ (i.e. xscanimage).
+ i.e.: export SANE_DEBUG_PLUSTEK=20 ; xscanimage
+
+ 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.
+
+
+
+KNOWN BUGS & RESTRICTIONS
+ * The Halftoning works, but the quality is poor
+ * Printers (especially HP models) will start to
+ print during scanning. This in fact is a problem
+ to other printers too, using bidirectional protocol
+ (see www.plustek.com (TAIWAN) page for further details)
+ * The driver does not support these manic scalings up
+ to 16 times the physical resolution. The only scaling
+ is done on resolutions between the physical resolution
+ of the CDD-sensor and the stepper motor i.e. you have a
+ 600x1200 dpi scanner and you are scanning using 800dpi,
+ so scaling is necesary, because the sensor only delivers
+ 600dpi but the motor is capable to perform 800dpi steps.
+ * On some devices, the pictures seems to be bluished
+
+ ASIC 98001 based models:
+ * The 300dpi transparency and negative mode does not work
+ correctly.
+ * There is currently no way to distinguish a model with
+ and without transpareny unit.
+ * The scanned images seem to be too dark (P9636T)
+
+ ASIC 96003/1 based models:
+ * 30bit mode is currently not supported.
+ * On low-end systems and under heavy system load, the
+ driver will loosing data, this might causes the sensor
+ to hit the scan-bed and/or the picture is corrupted.
+ * The scanspeed on 600x1200 dpi models is slow.
+ * The scanquality of the A3I is poor
+
+ USB models:
+ * Plusteks' model policy is somewhat inconsistent. This
+ means, they sell technical different devices under the
+ same product name. Therefore it is possible that some
+ devices like the UT12 or U12 won't work - please check
+ the model list above and compare the product-id to
+ the one your device has.
+ * Negative scanning quality is poor.
+
+sane-backends 1.0.12-cvs 17 September 2003 sane-plustek(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-pnm.5.html b/man/sane-pnm.5.html
new file mode 100644
index 00000000..f450de42
--- /dev/null
+++ b/man/sane-pnm.5.html
@@ -0,0 +1,85 @@
+
+
+sane-pnm.5
+
+
+sane-pnm.5
+
+
+
+sane-pnm(5) SANE Scanner Access Now Easy sane-pnm(5)
+
+
+
+NAME
+ sane-pnm - SANE PNM image reader pseudo-backend
+
+
+
+DESCRIPTION
+ The sane-pnm library implements a SANE (Scanner Access Now Easy) back-
+ end that provides access to PNM (Portable aNyMap files, which covers
+ PBM bitmap files, PGM grayscale files, and PPM pixmap files). The pur-
+ pose of this backend is primarly to aid in debugging of SANE frontends.
+ It also serves as an illustrative example of a minimal SANE backend.
+
+
+
+DEVICE NAMES
+ This backend provides two devices called 0 and 1.
+
+
+
+CONFIGURATION
+ No configuration required.
+
+
+
+FILES
+ /usr/local/lib/sane/libsane-pnm.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-pnm.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_DEBUG_PNM
+ 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.
+
+
+
+BUGS
+ If the pnm backend is installed and saned is used to allow users on
+ remote computers to scan on the local machine, pnm files can be read by
+ the remote user. This is limited to the files saned can access (usually
+ it's running as user "sane"). All pnm files can be read if saned runs
+ as root which isn't recommended anyway. The pnm backend is disabled by
+ default. If you want to use it, enable it with configure (see configure
+ --help for details). Be sure that only trusted users can access the pnm
+ backend over saned.
+
+
+
+AUTHOR
+ Andreas Beck, Gordon Matzigkeit, and David Mosberger
+
+
+
+SEE ALSO
+ sane(7)
+
+sane-backends 1.0.12-cvs 22 April 2001 sane-pnm(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-qcam.5.html b/man/sane-qcam.5.html
new file mode 100644
index 00000000..0e8fd489
--- /dev/null
+++ b/man/sane-qcam.5.html
@@ -0,0 +1,120 @@
+
+
+sane-qcam.5
+
+
+sane-qcam.5
+
+
+
+sane-qcam(5) SANE Scanner Access Now Easy sane-qcam(5)
+
+
+
+NAME
+ sane-qcam - SANE backend for Connectix QuickCam cameras
+
+
+
+DESCRIPTION
+ The sane-qcam library implements a SANE (Scanner Access Now Easy) back-
+ end that provides access Connectix QuickCam cameras.
+
+
+
+DEVICE NAMES
+ This backend expects device names of the form:
+
+ port
+
+ Where port is the I/O port address at which the device resides. This
+ address is normally specified in hexadecimal using C syntax (e.g.,
+ 0x37b) and may be prefixed with the letter "u" (e.g., u0x37b) to force
+ the backend to access the camera in uni-directional mode.
+
+
+
+CONFIGURATION
+ The contents of the qcam.conf file is a list port addresses that may be
+ connected to a Connectix QuickCam. Empty lines and everything starting
+ from a hash mark (#) up to the end of a line are ignored. A sample
+ configuration file is shown below:
+
+ 0x37b # /dev/lp0
+ 0x378 # /dev/lp1
+ u0x278 # /dev/lp2 forced in uni-directional mode
+ 0x3bc # /dev/lp0 (alternate address)
+
+ In general, it is safest to list only the port addresses that really
+ correspond to a QuickCam. For example, if one of the listed addresses
+ actually connect to a printer, then starting up this backend will cause
+ the printer to perform a device reset (which is generally undesirable).
+
+
+
+FILES
+ /usr/local/etc/sane.d/qcam.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-qcam.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-qcam.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_QCAM
+ 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.
+
+
+
+AUTHOR
+ David Mosberger
+
+
+
+BUGS
+ Support is currently limited to the color version of the QuickCam. The
+ black-and-white camera is starting to work too, but I don't believe it
+ works in all cases yet. Reportedly, acquiring images of certain sizes
+ work fine, but others result in shifted images (sounds like a problem
+ due to byte-padding).
+
+ The program needs root-priviledges since it needs to be able to access
+ the camera's I/O ports.
+
+
+
+SEE ALSO
+ sane(7)
+
+sane-backends 1.0.12-cvs 25 October 1997 sane-qcam(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-ricoh.5.html b/man/sane-ricoh.5.html
new file mode 100644
index 00000000..6fc321ba
--- /dev/null
+++ b/man/sane-ricoh.5.html
@@ -0,0 +1,96 @@
+
+
+sane-ricoh.5
+
+
+sane-ricoh.5
+
+
+
+sane-ricoh(5) SANE Scanner Access Now Easy sane-ricoh(5)
+
+
+
+NAME
+ sane-ricoh - SANE backend for Ricoh flatbed scanners
+
+
+
+DESCRIPTION
+ The sane-ricoh library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to the following Ricoh flatbed scanners:
+
+ IS50
+ IS60
+
+
+
+DEVICE NAMES
+ This backend expects device names of the form:
+
+ special
+
+ Where special is the path-name for the special device that corresponds
+ to a SCSI scanner. The special device name must be a generic SCSI
+ device or a symlink to such a device. The program sane-find-scanner
+ helps to find out the correct device. Under Linux, such a device name
+ could be /dev/sga or /dev/sge, for example. See sane-scsi(5) for
+ details.
+
+
+
+FILES
+ /usr/local/etc/sane.d/ricoh.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-ricoh.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-ricoh.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_RICOH
+ If the library was compiled with debug support enabled, this
+ environment variable controls the debug level for this backend.
+ Higher debug levels increase the verbosity of the output.
+
+ Example: export SANE_DEBUG_RICOH=4
+
+
+
+SEE ALSO
+ sane(7), sane-scsi(5)
+
+
+
+AUTHOR
+ Feico W. Dillema
+
+sane-backends 1.0.12-cvs 24 Jun 2000 sane-ricoh(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-s9036.5.html b/man/sane-s9036.5.html
new file mode 100644
index 00000000..41f3e600
--- /dev/null
+++ b/man/sane-s9036.5.html
@@ -0,0 +1,94 @@
+
+
+sane-s9036.5
+
+
+sane-s9036.5
+
+
+
+sane-s9036(5) SANE Scanner Access Now Easy sane-s9036(5)
+
+
+
+NAME
+ sane-s9036 - SANE backend for Siemens 9036 flatbed scanners
+
+
+
+DESCRIPTION
+ The sane-s9036 library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to Siemens 9036 flatbed scanners.
+
+
+
+DEVICE NAMES
+ This backend expects device names of the form:
+
+ special
+
+ Where special is the path-name for the special device that corresponds
+ to a SCSI scanner. The special device name must be a generic SCSI
+ device or a symlink to such a device. The program sane-find-scanner
+ helps to find out the correct device. Under Linux, such a device name
+ could be /dev/sga or /dev/sge, for example. See sane-scsi(5) for
+ details.
+
+
+
+FILES
+ /usr/local/etc/sane.d/s9036.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-s9036.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-s9036.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_S9036
+ If the library was compiled with debug support enabled, this
+ environment variable controls the debug level for this backend.
+ Higher debug levels increase the verbosity of the output.
+
+ Example: export SANE_DEBUG_S9036=4
+
+
+
+SEE ALSO
+ sane(7), sane-scsi(5)
+
+
+
+AUTHOR
+ Ingo Schneider
+
+
+sane-backends 1.0.12-cvs 24 Jun 2000 sane-s9036(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-sceptre.5.html b/man/sane-sceptre.5.html
new file mode 100644
index 00000000..7d136e59
--- /dev/null
+++ b/man/sane-sceptre.5.html
@@ -0,0 +1,158 @@
+
+
+sane-sceptre.5
+
+
+sane-sceptre.5
+
+
+
+sane-sceptre(5) SANE Scanner Access Now Easy sane-sceptre(5)
+
+
+
+NAME
+ sane-sceptre - SANE backend for SCEPTRE scanners
+
+
+
+DESCRIPTION
+ The sane-sceptre library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to Sceptre flatbed scanners. This backend
+ should be considered beta-quality software! Please report any strange
+ behavior to the maintainer of the backend or to the SANE mailing list.
+
+ At present, only one scanner is known to work with this backend:
+
+ Model Connection Type
+ --------------------------- -------------------
+ Sceptre VividScan S1200 SCSI
+
+ The make of this scanner is KINPO, so other scanners from that manufac-
+ turer may also work (eg. the S600).
+
+
+
+OPTIONS
+ The options the backend supports can either be selected through command
+ line options to programs like scanimage or through GUI elements in
+ xscanimage or xsane.
+
+ Valid command line options and their syntax can be listed by using
+ scanimage --help -d sceptre
+
+ Scan Mode
+
+ --mode selects the basic mode of operation of the scanner valid choices
+ are Lineart, Halftone, Gray and Color. The Lineart and Haltone
+ mode are black and white only (1 bit). Gray will produce 256
+ levels of gray (8 bits). Color will produce a 24 bits color
+ image. The scanner suports 30 bits internally but it only
+ exports 24.
+
+ --resolution
+ selects the resolution for a scan. The scanner can do several
+ resolutions between 50 and 1200.
+
+ --halftone-pattern
+ selects the pattern mode that is used in Halftone mode. Valid
+ options are 1, 2, 3 and 4.
+
+ --gamma-correction
+ controls the scanner internal gamma correction. Valid options
+ are "Default", "User defined", "High density printing" "Low den-
+ sity printing" and "High contrast printing".
+
+ --custom-gamma
+ (color mode only) allows the user to specify a gamma table (see
+ the next 3 parameters).
+
+ --red-gamma-table
+ (color mode only) can be used to download a user defined gamma
+ table for the red channel. The table must be 256 bytes long.
+
+ --green-gamma-table
+ (color mode only) can be used to download a user defined gamma
+ table for the green channel. The table must be 256 bytes long.
+
+ --blue-gamma-table
+ (color mode only) can be used to download a user defined gamma
+ table for the blue channel. The table must be 256 bytes long.
+
+ --threshold
+ sets the threshold for black and white pixels in lineart mode.
+ Possible values are from 0 (darker) to 255 (lighter).
+
+ --preview
+ requests a preview scan. The resolution used for that scan is 30
+ dpi and the scan area is the maximum allowed. The scan mode is
+ user selected. The default is "no".
+
+ The geometry options
+
+ -l -t -x -y
+ control the scan area: -l sets the top left x coordinate, -t the
+ top left y coordinate, -x selects the width and -y the height of
+ the scan area. All parameters are specified in milimeters by
+ default.
+
+
+
+CONFIGURATION FILE
+ The configuration file /usr/local/etc/sane.d/sceptre.conf supports only
+ one information: the device name to use (eg /dev/scanner).
+
+
+
+FILES
+ /usr/local/lib/sane/libsane-sceptre.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-sceptre.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_DEBUG_SCEPTRE
+ 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.
+
+
+
+LIMITATIONS
+ Resolutions
+ The windows TWAIN driver can be set to any resolution between 50
+ to 1200 (excluding software interpolation). This backend cannot.
+ Only a handful of resolution are available, although they should
+ be numerous enough.
+
+
+
+
+BUGS
+ None known.
+
+
+
+SEE ALSO
+ sane-scsi(5), scanimage(1), xscanimage(1), xsane(1), sane(7)
+
+
+
+AUTHOR
+ The package is actively maintained by Frank Zago.
+ http://fz.eryx.net/sane/#sceptre
+
+sane-backends 1.0.12-cvs April 21st, 2002 sane-sceptre(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-scsi.5.html b/man/sane-scsi.5.html
new file mode 100644
index 00000000..ab6980bb
--- /dev/null
+++ b/man/sane-scsi.5.html
@@ -0,0 +1,312 @@
+
+
+sane-scsi.5
+
+
+sane-scsi.5
+
+
+
+sane-scsi(5) SANE Scanner Access Now Easy sane-scsi(5)
+
+
+
+NAME
+ sane-scsi - SCSI adapter tips for scanners
+
+
+
+DESCRIPTION
+ This manual page contains various operating-system specific tips and
+ tricks on how to get scanners with a SCSI interface working.
+
+
+
+GENERAL INFO
+ For scanners with a SCSI interface, it may be necessary to edit the
+ appropriate backend configuration file before using SANE for the first
+ time. For most systems, the configuration file should list the name of
+ the generic SCSI device that the scanner is connected to (e.g., under
+ Linux, /dev/sg4 or /dev/sge is such a generic SCSI device). It is cus-
+ tomary to create a symlink from /dev/scanner to the generic SCSI device
+ that the scanner is connected to. In this case, the configuration file
+ simply lists the line /dev/scanner. For a detailed description of each
+ backend's configuration file, please refer to the relevant backend man-
+ ual page (e.g., sane-epson(5) for Epson scanners, sane-hp(5) for HP
+ scanners, etc.).
+
+ For some operating systems (e.g. Linux and OS/2), there is an alternate
+ way of specifying scanner devices. This alternate way allows to iden-
+ tify scanners by the SCSI vendor and model string and/or by the SCSI
+ device address (consisting of bus number, channel number, id, and logi-
+ cal unit number). The syntax for specifying a scanner in this way is:
+
+ scsi VENDOR MODEL TYPE BUS CHANNEL ID LUN
+
+ where VENDOR is the SCSI vendor string, MODEL is the SCSI model string,
+ TYPE is type SCSI device type string, BUS is the SCSI bus number (named
+ "host" in /proc/scsi/scsi), CHANNEL is the SCSI channel number, ID is
+ the SCSI id, and LUN is the logical unit number of the scanner device.
+ The first two fields are strings which must be enclosed in double-
+ quotes if they contain any whitespace. The remaining four fields are
+ non-negative integer numbers. The correct values for these fields can
+ be found by using operating system specific tools, e.g. for Linux by
+ looking at the output of the command "cat /proc/scsi/scsi". To sim-
+ plify configuration, a field's value can be replaced with an asterisk
+ symbol (``*''). An asterisk has the effect that any value is allowed
+ for that particular field. This can have the effect that a single
+ scsi-line matches multiple devices. When this happens, each matching
+ device will be probed by the backend one by one and registered if the
+ backend thinks it is a compatible device. For example, the line
+
+ scsi MUSTEK MFS-06000CX Scanner 0 00 03 00
+
+ would attach the Mustek SCSI scanner with the following /proc/scsi/scsi
+ entry:
+
+ Host: scsi0 Channel: 00 Id: 03 Lun: 00
+ Vendor: MUSTEK Model: MFS-06000CX Rev: 4.04
+ Type: Scanner ANSI SCSI revision: 0
+
+ Usually it's sufficient to use vendor and model strings only or even
+ only the vendor string. The following example
+
+ scsi MUSTEK * * * * * *
+
+ would have the effect that all SCSI devices in the system with a vendor
+ string of MUSTEK would be probed and recognized by the backend.
+
+ If the remainder of a scsi-string consists of asterisks only, the
+ asterisks can be omitted. For example, the following line is equiva-
+ lent to the one specified previously:
+
+ scsi MUSTEK
+
+ On some platforms (e.g., OpenStep), SANE device names take a special
+ form. This is explained below in the relevant platform-specific sec-
+ tion.
+
+ When using a SCSI scanner, ensure that the access permission for the
+ generic SCSI device is set appropriately. We recommend to add a group
+ "scanner" to /etc/group which contains all users that should have
+ access to the scanner. The permission of the device should then be set
+ to allow group read and write access. For example, if the scanner is
+ at generic SCSI device /dev/sg0, then the following two commands would
+ set the permission correctly:
+
+ $ chgrp scanner /dev/sg0
+ $ chmod 660 /dev/sg0
+
+ When your system uses the device filesystem (devfs), you have to edit
+ /etc/devfs/perms. There you should search the line
+
+ REGISTER ^sg[^/]* PERMISSIONS root.root 0600
+
+ and add a new line (eg. for changing permissions of sg4):
+
+ REGISTER ^sg4 PERMISSIONS root.scanner 0660
+
+
+
+FREEBSD INFO
+ Auto-configuration using the "scsi *" lines in the config files doesn't
+ seem to work. Set a link /dev/scanner to the appropriate /dev/uk
+ device.
+
+ Adaptec AHA1542CF
+ Reported to work fine under FreeBSD 2.2.2R with the aha
+ driver.
+
+ Adaptec 2940
+ Reported to work fine under FreeBSD 2.2.2.
+
+ Adaptec 1522
+ The scanner probes ok but any attempt to access it hangs
+ the entire system. It looks like something is disabling
+ interrupts and then not reenabling them, so it looks like
+ a bug in the FreeBSD aic driver.
+
+ Adaptec 1505
+ Works on FreeBSD 2.2.5R and 3.0 using the aic driver,
+ provided that Plug-and-Play support is disabled on the
+ card. If there are no uk devices, just do a ``sh MAKEDEV
+ uk0'' in the /dev directory. The scanner should then be
+ accessible as /dev/uk0 if it was probed during boot.
+
+ Tekram DC390
+ Reported to work fine under FreeBSD 2.2.2R with the amd
+ driver.
+
+
+
+LINUX INFO
+ First, make sure your kernel has SCSI generic support enabled. In
+ ``make xconfig'', this shows up under ``SCSI support->SCSI generic sup-
+ port''.
+
+ To keep scanning times to a minimum, it is strongly recommended to use
+ a large buffer size for the generic SCSI driver. From SG driver version
+ 2.0 on, the maximum buffer size can be changed at program run time, and
+ there is no restriction in size. This driver version is part of the
+ Linux kernels from version 2.2.7 on. If the new SG driver is available
+ some backends (e.g. sane-umax, sane-mustek, sane-sharp) automatically
+ request larger scsi buffers. If a backend does not automatically
+ request a larger scsi buffer, set the environment variable
+ SANE_SG_BUFFERSIZE to the desired buffer size in bytes. It is not rec-
+ ommended to use more than 1 MB, because for large values the probabil-
+ ity increases that the SG driver cannot allocate the necessary
+ buffer(s). For ISA cards, even 1 MB might be a too large value. For a
+ detailed discussion of memory issues of the SG driver, see
+ http://www.torque.net/sg.
+
+ For Linux kernels before version 2.2.7 the size of the buffer is only
+ 32KB. This works, but for many cheaper scanners this causes scanning
+ to be slower by about a factor of four than when using a size of 127KB.
+ Linux defines the size of this buffer by macro SG_BIG_BUFF in header
+ file /usr/include/scsi/sg.h. Unless a system is seriously short on
+ memory, it is recommended to increase this value to the maximum legal
+ value of 128*1024-512=130560 bytes. After changing this value, it is
+ necessary to recompile both the kernel (or the SCSI generic module) and
+ the SCSI backends. Keep in mind that this is only necessary with older
+ Linux kernels.
+
+ A common issue with SCSI scanners is what to do when you booted the
+ system while the scanner was turned off? In such a case, the scanner
+ won't be recognized by the kernel and SANE won't be able to access it.
+ Fortunately, Linux provides a simple mechanism to probe a SCSI device
+ on demand. Suppose you have a scanner connected to SCSI bus 2 and the
+ scanner has a SCSI id of 5. When the system is up and running and the
+ scanner is turned on, you can issue the command:
+
+ echo "scsi add-single-device 2 0 5 0" > /proc/scsi/scsi
+
+ and the kernel will probe and recognize your scanner (this needs to be
+ done as root). It's also possible to dynamically remove a SCSI device
+ by using the ``remove-single-device'' command. For details, please
+ refer to to the SCSI-2.4-HOWTO.
+
+ Scanners are known to work with the following SCSI adapters under
+ Linux. This list isn't complete, usually any SCSI adapter supported by
+ Linux should work.
+
+ Acard/Advance SCSI adapters
+ Some old versions of the kernel driver (atp870u.c) cut
+ the inquiry information. Therefore the scanner couldn't
+ be detected correctly. Use a current kernel.
+
+ Adaptec AHA-1505/AHA-1542/AHA-2940
+ Reported to work fine with Linux since v2.0. If you
+ encounter kernel freezes or other unexpected behaviour
+ get the latest Linux kernel (2.2.17 seems to work) or
+ reduce SCSI buffer size to 32 kB.
+
+ ASUS SC200
+ Reported to work fine with Linux v2.0.
+
+ BusLogic BT958
+ To configure the BusLogic card, you may need to follow
+ these instructions (contributed by Jeremy
+ <jeremy@xxedgexx.com>): During boot, when your BusLogic
+ adapter is being initialized, press Ctrl-B to enter your
+ BusLogic adapter setup. Choose the address which your
+ BusLogic containing your scanner is located. Choose
+ ``SCSI Device Configuration''. Choose ``Scan SCSI Bus''.
+ Choose whatever SCSI id that contains your scanner and
+ then choose ``View/Modify SCSI configuration''. Change
+ ``Negotiation'' to ``async'' and change ``Disconnect'' to
+ ``off''. Press Esc, save, and Esc again until you are
+ asked to reboot.
+
+ NCR/Symbios 53c400/53c400a or Domex DTC3181E/L/LE (DTCT436/436P)
+ ISA SCSI card
+ This card is supplied by Mustek (and other vendors). It's
+ supported since Linux 2.2. The SCSI cards are supported
+ by the module g_NCR5380. It's necessary to tell the ker-
+ nel the io port and type of card. Example for a 53c400a:
+ ``modprobe g_NCR5380 ncr_addr=0x280 ncr_53c400a=1''.
+ Once the kernel detects the card, it should work all
+ right. However, while it should work, do not expect good
+ performance out of this card---it has no interrupt line
+ and therefore while a scan is in progress, the system
+ becomes almost unusable. You may change the values of
+ the USLEEP macros in drivers/scsi/g_NCR5380.c. Some doc-
+ umentation is in this file and NCR5380.c.
+
+ NCR/Symbios 810
+ For some scanners it may be necssary to disable discon-
+ nect/reconnect. To achieve this use the option
+ ncr53c8xx="disc:n". Some people reported that their scan-
+ ner only worked with the 53c7,8xx driver, not the
+ ncr53c8xx. Try both if you have trouble.
+ For Linux kernels before 2.0.33 it may be necessary to
+ increase the SCSI timeout. The default timeout for the
+ Linux kernels before 2.0.33 is 10 seconds, which is way
+ too low when scanning large area. If you get messages of
+ the form ``restart (ncr dead ?)'' in your /var/log/mes-
+ sages file or on the system console, it's an indication
+ that the timeout is too short. In this case, find the
+ line ``if (np->latetime>10)'' in file ncr53c8xx.c (nor-
+ mally in directory /usr/src/linux/drivers/scsi) and
+ change the constant 10 to, say, 60 (one minute). Then
+ rebuild the kernel/module and try again.
+
+ Tekram DC315
+ The driver can be downloaded from
+ http://www.garloff.de/kurt/linux/dc395/. For some older
+ scanners it may be necessary to disable all the more
+ advanced features by using e.g. modprobe dc395x_trm
+ dc395x_trm=7,5,1,32.
+
+ Tekram DC390
+ Version 1.11 of the Tekram driver seems to work fine
+ mostly, except that the scan does not terminate properly
+ (it causes a SCSI timeout after 10 minutes). The generic
+ AM53C974 also seems to work fine and does not suffer from
+ the timeout problems.
+
+
+
+SOLARIS, OPENSTEP AND NEXTSTEP INFO
+ Under Solaris, OpenStep and NeXTStep, the generic SCSI device name
+ refers to a SCSI bus, not to an individual device. For example,
+ /dev/sg0 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 /dev/sg0a, and the device with target-
+ id 1 on that same bus would be called /dev/sg0b, and so on.
+
+
+
+ENVIRONMENT
+ SANE_DEBUG_SANEI_SCSI
+ 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.
+
+ SANE_SCSICMD_TIMEOUT
+ sets the timeout value for SCSI commands in seconds. Overriding
+ the default value of 120 seconds should only be necessary for
+ very slow scanners.
+
+
+
+SEE ALSO
+ sane(7), sane-find-scanner(1), sane-"backendname"(5), sane-usb(5)
+
+
+
+AUTHOR
+ David Mosberger
+
+sane-backends 1.0.12-cvs 07 Dec 2002 sane-scsi(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-sharp.5.html b/man/sane-sharp.5.html
new file mode 100644
index 00000000..c2365eed
--- /dev/null
+++ b/man/sane-sharp.5.html
@@ -0,0 +1,377 @@
+
+
+sane-sharp.5
+
+
+sane-sharp.5
+
+
+
+sane-sharp(5) SANE Scanner Access Now Easy sane-sharp(5)
+
+
+
+NAME
+ sane-sharp - SANE backend for SHARP scanners
+
+
+
+DESCRIPTION
+ The sane-sharp library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to Sharp SCSI scanners. This backend
+ should be considered beta-quality software! In the current state it is
+ known to work with JX-610 and JX-250 scanners. It is prepared for usage
+ with the JX-330 series scanners, but we are not able to test it with
+ these devices.
+
+ For other Sharp scanners, it may or may not work.
+
+ At present, the following scanners are known to work with this backend.
+
+ Vendor Product id:
+ ----- -----------
+ Sharp JX-610
+ Sharp JX-250
+ Sharp JX-320
+ Sharp JX-330
+ Sharp JX-350
+
+ The following scanners are detected by the backend, but not tested:
+
+ Vendor Product id:
+ ----- -----------
+ Sharp JX-325
+
+
+
+DEVICE NAMES
+ This backend expects device names of the form:
+
+ special
+
+ Where special is either the path-name for the special device that cor-
+ responds to a SCSI scanner. The special device name must be a generic
+ SCSI device or a symlink to such a device. Under Linux, such a device
+ name could be /dev/sga or /dev/sge, for example. See sane-scsi(5) for
+ details.
+
+
+
+SCAN OPTIONS
+ Scan Mode (parameter --mode for scanimage). Possible settings:
+ Lineart (1 bit black & white scans),
+ Gray (8 bit gray scale scans),
+ Lineart Color (bi-level color scans),
+ Color (8 bit RGB scans).
+ The default value is Color.
+
+ Halftone Pattern (parameter --halftone-pattern for scanimage). Avail-
+ able only for the JX-330 series scanners. Possible settings:
+ none
+ Dither Bayer
+ Dither Spiral
+ Dither Dispersed
+ Error Diffusion
+ The default value is none.
+
+ Paper Source (parameter --source for scanimage). This option is only
+ available, if an automatic document feeder or a transparency adapter is
+ installed. Possible settings:
+ Flatbed
+ Automatic Document Feeder
+ Transparency Adapter
+ If an ADF or a transparency adapter is installed, using it is the
+ default selection.
+
+ Custom Gamma (parameter --custom-gamma for scanimage). This option
+ determines whether a builtin or a custom gamma-table is used. Possible
+ settings:
+ yes enables custom gamma tables
+ no enables a built gamma table
+
+ Gamma (parameter --Gamma for scanimage). This option is only available,
+ if Custom Gamma is set to no. Possible values:
+ 1.0
+ 2.2
+ The default value is 2.2. (The JX-250 and JX-350 have no built in gamma
+ correction; for these scanner, a gamma table is downloaded to the scan-
+ ner by the backend.)
+
+ Gamma Table (parameter --gamma-table for scanimage). Allowed values:
+ 0..255; 256 numbers must be defined. The default values are 0, 1, 2,
+ .. 255 (i.e., gamma == 1). This table is only used for gray scale
+ scans.
+
+ Red Gamma Table (paramter --red-gamma-table for scanimage). Allowed
+ values: 0..255; 256 numbers must be defined. The default values are 0,
+ 1, 2, .. 255 (i.e., gamma == 1).
+
+ Green Gamma Table (paramter --green-gamma-table for scanimage). Allowed
+ values: 0..255; 256 numbers must be defined. The default values are 0,
+ 1, 2, .. 255 (i.e., gamma == 1).
+
+ Blue Gamma Table (paramter --blue-gamma-table for scanimage). Allowed
+ values: 0..255; 256 numbers must be defined. The default values are 0,
+ 1, 2, .. 255 (i.e., gamma == 1).
+
+ Resolution in pixel per inch (parameter --resolution for scanimage).
+ Selects the resolution of the scanned image. Allowed values:
+ 30..600 (JX-330, JX-350 and JX-610) resp. 30..400 (JX-250)
+ The default value is 150.
+
+ Scan Window
+
+ The possible settings depend on the scanner model and, for the JX-250
+ and the JX-350, also on the usage of the automatic document feeder
+ resp. the transparency adapter. Please refer to the values allowed by
+ xscanimage, or xsane. With scanimage, enter one of the following com-
+ mands:
+
+ scanimage -d sharp --source "Automatic Document Feeder" --help
+
+ scanimage -d sharp --source Flatbed --help
+
+ scanimage -d sharp --source "Transparency Adapter" --help
+
+ in order to see the allowed parameter values for the scan window.
+
+ The scan window parameters are:
+
+ Top-left x position of scan area (parameter -l for scanimage);
+ Top-left y position of scan area (parameter -t for scanimage);
+ bottom right x position of scan area (parameter -x for scanim-
+ age);
+ bottom right y position of scan area (parameter -y for scanim-
+ age);
+
+ Edge emphasis (parameter --Edge emphasis for scanimage). This option is
+ not available for the JX-250 and the JX-350. Possible settings:
+ None
+ Middle
+ Strong
+ Blur
+ The default value is None.
+
+ Threshold (parameter --threshold for scanimage). Sets the threshold for
+ black and white pixels in lineart mode. Possible values:
+ 1..255
+ The default value is 128. This option is only available in scan mode
+ lineart.
+
+ Threshold Red (parameter --threshold-red for scanimage). Sets the
+ threshold for the red component of a pixel in in lineart color scan
+ mode. Possible values:
+ 1..255
+ The default value is 128. This option is only available in scan mode
+ color lineart.
+
+ Threshold Green (parameter --threshold-green for scanimage). Sets the
+ threshold for the green component of a pixel in in lineart color scan
+ mode. Possible values:
+ 1..255
+ The default value is 128. This option is only available in scan mode
+ color lineart.
+
+ Threshold Blue (parameter --threshold-blue for scanimage). Sets the
+ threshold for the blue component of a pixel in in lineart color scan
+ mode. Possible values:
+ 1..255
+ The default value is 128. This option is only available in scan mode
+ color lineart.
+
+ Light Color (parameter --LightColor for scanimage). Sets the color of
+ the light source. Possible values:
+ white
+ red
+ green
+ blue
+ The default value is white. This option is only available in scan
+ modes lineart color and color.
+
+
+
+ADF USAGE
+ If a paper jam occured, the maintenance cover must be opened and
+ closed, even if the jammed paper can be removed without opening the
+ maintenance cover. Otherwise, the error condition cannot be cleared.
+
+
+
+CONFIGURATION
+ The contents of the sharp.conf file is a list of options and device
+ names that correspond to Sharp scanners. Empty lines and lines begin-
+ ning with a hash mark (#) are ignored. See sane-scsi(5) for details
+ about device names.
+
+ Lines setting an option start with the key word option, followed by the
+ option's name and the option's value. At present, three options are
+ defined: buffers, buffersize, and readqueue.
+
+ Options defined at the start of sharp.conf apply to all devices;
+ options defined after a device name apply to this device.
+
+ The options buffers and readqueue are only significant if the backend
+ has been compiled so that for each scan a second process is forked
+ (switch USE_FORK in sharp.c ). This process reads the scan data from
+ the scanner and writes this data into a block of shared memory. The
+ parent process reads the data from this memory block and delivers it to
+ the frontend. The options control the size and usage of this shared
+ memory block.
+
+ option buffers defines the number of buffers used. The smallest number
+ allowed is 2.
+
+ option buffersize defines the size of one buffer. Since each buffer is
+ filled with a single read command sent to the scanner, its size is lim-
+ ited automatically to the size allowed by the operating system or by
+ the Sane SCSI library for SCSI read commands. A buffer size of 128 kB
+ or 256 kB is recommended for scan resolutions of 300 dpi and above.
+
+ option readqueue defines how many read commands to be sent to the scan-
+ ner are queued. At present, the Sane SCSI library supports queued read
+ commands only for for Linux. For other operating systems, option read-
+ queue should be set to 0. For Linux, option readqueue should be set to
+ 2. Larger values than 2 for option readqueue are not reasonable in most
+ cases. option buffers should be greater than option readqueue.
+
+
+
+Performance Considarations
+ This section focuses on the problem of stops of the scanner's carriage
+ during a scan. Carriage stops happen mainly with the JX-250. This scan-
+ ner has obviously only a small internal buffer compared to its speed.
+ That means that the backend must read the data as fast as possible from
+ the scanner in order to avoid carriage stops.
+
+ Even the JX-250 needs only less than 10 seconds for a 400 dpi A4 gray
+ scale scan, which results in a data transfer rate of more than 1.6 MB
+ per second. This means that the data produced by the scanner must be
+ processed fairly fast. Due to the small internal buffer of the JX-250,
+ the backend must issue a read request for the next data block as soon
+ as possible after reading a block of data in order to avoid carriage
+ stops.
+
+ Stops of the carriage can be caused by the following reasons:
+
+ - too much "traffic" on the SCSI bus
+ - slow responses by the backend to the scanner,
+ - a program which processes the data aquired by the backend too
+ slow.
+
+ Too much "traffic" on the SCSI bus: This happens for example, if hard
+ disks are connected to the same SCSI bus as the scanner, and when data
+ transfer from/to these hard disks requires a considerable part of the
+ SCSI bandwidth during a scan. If this is the case, you should consider
+ to connect the scanner to a separate SCSI adapter.
+
+ Slow responses by the backend to the scanner: Unfortunately, Unix-like
+ operating systems generally have no real time capabilities. Thus there
+ is no guarantee that the backend is under any circumstances able to
+ communicate with the scanner as fast as required. To minimize this
+ problem, the backend should be compiled so that a separate reader pro-
+ cess is forked: Make sure that USE_FORK is defined when you compile
+ sharp.c. If slow responses of the backend remain to be problem, you
+ could try to reduce the load of the system. Even while the backend and
+ the reader process need only a minor amount of processor time, other
+ running processes can cause an increase in the time delay between two
+ time slices given to the reader process. On slower systems, such an
+ increased delay can be enough to cause a carriage stop with the JX-250.
+ For Linux, the usage of the SG driver version 2.1.36 or above is recom-
+ mended, because it supports, in combination with the SCSI library of
+ Sane version 1.0.2, command queueing within the kernel. This queueing
+ implementation, combined with a buffer size of at least 128 kB, should
+ avoid most carirage stops.
+
+ Slow processing of the scan data: An example for this situation is the
+ access to the scanner via a 10 MBit Ethernet, which is definitely too
+ slow to transfer the scan data as fast as they are produced by the
+ scanner. If you have enough memory available, you can increase option
+ buffers, so that an entire image can be stored in these buffers.
+
+ In order to see, if the backend is too slow or if the further process-
+ ing of the data is too slow, set the environment variable
+ SANE_DEBUG_SHARP to 1. When a scan is finished, the backend writes the
+ line "buffer full conditions: nn" to stderr. If nn is zero, carriage
+ stops are caused by too slow responses of the backend or too much
+ "traffic" on the SCSI bus. If nn is greater than zero, the backend had
+ to wait nn times until a buffer has been processed by the frontend.
+ (Please note that option buffers must be greater than option readqueue
+ in order to get useful output for "buffer full conditions".)
+
+
+
+FILES
+ /usr/local/etc/sane.d/sharp.conf
+ The backend configuration file.
+
+ /usr/local/lib/sane/libsane-sharp.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-sharp.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_DEBUG_SHARP
+ 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.
+
+
+
+KNOWN PROBLEMS
+ 1. ADF Mode
+ After several ADF scans, the scanner moves the carriage back to
+ the idle position and back to ADF scan position, before a scan
+ starts. We do not know, if this is a problem of the scanner, or
+ if this is a bug of the backend. At present, the scanner must
+ power off and on to stop this annoying behaviour.
+
+ 2. Threshold level does not work (only JX-610)
+
+ 3. The maximum resolution is limited to 600 dpi(JX-610 supported to
+ 1200 dpi) resp. 400 dpi (JX-250)
+
+ 4. If the JX250 is used with an ADF, the following situation can occur:
+ After several scans, the scanner moves, after loading a new sheet of
+ paper, the carriage to the idle position, and then back to the position
+ used for ADF scans. This happens for every scan, in contrast to the
+ calibration, which is done after 10 scans. (For the calibration, the
+ carriage is also moved to the idle position.) We do not know, if this
+ behavior is caused by the backend, or if it is a bug in the firmware of
+ the scanner.
+
+ 5. Usage of a transparency adapter (film scan unit) is supported, but
+ not tested.
+
+
+
+SEE ALSO
+ sane(7), sane-scsi(5)
+
+
+
+AUTHORS
+ Kazuya Fukuda, Abel Deuring
+
+
+
+CREDITS
+ The Sharp backend is based on the Canon backend written by Helmut Koe-
+ berle
+
+ Parts of this man page are a plain copy of sane-mustek(5) by David Mos-
+ berger-Tang, Andreas Czechanowski and Andreas Bolsch
+
+sane-backends 1.0.12-cvs 21 Nov 2000 sane-sharp(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-sm3600.5.html b/man/sane-sm3600.5.html
new file mode 100644
index 00000000..1c8426be
--- /dev/null
+++ b/man/sane-sm3600.5.html
@@ -0,0 +1,121 @@
+
+
+sane-sm3600.5
+
+
+sane-sm3600.5
+
+
+
+sane-sm3600(5) SANE Scanner Access Now Easy sane-sm3600(5)
+
+
+
+NAME
+ sane-sm3600 - SANE backend for Microtek scanners with M011 USB chip
+
+
+
+DESCRIPTION
+ The sane-sm3600 library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to some Microtek scanners with the Toshiba
+ M011 custom USB chip. This backend should be considered alpha.
+
+ There exist a backends for Microtek scanners with SCSI command set.
+ Refer to sane-microtek(5) and sane-microtek2(5) for details.
+
+ At present, the following scanners are known positively to work with
+ this backend:
+
+ Vendor Product id: Remark:
+ -------- -------------- -----------
+ Microtek ScanMaker 3600 all modes ok
+ Microtek ScanMaker 3700 reported to work
+ Microtek ScanMaker 3750 reported to work
+
+ If you own a Microtek scanner with the M011 chip other than the ones
+ listed above, it may or may not work with SANE!
+
+
+
+FRONTEND OPTIONS
+ This backend dynamically enables the options for the frontend, that are
+ supported by the scanner in dependence of the scanning-mode and other
+ options. Not supported options are disabled.
+
+ The following options are supported by the Microtek2-driver:
+
+ Color, grayscale, halftone and lineart scans.
+
+ contrast, brightness, control, gamma correction.
+
+
+
+DEVICE NAMES
+ This backend does not support device names in a standardized form.
+
+
+
+CONFIGURATION
+ This backend does not support a configuration file right now.
+
+
+
+FILES
+ /usr/local/lib/sane/libsane-sm3600.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-sm3600.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+PERMISSIONS AND INTERFACES
+ The backend uses libusb and it's pseudo files in /proc/bus/usb/*. Since
+ libusb versions 0.1.3b and 0.1.4 have incompatible binary data struc-
+ tures, You must be shure not to have obsolete header files. When You
+ mix wrong versions, the scanner detection code will raise a "segment
+ violation".
+
+ These files are normally owned by root and You are responsible to get
+ access to these files, for example chown-ing them to Yourself. If You
+ have no right permissions, the backend will find the device, but You'll
+ get an I/O error.
+
+ The better way is to use automatical hotplugging. See
+ http://sm3600.sf.net/hotplug.html for instructions and useful links.
+
+
+
+ENVIRONMENT
+ SANE_DEBUG_SM3600
+ If the library was compiled with debug support enabled, this
+ environment variable controls the debug level for this backend.
+ E.g., a value of 128 requests all debug output to be printed.
+ Smaller levels reduce verbosity. To see error messages on stderr
+ set SANE_DEBUG_SM3600 to 1.
+
+ E.g. just say:
+ export SANE_DEBUG_SM3600=5
+
+
+
+SEE ALSO
+ sane-microtek2(5), http://sm3600.sourceforge.net
+
+
+
+AUTHOR
+ Marian Eichholz (eichholz@computer.org)
+ Glenn Ramsey (glenn@componic.com)
+
+sane-backends 1.0.12-cvs 10.02.2002 sane-sm3600(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-snapscan.5.html b/man/sane-snapscan.5.html
new file mode 100644
index 00000000..07fec59e
--- /dev/null
+++ b/man/sane-snapscan.5.html
@@ -0,0 +1,125 @@
+
+
+sane-snapscan.5
+
+
+sane-snapscan.5
+
+
+
+sane-snapscan(5) SANE Scanner Access Now Easy sane-snapscan(5)
+
+
+
+NAME
+ sane-snapscan - SANE backend for AGFA SnapScan flatbed scanners
+
+
+
+DESCRIPTION
+ The sane-snapscan library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to AGFA SnapScan flatbed scanners. At
+ present, the following scanners are supported from this backend: AGFA
+ SnapScan 300, 310, 600, and 1236s, 1236u, 1212u, e20, e25, e40, e50,
+ e60, Vuego 310s, Acer 300f, 310s, 610s, 610plus, Prisa 620s, Prisa
+ 620u, Prisa 620ut, Prisa 640u, Prisa 640bu, Prisa 1240, Prisa 3300,
+ Prisa 4300, Prisa 5300 and Guillemot Maxi Scan A4 Deluxe (SCSI) (with
+ varying success).
+
+
+
+DEVICE NAMES
+ This backend expects device names of the form:
+
+ special
+
+ Where special is the path-name for the special device that corresponds
+ to a SCSI scanner. For SCSI scanners, the special device name must be a
+ generic SCSI device or a symlink to such a device. Under Linux, such a
+ device name could be /dev/sga or /dev/sge, for example. See sane-
+ scsi(5) for details.
+
+ For USB scanners the devicename must contain the keyword "usb", as in
+ /dev/usbscanner or /dev/usb/scanner0. For scanners that need a
+ firmware upload before scanning add a line starting with "firmware"
+ followed by the fully qualified path to your firmware file, e.g.
+
+ firmware /path/to/my/firmware.bin
+
+ For further details read http://snapscan.sourceforge.net.
+
+
+
+CONFIGURATION
+ The contents of the snapscan.conf file is a list of device names that
+ correspond to SnapScan scanners. Empty lines and lines starting with a
+ hash mark (#) are ignored. See sane-scsi(5) on details of what consti-
+ tutes a valid device name.
+
+
+
+FILES
+ /usr/local/etc/sane.d/snapscan.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-snapscan.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-snapscan.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_SNAPSCAN
+ 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.
+
+
+
+BUGS
+ Man page doesn't provide much information yet.
+
+
+
+SEE ALSO
+ sane(7), sane-scsi(5)
+ http://www.cs.ualberta.ca/~charter/SnapScan/snapscan.html
+ http://sourceforge.net/projects/snapscan/ (new development website)
+
+
+
+AUTHOR
+ Kevin Charter, Franck Schneider, Michel Roelofs, Emmanuel Blot, Mikko
+ Tyolajarvi, David Mosberger-Tang, Wolfgang Goeller, Petter Reinholdt-
+ sen, Gary Plewa, Sebastien Sable, Oliver Schwartz and Mikael Magnusson.
+ Man page by Henning Meier-Geinitz (mostly based on the web pages and
+ source code).
+
+sane-backends 1.0.12-cvs 26 May 2001 sane-snapscan(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-sp15c.5.html b/man/sane-sp15c.5.html
new file mode 100644
index 00000000..6f8725de
--- /dev/null
+++ b/man/sane-sp15c.5.html
@@ -0,0 +1,89 @@
+
+
+sane-sp15c.5
+
+
+sane-sp15c.5
+
+
+
+sane-sp15c(5) SANE Scanner Access Now Easy sane-sp15c(5)
+
+
+
+NAME
+ sane-sp15c - SANE backend for Fujitsu ScanPartner 15C flatbed scanner
+
+
+
+DESCRIPTION
+ The sane-sp15c library implements a SANE (Scanner Access Now Easy)
+ backend which provides access to the Fujitsu flatbed scanners. At
+ present, the following scanner is known to work with these backend:
+
+ Vendor: Model: Rev:
+ -------- ---------------- -----
+ FCPA ScanPartner 15C 1.01
+
+ The ScanPartner 15C driver supports lineart (1-bit), halftone (1-bit),
+ grayscale (4-bit and 8-bit), and color (3 x 8-bit) scanning.
+
+ Other scanners in these families may work. The ScanPartner 15C seems
+ to be a repackaging of the ScanPartner 600C. People are encouraged to
+ try these driver with the other scanners and to contact the author with
+ test results.
+
+
+
+CONFIGURATION
+ A modest effort has been made to expose the standard options to the
+ API. This allows frontends such as xscanimage to set scanning region,
+ resolution, bit-depth (and color), and enable the automatic document
+ feeder.
+
+
+
+SEE ALSO
+ sane(7), sane-scsi(5), sane-fujitsu(5)
+ Fujitsu ScanPartner 15C OEM Manual, Doc. No. 250-0081-0
+ Fujitsu M3096G OEM Manual, part number 50FH5028E-05
+ Fujitsu M3096GX/M3093GX/M3093DG OEM Manual, part number C150-E015...03
+
+
+
+AUTHOR
+ Randolph Bentson <bentson@holmsjoen.com>, with credit to the unnamed
+ author of the coolscan driver
+
+
+
+LIMITATIONS
+ Testing limited to a Linux 2.2.5 kernel
+ Can't quite get the scan page/minute performance in ADF modes. This
+ may be due to limited system buffer size.
+
+
+
+BUGS
+ I'm sure there are plenty, and not too well hidden, but I haven't seen
+ them yet.
+ Both scanners claim to have separate control of resolution in X and Y
+ directions. I confess I haven't tested this yet. I have found that
+ xsane doesn't even display this capability.
+ Threshold settings on the SP15C don't seem to affect the results of
+ lineart mode scans.
+ It might be possible to merge these two drivers without much effort
+ since the SP15C driver was derived from the M3096G driver. They were
+ split so as to keep the second driver development from breaking the
+ working first driver. Watch this space for changes.
+
+
+sane-backends 1.0.12-cvs 17 Apr 2002 sane-sp15c(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-st400.5.html b/man/sane-st400.5.html
new file mode 100644
index 00000000..130899cc
--- /dev/null
+++ b/man/sane-st400.5.html
@@ -0,0 +1,164 @@
+
+
+sane-st400.5
+
+
+sane-st400.5
+
+
+
+sane-st400(5) SANE Scanner Access Now Easy sane-st400(5)
+
+
+
+NAME
+ sane-st400 - SANE backend for Siemens ST/Highscan flatbed scanners
+
+
+
+DESCRIPTION
+ The sane-st400 library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to Siemens ST400 flatbed scanners and com-
+ patibles. At present, the following scanners are supported by this
+ backend:
+
+ Siemens ST400 (6 bit gray scale)
+ Siemens ST800 (6 bit gray scale)
+
+ The driver supports line art and gray scans up to 8bpp.
+
+ The Siemens ST/Highscan series includes several more models, e.g. the
+ ST300 and ST600. If you own one of these scanners, or a scanner other
+ than the ones listed above that works with this backend, please let us
+ know by sending the scanner's model name, SCSI ID, and firmware revi-
+ sion to sane-devel@mostang.com. Have a look at
+ http://www.mostang.com/sane/mail.html concerning subscription to sane-
+ devel.
+
+
+
+DEVICE NAMES
+ This backend expects device names of the form:
+
+ special
+
+ Where special 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 /dev/sga or /dev/sge, for example.
+ See sane-scsi(5) for details.
+
+
+
+CONFIGURATION
+ The contents of the st400.conf file is a list of device names that cor-
+ respond to Siemens scanners. Empty lines and lines starting with a
+ hash mark (#) are ignored. A sample configuration file is shown below:
+
+ /dev/scanner
+ # this is a comment
+ /dev/sge
+
+ The default configuration file that is distributed with SANE looks like
+ this:
+
+ scsi SIEMENS "ST 400" Scanner * * 3 0
+
+ In this configuration, the driver can only access the ST400 model at
+ SCSI ID 3 LUN 0 (see section "BUGS" below for the reason). To use the
+ driver with other scanner models, add an appropriate line to the con-
+ figuration file. For example, to use it with an ST800 at SCSI ID 3 LUN
+ 0, add the line:
+
+ scsi SIEMENS "ST 800" Scanner * * 3 0
+
+
+
+FILES
+ /usr/local/etc/sane.d/st400.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-st400.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-st400.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in /etc/sane.d. If the
+ value of the environment variable ends with the directory sepa-
+ rator character, then the default directories are searched after
+ the explicitly specified directories. For example, setting
+ SANE_CONFIG_DIR to "/tmp/config:" would result in directories
+ "tmp/config", ".", and "/etc/sane.d" being searched (in this
+ order).
+
+ SANE_DEBUG_ST400
+ 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.
+
+
+
+MISSING FUNCTIONALITY
+ Everything but the most basic stuff.
+
+
+
+BUGS
+ Currently, the backend does not check if the attached device really is
+ a ST400. It will happily accept everything that matches the configura-
+ tion entries. This makes it easy to test the backend with other scan-
+ ners: Just add an appropriate line to the configuration file. The con-
+ figuration file as distributed (see above) only works with the ST400.
+ Be careful: If there is no config file at all, the backend defaults to
+ /dev/scanner.
+
+ The ST400 answers on all eight SCSI LUNs. Normally this is not a prob-
+ lem, as LUN support is usually disabled in SCSI drivers, but if you are
+ seeing multiple instances of the scanner in a device list, either dis-
+ able LUNs in your SCSI setup or change the entry in the configuration
+ file to match LUN 0 only.
+
+
+
+DEBUG
+ If you encounter a bug please set the environment variable
+ SANE_DEBUG_ST400 to 128 and try to regenerate the problem. Then send me
+ a report with the log attached.
+
+ If you encounter a SCSI bus error or trimmed and/or displaced images
+ please also set the environment variable SANE_DEBUG_SANEI_SCSI to 128
+ before sending me the report.
+
+
+
+SEE ALSO
+ sane(7), sane-scsi(5)
+ http://www.informatik.uni-oldenburg.de/~ingo/sane/
+
+
+
+AUTHOR
+ Ingo Wilken <Ingo.Wilken@informatik.uni-oldenburg.de>
+
+sane-backends 1.0.12-cvs 08 Mar 1999 sane-st400(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-tamarack.5.html b/man/sane-tamarack.5.html
new file mode 100644
index 00000000..a9948d6f
--- /dev/null
+++ b/man/sane-tamarack.5.html
@@ -0,0 +1,98 @@
+
+
+sane-tamarack.5
+
+
+sane-tamarack.5
+
+
+
+sane-tamarack(5) SANE Scanner Access Now Easy sane-tamarack(5)
+
+
+
+NAME
+ sane-tamarack - SANE backend for Tamarack flatbed scanners
+
+
+
+DESCRIPTION
+ The sane-tamarack library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to the following Tamarack flatbed scan-
+ ners:
+
+ Artiscan 6000C
+ Artiscan 8000C
+ Artiscan 12000C
+
+
+
+DEVICE NAMES
+ This backend expects device names of the form:
+
+ special
+
+ Where special is the path-name for the special device that corresponds
+ to a SCSI scanner. The special device name must be a generic SCSI
+ device or a symlink to such a device. The program sane-find-scanner
+ helps to find out the correct device. Under Linux, such a device name
+ could be /dev/sga or /dev/sge, for example. See sane-scsi(5) for
+ details.
+
+
+
+FILES
+ /usr/local/etc/sane.d/tamarack.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-tamarack.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-tamarack.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_TAMARACK
+ If the library was compiled with debug support enabled, this
+ environment variable controls the debug level for this backend.
+ Higher debug levels increase the verbosity of the output.
+
+ Example: export SANE_DEBUG_TAMARACK=4
+
+
+
+SEE ALSO
+ sane(7), sane-scsi(5)
+
+
+
+AUTHOR
+ Roger Wolff
+
+sane-backends 1.0.12-cvs 24 Jun 2000 sane-tamarack(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-teco1.5.html b/man/sane-teco1.5.html
new file mode 100644
index 00000000..ffcc18a2
--- /dev/null
+++ b/man/sane-teco1.5.html
@@ -0,0 +1,177 @@
+
+
+sane-teco1.5
+
+
+sane-teco1.5
+
+
+
+sane-teco1(5) SANE Scanner Access Now Easy sane-teco1(5)
+
+
+
+NAME
+ sane-teco1 - SANE backend for TECO / RELISYS scanners
+
+
+
+DESCRIPTION
+ The sane-teco1 library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to some TECO SCSI flatbed scanners. This
+ backend should be considered beta-quality software! TECO scanners are
+ sold under various brands like RELISYS, PIOTECH, TRUST. This backend
+ may or may not support yours.
+
+ The scanners that should work with this backend are:
+
+ Vendor Model TECO model status
+ ---------------------- -------------- -----------
+ Relisys AVEC 2400 VM3520 tested
+ Relisys AVEC 2412 VM3520+ untested
+ Relisys AVEC 4800 VM4530 untested
+ Relisys AVEC 4816 VM4530+ untested
+ Relisys RELI 2400 VM3530 untested
+ Relisys RELI 2412 VM3530+ tested
+ Relisys RELI 2412 VM3530+ untested
+ Relisys RELI 4816 VM4540 untested
+ Relisys RELI 4830 VM4542 tested
+ Relisys RELI 9600 VM6530 untested
+ Relisys RELI 9612 VM6530* untested
+ Relisys RELI 9624 VM6530+ untested
+ Relisys RELI 9630 VM6540 untested
+ Relisys RELI DS15 VM3440 untested
+ Relisys RELI DS6 VM3420 untested
+ Dextra DF-600P VM3510 tested
+ Dextra DF-4830T VM4542 untested
+ Dextra DF-1200T+ VM3530+ untested
+ Dextra DF-9624 VM6530+ untested
+
+ Note that the untested scanner will not be directly supported. You
+ should contact the author for that.
+
+ The TECO VM number can usually be found at the back of the scanner. It
+ is also part of the FCC ID. "sane-find-scanner -v" will also show the
+ scsi inquiry, and if it is a TECO scanner, the name will be there too.
+
+ The options the backend supports can either be selected through command
+ line options to programs like scanimage or through GUI elements in
+ xscanimage or xsane.
+
+ If you have any success with a scanner not listed here, or if you have
+ any strange behavior, please report to the backend maintainer or to the
+ SANE mailing list.
+
+ Valid command line options and their syntax can be listed by using
+ scanimage --help -d teco1
+
+ Scan Mode
+
+ --mode selects the basic mode of operation of the scanner valid choices
+ are Black & White , Grayscale and Color The Black & White mode
+ is black and white only (1 bit). Grayscale will produce 256 lev-
+ els of gray (8 bits). Color will produce a 24 bits color image.
+
+ --resolution
+ selects the resolution for a scan. The scanner can do all reso-
+ lutions between 1 and 600, in increments of 1.
+
+ Geometry options
+
+ -l -t -x -y
+ control the scan area: -l sets the top left x coordinate, -t the
+ top left y coordinate, -x selects the width and -y the height of
+ the scan area. All parameters are specified in millimeters by
+ default.
+
+ Enhancement options
+
+ --custom-gamma
+ (color mode only) allows the user to specify a gamma table (see
+ the next 3 parameters).
+
+ --red-gamma-table
+ (color mode only) can be used to download a user defined gamma
+ table for the red channel. The table must be 256 bytes long.
+
+ --green-gamma-table
+ (color mode only) can be used to download a user defined gamma
+ table for the green channel. The table must be 256 bytes long.
+
+ --blue-gamma-table
+ (color mode only) can be used to download a user defined gamma
+ table for the blue channel. The table must be 256 bytes long.
+
+ --dither
+ (Black & White only) select the dither mask to use. Possible
+ values are Line art , 2x2 , 3x3 , 4x4 bayer , 4x4 smooth , 8x8
+ bayer , 8x8 smooth , 8x8 horizontal and 8x8 vertical
+
+ --preview
+ requests a preview scan. The resolution used for that scan is 22
+ dpi and the scan area is the maximum allowed. The scan mode is
+ user selected. The default is "no".
+
+
+
+CONFIGURATION FILE
+ The configuration file /usr/local/etc/sane.d/teco1.conf supports only
+ one information: the device name to use (eg /dev/scanner).
+
+
+
+FILES
+ /usr/local/lib/sane/libsane-teco1.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-teco1.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_DEBUG_TECO1
+ 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.
+
+
+
+LIMITATIONS
+ 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.
+
+
+
+BUGS
+ None known.
+
+
+
+SEE ALSO
+ sane-scsi(5), scanimage(1), xscanimage(1), xsane(1), sane(7)
+
+
+
+AUTHOR
+ The package is actively maintained by Frank Zago.
+ http://fz.eryx.net/sane/#teco
+
+
+
+CREDITS
+ 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 sane-teco1(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-teco2.5.html b/man/sane-teco2.5.html
new file mode 100644
index 00000000..7a47ae68
--- /dev/null
+++ b/man/sane-teco2.5.html
@@ -0,0 +1,187 @@
+
+
+sane-teco2.5
+
+
+sane-teco2.5
+
+
+
+sane-teco2(5) SANE Scanner Access Now Easy sane-teco2(5)
+
+
+
+NAME
+ sane-teco2 - SANE backend for TECO / RELISYS scanners
+
+
+
+DESCRIPTION
+ The sane-teco2 library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to some TECO SCSI flatbed scanners. This
+ backend should be considered beta-quality software! TECO scanners are
+ sold under various brands like Relisys, Piotech, TRUST. This backend
+ may or may not support yours.
+
+ The scanners that should work with this backend are:
+
+ Vendor Model TECO model status
+ ---------------------- -------------- -----------
+
+ Primax Jewel 4800 VM356A tested
+ Primax Profi 9600 VM6575 tested
+ Primax Profi 19200 VM6586 tested
+ Relisys APOLLO Express 3 VM356A tested
+ Relisys APOLLO Express 6 VM6565 tested
+ Relisys APOLLO Express 12 ? untested
+ Relisys AVEC II S3 VM3564 tested
+ Relisys AVEC Super 3 VM3575 tested
+ Relisys SCORPIO Pro VM6575 tested
+ Relisys SCORPIO Pro-S VM6586 tested
+ Relisys SCORPIO Super 3 VM3575 tested
+
+ For all these scanners, black&white and grayscale mode work well. How-
+ ever, most of them do not support more than a handful of resolutions in
+ color mode. See the backend home page (under AUTHOR) for the exact sta-
+ tus of each scanner.
+
+ Note that the untested scanner will not be directly supported. You
+ should contact the author for that.
+
+ The TECO VM number can usually be found at the back of the scanner. It
+ is also part of the FCC ID.
+
+ The options the backend supports can either be selected through command
+ line options to programs like scanimage or through GUI elements in
+ xscanimage or xsane.
+
+ If you have any success with a scanner not listed here, or if you have
+ any strange behavior, please report to the backend maintainer or to the
+ SANE mailing list.
+
+ Valid command line options and their syntax can be listed by using
+ scanimage --help -d teco2
+
+ Scan Mode
+
+ --mode selects the basic mode of operation of the scanner valid choices
+ are Black & White , Grayscale and Color The Black & White mode
+ is black and white only (1 bit). Grayscale will produce 256 lev-
+ els of gray (8 bits). Color will produce a 24 bits color image.
+
+ --resolution
+ selects the resolution for a scan. The scanner can do all reso-
+ lutions between 1 and 600, in increments of 1.
+
+ Geometry options
+
+ -l -t -x -y
+ control the scan area: -l sets the top left x coordinate, -t the
+ top left y coordinate, -x selects the width and -y the height of
+ the scan area. All parameters are specified in millimeters by
+ default.
+
+ Enhancement options
+
+ --custom-gamma
+ (color mode only) allows the user to specify a gamma table (see
+ the next 3 parameters).
+
+ --red-gamma-table
+ (color mode only) can be used to download a user defined gamma
+ table for the red channel. The table must be 256 bytes long.
+
+ --green-gamma-table
+ (color mode only) can be used to download a user defined gamma
+ table for the green channel. The table must be 256 bytes long.
+
+ --blue-gamma-table
+ (color mode only) can be used to download a user defined gamma
+ table for the blue channel. The table must be 256 bytes long.
+
+ --preview
+ requests a preview scan. The resolution used for that scan is 22
+ dpi and the scan area is the maximum allowed. The scan mode is
+ user selected. The default is "no".
+
+
+
+CONFIGURATION FILE
+ The configuration file /usr/local/etc/sane.d/teco2.conf supports only
+ one information: the device name to use (eg /dev/scanner).
+
+
+
+FILES
+ /usr/local/lib/sane/libsane-teco2.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-teco2.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_DEBUG_TECO2
+ If the library was compiled with debug support enabled, this
+ environment variable controls the debug level for this backend.
+ E.g., a value of 128 requests all debug output to be printed.
+ Smaller levels reduce verbosity.
+
+ SANE_TECO2_CAL_ALGO
+ 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.
+
+
+
+LIMITATIONS
+ 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.
+
+
+
+BUGS
+ Plenty. Parts of this backend are still under development.
+
+
+
+SEE ALSO
+ sane-scsi(5), scanimage(1), xscanimage(1), xsane(1), sane(7)
+
+
+
+AUTHORS
+ The package is actively maintained by Frank Zago.
+ http://fz.eryx.net/sane/#teco2
+
+ Gerard Klaver contributed a patch to support the VM3564 and VM356A.
+
+
+
+CREDITS
+ Thanks to:
+
+ Gerard Klaver for his relentless VM3575 testings.
+
+ Mark Plowman for providing the first SCSI traces from a VM3575.
+
+ Andreas Klaedtke for providing the first SCSI traces from a VM6586 and
+ for his testing, and to Stefan von Dombrowski for his testing.
+
+ Nicolas Peyresaubes for providing the first SCSI traces from a VM656A
+ and for his testing.
+
+ Dave Parker for testing the support for the VM6575.
+
+sane-backends 1.0.12-cvs 19 March 2002 sane-teco2(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-teco3.5.html b/man/sane-teco3.5.html
new file mode 100644
index 00000000..1c126e4b
--- /dev/null
+++ b/man/sane-teco3.5.html
@@ -0,0 +1,150 @@
+
+
+sane-teco3.5
+
+
+sane-teco3.5
+
+
+
+sane-teco3(5) SANE Scanner Access Now Easy sane-teco3(5)
+
+
+
+NAME
+ sane-teco3 - SANE backend for TECO / RELISYS scanners
+
+
+
+DESCRIPTION
+ The sane-teco3 library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to some TECO SCSI flatbed scanners. This
+ backend should be considered alpha-quality software! TECO scanners are
+ sold under various brands like RELYSIS, PIOTECH, TRUST. This backend
+ may or may not support yours.
+
+ The scanners that should work with this backend are:
+
+ Vendor Model TECO model status
+ --------------------------- ---------- ----------
+ Relisys Scorpio VM3552 tested
+ Plustek OpticPro 2400SP VM3552 untested
+ PIOTECH Splendeur 3024 VM3552 tested
+ Trust Imagery 2400 SP VM3552 tested
+ Trust Imagery 4800 SP+ VM3552 tested
+ Trust Imagery 9600 SP VM3552 untested
+
+ The TECO VM number can usually be found at the back of the scanner. It
+ is also part of the FCC ID.
+
+ The options the backend supports can either be selected through command
+ line options to programs like scanimage or through GUI elements in
+ xscanimage or xsane.
+
+ If you have any success with a scanner not listed here, or if you have
+ any strange behavior, please report to the backend maintainer or to the
+ SANE mailing list.
+
+ Valid command line options and their syntax can be listed by using
+ scanimage --help -d teco3
+
+ Scan Mode
+
+ --mode selects the basic mode of operation of the scanner valid choices
+ are Black & White , Grayscale and Color The Black & White mode
+ is black and white only (1 bit). Grayscale will produce 256 lev-
+ els of gray (8 bits). Color will produce a 24 bits color image.
+
+ --resolution
+ selects the resolution for a scan. The scanner can do all reso-
+ lutions between 1 and 1200, in increments of 1.
+
+ Geometry options
+
+ -l -t -x -y
+ control the scan area: -l sets the top left x coordinate, -t the
+ top left y coordinate, -x selects the width and -y the height of
+ the scan area. All parameters are specified in millimeters by
+ default.
+
+ Enhancement options
+
+ --custom-gamma
+ (color mode only) allows the user to specify a gamma table (see
+ the next 3 parameters).
+
+ --red-gamma-table
+ (color mode only) can be used to download a user defined gamma
+ table for the red channel. The table must be 1024 bytes long.
+
+ --green-gamma-table
+ (color mode only) can be used to download a user defined gamma
+ table for the green channel. The table must be 1024 bytes long.
+
+ --blue-gamma-table
+ (color mode only) can be used to download a user defined gamma
+ table for the blue channel. The table must be 1024 bytes long.
+
+ --preview
+ requests a preview scan. The resolution used for that scan is 22
+ dpi and the scan area is the maximum allowed. The scan mode is
+ user selected. The default is "no".
+
+
+
+CONFIGURATION FILE
+ The configuration file /usr/local/etc/sane.d/teco3.conf supports only
+ one information: the device name to use (eg /dev/scanner).
+
+
+
+FILES
+ /usr/local/lib/sane/libsane-teco3.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-teco3.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_DEBUG_TECO3
+ 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.
+
+
+
+LIMITATIONS
+ 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.
+
+
+
+BUGS
+ Not much.
+
+
+
+
+SEE ALSO
+ sane-scsi(5), scanimage(1), xscanimage(1), xsane(1), sane(7)
+
+
+
+AUTHOR
+ The package is actively maintained by Frank Zago.
+ http://fz.eryx.net/sane/#teco3
+
+sane-backends 1.0.12-cvs 25 July 2002 sane-teco3(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-test.5.html b/man/sane-test.5.html
new file mode 100644
index 00000000..76666a1e
--- /dev/null
+++ b/man/sane-test.5.html
@@ -0,0 +1,290 @@
+
+
+sane-test.5
+
+
+sane-test.5
+
+
+
+sane-test(5) SANE Scanner Access Now Easy sane-test(5)
+
+
+
+NAME
+ sane-test - SANE backend for testing frontends
+
+
+
+DESCRIPTION
+ The sane-test library implements a SANE (Scanner Access Now Easy) back-
+ end that allows testing the SANE installation and SANE frontends. It
+ provides access to a (nearly) unlimited number of virtual devices.
+ There is no support for real scanners or cameras. However, the backend
+ simulates scanning and setting options.
+
+ The idea is not only to find bugs in frontends but also to show all
+ capabilities of SANE. Therefore sane-test implements functions and
+ options that are not (or seldomly) found in other backends.
+
+ The backend is commented out in /usr/local/etc/sane.d/dll.conf, so
+ either the comment character must be removed or the backend must be
+ called explicitely. E.g. `scanimage -d test' or `xscanimage test'.
+
+
+
+SCAN MODE OPTIONS
+ Option mode selects the scan mode (Gray or Color).
+
+ Option depth determines the number of bits per sample (1. 8, or 16).
+ Keep in mind, that this value refers to the sample, not the pixel. So
+ depth=16 results in 48 bits per pixel in color mode. The most usual
+ combinations are mode=Gray, depth=1 for lineart, mode=Gray, depth=8 for
+ gray and mode=Color, depth=8 for color mode. The combination of color
+ and 1-bit mode is quite obscure (8 colors) but allowed in the SANE
+ standard. However, the meaning of bits is not defined. Currently 1 =
+ high intensity and 0 = low intensity is used.
+
+ Setting option hand-scanner results in the test-backend behaving like a
+ hand-scanner. Hand-scanners do not know the image height a priori.
+ Instead, they return a height of -1. Setting this option allows to
+ test whether a frontend can handle this correctly. This option also
+ enables a fixed width of 11 cm.
+
+ Setting option three-pass simulates a three-pass scanner. Older color
+ scanners needed to scan the image once per color (reg/green/blue) to
+ get the full image. Therefore, in this mode three single frames are
+ transmitted in color mode.
+
+ Option three-pass-order provides support for changing the order of the
+ three frames (see option three-pass above). A frontend should support
+ all orders.
+
+ Option resolution sets the resolution of the image in dots per inch.
+
+
+
+SPECIAL OPTIONS
+ Option test-picture allows to set the image that's returned to the
+ frontend. While "Solid white" and "Solid black" are quite obvious, the
+ other options need some more explanation. Color patterns are used to
+ determine if all modes and their colors are reprented correctly by the
+ frontend. The grid should look like the same in every mode and resolu-
+ tion. A table of all the test pictures can be found at:
+ http://www.meier-geinitz.de/sane/test-backend/test-pictures.html.
+
+ If option invert-endianess is set, the upper and lower bytes of image
+ data in 16 bit modes are exchanged. This option can be used to test
+ the 16 bit modes of frontends, e.g. if the frontend uses the correct
+ endianess.
+
+ If option read-limit is set, the maximum amount of data tranferred with
+ each call to sane_read() is limited.
+
+ Option read-limit-size sets the limit for option read-limit. A low
+ limit slows down scanning. It can be used to detect errors in frontend
+ that occur because of wrong assumptions on the size of the buffer or
+ timing problems.
+
+ Option read-delay enables delaying data to the frontend.
+
+ Option read-delay-duration selects the number of microseconds the back-
+ ends waits after each transfer of a buffer. This option is useful to
+ find timing-related bugs, especially if used over the network.
+
+ If option read-return-value is different from "Default", the selected
+ status will be returned by every call to sane_read(). This is useful
+ to test the frontend's handling of the SANE statii.
+
+ If option ppl-loss is different from 0, it determines the number of
+ pixels that are "lost" at the end of each line. That means, lines are
+ padded with unused data.
+
+ Option fuzzy-parameters selects that fuzzy (inexact) parameters are
+ returned as long as the scan hasn't been started. This option can be
+ used to test if the frontend uses the parameters it got before the
+ start of the scan (which it shouldn't).
+
+ Option non-blocking determines if non-blocking IO for sane_read()
+ should be used if supported by the frontend.
+
+ If option select-fd is set, the backend offers a select filedescriptor
+ for detecting if sane_read() will return data.
+
+ If option enable-test-options is set, a fairly big list of options for
+ testing the various SANE option types is enabled.
+
+ Option print-options can be used to print a list of all options to
+ standard error.
+
+
+
+GEOMETRY OPTIONS
+ Option tl-x determines the top-left x position of the scan area.
+
+ Option tl-y determines the top-left y position of the scan area.
+
+ Option br-x determines the bottom-right x position of the scan area.
+
+ Option br-y determines the bottom-right y position of the scan area.
+
+
+
+BOOL TEST OPTIONS
+ There are 6 bool test options in total. Each option is numbered.
+ (3/6) means: this is option 3 of 6. The numbering scheme is inetended
+ for easier detection of options not displayed by the frontend (bevause
+ of missing support or bugs).
+
+ Option bool-soft-select-soft-detect (1/6) is a bool test option that
+ has soft select and soft detect (and advanced) capabilities. That's
+ just a normal bool option.
+
+ Option bool-hard-select-soft-detect (2/6) is a bool test option that
+ has hard select and soft detect (and advanced) capabilities. That
+ means the option can't be set by the frontend but by the user (e.g. by
+ pressing a button at the device).
+
+ Option bool-hard-select (3/6) is a bool test option that has hard
+ select (and advanced) capabilities. That means the option can't be set
+ by the frontend but by the user (e.g. by pressing a button at the
+ device) and can't be read by the frontend.
+
+ Option bool-soft-detect (4/6) is a bool test option that has soft
+ detect (and advanced) capabilities. That means the option is read-
+ only.
+
+ Option bool-soft-select-soft-detect-emulated (5/6) is a Bool test
+ option that has soft select, soft detect, and emulated (and advanced)
+ capabilities.
+
+ Option bool-soft-select-soft-detect-auto (6/6) is a Bool test option
+ that has soft select, soft detect, and automatic (and advanced) capa-
+ bilities. This option can be automatically set by the backend.
+
+
+
+INT TEST OPTIONS
+ There are 6 int test options in total.
+
+ Option int (1/6) is an int test option with no unit and no constraint
+ set.
+
+ Option int-constraint-range (2/6) is an int test option with unit pixel
+ and constraint range set. Minimum is 4, maximum 192, and quant is 2.
+
+ Option int-constraint-word-list (3/6) is an int test option with unit
+ bits and constraint word list set.
+
+ Option int-constraint-array (4/6) is an int test option with unit mm
+ and using an array without constraints.
+
+ Option int-constraint-array-constraint-range (5/6) is an int test
+ option with unit mm and using an array with a range constraint. Mini-
+ mum is 4, maximum 192, and quant is 2.
+
+ Option int-constraint-array-constraint-word-list (6/6) is an int test
+ option with unit percent and using an array a word list constraint.
+
+
+
+FIXED TEST OPTIONS
+ There are 3 fixed test options in total.
+
+ Option fixed (1/3) is a fixed test option with no unit and no con-
+ straint set.
+
+ Option fixed-constraint-range (2/3) is a fixed test option with unit
+ microsecond and constraint range set. Minimum is -42.17, maximum
+ 32767.9999, and quant is 2.0.
+
+ Option fixed-constraint-word-list (3/3) is a Fixed test option with no
+ unit and constraint word list set.
+
+
+
+STRING TEST OPTIONS
+ There are 3 string test options in total.
+
+ Option string (1/3) is a string test option without constraint.
+
+ Option string-constraint-string-list (2/3) is a string test option with
+ string list constraint.
+
+ Option string-constraint-long-string-list (3/3) is a string test option
+ with string list constraint. Contains some more entries...
+
+
+
+BUTTON TEST OPTION
+ Option button (1/1) is a Button test option. Prints some text...
+
+
+
+FILES
+ /usr/local/etc/sane.d/test.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below). The initial values of most of the basic
+ SANE options can be configured in this file. A template contain-
+ ing all the default values is provided together with this back-
+ end. One of the more interesting values may be num-
+ ber_of_devices. It can be used to check the frontend's ability
+ to show a long list of devices. The config values concerning
+ resolution and geometry can be useful to test the handling of
+ big file sizes.
+
+ /usr/local/lib/sane/libsane-test.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-test.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_TEST
+ If the library was compiled with debug support enabled, this
+ environment variable controls the debug level for this backend.
+ Higher debug levels increase the verbosity of the output.
+
+ Example: export SANE_DEBUG_TEST=4
+
+
+
+SEE ALSO
+ sane(7), http://www.meier-geinitz.de/sane/test-backend/
+
+
+
+AUTHOR
+ Henning Meier-Geinitz <henning@meier-geinitz.de>
+
+
+
+BUGS
+ - config file values aren't tested for correctness
+
+sane-backends 1.0.12-cvs 24 Jul 2002 sane-test(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-umax.5.html b/man/sane-umax.5.html
new file mode 100644
index 00000000..635448ef
--- /dev/null
+++ b/man/sane-umax.5.html
@@ -0,0 +1,279 @@
+
+
+sane-umax.5
+
+
+sane-umax.5
+
+
+
+sane-umax(5) SANE Scanner Access Now Easy sane-umax(5)
+
+
+
+NAME
+ sane-umax - SANE backend for UMAX scanners
+
+
+
+ABOUT THIS FILE
+ This file only is a short descripton of the umax-backend for sane! For
+ detailled information take a look at sane-umax-doc.html (it is included
+ in the sane source directory and in the xsane online help)!
+
+
+
+DESCRIPTION
+ The sane-umax library implements a SANE backend that provides acces to
+ several UMAX-SCSI-scanners and some Linotye Hell SCSI-scanners, paral-
+ lel- and USB-scanners are not (and propably will never be) supported!
+
+ I suggest you hold one hand on the power-button of the scanner while
+ you try the first scans!
+
+
+
+CONFIGURATION
+ The configuration file for this backend resides in
+ /usr/local/etc/sane.d/umax.conf.
+
+ Its contents is a list of device names that correspond to UMAX and UMAX
+ compatible scanners. Empty lines and lines starting with a hash mark
+ (#) are ignored. A sample configuration file is shown below:
+
+ # this is a comment
+ #
+ option scsi-maxqueue 4
+ option scsi-buffer-size-min 65536
+ option scsi-buffer-size-max 131072
+ option scan-lines 40
+ option preview-lines 10
+ option scsi-maxqueue 2
+ option execute-request-sense 0
+ option force-preview-bit-rgb 0
+ option slow-speed -1
+ option care-about-smearing -1
+ option calibration-full-ccd -1
+ option calibration-width-offset -1
+ option calibration-bytes-pixel -1
+ option exposure-time-rgb-bind -1
+ option invert-shading-data -1
+ option lamp-control-available 0
+ option gamma-lsb-padded 0
+ /dev/sge
+
+ #scsi Vendor Model Type Bus Channel ID LUN
+ # The following scanner supports lamp control
+ option lamp-control-available 1
+ scsi UMAX * Scanner * * * * *
+
+ # scanner on /dev/scanner does not support lamp control
+ option lamp-control-available 0
+ /dev/scanner
+
+ - execute-request-sense:
+ values:
+ 0 = disabled
+ 1 = enabled
+ default = 0
+ If set to 1 umax_do_request_sense is called in
+ umax_do_calibration. This can hang the system
+ (but has been enabled until this version)
+
+ - scsi-buffer-size-min, scsi-buffer-size-max:
+ values: 4096-1048576, default min=32768, max=131072
+ Especially the minimum value is very important.
+ If this value is set too small the backend is not
+ able to send gamma tables to the scanner or to
+ do a correct color calibration. This may result in
+ strange color effects. If the minimum value is set
+ too large then the backend is not able to allocate
+ the requested scsi buffer size and aborts with
+ out of memory error. The default is 32KB, for
+ some scanners it should be increased to 64KB.
+
+ - scan-lines, preview-lines:
+ values: 1-65535,
+ default: scan-lines=40, preview-lines=10
+ define the maximum number of lines that are scanned
+ into one buffer
+
+ - force-preview-bit-rgb:
+ values:
+ 0 = disabled
+ 1 = enabled
+ default = 0
+ set preview bit in rgb real scan
+
+ - slow-speed, care-about-smearing:
+ values:
+ -1 = auto
+ 0 = disabled
+ 1 = enabled
+ default = -1
+ dangerous options, needed for some scanners
+ do not changed these options until you really know
+ what you do, you may destroy your scanner when you
+ define wrong values for this options
+
+ - calibration-full-ccd:
+ values:
+ -1 = auto
+ 0 = disabled
+ 1 = enabled
+ default = -1
+ do calibration for each pixel of ccd instead of
+ selected image
+
+ - calibration-width-offset:
+ values: -99999=auto, >-99999 set value
+ add an offset width to the calculated with for
+ image/ccd
+
+ - calibration-bytes-pixel:
+ values:
+ -1 = disabled
+ 0 = not set
+ 1 = 1 byte/pixel,
+ 2 = 2 bytes/pixel
+ use # bytes per pixel for calibration
+
+ - exposure-time-rgb-bind:
+ values:
+ -1 = automatically set by driver - if known
+ 0 = disabled (own selection for red, green and blue)
+ 1 = enabled (same values for red, green and blue)
+
+ - invert-shading-data:
+ values:
+ -1 = automatically set by driver - if known
+ 0 = disabled
+ 1 = enabled
+ default = -1
+ invert shading data before sending it back to the scanner
+
+ - lamp-control-available:
+ values:
+ 0 = automatically set by driver - if known
+ 1 = available
+ default = 0
+
+ - gamma-lsb-padded:
+ values:
+ -1 = automatically set by driver - if known
+ 0 = gamma data is msb padded
+ 1 = gamma data is lsb padded
+ default = -1
+
+ - handle-bad-sense-error:
+ values:
+ 0 = handle as device busy
+ 1 = handle as ok
+ 2 = handle as i/o error
+ 3 = ignore bad error code - continue sense handler,
+ default = 0
+
+ - scsi-maxqueue:
+ values:
+ 1..# (maximum defined at compile time)
+ default = 2
+ most scsi drivers allow internal command queueing with a depth
+ of 2 commands. In most cases it does not mprove anything when you
+ increase this value. When your scsi driver does not support any
+ command queueing you can try to set this value to 1.
+
+ The special device name must be a generic SCSI device or a symlink to
+ such a device. To find out to which device your scanner is assigned
+ and how you have to set the permissions of that device, have a look at
+ sane-scsi.
+
+
+
+SCSI ADAPTER TIPS
+ The ISA-SCSI-adapters that are shipped with some Umax-scanners are not
+ supported very well by Linux (I suggest not to use it), the PCI-SCSI-
+ adapters that come with some Umax-scanners are not supported at all (as
+ far as I know). On other platforms these SCSI-adapters are not sup-
+ ported. So you typically need to purchase another SCSI-adapter that is
+ supported by your platform. See the relevant hardware FAQs and HOWTOs
+ for your platform for more information.
+
+ The UMAX-scanners do block the scsi-bus for a few seconds while scan-
+ ning. It is not necessary to connect the scanner to its own SCSI-
+ adapter. But if you need short response time for your SCSI-harddisk
+ (e.g. if your computer is a file-server) or other scsi devices, I sug-
+ gest you use an own SCSI-adapter for your UMAX-scanner.
+
+ If you have any problems with your Umax scanner, check your scsi chain
+ (cable length, termination, ...).
+
+ See also: sane-scsi(5)
+
+
+
+FILES
+ The backend configuration file:
+ /usr/local/etc/sane.d/umax.conf
+
+ The static library implementing this backend:
+ /usr/local/lib/sane/libsane-umax.a
+
+ The shared library implementing this backend :
+ /usr/local/lib/sane/libsane-umax.so
+ (present on systems that support dynamic loading)
+
+
+
+ENVIRONMENT
+ SANE_DEBUG_UMAX
+ If the library was compiled with debug support enabled, this environ-
+ ment variable controls the debug level for this backend. E.g., a value
+ of 128 requests all debug output to be printed. Smaller levels reduce
+ verbosity: SANE_DEBUG_UMAX values
+
+ Number Remark
+ 0 print important errors (printed each time)
+ 1 print errors
+ 2 print sense
+ 3 print warnings
+ 4 print scanner-inquiry
+ 5 print informations
+ 6 print less important informations
+ 7 print called procedures
+ 8 print reader_process messages
+ 10 print called sane-init-routines
+ 11 print called sane-procedures
+ 12 print sane infos
+ 13 print sane option-control messages
+ Example:
+ export SANE_DEBUG_UMAX=8
+
+
+
+BUGS
+ X-resolutions greater than 600 dpi sometimes make problems
+
+
+
+SEE ALSO
+ sane(7)
+
+
+
+AUTHOR
+ Oliver Rauch
+
+
+
+EMAIL-CONTACT
+ Oliver.Rauch@Rauch-Domain.DE
+
+sane-backends 1.0.12-cvs 29 november 2002 sane-umax(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-umax1220u.5.html b/man/sane-umax1220u.5.html
new file mode 100644
index 00000000..7f3965aa
--- /dev/null
+++ b/man/sane-umax1220u.5.html
@@ -0,0 +1,145 @@
+
+
+sane-umax1220u.5
+
+
+sane-umax1220u.5
+
+
+
+sane-umax1220u(5) SANE Scanner Access Now Easy sane-umax1220u(5)
+
+
+
+NAME
+ sane-umax1220u - SANE backend for the UMAX Astra 1220U scanner
+
+
+
+DESCRIPTION
+ The sane-umax1220 library implements a SANE (Scanner Access Now Easy)
+ backend for the the UMAX Astra 1220U scanner.
+
+ For the latest information on this backend, please visit
+ http://umax1220u-sane.sourceforge.net/.
+
+
+
+UMAX ASTRA 2000U EXPERIMENTAL SUPPORT
+ This backend may also be able to drive the UMAX Astra 2000U. Some peo-
+ ple are successful with it, others report that the colors come out ter-
+ rible. Your milage may vary.
+
+ From Stephane (the author of sane-umax_pp), I learned that there are
+ differences in the way the color calibration is performed on the 1220U
+ and the 2000U and it may account for the problem. Stephane's backend
+ support the 2000P, the parallel port sibling to the 2000U. It may be
+ possible to use ideas and code from Stephane's backend to add complete
+ support for the 2000U to this backend. Since I do not have access to an
+ Astra 2000U, I do not plan to work on this -- any volunteers?
+
+
+
+CONFIGURATION
+ The configuration file for this backend resides in
+ /usr/local/etc/sane.d/umax1220u.conf.
+
+ Its contents is a list of device names that correspond to UMAX Astra
+ 1220U scanners. Empty lines and lines starting with a hash mark (#)
+ are ignored. A sample configuration file is shown below:
+
+ #usb vendor product
+ usb 0x1606 0x0010
+ # Device list for non-linux systems
+ /dev/scanner
+ /dev/usb/scanner0
+
+ When driving a Astra 2000U, use the product number 0x0030. See sane-
+ usb(5) for information on how to set the access permissions on the usb
+ device files.
+
+
+
+FILES
+ The backend configuration file:
+ /usr/local/etc/sane.d/umax1220u.conf
+
+ The static library implementing this backend:
+ /usr/local/lib/sane/libsane-umax1220u.a
+
+ The shared library implementing this backend :
+ /usr/local/lib/sane/libsane-umax1220u.so
+ (present on systems that support dynamic loading)
+
+
+
+ENVIRONMENT
+ SANE_DEBUG_UMAX1220U
+ If the library was compiled with debug support enabled, this environ-
+ ment variable controls the debug level for this backend. E.g., a value
+ of 128 requests all debug output to be printed. Smaller levels reduce
+ verbosity:
+
+ SANE_DEBUG_UMAX1220U values
+
+ Number Remark
+ 1 print failures
+ 2 print information
+ 3 print high-level function calls
+ 4 print high-level function checkpoints
+ 9 print mid-level function calls
+ 10 print mid-level function checkpoints
+ 80 print protocol-level function entry
+ 90 print protocol-level function exit
+
+ Example:
+ export SANE_DEBUG_UMAX1220U=10
+
+
+
+KNOWN BUGS
+ 600 dpi scanning may fail for large image sizes.
+
+ If you keep getting I/O errors, try cycling the power on your scanner
+ to reset it.
+
+ There is no way to cancel a scan, since the driver ignores sane_can-
+ cel().
+
+ If you try scanning an image which is too small, you will get I/O
+ errors. Be sure to adjust the scan area before doing a scan, since by
+ default, the scan area is zero.
+
+
+
+SEE ALSO
+ sane(7), sane-usb(5)
+
+ For latest bug fixes and information see
+ http://umax1220u-sane.sourceforge.net/
+
+
+
+AUTHOR
+ Marcio Luis Teixeira <marciot@users.sourceforge.net>
+
+
+
+EMAIL-CONTACT
+ umax1220u-sane-devel@lists.sourceforge.net
+
+
+
+REPORTING BUGS
+ 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 sane-umax1220u(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-umax_pp.5.html b/man/sane-umax_pp.5.html
new file mode 100644
index 00000000..fe9ccfe3
--- /dev/null
+++ b/man/sane-umax_pp.5.html
@@ -0,0 +1,245 @@
+
+
+sane-umax_pp.5
+
+
+sane-umax_pp.5
+
+
+
+sane-umax_pp(5) SANE Scanner Access Now Easy sane-umax_pp(5)
+
+
+
+NAME
+ sane-umax_pp - SANE backend for Umax Astra parallel port flatbed scan-
+ ners
+
+
+
+DESCRIPTION
+ The sane-umax_pp library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to Umax parallel port flatbed scanners.
+ The following scanners work with this backend:
+
+ Model:
+ --------------------
+ Astra 1220P
+ HP3200C
+ Astra 1600P
+ Astra 2000P
+
+ This backend handles 75x75, 150x150, 300x300, 600x600 and 600x1200 dpi
+ scan resolutions, in color and gray levels. There is a software lineart
+ mode.
+
+ These scanners share the same ASIC. Only parts such as CCD and ADC
+ change from one to another. They even all reports being UMAX Astra
+ 1220P via IEEE1284. There isn't software way to recognize them prop-
+ erly. Under windows, model is set by the driver installed, regardless
+ of the hardware.
+
+ EPP MODE ONLY
+ The current version of the backend use only EPP mode to communi-
+ cate with the scanner. PS/2 and SPP mode aren't implemented. It
+ is recommended that you set your parallel port to EPP in BIOS
+ with the current version of this backend. ECPEPP will only work
+ if you use a 2.4 kernel with ppdev character device support.
+
+ This backend does support parport sharing only if you have a kernel
+ with ppdev support.
+
+ Note that if you don't use the ppdev character device, the backend
+ needs to run as root. To allow user access to the scanner run the back-
+ end through the network interface (See saned(1) and sane-net(5)). A
+ more relaxed solution (security wise) is to add suid bit to the fron-
+ tend (See chmod(1)). The backend drop root priviledges as soon as it
+ can, right after gaining direct access to IO ports, which lessen risks
+ when being root.
+
+
+
+DEVICE NAMES
+ This backend expects device names of the form:
+
+ port value
+
+ Where value is the base address, or the ppdev device name of the port
+ your scanner is attached to. Known ports are 0x378, 0x278 and 0x3BC .
+ Or the name of the parallel port character device user interface, such
+ as /dev/parport0 for the linux ppdev, or /dev/ppi0 for FreeBSD ppi.
+ Under linux, if you are not sure which port your scanner is connected
+ to, may have a look at your /etc/modules.conf. Also typing dmesg|grep
+ parport in a command shell should show you a line like:
+ parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COM-
+ PAT,ECP,DMA]
+ telling you about port address and mode.
+
+ If you are using the linux ppdev character device, you will have to
+ specify the device name, which is /dev/parport0 for the first parallel
+ port. Check the permissions on /dev/paraport0, many linux distributions
+ restrict them for root only access. Get sure they are like:
+ crw-rw-rw- 1 root root 99, 0 mai 20 2002 /dev/parport0
+ crw-rw-rw- 1 root root 99, 1 mai 20 2002 /dev/parport1
+ crw-rw-rw- 1 root root 99, 2 mai 20 2002 /dev/parport2
+ crw-rw-rw- 1 root root 99, 3 mai 20 2002 /dev/parport3
+ The same apply with the /dev/ppi0 character device under FreeBSD.
+
+ You can rename any device using the
+
+ name devname
+ model model
+ vendor vendor
+
+ options. These options apply to the last port option.
+
+
+
+CONFIGURATION
+ Please make sure to edit umax_pp.conf before you use the backend.
+
+ The contents of the umax_pp.conf file is a list of options and device
+ names that correspond to Umax scanners. Empty lines and lines starting
+ with a hash mark (#) are ignored.
+
+ The height options supported are red-brightness, green-brightness,
+ blue-brightness, red-contrast, green-contrast, blue-contrast, astra,
+ and buffer.
+
+ Options red-brightness , green-brightness and blue-brightness allow you
+ to adjust the sensitivy of your scanner for the given color. Values
+ range from 0 (lowest brightness) to 15 (highest). If the advanced
+ option "Brightness" isn't checked in the frontend, the backend does
+ automatic brightness calibration, and do not use user provided values.
+
+ Options red-contrast , green-contrast and blue-contrast allow you to
+ adjust the contrast of your scanner for the given color. Values range
+ from 0 (lowest contrast) to 15 (highest).
+
+ Option astra allows you to change the model of your scanner. Current
+ auto detection is based on side effects on scanning when using 1220P
+ command set on other models, so it may fail on unkown hardware combina-
+ tion. Valid values are 1220, 1600 and 2000. It is usefull only when
+ autodetection fails to detect properly your scanner model. If your
+ scanner work properly but is reported wrongly, let it be that way. The
+ only valid case to change the model is when your scanner produces
+ 'black' or
+ 'inverted' scans. In this case you can put the model. Be aware that
+ it will prevent autodetection.
+
+ Option buffer 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.
+
+
+
+FILES
+ /usr/local/etc/sane.d/umax_pp.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-umax_pp.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-umax_pp.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_UMAX_PP
+ If the library was compiled with debug support enabled, this
+ environment variable controls the debug level for this backend.
+ E.g., a value of 128 requests all debug output to be printed.
+ Smaller levels reduce verbosity.
+
+ level debug output
+ ------- ------------------------------
+ 0 nothing
+ 1 errors
+ 2 warnings & minor errors
+ 3 additional information
+ 4 debug information
+ 5 code flow (not supported yet)
+ 6 special debug information
+
+ SANE_DEBUG_UMAX_PP_LOW
+ This variable sets the debug level for the SANE interface for
+ the Umax ASIC. Note that enabling this will spam your terminal
+ with some million lines of debug output.
+
+ level debug output
+ ------- -------------------------------
+ 0 nothing
+ 1 errors
+ 8 command blocks
+ 16 detailed code flow
+ 32 dump datafiles
+ 255 everything
+
+
+
+SEE ALSO
+ sane(7), sane-net(5), saned(1)
+
+
+ For latest bug fixes and information see
+ http://umax1220p.sourceforge.net/
+
+
+
+AUTHOR
+ St?phane VOLTZ <svoltz@wanadoo.fr>, man page derived from mustek_pp man
+ page by Jochen Eisinger <jochen.eisinger@gmx.net>
+
+
+
+BUG REPORTS
+ If something doesn't work, please contact me. But I need some informa-
+ tion about your scanner to be able to help you...
+
+ SANE version
+ run "scanimage -V" to determine this
+
+ the backend version and your scanner hardware
+ run "SANE_DEBUG_UMAX=255 scanimage -L 2>log" as root. If you
+ don't get any output from the umax_pp backend, make sure a line
+ "umax_pp" is included into your /usr/local/etc/sane.d/dll.conf.
+ If your scanner isn't detected, make sure you've defined the
+ right port address, or the correct device in your umax_pp.conf.
+
+ the name of your scanner/vendor
+ also a worthy information. Please also include the optical reso-
+ lution and lamp type of your scanner, both can be found in the
+ manual of your scanner.
+
+ any further comments
+ if you have comments about the documentation (what could be done
+ better), or you think I should know something, please include
+ it.
+
+sane-backends 1.0.12-cvs 16 September 2003 sane-umax_pp(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-usb.5.html b/man/sane-usb.5.html
new file mode 100644
index 00000000..5f43ab55
--- /dev/null
+++ b/man/sane-usb.5.html
@@ -0,0 +1,227 @@
+
+
+sane-usb.5
+
+
+sane-usb.5
+
+
+
+sane-usb(5) SANE Scanner Access Now Easy sane-usb(5)
+
+
+
+NAME
+ sane-usb - USB configuration tips for SANE
+
+
+
+DESCRIPTION
+ This manual page contains information on how to access scanners with a
+ USB interface. It focusses on two main topics: getting the scanner
+ detected by the operating system kernel and using it with SANE.
+
+ This page applies to most backends and scanners, as they use the
+ generic sanei_usb interface. However, there are some exceptions: USB
+ Scanners supported by the avision and microtek2 backends need special
+ USB kernel drivers, see sane-avision(5) and sane-microtek2(5) for
+ details. The sm3600 backend supports only access via libusb. See the
+ appropriate section in this manpage and sane-sm3600(5).
+
+
+
+QUICK START
+ This is a short HOWTO-like section. For the full details, read the fol-
+ lowing sections. The goal of this section is to get the scanner
+ detected by sane-find-scanner(5).
+
+ Run sane-find-scanner. If it lists your scanner with the correct vendor
+ and product ids, you are done. See section SANE ISSUES for details on
+ how to go on.
+
+ Sane-find-scanner lists your scanner, but can't detect the vendor- and
+ product ids? Scanning may work nevertheless, just try with section SANE
+ ISSUES. If it doesn't, install libusb (see section LIBUSB) or, if you
+ use Linux, upgrade your kernel (see section GENERIC KERNEL SCANNER
+ DRIVER).
+
+ Sane-find-scanner doesn't list your scanner? Does it work as root? If
+ yes, there is a permission issue. If sane-find-scanner lists a device
+ name starting with libusb:, read LIBUSB, otherwise have a look at the
+ section GENERIC KERNEL SCANNER DRIVER).
+
+ Nothing is found even as root? Either install libusb (see section
+ LIBUSB), or make sure, that the kernel scanner driver knows the ids of
+ your scanner (see section GENERIC KERNEL SCANNER DRIVER).
+
+
+
+USB ACCESS METHODS
+ Two methods for accessing USB devices are currently in use: direct
+ access using the kernel scanner driver and access over libusb. By
+ default, both methods are tried by SANE, if they are available. Cur-
+ rently USB access is tested for Linux (kernel, libusb), FreeBSD (ker-
+ nel, libsub), NetBSD (libusb), OpenBSD (kernel, libusb) and MacOS X
+ (libusb). Testing on MacOS X is very limited and not all scanners seem
+ to work reliably with the BSDs. For installation issues, also check the
+ /usr/local/doc/sane-1.0.12-cvs/README.platform files.
+
+ Generally speaking, if your scanner works with one method, there is no
+ need to switch to the other one.
+
+ Libusb is the more general approach and is able to access any scanner.
+ Also, it supports more platforms.
+
+ Autodetecting scanners and using USB control messages with the kernel
+ access method only works with recent (>=v2.4.12) Linux kernels. If you
+ need one of these two features on a different platform, use libusb
+ instead. Also, the kernel scanner driver may be removed from Linux
+ 2.5/2.6 in future so libusb will be the only access method.
+
+
+
+LIBUSB
+ SANE can only use libusb 0.1.6 or newer. It needs to be installed at
+ build-time.
+
+ Libusb can only access your scanner if it's not claimed by the kernel
+ scanner driver. If you want to use libusb, unload the kernel driver
+ (e.g. rmmod scanner under Linux) or disable the driver when compiling a
+ new kernel. For Linux, your kernel needs support for the USB filesystem
+ (usbfs). For kernels older than 2.4.19, replace "usbfs" with "usbdevfs"
+ because the name has changed. This filesystem must be mounted. That's
+ done automatically at boot time, if /etc/fstab contains a line like
+ this:
+
+ none /proc/bus/usb usbfs defaults 0 0
+
+ The permissions for the device files used by libusb must be adjusted
+ for user access. Otherwise only root can use SANE devices. For Linux,
+ the devices are located in /proc/bus/usb/. There are directories named
+ e.g. "001" (the bus name) containing files "001", "002" etc. (the
+ device files). The right device files can be found out by running scan-
+ image -L as root. Setting permissions with "chmod" is not permanent,
+ however. They will be resetted after reboot or replugging the scanner.
+ It's also possible to mount the usbfs with the option "devmode=0666",
+ e.g. by using the following line in /etc/fstab:
+
+ none /proc/bus/usb usbfs defaults,devmode=0666 0 0
+
+ However, this way everyone has access to all USB devices. Another way
+ to set permissions is to use the hotplug utilities (http://linux-hot-
+ plug.sourceforge.net/), which support dynamic setting of access permis-
+ sions. Last, the frontends can be run as root. However, that's not rec-
+ ommended for security reasons.
+
+ For the BSDs, the device files are named /dev/ugen*. Use chmod to
+ apply appropriate permissions.
+
+
+
+GENERIC KERNEL SCANNER DRIVER
+ Ensure that the access permissions for the USB device are set appropri-
+ ately. We recommend to add a group "scanner" to /etc/group which con-
+ tains all users that should have access to the scanner. The permission
+ of the device should then be set to allow group read and write access.
+ For example, if the scanner is at USB device /dev/usb/scanner0, then
+ the following two commands would set the permission correctly:
+
+ $ chgrp scanner /dev/usb/scanner0
+ $ chmod 660 /dev/usb/scanner0
+
+ If your scanner isn't detected automatically by your operating system's
+ scanner driver, you need to tell the kernel the vendor and product ids
+ of your scanner. For Linux, this can be done with modprobe parameters:
+ First, remove the scanner module (rmmod scanner), then load it again:
+ modprobe scanner vendor=0x0001 product=0x0002. Use the appropriate
+ vendor and product ids (e.g. from /var/log/messages, dmesg, or cat
+ /proc/bus/usb/devices). Some scanners supported by the gt68xx backend
+ are not supported by the current version of the generic scanner driver.
+ See sane-gt68xx(5) for details. For these scanners, there will be a
+ message concerning "only 2 or three endpoints" in syslog.
+
+ For OpenBSD the kernel may need to be recompiled. For details look at
+ /usr/local/doc/sane-1.0.12-cvs/README.openbsd. Similar approaches
+ should be used for the other BSDs.
+
+ Linux kernel messages in syslog like "kernel: scanner.c:
+ open_scanner(1): Unable to access minor data" can be ignored. They are
+ generated when SANE scans all available USB devices for scanners.
+
+
+
+SANE ISSUES
+ This section assumes that your scanner is detected by sane-find-scan-
+ ner. It doesn't make sense to go on, if this is not the case. While
+ sane-find-scanner is able to detect any USB scanner, actual scanning
+ will only work if the scanner is supported by a SANE backend. Informa-
+ tion on the level of support can be found on the SANE webpage
+ (http://www.mostang.com/sane/), and the individual backend manpages.
+
+ Most backends can detect USB scanners automatically using "usb" config-
+ uration file lines. This method allows to identify scanners by the USB
+ vendor and product numbers. The syntax for specifying a scanner this
+ way is:
+
+ usb VENDOR PRODUCT
+
+ where VENDOR is the USB vendor id, and PRODUCT is the USB product id of
+ the scanner. Both ids are non-negative integer numbers in decimal or
+ hexadecimal format. The correct values for these fields can be found by
+ looking into the syslog (e.g., /var/log/messages) or under Linux by
+ issuing the command "cat /proc/bus/usb/devices/". This is an example
+ of a config file line:
+
+ usb 0x055f 0x0006
+
+ would have the effect that all USB devices in the system with a vendor
+ id of 0x55f and a product id of 0x0006 would be probed and recognized
+ by the backend.
+
+ If your scanner is not detected automatically, it may be necessary to
+ edit the appropriate backend configuration file before using SANE for
+ the first time. For most systems, the configuration file should list
+ the name of the USB device file that the scanner is connected to (e.g.,
+ under Linux, /dev/usb/scanner0 or /dev/usbscanner0 is such a USB
+ device, the device file for FreeBSD is e.g. /dev/uscanner0). If
+ libusb is used, the device name looks like the following example:
+ libusb:001:002.
+
+ For a detailed description of each backend's configuration file, please
+ refer to the relevant backend manual page (e.g. sane-mustek_usb(5) for
+ Mustek USB scanners).
+
+ Do not create a symlink from /dev/scanner to the USB device because
+ this link is used by the SCSI backends. The scanner may be confused if
+ it receives SCSI commands.
+
+
+
+ENVIRONMENT
+ SANE_DEBUG_SANEI_USB
+ If the library was compiled with debug support enabled, this
+ environment variable controls the debug level for the USB I/O
+ subsystem. E.g., a value of 128 requests all debug output to be
+ printed. Smaller levels reduce verbosity. Values greater than 4
+ enable libusb debugging (if available). Example: export
+ SANE_DEBUG_SANEI_USB=4.
+
+
+
+SEE ALSO
+ sane(7), sane-find-scanner(1), sane-"backendname"(5), sane-scsi(5)
+
+
+
+AUTHOR
+ Henning Meier-Geinitz
+
+sane-backends 1.0.12-cvs 27 Nov 2002 sane-usb(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-v4l.5.html b/man/sane-v4l.5.html
new file mode 100644
index 00000000..483b51bc
--- /dev/null
+++ b/man/sane-v4l.5.html
@@ -0,0 +1,115 @@
+
+
+sane-v4l.5
+
+
+sane-v4l.5
+
+
+
+sane-v4l(5) SANE Scanner Access Now Easy sane-v4l(5)
+
+
+
+NAME
+ sane-v4l - SANE interface for Video for Linux API
+
+
+
+DESCRIPTION
+ The sane-v4l library implements a SANE (Scanner Access Now Easy) back-
+ end that provides generic access to video cameras and similar equipment
+ using the V4L (Video for Linux) API.
+
+ This is ALPHA software. Really! Important features are missing and
+ there are lots of bugs. The code is currently only tested on a Linux
+ 2.4 system with a Hauppauge WinTV video card.
+
+
+
+DEVICE NAMES
+ This backend expects device names of the form:
+
+ special
+
+ Where special is the UNIX path-name for the special device that corre-
+ sponds to the v4l device. The special device name must be a v4l device
+ or a symlink to such a device. For example, such a device name could
+ be /dev/video0 or /dev/bttv0.
+
+
+
+CONFIGURATION
+ The contents of the v4l.conf file is a list of device names that corre-
+ spond to v4l devices. Empty lines and lines starting with a hash mark
+ (#) are ignored. A sample configuration file is shown below:
+
+ /dev/bttv0
+ # this is a comment
+ /dev/video3
+
+
+
+FILES
+ /usr/local/etc/sane.d/v4l.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-v4l.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-v4l.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+ SANE_DEBUG_V4L
+ 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.
+
+
+
+AUTHOR
+ Juergen G. Schimmer, Henning Meier-Geinitz
+
+
+
+BUGS:
+ 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.
+
+
+
+SEE ALSO
+ sane(7), xcam(1).
+
+sane-backends 1.0.12-cvs 28 Aug 2002 sane-v4l(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane.7.html b/man/sane.7.html
new file mode 100644
index 00000000..4103bc20
--- /dev/null
+++ b/man/sane.7.html
@@ -0,0 +1,642 @@
+
+
+sane.7
+
+
+sane.7
+
+
+
+sane(7) SANE Scanner Access Now Easy sane(7)
+
+
+
+NAME
+ sane - Scanner Access Now Easy: API for accessing scanners
+
+
+
+DESCRIPTION
+ SANE is an application programming interface (API) that provides stan-
+ dardized access to any raster image scanner hardware. The standardized
+ interface makes it possible to write just one driver for each scanner
+ device instead of one driver for each scanner and application.
+
+ While SANE is primarily targeted at a UNIX environment, the standard
+ has been carefully designed to make it possible to implement the API on
+ virtually any hardware or operating system.
+
+ This manual page provides a summary of the information available about
+ SANE.
+
+ If you have trouble getting your scanner detected, read the PROBLEMS
+ section.
+
+
+
+TERMINOLOGY
+ An application that uses the SANE interface is called a SANE frontend.
+ A driver that implements the SANE interface is called a SANE backend.
+ A meta backend provides some means to manage one or more other back-
+ ends.
+
+
+
+SOFTWARE PACKAGES
+ The package `sane-backends' contains a lot of backends, documentation
+ (including the SANE standard), networking support, and the command line
+ frontend `scanimage'. The frontends `xscanimage', `xcam', and
+ `scanadf' are included in the package `sane-frontends'. Both packages
+ can be downloaded from the SANE homepage
+ (http://www.mostang.com/sane/). Information about other frontends and
+ backends can be found on the frontend page
+ (http://www.mostang.com/sane/frontends.html).
+
+
+
+GENERAL INFORMATION
+ The following sections provide short descriptions and links to more
+ information about several aspects of SANE. A name with a number in
+ parenthesis (e.g. `sane-dll(5)') points to a manual page. In this case
+ `man 5 sane-dll' will display the page. Entries like
+ `/usr/local/doc/sane-1.0.12-cvs/sane.tex' are references to text files
+ that were copied to the SANE documentation directory
+ (/usr/local/doc/sane-1.0.12-cvs/) during installation. Everything else
+ is a URL to a resource on the web.
+
+ SANE homepage
+ Information on all aspects of SANE including a tutorial and a link to
+ the SANE FAQ can be found on the SANE homepage:
+ http://www.mostang.com/sane/.
+
+ SANE device lists
+ The SANE device lists contain information about the status of SANE
+ support for a specific device. If your scanner is not listed there
+ (either supported or unsupported), please contact us. See section HOW
+ CAN YOU HELP SANE for details. There are lists for specific releases
+ of SANE, for the current development version and a search engine:
+ http://www.mostang.com/sane/sane-supported-devices.html. The lists
+ are also installed on your system at /usr/local/doc/sane-1.0.12-cvs/.
+
+ SANE mailing list
+ There is a mailing list for the purpose of discussing the SANE stan-
+ dard and its implementations: sane-devel. Despite its name, the list
+ is not only intended for developers, but also for users. Since this
+ is currently the only mailing list devoted to SANE, it's perfectly OK
+ to ask questions that are not strictly related to SANE development.
+ How to subscribe and unsubscribe:
+ http://www.mostang.com/sane/mail.html.
+
+ SANE IRC channel
+ The IRC (Internet Relay Chat) channel #sane can be found on the
+ Freenode network (irc.freenode.net). It's for discussing SANE prob-
+ lems, talking about development and general SANE related chatting.
+ Before asking for help, please read the other documentation mentioned
+ in this manual page.
+
+ Compiling and installing SANE
+ Look at /usr/local/doc/sane-1.0.12-cvs/README and the os-dependent
+ README files for information about compiling and installing SANE.
+
+ SCSI configuration
+ For information about various systems and SCSI controllers see
+ sane-scsi(5).
+
+ USB configuration
+ For information about USB configuration see sane-usb(5).
+
+
+
+FRONTENDS AND MISCELLANEOUS PROGRAMS
+ scanimage
+ Command-line frontend. See scanimage(1).
+
+ saned
+ SANE network daemon that allows remote clients to access image acqui-
+ sition devices available on the local host. See saned(1).
+
+ sane-find-scanner
+ Command-line tool to find SCSI and USB scanners and determine their
+ Unix device files. See sane-find-scanner(1).
+
+ Also, have a look at the sane-frontends package (including xscanimage,
+ xcam, and scanadf) and the frontend information page at
+ http://www.mostang.com/sane/sane-frontends.html.
+
+
+
+BACKENDS FOR SCANNERS
+ abaton
+ The SANE backend for Abaton flatbed scanners supports the Scan 300/GS
+ (8bit, 256 levels of gray) and the Scan 300/S (black and white,
+ untested). See sane-abaton(5) for details.
+
+ agfafocus
+ This backend supports AGFA Focus scanners and the Siemens S9036
+ (untested). See sane-agfafocus(5) for details.
+
+ apple
+ The SANE backend for Apple flatbed scanners supports the following
+ scanners: AppleScanner, OneScanner and ColorOneScanner. See
+ sane-apple(5) for details.
+
+ artec
+ The SANE Artec backend supports several Artec/Ultima SCSI flatbed
+ scanners as well as the BlackWidow BW4800SP and the Plustek 19200S.
+ See sane-artec(5) for details.
+
+ artec_eplus48u
+ The SANE artec_eplus48u backend supports the scanner Artec E+ 48U and
+ re-badged models like Tevion MD 9693, Medion MD 9693, Medion MD 9705
+ and Trust Easy Webscan 19200. See sane-artec_eplus48u(5) for details.
+
+ as6e
+ This is a SANE backend for using the Artec AS6E parallel port inter-
+ face scanner. See sane-as6e(5) for details.
+
+ avision
+ 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 sane-avision(5) for details.
+
+ bh
+ The bh backend provides access to Bell+Howell Copiscan II series doc-
+ ument scanners. See sane-bh(5) for details.
+
+ canon
+ The canon backend supports the CanoScan 300, CanoScan 600, and
+ CanoScan 2700F SCSI flatbed scanners. See sane-canon(5) for details.
+
+ canon630u
+ The canon630u backend supports the CanoScan 630u and 636u USB scan-
+ ners. See sane-canon630u(5) for details.
+
+ canon_pp
+ The canon_pp backend supports the CanoScan FB330P, FB630P, N340P and
+ N640P parallel port scanners. See sane-canon_pp(5) for details.
+
+ coolscan
+ This is a SANE backend for Nikon Coolscan film-scanners. See
+ sane-coolscan(5) for details.
+
+ coolscan2
+ This is a SANE backend for Nikon Coolscan film-scanners. See
+ sane-coolscan2(5) or http://coolscan2.sourceforge.net for details.
+
+ epson
+ The SANE epson backend provides support for Epson SCSI, parallel port
+ and USB flatbed scanners. See sane-epson(5) for details.
+
+ fujitsu
+ The fujitsu backend provides support for Fujitsu 3091, 3093, 3096 and
+ fi-4340 SCSI scanners. See sane-fujitsu(5) for details.
+
+ gt68xx
+ 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 sane-gt68xx(5) for details.
+
+ hp
+ The SANE hp backend provides access to Hewlett-Packard ScanJet scan-
+ ners which support SCL (Scanner Control Language by HP). See
+ sane-hp(5) for details.
+
+ hpsj5s
+ The SANE backend for the Hewlett-Packard ScanJet 5S scanner. See
+ sane-hpsj5s(5) for details.
+
+ hp5400
+ The SANE backend for the Hewlett-Packard ScanJet 54XXC series. See
+ sane-hp5400(5) for details.
+
+ ibm
+ The SANE backend for some IBM and Ricoh SCSI scanners. See
+ sane-ibm(5) for details.
+
+ leo
+ This backend supports the Leo S3 and the Across FS-1130, which is a
+ re-badged LEO FS-1130 scanner. See sane-leo(5) for details.
+
+ ma1509
+ The ma1509 backend supports the Mustek BearPaw 1200F USB flatbed
+ scanner. See sane-ma1509(5) for details.
+
+ matsushita
+ This backend supports some Panasonic KVSS high speed scanners. See
+ sane-matsushita(5) for details.
+
+ microtek
+ The microtek backend provides access to the "second generation"
+ Microtek scanners with SCSI-1 command set. See sane-microtek(5) for
+ details.
+
+ microtek2
+ The microtek2 backend provides access to some Microtek scanners with
+ a SCSI-2 command set. See sane-microtek2(5) for details.
+
+ mustek
+ 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 sane-mustek(5) for
+ details.
+
+ mustek_pp
+ The mustek_pp backend provides access to Mustek parallel port flatbed
+ scanners. See sane-mustek_pp(5) for details.
+
+ mustek_usb
+ The mustek_usb backend provides access to some Mustek ScanExpress USB
+ flatbed scanners. See sane-mustek_usb(5) for details.
+
+ nec
+ The SANE nec backend supports the NEC PC-IN500/4C SCSI scanner. See
+ sane-nec(5) for details.
+
+ pie
+ The pie backend provides access to Pacific Image Electronics (PIE)
+ and Devcom SCSI flatbed scanners. See sane-pie(5) for details.
+
+ plustek
+ 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 sane-plustek(5) for details.
+
+ ricoh
+ The ricoh backend provides access to the following Ricoh flatbed
+ scanners: IS50 and IS60. See sane-ricoh(5) for details.
+
+ s9036
+ The s9036 backend provides access to Siemens 9036 flatbed scanners.
+ See sane-s9036(5) for details.
+
+ sceptre
+ The sceptre backend provides access to the Sceptre S1200 flatbed
+ scanner. See sane-sceptre(5)
+ for details.
+
+ sharp
+ The SANE sharp backend supports Sharp SCSI scanners. See
+ sane-sharp(5) for details.
+
+ sm3600
+ The SANE sm3600 backend supports the Microtek ScanMaker 3600 USB
+ scanner. See sane-sm3600(5) for details.
+
+ snapscan
+ The snapscan backend supports AGFA SnapScan flatbed scanners. See
+ sane-snapscan(5) for details.
+
+ sp15c
+ This backend supports the Fujitsu FCPA ScanPartner 15C flatbed scan-
+ ner. See sane-sp15c(5) for details.
+
+ st400
+ The sane-st400 backend provides access to Siemens ST400 and ST800.
+ See sane-st400(5) for details.
+
+ tamarack
+ The SANE tamarack backend supports Tamarack Artiscan flatbed scan-
+ ners. See sane-tamarack(5) for details.
+
+ teco1 teco2 teco3
+ The SANE teco1, teco2 and teco3 backends support some TECO scanners,
+ usually sold under the Relisys, Trust, Primax, Piotech, Dextra names.
+ See sane-teco1(5), sane-teco2(5) and sane-teco3(5) for details.
+
+ umax
+ The sane-umax backend provides access to several UMAX-SCSI-scanners
+ and some Linotype Hell SCSI-scanners. See sane-umax(5) for details.
+
+ umax_pp
+ The sane-umax_pp backend provides access to Umax parallel port
+ flatbed scanners and the HP 3200C. See sane-umax_pp(5) for details.
+
+ umax1200u
+ The sane-umax1220u backend supports the UMAX Astra 1220U (USB)
+ flatbed scanner (and also the UMAX Astra 2000U, sort of). See
+ sane-umax1220u(5) for details.
+
+ Also, have a look at the backend information page at
+ http://www.mostang.com/sane/sane-supported-devices.html and the list of
+ projects in /usr/local/doc/sane-1.0.12-cvs/PROJECTS.
+
+
+
+BACKENDS FOR DIGITAL CAMERAS
+ dc210
+ Backend for Kodak DC210 Digital Camera. See sane-dc210(5).
+
+ dc240
+ Backend for Kodak DC240 Digital Camera. See sane-dc240(5).
+
+ dc25
+ Backend for Kodak DC20/DC25 Digital Cameras. See sane-dc25(5).
+
+ dmc
+ Backend for the Polaroid Digital Microscope Camera. See sane-dmc(5).
+
+ gphoto2
+ Backend for digital cameras supported by the gphoto2 library package.
+ (See http://www.gphoto.org 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 SANE backend. See
+ sane-gphoto2(5).
+
+ qcam
+ Backend for Connectix QuickCam cameras. See sane-qcam(5).
+
+ Also, have a look at the backend information page at
+ http://www.mostang.com/sane/sane-supported-devices.html and the list of
+ projects in /usr/local/doc/sane-1.0.12-cvs/PROJECTS.
+
+
+
+MISCELLANEOUS BACKENDS
+ dll
+ The sane-dll library implements a SANE backend that provides access
+ to an arbitrary number of other SANE backends by dynamic loading. See
+ sane-dll(5).
+
+ net
+ The SANE network daemon saned provides access to scanners located on
+ different computers in connection with the net backend. See
+ sane-net(5) and saned(1).
+
+ pnm
+ PNM image reader pseudo-backend. The purpose of this backend is pri-
+ marily to aid in debugging of SANE frontends. See sane-pnm(5).
+
+ pint
+ Backend for scanners that use the PINT (Pint Is Not Twain) device
+ driver. The PINT driver is being actively developed on the OpenBSD
+ platform, and has been ported to a few other *nix-like operating sys-
+ tems. See sane-pint(5).
+
+ test
+ The SANE test backend is for testing frontends and the SANE installa-
+ tion. It provides test pictures and various test options. See
+ sane-test(5).
+
+ v4l
+ The sane-v4l library implements a SANE backend that provides generic
+ access to video cameras and similar equipment using the V4L (Video
+ for Linux) API. See sane-v4l(5).
+
+ Also, have a look at the backend information page at
+ http://www.mostang.com/sane/sane-supported-devices.html and the list of
+ projects in /usr/local/doc/sane-1.0.12-cvs/PROJECTS.
+
+
+
+CHANGING THE TOP-LEVEL BACKEND
+ By default, all SANE backends (drivers) are loaded dynamically by the
+ sane-dll meta backend. If you have any questions about the dynamic
+ loading, read sane-dll(5). SANE frontend can also be linked to other
+ backends directly by copying or linking a backend to libsane.so in
+ /usr/local/lib/sane.
+
+
+
+DEVELOPER'S DOCUMENTATION
+ It's not hard to write a SANE backend. It can take some time, however.
+ You should have basic knowledege of C and enough patience to work
+ through the documentation and find out how your scanner works. Appended
+ is a list of some documents that help to write backends and frontends.
+
+ The SANE standard defines the application programming interface (API)
+ that is used to communicate between frontends and backends. It can be
+ found at /usr/local/doc/sane-1.0.12-cvs/sane.ps (if latex is installed
+ on your system) and on the SANE website:
+ http://www.mostang.com/sane/html/ (HTML), or
+ http://www.mostang.com/sane/sane.ps (Postscript).
+
+ There is some more information for programmers in
+ /usr/local/doc/sane-1.0.12-cvs/backend-writing.txt. Most of the inter-
+ nal SANE routines (sanei) are documented using doxygen:
+ http://sanei.meier-geinitz.de/. Before a new backend or frontend
+ project is started, have a look at
+ /usr/local/doc/sane-1.0.12-cvs/PROJECTS for projects that are planned
+ or not yet included into the SANE distribution and at the todo list:
+ /usr/local/doc/sane-1.0.12-cvs/TODO.
+
+ There are some links on how to find out about the protocol of a scan-
+ ner: http://www.meier-geinitz.de/sane/misc/develop.html.
+
+ If you start writing a backend or frontend or any other part of SANE,
+ please contact the sane-devel mailing list for coordination so the same
+ work isn't done twice.
+
+
+
+FILES
+ /usr/local/etc/sane.d/*.conf
+ The backend configuration files.
+
+ /usr/local/lib/sane/libsane-*.a
+ The static libraries implementing the backends.
+
+ /usr/local/lib/sane/libsane-*.so
+ The shared libraries implementing the backends (present on sys-
+ tems that support dynamic loading).
+
+ /usr/local/doc/sane-1.0.12-cvs/*
+ SANE documentation: The standard, READMEs, text files for back-
+ ends etc.
+
+
+
+PROBLEMS
+ If your device isn't found but you know that it is supported, make sure
+ that it is detected by your operating system. For SCSI and USB scan-
+ ners, use the sane-find-scanner tool (see sane-find-scanner(1) for
+ details). It prints one line for each scanner it has detected and some
+ comments (#). If sane-find-scanner finds your scanner only as root but
+ not as normal user, the permissions for the device files are not
+ adjusted correctly. If the scanner isn't found at all, the operating
+ system hasn't detected it and may need some help. Depending on the type
+ of your scanner, read sane-usb(5) or sane-scsi(5). If your scanner (or
+ other device) is not connected over the SCSI bus or USB, read the back-
+ end's manual page for details on how to set it up.
+
+ Now your scanner is detected by the operating system but not by SANE?
+ Try scanimage -L. If the scanner is not found, check that the back-
+ end's name is mentioned in /usr/local/etc/sane.d/dll.conf. Some back-
+ ends are commented out by default. Remove the comment sign for your
+ backend in this case. Also some backends aren't compiled at all if one
+ of their prerequisites are missing. Examples include dc210, dc240,
+ canon_pp, hpsj5s, gphoto2, pint, qcam, v4l, net, sm3600, snapscan, pnm.
+ If you need one of these backends and they aren't available, read the
+ build instructions in the README file and the individual manual pages
+ of the backends.
+
+ Another reason for not beeing detected by scanimage -L may be a missing
+ or wrong configuration in the backend's configuration file. While SANE
+ tries to automatically find most scanners, some can't be setup cor-
+ rectly without the intervention of the administrator. Also on some
+ operating systems auto-detection may not work. Check the backend's man-
+ ual page for details.
+
+ If your scanner is still not found, try setting the various environment
+ variables that are available to assist in debugging. The environment
+ variables are documented in the relevant manual pages. For example, to
+ get the maximum amount of debug information when testing a Mustek SCSI
+ scanner, set environment variables SANE_DEBUG_DLL, SANE_DEBUG_MUSTEK,
+ and SANE_DEBUG_SANEI_SCSI to 128 and then invoke scanimage -L . The
+ debug messages for the dll backend tell if the mustek backend was found
+ and loaded at all. The mustek messages explain what the mustek backend
+ is doing while the SCSI debugging shows the low level handling. If you
+ can't find out what's going on by checking the messages carefully, con-
+ tact the sane-devel mailing list for help (see REPORTING BUGS below).
+
+ Now that your scanner is found by scanimage -L, try to do a scan: scan-
+ image >image.pnm. This command starts a scan for the default scanner
+ with default settings. All the available options are listed by running
+ scanimage --help. If scanning aborts with an error message, turn on
+ debugging as mentioned above. Maybe the configuration file needs some
+ tuning, e.g. to setup the path to a firmware that is needed by some
+ scanners. See the backend's maunal page for details. If you can't find
+ out what's wrong, contact sane-devel.
+
+ To check that the SANE libraries are installed correctly you can use
+ the test backend, even if you don't have a scanner or other SANE
+ device:
+
+ scanimage -d test -T
+
+ You should get a list of PASSed tests. You can do the same with your
+ backend by changing "test" to your backend's name.
+
+ So now scanning with scanimage works and you want to use one of the
+ graphical frontends like xsane, xscanimage, or quiteinsane but those
+ frontends don't detect your scanner? One reason may be that you
+ installed two versions of SANE. E.g. the version that was installed by
+ your distribution in /usr and one you installed from source in
+ /usr/local/. Make sure that only one version is installed. Another
+ possible reason is, that your system's dynamic loader can't find the
+ SANE libraries. For Linux, make sure that /etc/ld.so.conf contains
+ /usr/local/lib and does not contain /usr/local/lib/sane. See also the
+ documentation of the frontends.
+
+
+
+HOW CAN YOU HELP SANE
+ We appreciate any help we can get. Here are some topics on which you
+ can work:
+
+ Writing backends
+ 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.
+
+ Writing frontends
+ 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.
+
+ Reporting unsupported scanners
+ 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 sane-find-scanner -v -v. For Linux: If it's a SCSI
+ scanner, show us the output of cat /proc/scsi/scsi, for a USB
+ scanner: cat /proc/bus/usb/devices (if the file is not there, do
+ mount -t usbdevfs /proc/bus/usb /proc/bus/usb). See CONTACT
+ section.
+
+ Reporting bugs and missing features
+ If you think something in SANE 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.
+
+ Adding and fixing documentation
+ 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.
+
+ Translations
+ 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 po/ directory
+ in the source code.
+
+ Success reports
+ If you had success using SANE we want to know about that, too.
+ Especially if your scanner is not in the lists yet or is marked
+ "untested".
+
+
+
+CONTACT
+ 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
+ /usr/local/doc/sane-1.0.12-cvs/AUTHORS file or the backend's manpage.
+ If the author isn't marked as `active maintainer' or doesn't answer,
+ you can also contact the SANE mailing list sane-devel (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.
+
+ If you want to report bugs concerning security, compilation, installa-
+ tion, porting, and documentation of SANE, you can also contact the
+ author of this manual page: <henning@meier-geinitz.de>.
+
+
+
+SEE ALSO
+ saned(1), sane-find-scanner(1), scanimage(1), sane-abaton(5),
+ sane-agfafocus(5), sane-apple(5), sane-artec(5),
+ sane-artec_eplus48u(5), sane-as6e(5), sane-avision(5), sane-bh(5),
+ sane-canon(5), sane-canon630u(5), sane-canon_pp(5), sane-coolscan2(5),
+ sane-coolscan(5), sane-dc210(5), sane-dc240(5), sane-dc25(5),
+ sane-dll(5), sane-dmc(5), sane-epson(5), sane-fujitsu(5),
+ sane-gphoto2(5), sane-gt68xx(5), sane-hp(5), sane-hpsj5s(5),
+ sane-hp5400(5) sane-ibm(5), sane-leo(5), sane-ma1509(5), sane-mat-
+ sushita(5), sane-microtek2(5), sane-microtek(5), sane-mustek(5),
+ sane-mustek_pp(5), sane-mustek_usb(5), sane-nec(5), sane-net(5),
+ sane-pie(5), sane-pint(5), sane-plustek(5), sane-pnm(5), sane-qcam(5),
+ sane-ricoh(5), sane-s9036(5), sane-sceptre(5), sane-scsi(5),
+ sane-sharp(5), sane-sm3600(5), sane-snapscan(5), sane-sp15c(5),
+ sane-st400(5), sane-tamarack(5), sane-teco1(5), sane-teco2(5),
+ sane-teco3(5), sane-test(5), sane-umax1220u(5), sane-umax(5),
+ sane-umax_pp(5), sane-usb(5), sane-v4l(5)
+
+
+
+AUTHOR
+ David Mosberger-Tang and many many more (see
+ /usr/local/doc/sane-1.0.12-cvs/AUTHORS for details). This man page was
+ written by Henning Meier-Geinitz. Quite a lot of text was taken from
+ the SANE standard, several man pages, and README files.
+
+sane-backends 1.0.12-cvs 19 Apr 2003 sane(7)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/saned.1.html b/man/saned.1.html
new file mode 100644
index 00000000..0f938ba9
--- /dev/null
+++ b/man/saned.1.html
@@ -0,0 +1,181 @@
+
+
+saned.1
+
+
+saned.1
+
+
+
+saned(1) SANE Scanner Access Now Easy saned(1)
+
+
+
+NAME
+ saned - SANE network daemon
+
+
+
+SYNOPSIS
+ saned [-d|-s [n]]
+
+
+
+DESCRIPTION
+ saned is the SANE (Scanner Access Now Easy) daemon that allows remote
+ clients to access image acquisition devices available on the local
+ host.
+
+
+
+OPTIONS
+ The -d and -s flags request that saned run in debug mode (as opposed to
+ inetd(8) mode). In this mode, saned explicitly waits for a connection
+ request. When compiled with debugging enabled, these flags may be fol-
+ lowed by a number to request debug info. The larger the number, the
+ more verbose the debug output. E.g., -d128 will request printing of
+ all debug info. Debug level 0 means no debug output at all. The default
+ value is 2. If flag -d is used, the debug messages will be printed to
+ stderr while -s requests using syslog.
+
+ If saned is run from inetd or xinetd, no option can be given.
+
+
+
+CONFIGURATION
+ First and foremost: saned is not intended to be exposed to the internet
+ or other non-trusted networks. Make sure that access is limited by tcp-
+ wrappers and/or a firewall setup. Don't depend only on saned's own
+ authentification. Don't run saned as root if it's not necessary. And do
+ not install saned as setuid root.
+
+ The contents of the saned.conf file is a list of host names or IP
+ addresses that are permitted to use local SANE devices. Connections
+ from localhost are always permitted. Empty lines and lines starting
+ with a hash mark (#) are ignored. A line containing the single charac-
+ ter ``+'' is interpreted to match any hostname. This allows any remote
+ machine to use your scanner and may present a security risk, so this
+ shouldn't be used unless you know what you're doing. A sample configu-
+ ration file is shown below:
+
+ scan-client.somedomain.firm
+ # this is a comment
+ 192.168.0.1
+ ::1
+
+ The case of the host names does not matter, so AHost.COM is considered
+ identical to ahost.com. IPv6 addresses should always be specified in
+ their compressed form.
+
+ For saned to work properly, it is also necessary to add a configuration
+ line to /etc/inetd.conf. Note that your inetd must support IPv6 if you
+ want to connect to saned over IPv6 ; xinetd and openbsd-inetd are known
+ to support IPv6, check the documentation for your inetd daemon.
+
+ The configuration line normally looks like this:
+
+ sane stream tcp nowait saned.saned /usr/local/sbin/saned saned
+
+ However, if your system uses tcpd(8) for additional security screening,
+ you may want to disable saned access control by putting ``+'' in
+ saned.conf and use a line of the following form in /etc/inetd.conf
+ instead:
+
+ sane stream tcp nowait saned.saned /usr/sbin/tcpd
+ /usr/local/sbin/saned
+
+ Note that both examples assume that there is a saned group and a saned
+ user. If you follow this example, please make sure that the access
+ permissions on the special device are set such that saned can access
+ the scanner (the program generally needs read and write access to scan-
+ ner devices).
+
+ If xinetd is installed on your system instead of inetd the following
+ example for xinetd.conf may be helpful:
+
+ # default: off
+ # description: The sane server accepts requests
+ # for network access to a local scanner via the
+ # network.
+ service sane
+ {
+ port = 6566
+ socket_type = stream
+ wait = no
+ user = saned
+ group = saned
+ server = /usr/local/sbin/saned
+ }
+
+ Finally, it is also necessary to add a line of the following form to
+ /etc/services:
+
+ sane 6566/tcp # SANE network scanner daemon
+
+
+
+RESTRICTIONS
+ 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).
+
+
+
+FILES
+ /etc/hosts.equiv
+ 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.
+
+ /usr/local/etc/sane.d/saned.conf
+ Contains a list of hosts permitted to access local SANE devices
+ (see also description of SANE_CONFIG_DIR below).
+
+ /usr/local/etc/sane.d/saned.users
+ If this file contains lines of the form
+
+ user:password:backend
+
+ access to the listed backends is restricted. A backend may be
+ listed multiple times for different user/password combinations.
+ The server uses MD5 encryption if supported by the client.
+
+
+
+ENVIRONMENT
+ SANE_CONFIG_DIR
+ This environment variable specifies the list of directories that
+ may contain the configuration file. Under UNIX, the directories
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi-colon (`;'). If this variable is not set, the config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
+ /usr/local/etc/sane.d. If the value of the environment variable
+ ends with the directory separator character, then the default
+ directories are searched after the explicitly specified directo-
+ ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
+ would result in directories "tmp/config", ".", and
+ "/usr/local/etc/sane.d" being searched (in this order).
+
+
+
+SEE ALSO
+ sane(7), scanimage(1), xscanimage(1), xcam(1), sane-dll(5), sane-
+ net(5), sane-"backendname"(5)
+ http://www.penguin-breeder.org/?page=sane-net
+
+
+
+AUTHOR
+ David Mosberger
+
+sane-backends 1.0.12-cvs 9 Feb 2003 saned(1)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/scanadf.1.html b/man/scanadf.1.html
new file mode 100644
index 00000000..2f2c6b6a
--- /dev/null
+++ b/man/scanadf.1.html
@@ -0,0 +1,151 @@
+
+
+scanadf.1
+
+
+scanadf.1
+
+
+
+
+
+
+SYNOPSIS
+ scanadf [-d|--device-name dev] [-h|--help] [-L|--list-devices]
+ [-v|--verbose] [-V|--version] [-o|--output-file name] [-S|--scan-script
+ name] [-s|--start-count num] [-e|--end-count num] [-r|--raw] [device-
+ specific-options]
+
+
+
+DESCRIPTION
+ scanadf is a command-line interface to control image acquisition
+ devices which are capable of returning a series of images (e.g. a scan-
+ ner with an automatic document feeder (ADF)). The device is controlled
+ via command-line options. After command-line processing, scanadf nor-
+ mally proceeds to acquire a series of images until the device returns
+ the SANE_STATUS_NO_DOCS status code.
+
+ The images are written to output files, specified by the --output-file
+ option. These files are typically written in one of the PNM (portable
+ aNyMaP) formats (PBM for black-and-white images, PGM for grayscale
+ images, and PPM for color images). Several optional frame formats
+ (SANE_FRAME_JPEG, SANE_FRAME_G31D, SANE_FRAME_G32D, SANE_FRAME_G42D,
+ and SANE_FRAME_TEXT) are supported. In each case, the data is written
+ out to the output file as-is without a header. Unrecognized frame for-
+ mats are handled in the same way, although a warning message is printed
+ in verbose mode.
+
+ Typically, the optional frame formats are used in conjunction with a
+ scan script (specified by the --scanscript option) which is invoked for
+ each acquired image. The script is provided with a series of environ-
+ ment variables which describe the parameters and format of the image
+ file.
+
+ scanadf accesses image acquisition devices through the SANE (Scanner
+ Access Now Easy) interface and can thus support any device for which
+ there exists a SANE backend (try "apropos sane-" to get a list of
+ available backends).
+
+
+
+OPTIONS
+ The -d or --device-name options must be followed by a SANE device-name.
+ A (partial) list of available devices can be obtained with the --list-
+ devices option (see below). If no device-name is specified explicitly,
+ scanadf will attempt to open the first available device.
+
+ The -h or --help options request help information. The information is
+ printed on standard output and in this case, no attempt will be made to
+ acquire an image.
+
+ The -L or --list-devices option requests a (partial) list of devices
+ that are available. The list is not complete since some devices may be
+ available, but are not listed in any of the configuration files (which
+ are typically stored in directory /usr/local/etc/sane.d). This is par-
+ ticularly the case when accessing scanners through the network. If a
+ device is not listed in a configuration file, the only way to access it
+ is by its full device name. You may need to consult your system admin-
+ istrator to find out the names of such devices.
+ replacement in the output file name; this will be replaced with the
+ current page number. The default format string is image-%04d.
+
+ The -S or --scan-script option specifies the name of script to run
+ after each scanned image is acquired. The script receives the name of
+ the image output file as its first and only command line argument.
+ Additionally the scan script can reference the following environment
+ variables to get information about the parameters of the image.
+
+ SCAN_RES - the image resolution (in DPI)
+ SCAN_WIDTH - the image width (in pixels)
+ SCAN_HEIGHT - the image height (in pixels)
+ SCAN_DEPTH - the image bit-depth (in bits)
+ SCAN_FORMAT - a string representing the image format (e.g. gray,
+ g42d, text, etc)
+ SCAN_FORMAT_ID - the numeric image format identifier
+
+ The -s or --start-count option specifies the page number of first
+ scanned image.
+
+ The -e or --end-count option specifies the last page number to scan.
+ Using this option, you can request a specific number of pages to be
+ scanned, rather than scanning until there are no more images available.
+
+ The -r or --raw option specifies that the raw image data be written to
+ the output file as-is without interpretation. This disables the writ-
+ ing of the PNM header for basic frame types. This feature is usually
+ used in conjunction with the --scan-script option where the scan script
+ uses the environment variables to understand the format and parameters
+ of the image and converts the file to a more useful format. NOTE: With
+ support for the optional frame types and the default handling of unrec-
+ ognized frametypes, this option becomes less and less useful.
+
+ As you might imagine, much of the power of scanadf comes from the fact
+ that it can control any SANE backend. Thus, the exact set of command-
+ line options depends on the capabilities of the selected device. To
+ see the options for a device named dev, invoke scanadf via a command-
+ line of the form:
+
+ scanadf --help --device dev
+
+ The documentation for the device-specific options printed by --help is
+ explained in the manual page for scanimage.
+
+
+
+FILES
+ /usr/local/etc/sane.d
+ This directory holds various configuration files. For details,
+ please refer to the manual pages listed below.
+
+ Please send reports to sane-devel@mostang.com
+
+ This program relies on the backend to return the SANE_STATUS_NO_DOCS
+ status code when the automatic document feeder is out of paper. Use of
+ this program with backends that do not support ADFs (e.g. flatbed scan-
+ ners) will likely result in repeated scans of the same document. In
+ this case, it is essential to use the start-count and end-count to con-
+ trol the number of images acquired.
+
+ Only a subset of the SANE backends support feeders and return SANE_STA-
+ TUS_NO_DOCS appropriately. Backends which are known to work at this
+ time are:
+
+ sane-bh - Bell+Howell Copiscan II series scanners.
+ sane-hp - Hewlett Packard scanners. A patch to the sane-hp
+ backend is necessary. The --scantype=ADF option must be speci-
+ fied (earlier versions of the backend used the --scan-from-adf
+ option, instead).
+ sane-umax - UMAX scanners. Support exists in build 12 and
+ later. The --source="Automatic Document Feeder" option must be
+ specified.
+
+ 15 Sep 1999 scanadf(1)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/scanimage.1.html b/man/scanimage.1.html
new file mode 100644
index 00000000..2735b2ea
--- /dev/null
+++ b/man/scanimage.1.html
@@ -0,0 +1,283 @@
+
+
+scanimage.1
+
+
+scanimage.1
+
+
+
+scanimage(1) SANE Scanner Access Now Easy scanimage(1)
+
+
+
+NAME
+ scanimage - scan an image
+
+
+
+SYNOPSIS
+ scanimage [-d|--device-name dev] [--format format] [-i|--icc-profile
+ profile] [-L|--list-devices] [-f|--formatted-device-list format]
+ [--batch [=format]] [--batch-start start] [--batch-count count]
+ [--batch-increment increment] [--batch-double] [--accept-md5-only]
+ [-n|--dont-scan] [-T|--test] [-h|--help] [-v|--verbose] [-V|--version]
+ [device-specific-options]
+
+
+
+DESCRIPTION
+ scanimage is a command-line interface to control image acquisition
+ devices such as flatbed scanners or cameras. The device is controlled
+ via command-line options. After command-line processing, scanimage
+ normally proceeds to acquire an image. The image data is written to
+ standard output in one of the PNM (portable aNyMaP) formats (PBM for
+ black-and-white images, PGM for grayscale images, and PPM for color
+ images) or in TIFF (black-and-white, grayscale or color). scanimage
+ accesses image acquisition devices through the SANE (Scanner Access Now
+ Easy) interface and can thus support any device for which there exists
+ a SANE backend (try apropos sane- to get a list of available backends).
+
+
+
+EXAMPLES
+ To get a list of devices:
+
+ scanimage -L
+
+ To scan with default settings to the file image.pnm:
+
+ scanimage >image.pnm
+
+ To print all available options:
+
+ scanimage -h
+
+
+
+OPTIONS
+ The -d or --device-name options must be followed by a SANE device-name
+ like `epson:/dev/sg0' or `hp:/dev/usbscanner0'. A (partial) list of
+ available devices can be obtained with the --list-devices option (see
+ below). If no device-name is specified explicitly, scanimage reads a
+ device-name from the environment variable SANE_DEFAULT_DEVICE. If this
+ variable is not set, scanimage will attempt to open the first available
+ device.
+
+ The --format format option selects how image data is written to stan-
+ dard output. format can be pnm or tiff. If --format is not used, PNM
+ is written.
+
+ The -i or --icc-profile option is used to include an ICC profile into a
+ TIFF file.
+
+ The -L or --list-devices option requests a (partial) list of devices
+ that are available. The list is not complete since some devices may be
+ available, but are not listed in any of the configuration files (which
+ are typically stored in directory /usr/local/etc/sane.d). This is par-
+ ticularly the case when accessing scanners through the network. If a
+ device is not listed in a configuration file, the only way to access it
+ is by its full device name. You may need to consult your system admin-
+ istrator to find out the names of such devices.
+
+ The -f or --formatted-device-list option works similar to --list-
+ devices, but requires a format string. scanimage replaces the place-
+ holders %d %v %m %t %i with the device name, vendor name, model name,
+ scanner type and an index number respectively. The command
+
+ scanimage -f " scanner number %i device %d is a %t, model %m,
+ produced by %v "
+
+ will produce something like:
+
+ scanner number 0 device sharp:/dev/sg1 is a flatbed scanner,
+ model JX250 SCSI, produced by SHARP
+
+ The --batch* options provide the features for scanning documents using
+ document feeders. --batch [format] is used to specify the format of
+ the filename that each page will be written to. Each page is written
+ out to a single file. If format is not specified, the default of
+ out%d.pnm (or out%d.tif for --format tiff) will be used. format is
+ given as a printf style string with one integer parameter. --batch-
+ start start selects the page number to start naming files with. If this
+ option is not given, the counter will start at 0. --batch-count count
+ specifies the number of pages to attempt to scan. If not given, scan-
+ image will continue scanning until the scanner returns a state other
+ than OK. Not all scanners with document feeders signal when the ADF is
+ empty, use this command to work around them. With --batch-increment
+ increment you can change the amount that the number in the filename is
+ incremented by. Generally this is used when you are scanning double-
+ sided documents on a single-sided document feeder. A specific command
+ is provided to aid this: --batch-double will automatically set the
+ increment to 2.
+
+ The --accept-md5-only option only accepts user authorization requests
+ that support MD5 security. The SANE network daemon (saned) is capable
+ of doing such requests. See saned(1).
+
+ The -n or --dont-scan option requests that scanimage only sets the
+ options provided by the user but doesn't actually perform a scan. This
+ option can be used to e.g. turn off the scanner's lamp (if supported by
+ the backend).
+
+ The -T or --test option requests that scanimage performs a few simple
+ sanity tests to make sure the backend works as defined by the SANE API
+ (in particular the sane_read function is excercised by this test).
+
+ The -h or --help options request help information. The information is
+ printed on standard output and in this case, no attempt will be made to
+ acquire an image.
+
+ The -v or --verbose options increase the verbosity of the operation of
+ scanimage. The option may be specified repeatedly, each time increas-
+ ing the verbosity level.
+
+ The -V or --version option requests that scanimage prints the program
+ and package name, the version number of the SANE distribution that it
+ came with and the version of the backend that it loads. Usually that's
+ the dll backend. If more information about the version numbers of the
+ backends are necessary, the DEBUG variable for the dll backend can be
+ used. Example: SANE_DEBUG_DLL=3 scanimage -L.
+
+ As you might imagine, much of the power of scanimage comes from the
+ fact that it can control any SANE backend. Thus, the exact set of com-
+ mand-line options depends on the capabilities of the selected device.
+ To see the options for a device named dev, invoke scanimage via a com-
+ mand-line of the form:
+
+ scanimage --help --device-name dev
+
+ The documentation for the device-specific options printed by --help is
+ best explained with a few examples:
+
+ --brightness -100..100% [0]
+ Controls the brightness of the acquired image.
+
+ The description above shows that option --brightness expects an
+ option value in the range from -100 to 100 percent. The value
+ in square brackets indicates that the current option value is 0
+ percent.
+
+ --default-enhancements
+ Set default values for enhancement controls.
+
+ The description above shows that option --default-enhancements
+ has no option value. It should be thought of as having an imme-
+ diate effect at the point of the command-line at which it
+ appears. For example, since this option resets the --brightness
+ option, the option-pair --brightness 50 --default-enhancements
+ would effectively be a no-op.
+
+ --mode Lineart|Gray|Color [Gray]
+ Selects the scan mode (e.g., lineart or color).
+
+ The description above shows that option --mode accepts an argu-
+ ment that must be one of the strings Lineart, Gray, or Color.
+ The value in the square bracket indicates that the option is
+ currently set to Gray. For convenience, it is legal to abbrevi-
+ ate the string values as long as they remain unique. Also, the
+ case of the spelling doesn't matter. For example, option set-
+ ting --mode col is identical to --mode Color.
+
+ --custom-gamma[=(yes|no)] [inactive]
+ Determines whether a builtin or a custom gamma-table
+ should be used.
+
+ The description above shows that option --custom-gamma expects
+ either no option value, a "yes" string, or a "no" string. Spec-
+ ifying the option with no value is equivalent to specifying
+ "yes". The value in square-brackets indicates that the option
+ is not currently active. That is, attempting to set the option
+ would result in an error message. The set of available options
+ typically depends on the settings of other options. For exam-
+ ple, the --custom-gamma table might be active only when a
+ grayscale or color scan-mode has been requested.
+
+ Note that the --help option is processed only after all other
+ options have been processed. This makes it possible to see the
+ option settings for a particular mode by specifying the appro-
+ priate mode-options along with the --help option. For example,
+ the command-line:
+
+ scanimage --help --mode color
+
+ would print the option settings that are in effect when the
+ color-mode is selected.
+
+ --gamma-table 0..255,...
+ Gamma-correction table. In color mode this option
+ equally affects the red, green, and blue channels
+ simultaneously (i.e., it is an intensity gamma table).
+
+ The description above shows that option --gamma-table expects
+ zero or more values in the range 0 to 255. For example, a legal
+ value for this option would be "3,4,5,6,7,8,9,10,11,12". Since
+ it's cumbersome to specify long vectors in this form, the same
+ can be expressed by the abbreviated form "[0]3-[9]12". What
+ this means is that the first vector element is set to 3, the
+ 9-th element is set to 12 and the values inbetween are interpo-
+ lated linearly. Of course, it is possible to specify multiple
+ such linear segments. For example, "[0]3-[2]3-[6]7,[7]10-[9]6"
+ is equivalent to "3,3,3,4,5,6,7,10,8,6". The program
+ gamma4scanimage can be used to generate such gamma tables (see
+ gamma4scanimage(1) for details).
+
+ --filename <string> [/tmp/input.ppm]
+ The filename of the image to be loaded.
+
+ The descriptoin above is an example of an option that takes an
+ arbitrary string value (which happens to be a filename). Again,
+ the value in brackets show that the option is current set to the
+ filename /tmp/input.ppm.
+
+
+
+ENVIRONMENT
+ SANE_DEFAULT_DEVICE
+ The default device-name.
+
+
+
+FILES
+ /usr/local/etc/sane.d
+ This directory holds various configuration files. For details,
+ please refer to the manual pages listed below.
+
+ ~/.sane/pass
+ This file contains lines of the form
+
+ user:password:resource
+
+ scanimage uses this information to answer user authorization
+ requests automatically. The file must have 0600 permissions or
+ stricter. You should use this file in conjunction with the
+ --accept-md5-only option to avoid server-side attacks. The
+ resource may contain any character but is limited to 127 charac-
+ ters.
+
+
+
+SEE ALSO
+ sane(7), gamma4scanimage(1), xscanimage(1), xcam(1), xsane(1),
+ scanadf(1), sane-dll(5), sane-net(5), sane-"backendname"(5)
+
+
+
+AUTHOR
+ David Mosberger, Andreas Beck, Gordon Matzigkeit and Caskey Dickson
+
+
+
+BUGS
+ 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 scanimage(1)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/xcam.1.html b/man/xcam.1.html
new file mode 100644
index 00000000..6f695d50
--- /dev/null
+++ b/man/xcam.1.html
@@ -0,0 +1,52 @@
+
+
+xcam.1
+
+
+xcam.1
+
+
+
+
+
+
+SYNOPSIS
+ xcam
+
+
+
+DESCRIPTION
+ Should be straightforward to use. Just be sure to use a very recent
+ version of GTK.
+
+
+
+FILES
+ $HOME/.sane/xcam/devicename.rc
+ For each device, there is one rc-file that holds the saved set-
+ tings for that particular device. Normally, this file should
+ not be manipulated directly. Instead, the user should use the
+ xcam interface to select appropriate values and then save the
+ device settings using the "Preferences->Save as default set-
+ tings" menubar entry.
+
+
+
+SEE ALSO
+ sane(7), xscanimage(1), scanimage(1), sane-dll(5) and the backend man-
+ pages
+
+
+
+AUTHOR
+ David Mosberger-Tang
+
+ 24 Jun 2000 xcam(1)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/xscanimage.1.html b/man/xscanimage.1.html
new file mode 100644
index 00000000..3e34f6bd
--- /dev/null
+++ b/man/xscanimage.1.html
@@ -0,0 +1,135 @@
+
+
+xscanimage.1
+
+
+xscanimage.1
+
+
+
+
+
+
+SYNOPSIS
+ xscanimage [--version|-V] [--help|-h] [--display d] [--no-xshm]
+ [--sync] [devicename]
+
+
+
+DESCRIPTION
+ xscanimage provides a graphical user-interface to control an image
+ acquisition device such as a flatbed scanner or a camera. It allows
+ previewing and scanning invidual images and can be invoked either
+ directly from the command-line or through The GIMP image manipulation
+ program. In the former case, xscanimage acts as a stand-alone program
+ that saves acquired images in a suitable PNM format (PBM for black-and-
+ white images, PGM for grayscale images, and PPM for color images). In
+ the latter case, the images are directly passed to The GIMP for further
+ processing.
+
+ xscanimage accesses image acquisition devices through the SANE (Scanner
+ Access Now Easy) interface. The list of available devices depends on
+ installed hardware and configuration. When invoked without an explicit
+ devicename argument, xscanimage presents a dialog listing of all known
+ and available devices. If the environment variable SANE_DEFAULT_DEVICE
+ is set to the devicename, the device is preselected in the dialog. To
+ access an available device that is not known to the system, the device-
+ name must be specified explicitly. The format of devicename is backend-
+ name:devicefile (e.g. umax:/dev/sga).
+
+
+
+RUNNING UNDER THE GIMP
+ To run xscanimage under the gimp(1), simply copy it to one of the
+ gimp(1) plug-ins directories. If you want to conserve disk-space, you
+ can create a symlink instead. For example, for gimp-1.0.x the command
+
+ ln -s /usr/local/bin/xscanimage ~/.gimp/plug-ins/
+
+ and for gimp-1.2.x the command
+
+ ln -s /usr/local/bin/xscanimage ~/.gimp-1.2/plug-ins/
+
+ adds a symlink for the xscanimage binary to the user's plug-ins direc-
+ tory. After creating this symlink, xscanimage will be queried by
+ gimp(1) the next time it's invoked. From then on, xscanimage can be
+ invoked through "File->Acquire->Xscanimage->Device dialog..." menu
+ entry.
+
+ You'll also find that the "File->Acquire->Xscanimage" menu contains
+ short-cuts to the SANE devices that were available at the time xscanim-
+ age was queried. For example, the first PNM pseudo-device is typically
+ available as the short-cut "File->Acquire->Xscanimage->pnm:0". Note
+ that gimp(1) caches these short-cuts in ~/.gimp/pluginrc. Thus, when
+ the list of available devices changes (e.g., a new scanner is
+ installed), then it is typically desirable to rebuild this cache. To
+ do this, you can either touch(1) the xscanimage binary (e.g., "touch
+ /usr/local/bin/xscanimage") or delete the plug-ins cache (e.g., "rm
+ ~/.gimp/plug-ins"). Either way, invoking gimp(1) afterwards will cause
+ the pluginrc to be rebuilt.
+ buggy X11 servers. Unless your X11 server dies when running this pro-
+ gram, there is no need or advantage to specify this flag.
+
+ The --sync flag requests a synchronous connection with the X11 server.
+ This is for debugging purposes only.
+
+
+
+ENVIRONMENT
+ SANE_DEFAULT_DEVICE
+ The default device-name. Example:
+ SANE_DEFAULT_DEVICE="hp:/dev/scanner".
+
+ SANE_DEBUG_XSCANIMAGE
+ This environment variable controls the debug level xscanimage.
+ Higher debug levels increase the verbosity of the output.
+
+ Value Descsription
+ 0 print fatal errors
+ 1 print errors
+ 2 print warnings
+ 3 print information messages
+ 4 print everything
+
+ Example:
+ SANE_DEBUG_XSCANIMAGE=3
+
+
+
+FILES
+ $HOME/.sane/xscanimage/xscanimage.rc
+ This files holds the user preferences. Normally, this file
+ should not be manipulated directly. Instead, the user should
+ customize the program through the "Preferences" dialog.
+
+ $HOME/.sane/xscanimage/devicename.rc
+ For each device, there is one rc-file that holds the saved set-
+ tings for that particular device. Normally, this file should
+ not be manipulated directly. Instead, the user should use the
+ xscanimage interface to select appropriate values and then save
+ the device settings using the "Preferences->Save Device Set-
+ tings" menubar entry.
+
+ $HOME/.sane/preview-devicename.ppm
+ After acquiring a preview, xscanimage normally saves the preview
+ image in this device-specific file. Thus, next time the program
+ is started up, the program can present the old preview image.
+ This feature can be turned off through the "Preferences->Preview
+ Options..." dialog.
+
+ /usr/local/share/sane-style.rc
+ This system-wide file controls the aspects of the user-interface
+ such as colors and fonts. It is a GTK style file and provides
+ fine control over the visual aspects of the user-interface.
+
+ $HOME/.sane/sane-style.rc
+ This file serves the same purpose as the system-wide style file.
+ If present, it takes precedence over the system wide style file.
+
+
+
+Man(1) output converted with
+man2html
+
+
+