Oliver.Rauch@Rauch-Domain.DE
-sane-backends 1.0.16 11 Sep 2002 gamma4scanimage(1)
+sane-backends 1.0.17 11 Sep 2002 gamma4scanimage(1)
Ingo Schneider and Karl Anders Řygard.
-sane-backends 1.0.16 17 Oct 1998 sane-agfafocus(5)
+sane-backends 1.0.17 17 Oct 1998 sane-agfafocus(5)
- 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 + 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 + 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 scanners are typically delivered with an ISA SCSI adapter. Unfor-
- tunately, that adapter is not worth much since it is not interrupt
- driven. It is (sometimes) possible to get the supplied card to work,
- but without interrupt line, scanning will put so much load on the sys-
+ tunately, that adapter is not worth much since it is not interrupt
+ driven. It is (sometimes) possible to get the supplied card to work,
+ but without interrupt line, scanning will put so much load on the sys-
tem, that it becomes almost unusable for other tasks.
/usr/local/etc/sane.d/apple.conf
- The backend configuration file (see also description of
+ The backend configuration file (see also description of
SANE_CONFIG_DIR below).
/usr/local/lib/sane/libsane-apple.a
@@ -88,34 +87,34 @@
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
+ are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
- uration file is searched in two default directories: first, the
- current working directory (".") and then in
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
- ends with the directory separator character, then the default
+ ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
+ 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.
+ 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.
The apple backend is now in version 0.3 (Tue Jul 21 1998). Since I only
- have the AppleScanner and not the other models (OneScanner, ColorOneS-
+ have the AppleScanner and not the other models (OneScanner, ColorOneS-
canner) I can only develop/test for the AppleScanner effectively. How-
- ever with this release I almost complete the gui part of all scanners.
- Most of the functionality is there. At least OneScanner should scan at
- the AppleScanner's compatible modes (LineArt, HalfTone, Gray16). My
+ ever with this release I almost complete the gui part of all scanners.
+ Most of the functionality is there. At least OneScanner should scan at
+ the AppleScanner's compatible modes (LineArt, HalfTone, Gray16). My
personal belief is that with a slight touch of debugging the OneScanner
- could be actually usable. The ColorOneScanner needs more work. AppleS-
+ could be actually usable. The ColorOneScanner needs more work. AppleS-
canner is of course almost fully supported.
@@ -131,44 +130,44 @@
ColorOneScanner
Cannot up/download halftone pattern, calibration vectors, custom
- Color Correction Table (CCT) and of course custom gamma tables.
+ Color Correction Table (CCT) and of course custom gamma tables.
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
+ 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.
-- The following "features" will never be supported. At least as I am +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 + The scanner lamp stays on and the carriage assembly remains where it stops at the end of the scan. After two minutes, if the - scanner does not receive another SCAN command the lamp goes off + scanner does not receive another SCAN command the lamp goes off and the carriage returns to the home position. Compression (AppleScanner) - The Scanner can compress data with CCITT Group III, one dimen- + The Scanner can compress data with CCITT Group III, one dimen- sional algorithm (fax), and the Skip White Line algorithm. 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 + 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 + This option controls the status of the button in OneScanner model. You can also reset the button status by software. @@ -177,56 +176,52 @@ 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 + We know we have a GUI bug when a parameter is not showing up itself when it should (active) or vice versa. To find out which parameters are - active accross various Apple modes and models from the documentation + active accross various Apple modes and models from the documentation 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 + dancies. For example for the threshold parameter the Apple Scanners + Programming guide says nothing. I had to assume that is valid only in LineArt mode. - Scanner specific bugs are mostly due to mandatory round offs in order - to scan. In the documentation in some place states that the width of - the scan area should be a byte multiple. In an other place says that - the width of the scan area should be an even byte multiple. Go fig- + Scanner specific bugs are mostly due to mandatory round offs in order + to scan. In the documentation in some place states that the width of + the scan area should be a byte multiple. In an other place says that + the width of the scan area should be an even byte multiple. Go fig- ure... - Other source of bugs are due to scsi communcation, scsi connects and - disconnects. However the classical bugs are still there. So you may + Other source of bugs are due to scsi communcation, scsi connects and + disconnects. However the classical bugs are still there. So you may encouter buffer overruns, null pointers, memory corruption and 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 + 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 + 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. + 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... + 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 hard- + ware, or may be bugs in your driver or in SANE itself...@@ -275,7 +270,7 @@ Firikis. It is mostly based on the mustek backend from David Mosberger and Andreas Czechanowski -sane-backends 1.0.16 13 May 1998 sane-apple(5) +sane-backends 1.0.17 13 May 1998 sane-apple(5)
Chris Pinkham (cpinkham@corp.infi.net)
-sane-backends 1.0.16 24 Jan 2000 sane-artec(5)
+sane-backends 1.0.17 24 Jan 2000 sane-artec(5)
yossarian@users.sourceforge.net
-sane-backends 1.0.16 Dec 14th, 2003 sane-as6e(5)
+sane-backends 1.0.17 Dec 14th, 2003 sane-as6e(5)
René Rebe and Meino Christian Cramer
-sane-backends 1.0.16 04 Mar 2003 sane-avision(5)
+sane-backends 1.0.17 04 Mar 2003 sane-avision(5)
Nathan Rutman
-sane-backends 1.0.16 06 Apr 2002 sane-canon630u(5)
+sane-backends 1.0.17 06 Apr 2002 sane-canon630u(5)
andreas.rick@free.fr
-sane-backends 1.0.16 4 July 2000 sane-coolscan(5)
+sane-backends 1.0.17 4 July 2000 sane-coolscan(5)
- This backend needs libusb-0.1.6 or later installed, and hasn't tested
+ This backend needs libusb-0.1.6 or later installed, and hasn't tested
in other configuration than a linux kernel 2.6.9 or higher. However, it
- should work any system with libusb where the SANE package can be com-
- piled. For setting permissions and general USB information look at
+ should work any system with libusb where the SANE package can be com-
+ piled. For setting permissions and general USB information look at
sane-usb(5).
The contents of the genesys.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 genesys.conf .
- "vendor_id" and "product_id" are hexadecimal numbers that identfy the
+ 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 genesys.conf.
+ "vendor_id" and "product_id" are hexadecimal numbers that identfy the
scanner.
/usr/local/etc/sane.d/genesys.conf
- The backend configuration file (see also description of
+ The backend configuration file (see also description of
SANE_CONFIG_DIR below).
/usr/local/lib/sane/libsane-genesys.a
@@ -82,29 +82,36 @@
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
+ are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
- uration file is searched in two default directories: first, the
- current working directory (".") and then in
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
- ends with the directory separator character, then the default
+ ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
+ 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_GENESYS
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this
+ environment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output. If the
- debug level is set to 1 or higher, some debug options become
- available that are normally hidden. Handle them with care. This
- will print messages related to core genesys functions.
- SANE_DEBUG_GENESYS_GL646 This environment variable controls the
- debug level for the specific GL646 code part.
+ debug level is set to 1 or higher, some debug options become
+ available that are normally hidden. Handle them with care. This
+ will print messages related to core genesys functions.
- Example (full and highly verbose output): export
- SANE_DEBUG_GENESYS=255 export SANE_DEBUG_GENESYS_GL646=255
+ SANE_DEBUG_GENESYS_GL646
+ This environment variable controls the debug level for the spe-
+ cific GL646 code part.
+
+ SANE_DEBUG_GENESYS_GL841
+ This environment variable controls the debug level for the spe-
+ cific GL841 code part.
+
+ Example (full and highly verbose output for gl646):
+ export SANE_DEBUG_GENESYS=255
+ export SANE_DEBUG_GENESYS_GL646=255
@@ -125,7 +132,7 @@
Support for buttons is missing.
-sane-backends 1.0.16 3 July 2005 sane-genesys(5)
+sane-backends 1.0.17 20 Nov 2005 sane-genesys(5)
- Please use libusb-0.1.6 or later. Without libusb or with older libusb +LIBUSB ISSUES
+ Please use libusb-0.1.8 or later. Without libusb or with older libusb versions all kinds of trouble can be expected. The scanner should be found by sane-find-scanner without further actions. For setting permis- sions and general USB information looks at sane-usb(5). @@ -161,9 +161,9 @@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.16/gt68xx/gt68xx.CHANGES + 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.17/gt68xx/gt68xx.CHANGES http://www.meier-geinitz.de/sane/gt68xx @@ -177,10 +177,6 @@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- @@ -189,12 +185,12 @@ 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 + page http://www.meier-geinitz.de/sane/gt68xx-backend/. 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.16 29 May 2005 sane-gt68xx(5) +sane-backends 1.0.17 29 September 2005 sane-gt68xx(5)
diff --git a/man/sane-hp.5.html b/man/sane-hp.5.html index 48f89c96..6a568246 100644 --- a/man/sane-hp.5.html +++ b/man/sane-hp.5.html @@ -45,8 +45,8 @@ 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) + the ppSCSI driver available at http://cyberelk.net/tim/par- + port/ppscsi.html and http://penguin-breeder.org/kernel/download/. Support for models 5200C/62X0C/63X0C connected to the USB require the kernel scanner driver or libusb. See sane-usb(5) for more details. @@ -60,8 +60,8 @@ 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.sane-project.org/. - You can also watch the sane-devel mailinglist at - http://www.sane-project.org/mailing-lists.html. + You can also watch the sane-devel mailinglist at http://www.sane- + project.org/mailing-lists.html. More details about the hp backend can be found on its homepage http://www.kirchgessner.net/sane.html. @@ -217,9 +217,9 @@ 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). + for repeated scans. The use of the preview window is not + recommended 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- @@ -255,7 +255,7 @@ The sane-hp backend was written by Geoffrey T. Dairiki. HP PhotoSmart PhotoScanner support by Peter Kirchgessner. -sane-backends 1.0.16 27 Mar 2004 sane-hp(5) +sane-backends 1.0.17 27 Mar 2004 sane-hp(5)
+ +sane-lexmark(5) SANE Scanner Access Now Easy sane-lexmark(5) + + ++
+ sane-lexmark - SANE backend for Lexmark X1100 Series scanners + + ++
+ The sane-lexmark library implements a SANE (Scanner Access Now Easy) + backend that provides access to the scanner part of Lexmark X1100 AIOs. + This backend should be considered beta-quality software! + + The scanners that should work with this backend are: + + Vendor Model status + ---------------------- ----------- + Lexmark X1110 untested + Lexmark X1140 untested + Lexmark X1150 untested + Lexmark X1170 untested + Lexmark X1180 basic + Lexmark X1185 basic + + 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 lexmark:usb:<usb port> + + Scan Mode Options + + --mode selects the basic mode of operation of the scanner valid choices + are Color, Gray and Lineart The default mode is Color. The Lin- + eart mode is black and white only (1 bit). Grayscale will pro- + duce 256 levels of gray (8 bits). Color mode allows for over 16 + million different colors produced from 24 bits of color informa- + tion. + + --resolution + selects the resolution for a scan. The horizontal and vertical + resolutions are set by the value of this option. The scanner is + capable of the following resolutions for the specified option + value: + + Value Hor. Resolution Vert. Resolution + ----- --------------- ------------------- + 75 75dpi 75dpi + 150 150dpi 150dpi + 300 300dpi 300dpi + 600 600dpi 600dpi + 1200 600dpi 1200dpi + + --preview + requests a preview scan. The resolution used for that scan is 75 + dpi and the scan area and the scan mode are as specified through + their options, or the default if not specified. The default + value for preview mode is "no". + + + --paper-size + selects the size of the area to be scanned. Valid sizes are Wal- + let, 3x5, 4x6, 5x7, 8x10, Letter, the default size is 3x5. + + --threshold + selects the minimum-brightness to get a white point. The + threshold is only used with Lineart mode scans. It is specified + as a percentage in the range 0..100% (in steps of 1). The + default value of the threshold option is 50. + + ++
+ The configuration file /usr/local/etc/sane.d/lexmark.conf contains only + the usb device id (eg usb 0x043d 0x007c). + + ++
+ /usr/local/lib/sane/libsane-lexmark.a + The static library implementing this backend. + + /usr/local/lib/sane/libsane-lexmark.so + The shared library implementing this backend (present on systems + that support dynamic loading). + + ++
+ SANE_DEBUG_LEXMARK + 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. + + ++
+ 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. + + ++
+ Jerky movement on 600dpi gray 8x10 scan. + Color calibration not implemented. + Dark compensation not implemented. + + ++
+ sane-scsi(5), scanimage(1), xscanimage(1), xsane(1), sane(7) + + ++
+ The package is actively maintained by Fred Odendaal. + http://ca.geocities.com/freshshelf@rogers.com/ + +sane-backends 1.0.17 02 September 2005 sane-lexmark(5) ++
The contents of the ma1509.conf file is a list of options and device
- names that correspond to Mustek BearPAw 1200F scanners. Empty lines
+ 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
@@ -127,7 +127,7 @@
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.16 24 Feb 2003 sane-ma1509(5)
+sane-backends 1.0.17 24 Feb 2003 sane-ma1509(5)
This backend dynamically enables the options for the frontend, that are
- supported by the scanner in dependence of the scanning-mode and other
+ 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
+ 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
+ Additional options can be enabled or disabled in the microtek2.conf
file. See the configuration section of this manpage.
@@ -117,9 +118,9 @@
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
+ 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.
@@ -128,16 +129,16 @@
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
+ 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
+ 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>
@@ -149,29 +150,29 @@
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 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
+ 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
+ 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
+ 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 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
+ 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
+ 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
@@ -179,26 +180,26 @@
tend.
option no-backtrack-option <on/off> prevents the scanner head from mov-
- ing backwards between the read commands. This speeds up scanning. Try
+ 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
+ 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
+ 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
+ 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 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
+ 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.
@@ -212,9 +213,9 @@
/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 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
@@ -251,11 +252,11 @@
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.
+ 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-
+ 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
@@ -271,7 +272,7 @@
Bernd Schroeder (not active anymore)
Karsten Festag karsten.festag@gmx.de
-sane-backends 1.0.16 28 Jan 2002 sane-microtek2(5)
+sane-backends 1.0.17 28 Jan 2002 sane-microtek2(5)
/usr/local/etc/sane.d/mustek.conf
- The backend configuration file (see also description of
+ The backend configuration file (see also description of
SANE_CONFIG_DIR below).
/usr/local/lib/sane/libsane-mustek.a
@@ -279,20 +280,20 @@
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
+ 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
+ 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
+ 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.
+ 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
@@ -308,15 +309,15 @@
- sane(7), sane-find-scanner(1), sane-scsi(5), sane-mustek_usb(5), sane- + 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.16/mustek/mustek.CHANGES + /usr/local/doc/sane-1.0.17/mustek/mustek.CHANGES http://www.meier-geinitz.de/sane/mustek-backend/
- David Mosberger, Andreas Czechanowski, Andreas Bolsch (SE extensions),
+ David Mosberger, Andreas Czechanowski, Andreas Bolsch (SE extensions),
Henning Meier-Geinitz, James Perry (600 II EP).
@@ -327,13 +328,13 @@
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
+ 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-
+ More detailed bug information is available at the Mustek backend home-
page: http://www.meier-geinitz.de/sane/mustek-backend/.
-sane-backends 1.0.16 25 Dec 2002 sane-mustek(5)
+sane-backends 1.0.17 18 Sep 2005 sane-mustek(5)
- 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
+ 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:
@@ -113,26 +118,26 @@
<name> is an arbitrary name for the device, optionally enclosed by dou-
ble quotes, for instance "LifeTec 9350".
- <port name> is the name of the parallel port to which the device is
- connected. In case libieee1284 is used for communication with
- the port (default setup), valid port names are parport0, par-
+ <port name> is the name of the parallel port to which the device is
+ connected. In case libieee1284 is used for communication with
+ the port (default setup), valid port names are parport0, par-
port1, and parport2.
- In case the backend is configured for raw IO (old setup), port
- addresses have to be used instead of port names: 0x378, 0x278,
- or 0x3BC. The mapping of parallel ports (lp0, lp1, and lp2) to
+ In case the backend is configured for raw IO (old setup), port
+ addresses have to be used instead of port names: 0x378, 0x278,
+ or 0x3BC. The mapping of parallel ports (lp0, lp1, and lp2) to
these addresses can be different for different Linux kernel ver-
- sions. For instance, if you are using a Kernel 2.2.x or better
- and you have only one parallel port, this port is named lp0
- regardless of the base address. However, this backend requires
- the base address of your port. If you are not sure which port
+ sions. For instance, if you are using a Kernel 2.2.x or better
+ and you have only one parallel port, this port is named lp0
+ regardless of the base address. However, this backend requires
+ the base address of your port. If you are not sure which port
your scanner is connected to, have a look at your /etc/conf.mod-
ules, /etc/modules.conf and/or /proc/ioports.
If you are unsure which port to use, you can use the magic value
* to probe for your scanner.
- <driver> is the driver to use for this device. Currently available
+ <driver> is the driver to use for this device. Currently available
drivers are:
cis600 : for 600 CP, 96 CP & OEM versions
@@ -142,16 +147,16 @@
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-
+ If the scanner starts making a loud noice, turn it off immedi-
ately !!!
Using the cis600 driver on a 1200CP or a 1200CP+ is probably not
- dangerous. The cis1200+ driver also works for the 1200CP, and
- using the cis1200 driver on a 1200CP+ will typically result in
- scans that cover only half of the width of the scan area (also
+ dangerous. The cis1200+ driver also works for the 1200CP, and
+ using the cis1200 driver on a 1200CP+ will typically result in
+ scans that cover only half of the width of the scan area (also
not dangerous).
- If unsure about the exact model of your OEM version, check the
- optical resolution in the manual or on the box: the 600CP has a
- maximum optical resolution of 300x600 DPI, whereas the 1200CP
+ If unsure about the exact model of your OEM version, check the
+ optical resolution in the manual or on the box: the 600CP has a
+ maximum optical resolution of 300x600 DPI, whereas the 1200CP
and 1200CP+ have a maximum optical resolution of 600x1200 DPI.
Examples:
@@ -162,8 +167,8 @@
scanner Mustek_600IIIEP * ccd300
- If in doubt which port you have to use, or whether your scanner is
- detected at all, you can use sane-find-scanner -p to probe all config-
+ If in doubt which port you have to use, or whether your scanner is
+ detected at all, you can use sane-find-scanner -p to probe all config-
ured ports.
@@ -171,20 +176,20 @@
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-
+ 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:
+ 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
+ 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
@@ -194,12 +199,12 @@
CIS driver options
- top_adjust <value> Vertical adjustment of the origin, expressed in
- millimeter (floating point). This option can be used to
+ 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
+ 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
@@ -207,19 +212,42 @@
Example: option top_adjust -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
+ 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
+ engine_delay <value> Under normal circumstances, it is sufficient
+ for the driver to wait for the scanner signaling that the
+ engine is stable, before a new engine command can be trans-
+ mitted. In rare cases, certain scanners and/or parallel port
+ chipsets appear to prevent reliable detection of the engine
+ state. As a result, engine commands are transmitted too soon
+ and the movement of the scanner head becomes unreliable.
+ Inaccuracies ranging up to 10 cm over the whole vertical
+ scan range have been reported. To work around this problem,
+ the engine_delay option can be set. If it is set, the driver
+ waits an additional amount of time after every engine com-
+ mand, equal to the engine_delay parameter, expressed in mil-
+ liseconds. It practice an engine_delay of 1 ms is usually
+ sufficient. The maximum delay is 100 ms.
+ Note that every additional ms of delay can add up to 14 sec-
+ onds to the total scanning time (highest resolution), so an
+ as small as possible value is prefered.
+ Default value: 0
+ Minimum: 0
+ Maximum: 100
+
+ Example: option engine_delay 1
+
CCD driver options
top <value> Number of scanlines to skip to the start of the scan
@@ -377,10 +405,10 @@
BUGS
- Too many... please send bug reports to
- sane-devel@lists.alioth.debian.org (note that you have to subscribe
- first to the list before you can send emails... see
- http://www.sane-project.org/mailing-lists.html)
+ Too many... please send bug reports to sane-
+ devel@lists.alioth.debian.org (note that you have to subscribe first to
+ the list before you can send emails... see http://www.sane-
+ project.org/mailing-lists.html)
diff --git a/man/sane-mustek_usb.5.html b/man/sane-mustek_usb.5.html
index 6edbcd14..a2d1c9a6 100644
--- a/man/sane-mustek_usb.5.html
+++ b/man/sane-mustek_usb.5.html
@@ -148,8 +148,8 @@
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.16/mustek_usb/mustek_usb.CHANGES,
- /usr/local/doc/sane-1.0.16/mustek_usb/mustek_usb.TODO
+ /usr/local/doc/sane-1.0.17/mustek_usb/mustek_usb.CHANGES,
+ /usr/local/doc/sane-1.0.17/mustek_usb/mustek_usb.TODO
http://www.meier-geinitz.de/sane/mustek_usb-backend/
@@ -175,7 +175,7 @@
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.16 3 Mar 2004 sane-mustek_usb(5)
+sane-backends 1.0.17 3 Mar 2004 sane-mustek_usb(5)
diff --git a/man/sane-mustek_usb2.5.html b/man/sane-mustek_usb2.5.html
new file mode 100644
index 00000000..4766a0f3
--- /dev/null
+++ b/man/sane-mustek_usb2.5.html
@@ -0,0 +1,114 @@
+
+
+sane-mustek_usb2.5
+
+
+sane-mustek_usb2.5
+
+
+
+sane-mustek_usb2(5) SANE Scanner Access Now Easy sane-mustek_usb2(5)
+
+
+
+NAME
+ sane-mustek_usb2 - SANE backend for SQ113 based USB flatbed scanners
+
+
+
+DESCRIPTION
+ The sane-mustek_usb2 library implements a SANE (Scanner Access Now
+ Easy) backend that provides access to USB flatbed scanners based on the
+ Service & Quality SQ113 chipset. At the moment, only the Mustek BearPaw
+ 2448 TA Pro is supported. It's planned to add support for other scan-
+ ners that are based on the SQ113 and maybe SQ11 chip. For more details,
+ see the mustek_usb2 backend homepage: http://www.meier-
+ geinitz.de/sane/mustek_usb2-backend/.
+
+ 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 on the mustek_usb2
+ homepage that works with this backend, please let me know this by send-
+ ing the scanner's exact model name and the USB vendor and device ids
+ (e.g. from sane-find-scanner or syslog) to me. Even if the scanner's
+ name is only slightly different from the models already listed as sup-
+ ported, please let me know.
+
+
+
+LIBUSB ISSUES
+ Please use libusb-0.1.8 or later. Without libusb or with older libusb
+ versions all kinds of trouble can be expected. The scanner should be
+ found by sane-find-scanner without further actions. For setting permis-
+ sions and general USB information looks at sane-usb(5).
+
+
+
+FILES
+ /usr/local/etc/sane.d/mustek_usb2.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-mustek_usb2.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-mustek_usb2.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_USB2
+ 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_MUSTEK_USB2=4
+
+
+
+SEE ALSO
+ sane(7), sane-usb(5), sane-plustek(5), sane-ma1509(5), sane-
+ mustek_usb(5), sane-mustek(5), sane-mustek_pp(5)
+ /usr/local/doc/sane-1.0.17/mustek_usb2/mustek_usb2.CHANGES
+ http://www.meier-geinitz.de/sane/mustek_usb2-backend/
+
+
+
+AUTHOR
+ The driver has been written Roy Zhou, Jack Xu, and Vinci Cen from
+ Mustek. Adjustments to SANE by Henning Meier-Geinitz.
+
+
+
+BUGS
+ 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_MUSTEK_USB2 above).
+
+sane-backends 1.0.17 29 Sep 2005 sane-mustek_usb2(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-nec.5.html b/man/sane-nec.5.html
index 43d295fb..c529187b 100644
--- a/man/sane-nec.5.html
+++ b/man/sane-nec.5.html
@@ -67,7 +67,7 @@
AUTHORS
Kazuya Fukuda
-sane-backends 1.0.16 17 Feb 2000 sane-nec(5)
+sane-backends 1.0.17 17 Feb 2000 sane-nec(5)
diff --git a/man/sane-net.5.html b/man/sane-net.5.html
index 0bfd2801..931aba70 100644
--- a/man/sane-net.5.html
+++ b/man/sane-net.5.html
@@ -131,7 +131,7 @@
AUTHOR
David Mosberger and Andreas Beck
-sane-backends 1.0.16 8 Oct 2002 sane-net(5)
+sane-backends 1.0.17 8 Oct 2002 sane-net(5)
diff --git a/man/sane-niash.5.html b/man/sane-niash.5.html
index e3df1c5f..c9a2b197 100644
--- a/man/sane-niash.5.html
+++ b/man/sane-niash.5.html
@@ -54,8 +54,8 @@
If you use a
Hewlett-Packard Scanjet 3400c or
Hewlett-Packard Scanjet 4300c
- together with Linux kernel 2.6 , kernel version 2.6.8 or newer is nec-
- essary.
+ together with Linux kernel 2.6, kernel version 2.6.8 or newer is neces-
+ sary.
@@ -78,7 +78,7 @@
Bertrik Sikken <bertrik@zonnet.nl>
-sane-backends 1.0.16 29 July 2004 sane-niash(5)
+sane-backends 1.0.17 29 July 2004 sane-niash(5)
- 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
+ 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
@@ -62,7 +61,7 @@
/usr/local/etc/sane.d/pint.conf
- The backend configuration file (see also description of
+ The backend configuration file (see also description of
SANE_CONFIG_DIR below).
/usr/local/lib/sane/libsane-pint.a
@@ -78,21 +77,21 @@
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
+ are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
- uration file is searched in two default directories: first, the
- current working directory (".") and then in
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
- ends with the directory separator character, then the default
+ ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
+ 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.
+ 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.
@@ -109,33 +108,33 @@
- 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
+ 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
+ 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
+ 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
+ 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
+ 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
+ No testing has been done on three-pass or handheld scanners, or with
Automatic Document Feeder support.
-sane-backends 1.0.16 13 May 1998 sane-pint(5)
+sane-backends 1.0.17 13 May 1998 sane-pint(5)
To use your scanner with this backend, you need at least two entries in
- the configuration file
- /usr/local/etc/sane.d/plustek.conf
+ the configuration file /usr/local/etc/sane.d/plustek.conf
+ [usb] vendor-id product-id
+ device /dev/usbscanner
- [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 is set to auto then the next matching device
- is used.
+ [usb] tells the backend, that the following devicename (here /dev/usb-
+ scanner) has to be interpreted as USB scanner device. If vendor- and
+ product-id has not been specified, the backend tries to detect this by
+ its own. If device is set to auto then the next matching device is
+ used.
The following options can be used for a default setup of your device.
Most of them are also availaby through the frontend.
@@ -283,7 +281,7 @@
sane(7), sane-usb(5), sane-u12(5), sane-gt68xx(5),
- /usr/local/doc/sane-1.0.16/plustek/Plustek-USB.changes
+ /usr/local/doc/sane-1.0.17/plustek/Plustek-USB.changes
http://www.gjaeger.de/scanner/plustek/
@@ -327,7 +325,7 @@
* Negative/Slide scanning quality is poor.
-sane-backends 1.0.16 02 July 2004 sane-plustek(5)
+sane-backends 1.0.17 08 August 2005 sane-plustek(5)
This section decribes the backends' configuration file entries. The
- file is located at:
-
- /usr/local/etc/sane.d/plustek_pp.conf
+ file is located at: /usr/local/etc/sane.d/plustek_pp.conf
For a proper setup, you will need at least two entries:
-
- [direct]
-
- device 0x378
+ [direct]
+ device 0x378
or
+ [kernel]
+ device /dev/pt_drv
- [kernel]
-
- device /dev/pt_drv
-
- direct tells the backend, that the following devicename (here 0x378 )
+ direct tells the backend, that the following devicename (here 0x378)
has to be interpreted as parallel port scanner device. In fact it is
the address to use, alternatively you can use /dev/parport0 if the
backend has been compiled with libieee1284 support. kernel should only
@@ -205,14 +199,13 @@
Note: Installing and loading the can only be done as superuser.
-
The configuration of the kernel module is done by providing some or
more options found below to the kernel module at load time. This can be
done by invoking insmod with the appropriate parameters or appending
- the options to the file /etc/modules.conf (kernel < 2.6.x) or /etc/mod-
- probe.conf (kernel >= 2.6.x)
+ the options to the file /etc/modules.conf (kernel < 2.6.x) or
+ /etc/modprobe.conf (kernel >= 2.6.x)
The Options:
lampoff=lll
@@ -345,10 +338,11 @@
Example: export SANE_DEBUG_PLUSTEK_PP=10
+
sane(7),
- /usr/local/doc/sane-1.0.16/plustek/Plustek-PARPORT.changes
+ /usr/local/doc/sane-1.0.17/plustek/Plustek-PARPORT.changes
http://www.gjaeger.de/scanner/plustek_pp/
@@ -410,7 +404,7 @@
* The scanquality of the A3I is poor
-sane-backends 1.0.16 18 June 2004 sane-plustek_pp(5)
+sane-backends 1.0.17 18 June 2004 sane-plustek_pp(5)
sane(7)
-sane-backends 1.0.16 22 April 2001 sane-pnm(5)
+sane-backends 1.0.17 22 April 2001 sane-pnm(5)
sane(7)
-sane-backends 1.0.16 25 October 1997 sane-qcam(5)
+sane-backends 1.0.17 25 October 1997 sane-qcam(5)
Feico W. Dillema
-sane-backends 1.0.16 24 Jun 2000 sane-ricoh(5)
+sane-backends 1.0.17 24 Jun 2000 sane-ricoh(5)
David Mosberger
-sane-backends 1.0.16 28 Oct 2003 sane-scsi(5)
+sane-backends 1.0.17 28 Oct 2003 sane-scsi(5)
- 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. - -
SANE_DEBUG_SM3600
@@ -110,7 +93,7 @@
Marian Eichholz (eichholz@computer.org)
Glenn Ramsey (glenn@componic.com)
-sane-backends 1.0.16 10.02.2002 sane-sm3600(5)
+sane-backends 1.0.17 16 August 2005 sane-sm3600(5)
Earle F. Philhower III (earle@ziplabel.com)
-sane-backends 1.0.16 Mar 15, 2005 sane-sm3840(5)
+sane-backends 1.0.17 Mar 15, 2005 sane-sm3840(5)
Ingo Wilken <Ingo.Wilken@informatik.uni-oldenburg.de>
-sane-backends 1.0.16 08 Mar 1999 sane-st400(5)
+sane-backends 1.0.17 08 Mar 1999 sane-st400(5)
Roger Wolff
-sane-backends 1.0.16 24 Jun 2000 sane-tamarack(5)
+sane-backends 1.0.17 24 Jun 2000 sane-tamarack(5)
- config file values aren't tested for correctness
-sane-backends 1.0.16 24 Jul 2002 sane-test(5)
+sane-backends 1.0.17 24 Jul 2002 sane-test(5)
To use your scanner with this backend, you need at least two entries in
- the configuration file
- /usr/local/etc/sane.d/u12.conf
-
- [usb] vendor-id product-id
-
- device /dev/usbscanner
+ the configuration file /usr/local/etc/sane.d/u12.conf
+ [usb] vendor-id product-id
+ device /dev/usbscanner
[usb] tells the backend, that the following devicename (here /dev/usb-
- scanner ) has to be interpreted as USB scanner device. If vendor- and
+ scanner) has to be interpreted as USB scanner device. If vendor- and
product-id has not been specified, the backend tries to detect this by
- its own. If device ist set to auto then the next matching device is
+ its own. If device is set to auto then the next matching device is
used.
The Options:
@@ -78,6 +75,7 @@
b specifies the behaviour when closing the backend, 1 --> switch
lamps off, 0 --> do not change lamp status
+
See the u12.conf file for examples.
Note:
@@ -130,7 +128,7 @@
sane(7), sane-usb(5), sane-plustek(5),
- /usr/local/doc/sane-1.0.16/u12/U12.changes
+ /usr/local/doc/sane-1.0.17/u12/U12.changes
http://www.gjaeger.de/scanner/u12/
@@ -161,7 +159,7 @@
* When using libusb, it might be, that the backend hangs. In that
case, reconnect the scanner.
-sane-backends 1.0.16 18 June 2004 sane-u12(5)
+sane-backends 1.0.17 18 June 2004 sane-u12(5)
Oliver.Rauch@Rauch-Domain.DE
-sane-backends 1.0.16 29 november 2002 sane-umax(5)
+sane-backends 1.0.17 29 november 2002 sane-umax(5)
- This section assumes that your scanner is detected by sane-find-scan-
- ner. It doesn't make sense to go on, if this is not the case. While
- sane-find-scanner is able to detect any USB scanner, actual scanning
- will only work if the scanner is supported by a SANE backend. Informa-
- tion on the level of support can be found on the SANE webpage
+ This section assumes that your scanner is detected by sane-find-scan-
+ ner. It doesn't make sense to go on, if this is not the case. While
+ sane-find-scanner is able to detect any USB scanner, actual scanning
+ will only work if the scanner is supported by a SANE backend. Informa-
+ tion on the level of support can be found on the SANE webpage
(http://www.sane-project.org/), and the individual backend manpages.
Most backends can detect USB scanners automatically using "usb" config-
- uration file lines. This method allows to identify scanners by the USB
- vendor and product numbers. The syntax for specifying a scanner this
+ uration file lines. This method allows to identify scanners by the USB
+ vendor and product numbers. The syntax for specifying a scanner this
way is:
usb 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
+ the scanner. Both ids are non-negative integer numbers in decimal or
hexadecimal format. The correct values for these fields can be found by
running sane-find-scanner, looking into the syslog (e.g., /var/log/mes-
- sages) or under Linux by issuing the command "cat
+ sages) or under Linux by issuing the command "cat
/proc/bus/usb/devices/". This is an example of a config file line:
usb 0x055f 0x0006
- would have the effect that all USB devices in the system with a vendor
- id of 0x55f and a product id of 0x0006 would be probed and recognized
+ would have the effect that all USB devices in the system with a vendor
+ id of 0x55f and a product id of 0x0006 would be probed and recognized
by the backend.
- If your scanner is not detected automatically, it may be necessary to
- edit the appropriate backend configuration file before using SANE for
- the first time. For a detailed description of each backend's configu-
- ration file, please refer to the relevant backend manual page (e.g.
+ 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 a detailed description of each backend's configu-
+ ration 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
+ 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.
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
+ If the library was compiled with debug support enabled, this
+ environment variable controls the debug level for the USB I/O
subsystem. E.g., a value of 128 requests all debug output to be
printed. Smaller levels reduce verbosity. Values greater than 4
- enable libusb debugging (if available). Example: export
+ enable libusb debugging (if available). Example: export
SANE_DEBUG_SANEI_USB=4.
@@ -148,12 +145,11 @@
sane(7), sane-find-scanner(1), sane-"backendname"(5), sane-scsi(5)
-
Henning Meier-Geinitz <henning@meier-geinitz.de>
-sane-backends 1.0.16 29 May 2005 sane-usb(5)
+sane-backends 1.0.17 16 August 2005 sane-usb(5)
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@lists.alioth.debian.org. You must be subscribed to the list
- to send mail. See http://www.sane-project.org/mailing-lists.html for
+ Send bug reports to the SANE mailing list: sane-
+ devel@lists.alioth.debian.org. You must be subscribed to the list to
+ send mail. See http://www.sane-project.org/mailing-lists.html for
details.
@@ -105,7 +105,7 @@
SEE ALSO
sane(7), xcam(1).
-sane-backends 1.0.16 28 Aug 2002 sane-v4l(5)
+sane-backends 1.0.17 28 Aug 2002 sane-v4l(5)
diff --git a/man/sane.7.html b/man/sane.7.html
index 6f4f78d4..c8bb6ada 100644
--- a/man/sane.7.html
+++ b/man/sane.7.html
@@ -47,9 +47,9 @@
(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.sane-project.org/). Information about other frontends and
- backends can also be found on the SANE homepage.
+ can be downloaded from the SANE homepage (http://www.sane-
+ project.org/). Information about other frontends and backends can also
+ be found on the SANE homepage.
@@ -58,15 +58,15 @@
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.16/sane.tex' are references to text files that
+ `/usr/local/doc/sane-1.0.17/sane.tex' are references to text files that
were copied to the SANE documentation directory
- (/usr/local/doc/sane-1.0.16/) during installation. Everything else is a
+ (/usr/local/doc/sane-1.0.17/) 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.sane-project.org/.
+ the SANE FAQ can be found on the SANE homepage: http://www.sane-
+ project.org/.
SANE device lists
The SANE device lists contain information about the status of SANE
@@ -75,7 +75,7 @@
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.sane-project.org/sane-supported-devices.html. The lists
- are also installed on your system at /usr/local/doc/sane-1.0.16/.
+ are also installed on your system at /usr/local/doc/sane-1.0.17/.
SANE mailing list
There is a mailing list for the purpose of discussing the SANE stan-
@@ -95,12 +95,12 @@
server, etc.).
Compiling and installing SANE
- Look at /usr/local/doc/sane-1.0.16/README and the os-dependent README
+ Look at /usr/local/doc/sane-1.0.17/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).
+ For information about various systems and SCSI controllers see sane-
+ scsi(5).
USB configuration
For information about USB configuration see sane-usb(5).
@@ -137,8 +137,8 @@
apple
The SANE backend for Apple flatbed scanners supports the following
- scanners: AppleScanner, OneScanner and ColorOneScanner. See
- sane-apple(5) for details.
+ scanners: AppleScanner, OneScanner and ColorOneScanner. See sane-
+ apple(5) for details.
artec
The SANE Artec backend supports several Artec/Ultima SCSI flatbed
@@ -177,12 +177,12 @@
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.
+ 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.
+ 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
@@ -207,25 +207,33 @@
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.
+ 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.
+ hp4200
+ The SANE backend for the Hewlett-Packard ScanJet 4200 series. See
+ sane-hp4200(5) for details.
+
hp5400
- The SANE backend for the Hewlett-Packard ScanJet 54XXC series. See
+ 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.
+ 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
+ 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.
+ lexmark
+ This backend supports the Lexmark X1100 series of USB scanners. See
+ sane-lexmark(5) for details.
+
ma1509
The ma1509 backend supports the Mustek BearPaw 1200F USB flatbed
scanner. See sane-ma1509(5) for details.
@@ -246,8 +254,8 @@
mustek
The SANE mustek backend supports most Mustek SCSI flatbed scanners
including the Paragon and ScanExpress series and the 600 II N and 600
- II EP (non-SCSI). Some Trust scanners are also supported. See
- sane-mustek(5) for details.
+ II EP (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
@@ -257,6 +265,11 @@
The mustek_usb backend provides access to some Mustek ScanExpress USB
flatbed scanners. See sane-mustek_usb(5) for details.
+ mustek_usb2
+ The mustek_usb2 backend provides access to scanners using the SQ113
+ chipset like the Mustek BearPaw 2448 TA Pro USB flatbed scanner. See
+ sane-mustek_usb2(5) for details.
+
nec
The SANE nec backend supports the NEC PC-IN500/4C SCSI scanner. See
sane-nec(5) for details.
@@ -296,8 +309,8 @@
scanner. See sane-sceptre(5) for details.
sharp
- The SANE sharp backend supports Sharp SCSI scanners. See
- sane-sharp(5) for details.
+ 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
@@ -328,22 +341,28 @@
usually sold under the Relisys, Trust, Primax, Piotech, Dextra names.
See sane-teco1(5), sane-teco2(5) and sane-teco3(5) for details.
+ u12
+ The sane-u12 backend provides USB flatbed scanners based on Plustek's
+ ASIC 98003 (parallel-port ASIC) and a GeneSys Logics' USB-parport
+ bridge chip like the Plustek OpticPro U(T)12. See sane-u12(5) for
+ details.
+
umax
- The sane-umax backend provides access to several UMAX-SCSI-scanners
+ The sane-umax backend provides access to several UMAX-SCSI-scanners
and some Linotype Hell SCSI-scanners. See sane-umax(5) for details.
umax_pp
- The sane-umax_pp backend provides access to Umax parallel port
+ The sane-umax_pp backend provides access to Umax parallel port
flatbed scanners and the HP 3200C. See 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.
+ 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.sane-project.org/sane-supported-devices.html and the list of
- projects in /usr/local/doc/sane-1.0.16/PROJECTS.
+ Also, have a look at the backend information page at http://www.sane-
+ project.org/sane-supported-devices.html and the list of projects in
+ /usr/local/doc/sane-1.0.17/PROJECTS.
@@ -358,96 +377,96 @@
Backend for Kodak DC20/DC25 Digital Cameras. See sane-dc25(5).
dmc
- Backend for the Polaroid Digital Microscope Camera. See sane-dmc(5).
+ 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
+ (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.sane-project.org/sane-supported-devices.html and the list of
- projects in /usr/local/doc/sane-1.0.16/PROJECTS.
+ Also, have a look at the backend information page at http://www.sane-
+ project.org/sane-supported-devices.html and the list of projects in
+ /usr/local/doc/sane-1.0.17/PROJECTS.
dll
- The sane-dll library implements a SANE backend that provides access
+ 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(8).
+ 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(8).
pnm
- PNM image reader pseudo-backend. The purpose of this backend is pri-
+ PNM image reader pseudo-backend. The purpose of this backend is pri-
marily to aid in debugging of 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).
+ 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
+ systems. 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).
+ 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
+ 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.sane-project.org/sane-supported-devices.html and the list of
- projects in /usr/local/doc/sane-1.0.16/PROJECTS.
+ Also, have a look at the backend information page at http://www.sane-
+ project.org/sane-supported-devices.html and the list of projects in
+ /usr/local/doc/sane-1.0.17/PROJECTS.
- 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 + 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.
- It's not hard to write a SANE backend. It can take some time, however.
- You should have basic knowledge of C and enough patience to work
+ It's not hard to write a SANE backend. It can take some time, however.
+ You should have basic knowledge of C and enough patience to work
through the documentation and find out how your scanner works. Appended
- is a list of some documents that help to write backends and frontends.
+ is a list of some documents that help to write backends and frontends.
- The 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.16/sane.ps (if latex is installed on
+ 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.17/sane.ps (if latex is installed on
your system) and on the SANE website: http://www.sane-project.org/html/
(HTML), or http://www.sane-project.org/sane.ps (Postscript).
- There is some more information for programmers in
- /usr/local/doc/sane-1.0.16/backend-writing.txt. Most of the internal
- SANE routines (sanei) are documented using doxygen: http://www.sane-
- project.org/sanei/. Before a new backend or frontend project is
- started, have a look at /usr/local/doc/sane-1.0.16/PROJECTS for
- projects that are planned or not yet included into the SANE distribu-
- tion and at our bug-tracking system:
- http://www.http://www.sane-project.org/bugs.html.
+ There is some more information for programmers in
+ /usr/local/doc/sane-1.0.17/backend-writing.txt. Most of the internal
+ SANE routines (sanei) are documented using doxygen: http://www.sane-
+ project.org/sanei/. Before a new backend or frontend project is
+ started, have a look at /usr/local/doc/sane-1.0.17/PROJECTS for
+ projects that are planned or not yet included into the SANE distribu-
+ tion and at our bug-tracking system: http://www.http://www.sane-
+ project.org/bugs.html.
- There are some links on how to find out about the protocol of a scan-
+ 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,
+ 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.
@@ -461,134 +480,135 @@
The static libraries implementing the backends.
/usr/local/lib/sane/libsane-*.so
- The shared libraries implementing the backends (present on sys-
+ The shared libraries implementing the backends (present on sys-
tems that support dynamic loading).
- /usr/local/doc/sane-1.0.16/*
- SANE documentation: The standard, READMEs, text files for back-
+ /usr/local/doc/sane-1.0.17/*
+ SANE documentation: The standard, READMEs, text files for back-
ends etc.
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
+ 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,
+ 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
+ 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 being 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
+ Another reason for not being 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 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
+ 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
+ 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 manual page for details. If you can't find
+ 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 manual 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
+ 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
+ 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
+ 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
+ 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.
- We appreciate any help we can get. Please have a look at our web page
+ We appreciate any help we can get. Please have a look at our web page
about contributing to SANE: http://www.sane-project.org/contrib.html
- For reporting bugs or requesting new features, please use our bug- - tracking system: http://www.sane-project.org/bugs.html. You can also - contact the author of your backend directly. Usually the email address - can be found in the /usr/local/doc/sane-1.0.16/AUTHORS file or the - backend's manpage. For general discussion about SANE, please use the - SANE mailing list sane-devel (see http://www.sane-project.org/mail- - ing-lists.html for details). + For reporting bugs or requesting new features, please use our bug- + tracking system: http://www.sane-project.org/bugs.html. You can also + contact the author of your backend directly. Usually the email address + can be found in the /usr/local/doc/sane-1.0.17/AUTHORS file or the + backend's manpage. For general discussion about SANE, please use the + SANE mailing list sane-devel (see http://www.sane-project.org/mailing- + lists.html for details).
- saned(8), 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-niash(5), sane-pie(5), sane-pint(5), sane-plustek(5), sane-plus- - tek_pp(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-u12(5), - sane-umax1220u(5), sane-umax(5), sane-umax_pp(5), sane-usb(5), - sane-v4l(5) + saned(8), 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-genesys(5), sane-gphoto2(5), sane- + gt68xx(5), sane-hp(5), sane-hpsj5s(5), sane-hp4200(5), sane-hp5400(5), + sane-ibm(5), sane-leo(5), sane-lexmark(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-mustek_usb2(5), sane-nec(5), + sane-net(5), sane-niash(5), sane-pie(5), sane-pint(5), sane-plustek(5), + sane-plustek_pp(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-sm3840(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-u12(5), sane-umax1220u(5), sane-umax(5), sane-umax_pp(5), sane- + usb(5), sane-v4l(5)
- David Mosberger-Tang and many many more (see
- /usr/local/doc/sane-1.0.16/AUTHORS for details). This man page was
- written by Henning Meier-Geinitz. Quite a lot of text was taken from
+ David Mosberger-Tang and many many more (see
+ /usr/local/doc/sane-1.0.17/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.16 29 May 2005 sane(7)
+
+sane-backends 1.0.17 16 October 2005 sane(7)
David Mosberger
-sane-backends 1.0.16 30 May 2004 saned(8)
+sane-backends 1.0.17 30 May 2004 saned(8)
- David Mosberger, Andreas Beck, Gordon Matzigkeit and Caskey Dickson + David Mosberger, Andreas Beck, Gordon Matzigkeit, Caskey Dickson, and + many others. For questions and comments contact the sane-devel mail- + inglist (see http://www.sane-project.org/mailing-lists.html).@@ -277,7 +283,7 @@ For vector options, the help output currently has no indication as to how many elements a vector-value should have. -sane-backends 1.0.16 15 April 2005 scanimage(1) +sane-backends 1.0.17 23 Sep 2005 scanimage(1)