diff --git a/man/sane-mustek.5.html b/man/sane-mustek.5.html
index 24fc1cce..627bca49 100644
--- a/man/sane-mustek.5.html
+++ b/man/sane-mustek.5.html
@@ -12,15 +12,16 @@
NAME
- sane-mustek - SANE backend for Mustek SCSI flatbed scanners
+ sane-mustek - SANE backend for Mustek SCSI flatbed scanners (and some
+ other devices)
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:
+ The sane-mustek library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to Mustek (and some relabeled Trust and
+ Primax) SCSI and parport flatbed scanners. At present, the following
+ scanners are known to work more or less with this backend:
Paragon MFS-6000CX
Paragon MFS-12000CX
@@ -30,12 +31,13 @@
Paragon MFS-8000SP
Paragon MFS-1200SP, MFS-12000SP
ScanExpress 6000SP
- ScanExpress 12000SP, 12000SP Plus, Paragon 1200 III SP, Scan-
+ ScanExpress 12000SP, 12000SP Plus, Paragon 1200 III SP, Scan-
Magic 9636S, 9636S Plus
Paragon 1200 LS
ScanExpress A3 SP
Paragon 1200 SP Pro
Paragon 1200 A3 Pro
+ Paragon 600 II EP
Paragon 600 II N
Trust Imagery 1200
Trust Imagery 1200 SP
@@ -46,20 +48,21 @@
More details can be found on the Mustek SCSI backend homepage
http://www.meier-geinitz.de/sane/mustek-backend/.
- Don't mix up MFS (Paragon), Pro and ScanExpress models! They're com-
+ Don't mix up MFS (Paragon), Pro and ScanExpress models! They're com-
pletely different. Check the exact model name!
- Note that most of the above scanners come with a SCSI interface. The
- only non-SCSI scanner that has some support at this point is the 600 II
- N scanner which comes with its own parallel port adapter (i.e., it does
- 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).
+ Note that most of the above scanners come with a SCSI interface. The
+ only non-SCSI scanners that have some support at this point is the 600
+ II N and 600 II EP scanners. The former one comes with its own parallel
+ port adapter (i.e., it does not attach to the printer port). Both scan-
+ ners use the SCSI protocoll internally, too. More info on how to use
+ these parallel port scanners can be found below in section PARALLEL
+ PORT SCANNERS. Other parallel port scanners are not supported by this
+ backend but you may be successful using the Mustek parallel port back-
+ end mustek_pp, see sane-mustek_pp(5). USB scanners are also not sup-
+ ported by this backend but the ma1509, mustek_usb, gt68xx, and plustek
+ backends include support for some of them, see sane-ma1509(5), 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
@@ -67,7 +70,7 @@
noises and the scan mechanism may be damaged. Thus, if you hear such a
noise, IMMEDIATELY turn off the scanner. This shouldn't happen if your
scanner is in the list of known scanners. There is more information in
- the /usr/local/doc/sane-1.0.13/PROBLEMS file.
+ the /usr/local/doc/sane-1.0.14-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-
@@ -87,87 +90,88 @@
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.
+ responds to a SCSI scanner or the port number at which the parallel
+ port scanners can be found (see section PARALLEL PORT SCANNERS 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/sg0 or /dev/sg3, for example. See sane-scsi(5) for
+ details.
CONFIGURATION
- The contents of the mustek.conf file is a list of options and device
+ 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
+ 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,
+ 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
+ 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.
+ 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
+ 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-
+ 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
+ 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
+ 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
+ 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
+ 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-
+ 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
+ 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
+ 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
+ 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.
+ 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:
@@ -186,74 +190,67 @@
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-
+ the same as that of parallel port scanners, connecting it to the com-
puters parallel port will NOT work.
- Mustek SCSI scanners are typically delivered with an ISA SCSI adapter.
+ Mustek SCSI scanners are typically delivered with an ISA SCSI adapter.
Unfortunately, that adapter is not worth much since it is not interrupt
- driven. It is (sometimes) possible to get the supplied card to work,
- but without interrupt line, scanning will be very slow and put so much
+ driven. It is (sometimes) possible to get the supplied card to work,
+ but without interrupt line, scanning will be very slow and put so much
load on the system, that it becomes almost unusable for other tasks.
- If you already have a working SCSI controller in your system, you
- should consider that Mustek scanners do not support the SCSI-2 discon-
- nect/reconnect protocol and hence tie up the SCSI bus while a scan is
- in progress. This means that no other SCSI device on the same bus can
+ If you already have a working SCSI controller in your system, you
+ should consider that Mustek scanners do not support the SCSI-2 discon-
+ nect/reconnect protocol and hence tie up the SCSI bus while a scan is
+ in progress. This means that no other SCSI device on the same bus can
be accessed while a scan is in progress.
- Because the Mustek-supplied adapter is not worth much and because
- Mustek scanners do not support the SCSI-2 disconnect/reconnect proto-
- col, it is recommended to install a separate (cheap) SCSI controller
+ Because the Mustek-supplied adapter is not worth much and because
+ Mustek scanners do not support the SCSI-2 disconnect/reconnect proto-
+ col, it is recommended to install a separate (cheap) SCSI controller
for Mustek scanners. For example, ncr810 based cards are known to work
fine and cost as little as fifty US dollars.
- For Mustek scanners, it is typically necessary to configure the low-
- level SCSI driver to disable synchronous transfers (sync negotiation),
- tagged command queuing, and target disconnects. See sane-scsi(5) for
+ For Mustek scanners, it is typically necessary to configure the low-
+ level SCSI driver to disable synchronous transfers (sync negotiation),
+ tagged command queuing, and target disconnects. See 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-
+ 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.
+ 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).
+PARALLEL PORT SCANNERS
+ This backend has support for the Paragon 600 II EP and Paragon 600 II N
+ parallel port scanners. Note that the latter scanner comes with its
+ own ISA card that implements a funky parallel port (in other words, the
+ scanner does not connected to the printer parallel port).
- This scanner can be configured by listing the port number of the
- adapter in the mustek.conf file. Valid port numbers are 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:
+ These scanners can be configured by listing the port number of the
+ adapter or the parallel port in the mustek.conf file. Valid port num-
+ bers for the 600 II N are 0x26b, 0x2ab, 0x2eb, 0x22b, 0x32b, 0x36b,
+ 0x3ab, 0x3eb. For the 600 II EP use one of these: 0x378, 0x278, 0x3bc.
+ Pick one that doesn't conflict with the other hardware in your com-
+ puter. 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.
+ Note that for these scanners usually root privileges are required to
+ access the I/O ports. Thus, either make frontends such as scanimage(1)
+ and xscanimage(1) setuid root (generally not recommended for safety
+ reasons) or, alternatively, access this backend through the network
+ daemon saned(1).
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
+ Also note that after a while of no activity, some scanners themselves
(not the SANE backend) turns off their CCFL lamps. This shutdown is not
always perfect with the result that the lamp sometimes continues to
glow dimly at one end. This doesn't appear to be dangerous since as
@@ -314,14 +311,14 @@
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.13/mustek/mustek.CHANGES
+ /usr/local/doc/sane-1.0.14-cvs/mustek/mustek.CHANGES
http://www.meier-geinitz.de/sane/mustek-backend/
AUTHOR
David Mosberger, Andreas Czechanowski, Andreas Bolsch (SE extensions),
- Henning Meier-Geinitz
+ Henning Meier-Geinitz, James Perry (600 II EP).
@@ -337,7 +334,7 @@
More detailed bug information is available at the Mustek backend home-
page: http://www.meier-geinitz.de/sane/mustek-backend/.
-sane-backends 1.0.13 5 Dec 2002 sane-mustek(5)
+sane-backends 1.0.14-cvs 25 Dec 2002 sane-mustek(5)
diff --git a/man/sane-mustek_pp.5.html b/man/sane-mustek_pp.5.html
index 3b4e02e3..3f7685ce 100644
--- a/man/sane-mustek_pp.5.html
+++ b/man/sane-mustek_pp.5.html
@@ -24,24 +24,19 @@
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. Currently
- there is no CCD support however. For CCD scanners, use the sane-
- mustek_pp_ccd(5) backend.
+ The current version of this backend supports both CCD type scanners and
+ CIS type scanners.
The following scanners might work with this backend:
- CCD scanners (currently not hooked up yet, use mustek_pp_ccd backend)
+ CCD scanners
Model: ASIC ID: CCD Type: works:
-------------------- --------- ---------- -------
SE 6000 P 1013 00 yes
SM 4800 P 1013/1015 04/01 yes
- SE 1200 ED Plus 1015 01 partly
- SM 1200 ED Plus 1015 01 partly
+ SE 1200 ED Plus 1015 01 no
+ SM 1200 ED Plus 1015 01 no
SE 12000 P 1505 05 no
600 III EP Plus 1013/1015 00/01 yes
SE 600 SEP 1013 ?? yes
@@ -71,18 +66,18 @@
Trust
Easy Connect 9600+ 600 CP yes
- (*) Calibration problems existed with earlier version of this
+ (*) Calibration problems existed with earlier version of this
driver. They seem to be solved now.
- (**) Problems have been reported in the past for the MD/LT9850 type
- (striped scans, head moving in wrong direction at some resolu-
- tions). It is not known whether the current version of the
+ (**) Problems have been reported in the past for the MD/LT9850 type
+ (striped scans, head moving in wrong direction at some resolu-
+ tions). It is not known whether the current version of the
driver still has these problems.
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-
+ 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.
@@ -91,17 +86,17 @@
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
+ 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
+ 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,28 +108,32 @@
<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
drivers are:
cis600 : for 600 CP, 96 CP & OEM versions
cis1200 : for 1200 CP & OEM versions
cis1200+ : for 1200 CP+ & OEM versions
+ ccd300 : for 600 IIIE P & OEM version
Choosing the wrong driver can damage your scanner!
Especially, using the 1200CP settings on a 600CP can be harmful.
@@ -156,6 +155,12 @@
scanner Mustek_600CP 0x378 cis600
+ scanner Mustek_600IIIEP * ccd300
+
+ If in doubt which port you have to use, or whether your scanner is
+ detected at all, you can use sane-find-scanner -p to probe all config-
+ ured ports.
+
CONFIGURATION
@@ -212,7 +217,23 @@
CCD driver options
- To be defined.
+ top <value> Number of scanlines to skip to the start of the scan
+ area. The number can be any positive integer. Values known
+ to me are 47 and 56.
+ Default value: 47
+ Minimum: 0
+ Maximum: none
+
+ Example: option top 56
+
+ waitbank <value> The number of usecs to wait for a bank change. You
+ should not touch this value actually. May be any positive
+ integer
+ Default value: 700
+ Minimum: 0
+ Maximum: none
+
+ Example: option waitbank 700
A sample configuration file is shown below:
@@ -243,6 +264,15 @@
option bw 130
option top_skip 0.2
+ #
+ # A Mustek 600 III EPP on port parport0
+ #
+ scanner "Mustek 600 III EPP" parport0 ccd300
+
+ # Some calibration options (examples!).
+ option bw 130
+ option top 56
+
FILES
@@ -308,10 +338,10 @@
SEE ALSO
- sane(7), sane-mustek_pp_ccd(5), sane-mustek(5), sane-net(5), saned(1)
+ sane(7), sane-mustek(5), sane-net(5), saned(1), sane-find-scanner(1)
For latest bug fixes and information see
- http://www.penguin-breeder.org/?page=mustek_pp
+ http://www.penguin-breeder.org/sane/mustek_pp/
For the latest CIS driver versions, see
http://home.tiscalinet.be/EddyDeGreef/
@@ -330,10 +360,6 @@
first to the list before you can send emails... see
http://www.sane-project.org/mailing-lists.html)
- * 1013 support isn't bullet proofed
- * 1505 support isn't even present
- * 1015 only works for CCD type 00 & 01 (01 only bw/grayscale)
-
BUG REPORTS
@@ -364,7 +390,7 @@
some nice greetings
- February 20 2002 sane-mustek_pp(5)
+ November 17 2003 sane-mustek_pp(5)
diff --git a/man/sane-mustek_usb.5.html b/man/sane-mustek_usb.5.html
index 94a8f9f9..44920074 100644
--- a/man/sane-mustek_usb.5.html
+++ b/man/sane-mustek_usb.5.html
@@ -149,8 +149,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.13/mustek_usb/mustek_usb.CHANGES,
- /usr/local/doc/sane-1.0.13/mustek_usb/mustek_usb.TODO
+ /usr/local/doc/sane-1.0.14-cvs/mustek_usb/mustek_usb.CHANGES,
+ /usr/local/doc/sane-1.0.14-cvs/mustek_usb/mustek_usb.TODO
http://www.meier-geinitz.de/sane/mustek_usb-backend/
@@ -164,20 +164,19 @@
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.
+ can't be reset (toggle = DATA0). That means, any operation that tries
+ to reset the device will result in running into timeouts.
- That means that this backend will fail when it is loaded the second
- time in some configurations: E.g. using libusb, (Free|Open|Net)BSD or
- with Linux if you unload and reload the scanner module. The only choice
- is to replug the scanner in this case. The workaround for Linux is to
- use the scanner module (modprobe scanner) instead of libusb. See sane-
- usb(5) for details.
+ In earlier versions this backend failed when it is loaded the second
+ time in some configurations. The only choice was to replug the scanner
+ in this case. The backend uses a workaround for that bug now but it's
+ only tested on Linux. Reports for other operating systems are apprici-
+ ated.
- More detailed bug information is available at the Mustek backend home-
+ More detailed bug information is available at the Mustek backend home-
page http://www.meier-geinitz.de/sane/mustek_usb-backend/.
-sane-backends 1.0.13 21 Oct 2003 sane-mustek_usb(5)
+sane-backends 1.0.14-cvs 3 Mar 2004 sane-mustek_usb(5)
diff --git a/man/sane-nec.5.html b/man/sane-nec.5.html
index 609e7ad9..2606ab8d 100644
--- a/man/sane-nec.5.html
+++ b/man/sane-nec.5.html
@@ -67,7 +67,7 @@
AUTHORS
Kazuya Fukuda
-sane-backends 1.0.13 17 Feb 2000 sane-nec(5)
+sane-backends 1.0.14-cvs 17 Feb 2000 sane-nec(5)
diff --git a/man/sane-net.5.html b/man/sane-net.5.html
index b1da7e26..834bbbd7 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.13 8 Oct 2002 sane-net(5)
+sane-backends 1.0.14-cvs 8 Oct 2002 sane-net(5)
diff --git a/man/sane-pie.5.html b/man/sane-pie.5.html
index 0e6be386..45a525bf 100644
--- a/man/sane-pie.5.html
+++ b/man/sane-pie.5.html
@@ -66,7 +66,7 @@
Please send any information and bug-reports to:
Simon Munton <simon@munton.demon.co.uk>
-sane-backends 1.0.13 7 Sept 2000 sane-pie(5)
+sane-backends 1.0.14-cvs 7 Sept 2000 sane-pie(5)
diff --git a/man/sane-pint.5.html b/man/sane-pint.5.html
index 2bffdbbb..16a09e33 100644
--- a/man/sane-pint.5.html
+++ b/man/sane-pint.5.html
@@ -135,7 +135,7 @@
No testing has been done on three-pass or handheld scanners, or with
Automatic Document Feeder support.
-sane-backends 1.0.13 13 May 1998 sane-pint(5)
+sane-backends 1.0.14-cvs 13 May 1998 sane-pint(5)
diff --git a/man/sane-plustek.5.html b/man/sane-plustek.5.html
index f7d26f65..77aa299e 100644
--- a/man/sane-plustek.5.html
+++ b/man/sane-plustek.5.html
@@ -12,8 +12,7 @@
NAME
- sane-plustek - SANE backend for Plustek parallel port and LM983[1/2/3]
- based USB flatbed scanners
+ sane-plustek - SANE backend for LM983[1/2/3] based USB flatbed scanners
@@ -30,8 +29,8 @@
The Backend is able to support USB scanner based on the National Semi-
conductor chipsets LM9831, LM9832 and LM9833. The following tables show
various devices which are currently reported to work. If your Plustek
- scanner has another Product ID, then the device is NOT supported, as it
- contains an unsupported ASIC inside.
+ scanner has another Product ID, then the device is NOT supported by
+ this backend.
Vendor Plustek - ID: 0x07B3
----------------------------------------------------------
@@ -68,7 +67,9 @@
USB Model: ASIC: Properties: Prod-ID
----------------------------------------------------------
BearPaw 1200 LM9831 600x1200dpi 42bit 512Kb 0x1000
+ BearPaw 1200 LM9832 600x1200dpi 42bit 512Kb 0x1001*
BearPaw 2400 LM9832 1200x2400dpi 42bit 2Mb 0x1001
+ * see also description for model override switch below!
Vendor UMAX - ID: 0x1606
----------------------------------------------------------
@@ -96,6 +97,7 @@
----------------------------------------------------------
CanoScan N650/656U LM9832 600x1200dpi 42bit 512Kb 0x2206
CanoScan N1220U LM9832 1200x2400dpi 42bit 512Kb 0x2207
+ CanoScan D660U LM9832 600x1200dpi 42bit 512Kb 0x2208
CanoScan N670/676U LM9833 600x1200dpi 48bit 512Kb 0x220D
CanoScan N1240U LM9833 1200x2400dpi 48bit 512Kb 0x220E
CanoScan LIDE20 LM9833 600x1200dpi 48bit 512Kb 0x220D
@@ -108,13 +110,18 @@
The SCSI scanner OpticPro 19200S is a rebadged Artec AM12S scanner and
is supported by the Artec backend.
Only the National Semiconductor LM983[1/2/] based devices of Plustek
- are supported by this driver. Older versions of the U12, the UT12, the
+ are supported by this backend. Older versions of the U12, the UT12, the
U1212 and U1248 (GrandTech chipset) are not supported.
Model Chipset backend
---------------------------
U1248 GrandTech gt68xx
UT16B GrandTech gt68xx
+ U12 P98003 u12
+ UT12 P98003 u12
+ 1212U P98003 u21
+ For a more complete and up to date list see: http://www.sane-
+ project.org/sane-supported-devices.html
@@ -127,9 +134,9 @@
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
- product-id has not been specified, the backend tries to detect this by
+ [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 ist set to auto
then the next matching device is used.
@@ -139,13 +146,21 @@
t specifies the warmup period in seconds
option lampOff t
- t is the time in seconds for switching off the lamps in standby
+ 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 mov m
+ m is the model override switch. It works only with Mustek
+ BearPaw devices.
+ m/PID | 0x1000 | 0x1001
+ ------+--------------+--------------
+ 0 | BearPaw 1200 | BearPaw 2400
+ 1 | no function | BearPaw 1200
+
option invertNegatives b
b 0 --> do not invert the picture during negativ scans, 1 -->
invert picture
@@ -211,17 +226,9 @@
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.
- Alternatively, the backend is able to access your scanner via libusb.
- You might use sane-find-scanner to check that you have access to your
- device.
+ you have access to the device-node. For more details see sane-usb (5)
+ manpage. You might use sane-find-scanner to check that you have access
+ to your device.
Note:
If there's no configuration file, the backend defaults to device auto
@@ -240,6 +247,37 @@
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_PLUSTEK
+ If the library was compiled with debug support enabled, this
+ environment variable controls the debug level for this backend.
+ Higher debug levels increase the verbosity of the output.
+
+ Example: export SANE_DEBUG_PLUSTEK=10
+
+
+
+SEE ALSO
+ sane(7), sane-usb(5), sane-plustek(5),
+ /usr/local/doc/sane-1.0.14-cvs/plustek/Plustek-USB.changes
+ http://www.gjaeger.de/scanner/plustek.html
+
+
CONTACT AND BUG-REPORTS
Please send any information and bug-reports to:
@@ -254,14 +292,14 @@
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
+ 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-
+ ues greater than 19 force the backend to output raw data files, which
+ could be rather large. The ending of these files is ".raw". For prob-
lem reports it should be enough the set the verbosity to 13.
@@ -273,7 +311,7 @@
of the CDD-sensor and the stepper motor i.e. you have a
600x1200 dpi scanner and you are scanning using 800dpi,
so scaling is necesary, because the sensor only delivers
- 600dpi but the motor is capable to perform 800dpi steps.
+ 600dpi but the motor is capable to perform 1200dpi steps.
* Plusteks' model policy is somewhat inconsistent. This
means, they sell technical different devices under the
same product name. Therefore it is possible that some
@@ -282,7 +320,7 @@
the one your device has.
* Negative/Slide scanning quality is poor.
-sane-backends 1.0.13 27 October 2003 sane-plustek(5)
+sane-backends 1.0.14-cvs 22 Mar 2004 sane-plustek(5)
diff --git a/man/sane-plustek_pp.5.html b/man/sane-plustek_pp.5.html
index 8fdc192f..5be16f4b 100644
--- a/man/sane-plustek_pp.5.html
+++ b/man/sane-plustek_pp.5.html
@@ -113,13 +113,13 @@
/usr/local/etc/sane.d/plustek_pp.conf
- See the plustek_pp.conf file for examples.
+ See this file for examples.
CONFIGURATION
- Beside the kernel-module options, which are described below, you need
- to enable the parallel port device in the configuration file
+ This section decribes the backends' configuration file entries. The
+ file is located at:
/usr/local/etc/sane.d/plustek_pp.conf
@@ -135,24 +135,89 @@
device /dev/pt_drv
- direct tells the backend, that the following devicename (here
- /dev/pt_drv ) has to be interpreted as parallel port scanner device.
+ 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
+ be used, when a kernel-module has been built out of the backend
+ sources. See below for more instructions about this.
- To have this device, you will need to setup the kernel module. As the
- driver is a loadable kernel module, it is configured by invoking insmod
- with the appropriate parameters or appending the options to the file
- /etc/conf.modules
+ Further 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 mov m
+ m is the model override switch, which only works in direct mode.
+ 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)
+
+ See the plustek_pp.conf file for examples.
+
+
+
+BUILDING THE KERNEL MODULE
+ As mentioned before, the plustek_pp backend code can also be compiled
+ and installed as linux kernel module. To do so, you will need the
+ source-files of this sane-backend installation. Unpack this tar-ball
+ and go to the directory:
+ sane-backends/doc/plustek
+ Within this directory, you should find a file called:
+ Makefile.module
+ Now if your Linux kernelsources are installed correctly, it should be
+ possible to build, install and load the module pt_drv. Try
+ make -f Makefile.module
+ to obtain a help text, about the targets, the makefile supports.
+ Use
+ make -f Makefile.module all
+ to build the module. Use
+ make -f Makefile.module install
+ to install the module. Use
+ make -f Makefile.module load
+ to load the module.
+ Note: Installing and loading the can only be done as superuser.
+
+
+
+KERNEL MODULE SETUP
+ 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/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-
+ 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
+ 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-
+ ppp specifies the port base address, where the scanner is con-
nected to. The default value is 0x378 which normaly is standard.
warmup=www
@@ -160,7 +225,7 @@
until the driver will start to scan. The default value is 30.
lOffonEnd=e
- e specifies the behaviour when unloading the driver, 1 -->
+ e specifies the behaviour when unloading the driver, 1 -->
switch lamps off, 0 --> do not change lamp status
slowIO=s
@@ -168,7 +233,7 @@
delayed functions, 0 --> use the non-delayed ones
forceMode=fm
- fm specifies port mode which should be used, 0 --> autodetec-
+ fm specifies port mode which should be used, 0 --> autodetec-
tion, 1 --> use SPP mode and 2 --> use EPP mode
mov=m
@@ -187,8 +252,8 @@
been detected) enables A3 scanning
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)
+ 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
@@ -196,19 +261,20 @@
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
+ 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.
+
+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 parallel ports.
Former Plustek scanner models (4830, 9630) supplied a ISA parallel port
adapter card. This card is not supported by the driver.
@@ -221,12 +287,6 @@
See the plustek_pp.conf file for examples.
-
-BUILDING THE KERNEL MODULE
- As mentioned before, the plustek_pp backend code can also be compiled
- and installed as linux kernel module...
-
-
FILES
/usr/local/etc/sane.d/plustek_pp.conf
@@ -243,6 +303,37 @@
The Linux Kernelmodule.
+
+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_PLUSTEK_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_PLUSTEK_PP=10
+
+
+
+SEE ALSO
+ sane(7),
+ /usr/local/doc/sane-1.0.14-cvs/plustek/Plustek-PARPORT.changes
+ http://www.gjaeger.de/scanner/plustek.html
+
+
CONTACT AND BUG-REPORTS
Please send any information and bug-reports to:
@@ -258,8 +349,8 @@
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).
+ variable SANE_DEBUG_PLUSTEK_PP before calling your favorite scan-fron-
+ tend (i.e. xscanimage).
i.e.: export SANE_DEBUG_PLUSTEK_PP=20 ; xscanimage
The value controls the verbosity of the backend.
@@ -296,7 +387,7 @@
* The scanspeed on 600x1200 dpi models is slow.
* The scanquality of the A3I is poor
-sane-backends 1.0.13 24 September 2003 sane-plustek_pp(5)
+sane-backends 1.0.14-cvs 13 Jan 2004 sane-plustek_pp(5)
diff --git a/man/sane-pnm.5.html b/man/sane-pnm.5.html
index 1dd5182a..653f595a 100644
--- a/man/sane-pnm.5.html
+++ b/man/sane-pnm.5.html
@@ -74,7 +74,7 @@
SEE ALSO
sane(7)
-sane-backends 1.0.13 22 April 2001 sane-pnm(5)
+sane-backends 1.0.14-cvs 22 April 2001 sane-pnm(5)
diff --git a/man/sane-qcam.5.html b/man/sane-qcam.5.html
index 597726ab..0bcb2eeb 100644
--- a/man/sane-qcam.5.html
+++ b/man/sane-qcam.5.html
@@ -109,7 +109,7 @@
SEE ALSO
sane(7)
-sane-backends 1.0.13 25 October 1997 sane-qcam(5)
+sane-backends 1.0.14-cvs 25 October 1997 sane-qcam(5)
diff --git a/man/sane-ricoh.5.html b/man/sane-ricoh.5.html
index 1acc26b7..36b03c01 100644
--- a/man/sane-ricoh.5.html
+++ b/man/sane-ricoh.5.html
@@ -85,7 +85,7 @@
AUTHOR
Feico W. Dillema
-sane-backends 1.0.13 24 Jun 2000 sane-ricoh(5)
+sane-backends 1.0.14-cvs 24 Jun 2000 sane-ricoh(5)
diff --git a/man/sane-s9036.5.html b/man/sane-s9036.5.html
index 991fc720..bc50dca0 100644
--- a/man/sane-s9036.5.html
+++ b/man/sane-s9036.5.html
@@ -83,7 +83,7 @@
Ingo Schneider
-sane-backends 1.0.13 24 Jun 2000 sane-s9036(5)
+sane-backends 1.0.14-cvs 24 Jun 2000 sane-s9036(5)
diff --git a/man/sane-sceptre.5.html b/man/sane-sceptre.5.html
index c668a098..c5913ab6 100644
--- a/man/sane-sceptre.5.html
+++ b/man/sane-sceptre.5.html
@@ -147,7 +147,7 @@
The package is actively maintained by Frank Zago.
http://www.zago.net/sane/#sceptre
-sane-backends 1.0.13 April 21st, 2002 sane-sceptre(5)
+sane-backends 1.0.14-cvs April 21st, 2002 sane-sceptre(5)
diff --git a/man/sane-scsi.5.html b/man/sane-scsi.5.html
index 60673e8e..9dd05eb5 100644
--- a/man/sane-scsi.5.html
+++ b/man/sane-scsi.5.html
@@ -303,7 +303,7 @@
AUTHOR
David Mosberger
-sane-backends 1.0.13 28 Oct 2003 sane-scsi(5)
+sane-backends 1.0.14-cvs 28 Oct 2003 sane-scsi(5)
diff --git a/man/sane-sharp.5.html b/man/sane-sharp.5.html
index f9c9c430..25679dc3 100644
--- a/man/sane-sharp.5.html
+++ b/man/sane-sharp.5.html
@@ -366,7 +366,7 @@
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.13 21 Nov 2000 sane-sharp(5)
+sane-backends 1.0.14-cvs 21 Nov 2000 sane-sharp(5)
diff --git a/man/sane-sm3600.5.html b/man/sane-sm3600.5.html
index adac5174..04a1eab7 100644
--- a/man/sane-sm3600.5.html
+++ b/man/sane-sm3600.5.html
@@ -110,7 +110,7 @@
Marian Eichholz (eichholz@computer.org)
Glenn Ramsey (glenn@componic.com)
-sane-backends 1.0.13 10.02.2002 sane-sm3600(5)
+sane-backends 1.0.14-cvs 10.02.2002 sane-sm3600(5)
diff --git a/man/sane-snapscan.5.html b/man/sane-snapscan.5.html
index f7db3b68..e300bdde 100644
--- a/man/sane-snapscan.5.html
+++ b/man/sane-snapscan.5.html
@@ -114,7 +114,7 @@
Man page by Henning Meier-Geinitz (mostly based on the web pages and
source code).
-sane-backends 1.0.13 26 May 2001 sane-snapscan(5)
+sane-backends 1.0.14-cvs 26 May 2001 sane-snapscan(5)
diff --git a/man/sane-sp15c.5.html b/man/sane-sp15c.5.html
index 5671c384..3c0f6b16 100644
--- a/man/sane-sp15c.5.html
+++ b/man/sane-sp15c.5.html
@@ -78,7 +78,7 @@
working first driver. Watch this space for changes.
-sane-backends 1.0.13 17 Apr 2002 sane-sp15c(5)
+sane-backends 1.0.14-cvs 17 Apr 2002 sane-sp15c(5)
diff --git a/man/sane-st400.5.html b/man/sane-st400.5.html
index e9cd6c8e..7df35510 100644
--- a/man/sane-st400.5.html
+++ b/man/sane-st400.5.html
@@ -153,7 +153,7 @@
AUTHOR
Ingo Wilken <Ingo.Wilken@informatik.uni-oldenburg.de>
-sane-backends 1.0.13 08 Mar 1999 sane-st400(5)
+sane-backends 1.0.14-cvs 08 Mar 1999 sane-st400(5)
diff --git a/man/sane-tamarack.5.html b/man/sane-tamarack.5.html
index 45181dde..1da54146 100644
--- a/man/sane-tamarack.5.html
+++ b/man/sane-tamarack.5.html
@@ -87,7 +87,7 @@
AUTHOR
Roger Wolff
-sane-backends 1.0.13 24 Jun 2000 sane-tamarack(5)
+sane-backends 1.0.14-cvs 24 Jun 2000 sane-tamarack(5)
diff --git a/man/sane-teco1.5.html b/man/sane-teco1.5.html
index ae7b39b7..1405c565 100644
--- a/man/sane-teco1.5.html
+++ b/man/sane-teco1.5.html
@@ -28,13 +28,13 @@
Vendor Model TECO model status
---------------------- -------------- -----------
Relisys AVEC 2400 VM3520 tested
- Relisys AVEC 2412 VM3520+ untested
+ Relisys AVEC 2412 VM3520+ tested
Relisys AVEC 4800 VM4530 untested
Relisys AVEC 4816 VM4530+ untested
Relisys RELI 2400 VM3530 untested
Relisys RELI 2412 VM3530+ tested
Relisys RELI 2412 VM3530+ untested
- Relisys RELI 4816 VM4540 untested
+ Relisys RELI 4816 VM4540 tested
Relisys RELI 4830 VM4542 tested
Relisys RELI 9600 VM6530 untested
Relisys RELI 9612 VM6530* untested
@@ -166,7 +166,7 @@
Thanks to Gerard Delafond for the VM4542 support. Thanks to Jean-Yves
Simon for the VM3510 support.
-sane-backends 1.0.13 August 30th, 2002 sane-teco1(5)
+sane-backends 1.0.14-cvs August 30th, 2002 sane-teco1(5)
diff --git a/man/sane-teco2.5.html b/man/sane-teco2.5.html
index 18d8a10d..2e108632 100644
--- a/man/sane-teco2.5.html
+++ b/man/sane-teco2.5.html
@@ -29,17 +29,17 @@
---------------------- -------------- -----------
Mustek ScanMagic 4830S VM3575 untested
- Primax Jewel 4800 VM356A tested
- Primax Profi 9600 VM6575 tested
- Primax Profi 19200 VM6586 tested
- Relisys APOLLO Express 3 VM356A tested
- Relisys APOLLO Express 6 VM6565 tested
+ Primax Jewel 4800 VM356A basic
+ Primax Profi 9600 VM6575 basic
+ Primax Profi 19200 VM6586 good
+ Relisys APOLLO Express 3 VM356A basic
+ Relisys APOLLO Express 6 VM6565 good
Relisys APOLLO Express 12 ? untested
- Relisys AVEC II S3 VM3564 tested
- Relisys AVEC Super 3 VM3575 tested
- Relisys SCORPIO Pro VM6575 tested
- Relisys SCORPIO Pro-S VM6586 tested
- Relisys SCORPIO Super 3 VM3575 tested
+ Relisys AVEC II S3 VM3564 basic
+ Relisys AVEC Super 3 VM3575 basic
+ Relisys SCORPIO Pro VM6575 good
+ Relisys SCORPIO Pro-S VM6586 untested
+ Relisys SCORPIO Super 3 VM3575 basic
For all these scanners, black&white and grayscale mode work well. How-
ever, most of them do not support more than a handful of resolutions in
@@ -104,20 +104,33 @@
(color mode only) can be used to download a user defined gamma
table for the blue channel. The table must be 256 bytes long.
- --white-level
- (VM3564, VM356A, VM3575 only)can be used to reduce the noise,
- when scanning some sheets by changing the calibration value
- loaded into the scanner.
+ --white-level-r
+ (VM3564, VM356A, VM3575 only) Selects what red radiance level
+ should be considered "white", when scanning some sheets by
+ changing the calibration value loaded into the scanner. Scale
+ 0..64 in steps of 1.
+
+ --white-level-g
+ (VM3564, VM356A, VM3575 only) Selects what green radiance level
+ should be considered "white", when scanning some sheets by
+ changing the calibration i value loaded into the scanner. Scale
+ 0..64 in steps of 1.
+
+ --white-level-g
+ (VM3564, VM356A, VM3575 only) Selects what blue radiance level
+ should be considered "white", when scanning some sheets by
+ changing the calibration value loaded into the scanner. Scale
+ 0..64 in steps of 1.
--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
+ 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
+ The configuration file /usr/local/etc/sane.d/teco2.conf supports only
one information: the device name to use (eg /dev/scanner).
@@ -134,13 +147,13 @@
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.
+ 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
+ Either 0 or 1. Selects the algorithm for the calibration. A
value of 1 seems to give better scans on the VM3575. Feedback on
it is welcome. For VM356A and VM3575 default 1. For other sup-
ported types default 0.
@@ -148,8 +161,8 @@
LIMITATIONS
- The windows TWAIN driver has many more options than this SANE backend.
- However they are only software adjustments. This backend only imple-
+ The windows TWAIN driver has many more options than this SANE backend.
+ However they are only software adjustments. This backend only imple-
ments what the scanner can support.
@@ -165,33 +178,32 @@
AUTHORS
- The package is actively maintained by Frank Zago, Gerard Klaver.
- http://www.zago.net/sane/#teco2
- http://gkall.hobby.nl/index.html
+ Frank Zago http://www.zago.net/sane/#teco2
- Gerard Klaver contributed a patch to support the VM3564 and VM356A.
+ The package is actively maintained by Gerard Klaver.
+ http://gkall.hobby.nl/teco2.html
CREDITS
Thanks to:
- Gerard Klaver for his relentless VM3575 testings.
+ Gerard Klaver for his relentless VM3575 testings and contributed a
+ patch to support the VM3564 and VM356A.
Mark Plowman for providing the first SCSI traces from a VM3575.
- Andreas Klaedtke for providing the first SCSI traces from a VM6586 and
+ Andreas Klaedtke for providing the first SCSI traces from a VM6586 and
for his testing, and to Stefan von Dombrowski for his testing.
- Nicolas Peyresaubes for providing the first SCSI traces from a VM656A
+ Nicolas Peyresaubes for providing the first SCSI traces from a VM656A
and for his testing.
Dave Parker for testing the support for the VM6575.
Michael Hoeller for his testing the VM356A.
-
-sane-backends 1.0.13 23 October 2003 sane-teco2(5)
+sane-backends 1.0.14-cvs 15 January 2004 sane-teco2(5)
diff --git a/man/sane-teco3.5.html b/man/sane-teco3.5.html
index 0aa07e3c..8de004ae 100644
--- a/man/sane-teco3.5.html
+++ b/man/sane-teco3.5.html
@@ -139,7 +139,7 @@
The package is actively maintained by Frank Zago.
http://www.zago.net/sane/#teco3
-sane-backends 1.0.13 25 July 2002 sane-teco3(5)
+sane-backends 1.0.14-cvs 25 July 2002 sane-teco3(5)
diff --git a/man/sane-test.5.html b/man/sane-test.5.html
index 2e419a66..38edd599 100644
--- a/man/sane-test.5.html
+++ b/man/sane-test.5.html
@@ -279,7 +279,7 @@
BUGS
- config file values aren't tested for correctness
-sane-backends 1.0.13 24 Jul 2002 sane-test(5)
+sane-backends 1.0.14-cvs 24 Jul 2002 sane-test(5)
diff --git a/man/sane-u12.5.html b/man/sane-u12.5.html
new file mode 100644
index 00000000..b5099955
--- /dev/null
+++ b/man/sane-u12.5.html
@@ -0,0 +1,172 @@
+
+
+sane-u12.5
+
+
+sane-u12.5
+
+
+
+sane-u12(5) SANE Scanner Access Now Easy sane-u12(5)
+
+
+
+NAME
+ sane-u12 - SANE backend for Plustek USB flatbed scanners, based on
+ older parport designs
+
+
+
+DESCRIPTION
+ The sane-u12 library implements a SANE (Scanner Access Now Easy) back-
+ end that provides access to USB flatbed scanners based on Plusteks'
+ ASIC 98003 (parallel-port ASIC) and a GeneSys Logics' USB-parport
+ bridge chip.
+
+
+
+SUPPORTED DEVICES
+ The backend is able to support some early Plustek USB scanner based
+ their old parport design around the ASIC 98003 and other rebadged Plus-
+ tek devices. The following tables will give you a short overview.
+
+ If your Plustek scanner has another Product ID, then the device is NOT
+ supported by this backend.
+
+ Vendor Plustek - ID: 0x07B3
+ ----------------------------------------------------------
+ Model: Vendor-ID: Product-ID:
+ ----------------------------------------------------------
+ OpticPro U12 0x07B3 0x0001
+ OpticPro U1212 0x07B3 0x0001
+ OpticPro UT12 0x07B3 0x0001
+
+ Vendor KYE/Genius
+ --------------------------------------------------------
+ USB Model: Vendor-ID: Product-ID:
+ --------------------------------------------------------
+ ColorPage Vivid III USB 0x07B3 0x0001
+ ColorPage HR6 V1 0x0458 0x2004
+
+
+
+CONFIGURATION
+ 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
+
+ [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 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
+
+ See the u12.conf file for examples.
+
+ Note:
+ You have to make sure, that the USB subsystem is loaded correctly and
+ you have access to the device-node. For more details see sane-usb (5)
+ manpage. You might use sane-find-scanner to check that you have access
+ to your device.
+
+ Note:
+ If there's no configuration file, the backend defaults to device auto
+
+
+
+FILES
+ /usr/local/etc/sane.d/u12.conf
+ The backend configuration file
+
+ /usr/local/lib/sane/libsane-u12.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-u12.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_U12
+ If the library was compiled with debug support enabled, this
+ environment variable controls the debug level for this backend.
+ Higher debug levels increase the verbosity of the output.
+
+ Example: export SANE_DEBUG_U12=10
+
+
+
+SEE ALSO
+ sane(7), sane-usb(5), sane-plustek(5),
+ /usr/local/doc/sane-1.0.14-cvs/u12/U12.changes
+ http://www.gjaeger.de/scanner/u12.html
+
+
+
+CONTACT AND BUG-REPORTS
+ Please send any information and bug-reports to:
+ SANE Mailing List
+
+ Additional info and hints can be obtained from our
+ Mailing-List archive at:
+ http://www.sane-project.org/mailing-lists.html
+
+ or directly from the projects' homepage at:
+ http://www.gjaeger.de/scanner/u12.html
+
+ To obtain debug messages from the backend, please set the environment-
+ variable SANE_DEBUG_U12 before calling your favorite scan-frontend
+ (i.e. xscanimage).
+ i.e.: export SANE_DEBUG_U12=20 ; xscanimage
+
+ The value controls the verbosity of the backend.
+
+
+
+KNOWN BUGS & RESTRICTIONS
+ * The driver is in alpha state, so please don't expect too
+ much!!!
+ * When using libusb, it might be, that the backend hangs.
+ In that case, reconnect the scanner.
+
+sane-backends 1.0.14-cvs 23 Apr 2004 sane-u12(5)
+
+
+
+Man(1) output converted with
+man2html
+
+
+
diff --git a/man/sane-umax.5.html b/man/sane-umax.5.html
index be6ce6d5..14e236dd 100644
--- a/man/sane-umax.5.html
+++ b/man/sane-umax.5.html
@@ -268,7 +268,7 @@
EMAIL-CONTACT
Oliver.Rauch@Rauch-Domain.DE
-sane-backends 1.0.13 29 november 2002 sane-umax(5)
+sane-backends 1.0.14-cvs 29 november 2002 sane-umax(5)
diff --git a/man/sane-umax1220u.5.html b/man/sane-umax1220u.5.html
index 1cb29109..4923ab4b 100644
--- a/man/sane-umax1220u.5.html
+++ b/man/sane-umax1220u.5.html
@@ -134,7 +134,7 @@
When reporting bugs, please run the backend with SANE_DEBUG_UMAX1220U
set to 10 and attach a copy of the log messages.
-sane-backends 1.0.13 6 Jan 2002 sane-umax1220u(5)
+sane-backends 1.0.14-cvs 6 Jan 2002 sane-umax1220u(5)
diff --git a/man/sane-umax_pp.5.html b/man/sane-umax_pp.5.html
index b2480835..2e4652b4 100644
--- a/man/sane-umax_pp.5.html
+++ b/man/sane-umax_pp.5.html
@@ -24,6 +24,7 @@
Model:
--------------------
+ Astra 610P
Astra 1220P
HP3200C
Astra 1600P
@@ -39,22 +40,26 @@
erly. Under windows, model is set by the driver installed, regardless
of the hardware.
- 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.
+ EPP/ECP MODES ONLY
+ The current version of the backend uses only EPP or ECP mode to
+ communicate with the scanner. PS/2 and SPP mode aren't imple-
+ mented. It is recommended that you set your parallel port to EPP
+ in BIOS with the current version of this backend. You can leave
+ it to ECP or ECP+EPP, but in this case you may not use ppdev but
+ only direct hardware access if you have to use ECP. ECPEPP will
+ only
+ work if you use a 2.4 or 2.6 kernel with ppdev character device
+ support.
- This backend does support parport sharing only if you have a kernel
+ 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
+ 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
+ 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.
@@ -88,7 +93,7 @@
NOTE: in all cases, you must have sufficient priviledges
to get access to the chosen device or address. Depending on the
security settings, devices may not be available for all users.
- You have to change permissions on the dev/ppi* or /dev/parport*
+ You have to change permissions on the dev/ppi* or /dev/parport*
devices.
You can rename any device using the
@@ -104,44 +109,43 @@
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
+ 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,
+ 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.
+ 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
+ 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
+ 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
+ tion. Valid values are 610, 1220, 1600 and 2000. It is usefull only
+ when autodetection fails to detect properly your scanner model. If your
scanner work properly but is reported wrongly, let it be that way. The
- only valid case to change the model is when your scanner produces
+ only valid case to change the model is when your scanner produces
'black' or prevent scanner model autodetection.
- Option 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 smoothness of the updates of
- progress status in the frontend, but will stall the scan more often.
-
+ 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 smoothness of progress bar 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
+ The backend configuration file (see also description of
SANE_CONFIG_DIR below).
/usr/local/lib/sane/libsane-umax_pp.a
@@ -157,21 +161,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_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.
+ If the library was compiled with debug support enabled, this
+ environment variable controls the debug level for this backend.
+ E.g., a value of 128 requests all debug output to be printed.
Smaller levels reduce verbosity.
level debug output
@@ -185,8 +189,8 @@
6 special debug information
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
+ This variable sets the debug level for the SANE interface for
+ the Umax ASIC. Note that enabling this will spam your terminal
with some million lines of debug output.
level debug output
@@ -199,7 +203,6 @@
255 everything
-
SEE ALSO
sane(7), sane-net(5), saned(1)
@@ -215,30 +218,30 @@
BUG REPORTS
- If something doesn't work, please contact me. But I need some informa-
+ If something doesn't work, please contact me. But I need some informa-
tion about your scanner to be able to help you...
SANE version
run "scanimage -V" to determine this
the backend version and your scanner hardware
- run "SANE_DEBUG_UMAX_PP=255 scanimage -L 2>log" as root. If you
- don't get any output from the umax_pp backend, make sure a line
- "umax_pp" is included into your /usr/local/etc/sane.d/dll.conf.
- If your scanner isn't detected, make sure you've defined the
- right port address, or the correct device in your umax_pp.conf.
+ run "SANE_DEBUG_UMAX_PP=255 scanimage -L 2>log" as root. If you
+ don't get any output from the umax_pp backend, make sure a line
+ "umax_pp" is included into your /usr/local/etc/sane.d/dll.conf.
+ If your scanner isn't detected, make sure you've defined the
+ right port address, or the correct device in your umax_pp.conf.
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
+ 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
+ better), or you think I should know something, please include
it.
-sane-backends 1.0.13 16 September 2003 sane-umax_pp(5)
+sane-backends 1.0.14-cvs 16 September 2003 sane-umax_pp(5)
diff --git a/man/sane-usb.5.html b/man/sane-usb.5.html
index b06b23e9..b718711f 100644
--- a/man/sane-usb.5.html
+++ b/man/sane-usb.5.html
@@ -64,7 +64,8 @@
nel, libsub), NetBSD (libusb), OpenBSD (kernel, libusb) and MacOS X
(libusb). Testing on MacOS X is very limited and not all scanners seem
to work reliably with the BSDs. For installation issues, also check the
- /usr/local/doc/sane-1.0.13/README.platform files.
+ /usr/local/doc/sane-1.0.14-cvs/README.platform files. The scanner mod-
+ ule is on longer available on Linux 2.6 and later. Use libusb instead.
Generally speaking, if your scanner works with one method, there is no
need to switch to the other one.
@@ -102,108 +103,113 @@
device files). The right device files can be found out by running scan-
image -L as root. Setting permissions with "chmod" is not permanent,
however. They will be resetted after reboot or replugging the scanner.
- It's also possible to mount the usbfs with the option "devmode=0666",
- e.g. by using the following line in /etc/fstab:
+ In Linux versions before 2.6 it was also possible to mount the usbfs
+ with the option "devmode=0666", e.g. by using the following line in
+ /etc/fstab:
none /proc/bus/usb usbfs defaults,devmode=0666 0 0
+ DUE TO A KERNEL BUG THIS WON'T WORK WITH CURRENT 2.6 KERNELS. USE HOT-
+ PLUG INSTEAD
+
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.
+ sions. SANE comes with hotplug scripts in the directory tools/hotplug.
+ They can be used for setting permissions. Last, the frontends can be
+ run as root. However, that's not recommended for security reasons.
- For the BSDs, the device files are named /dev/ugen*. Use chmod to
+ 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-
+ 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
+ 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
+ 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
+ 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.13/README.openbsd. Similar approaches should be
- used for the other BSDs.
+ For OpenBSD the kernel may need to be recompiled. For details look at
+ /usr/local/doc/sane-1.0.14-cvs/README.openbsd. Similar approaches
+ should be used for the other BSDs.
- Linux kernel messages in syslog like "kernel: scanner.c:
- open_scanner(1): Unable to access minor data" can be ignored. They are
- generated when SANE scans all available USB devices for scanners.
+ Linux kernel messages in syslog like "kernel: scanner.c: open_scan-
+ ner(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
+ 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
- looking into the syslog (e.g., /var/log/messages) or under Linux by
- issuing the command "cat /proc/bus/usb/devices/". This is an example
+ looking into the syslog (e.g., /var/log/messages) or under Linux by
+ issuing the command "cat /proc/bus/usb/devices/". This is an example
of a config file line:
usb 0x055f 0x0006
- would have the effect that all USB devices in the system with a vendor
- id of 0x55f and a product id of 0x0006 would be probed and recognized
+ would have the effect that all USB devices in the system with a vendor
+ id of 0x55f and a product id of 0x0006 would be probed and recognized
by the backend.
- If your scanner is not detected automatically, it may be necessary to
- edit the appropriate backend configuration file before using SANE for
- the first time. For most systems, the configuration file should list
+ If your scanner is not detected automatically, it may be necessary to
+ edit the appropriate backend configuration file before using SANE for
+ the first time. For most systems, the configuration file should list
the name of the USB device file that the scanner is connected to (e.g.,
- under Linux, /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:
+ 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
+ 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
+ If the library was compiled with debug support enabled, this
+ environment variable controls the debug level for the USB I/O
subsystem. E.g., a value of 128 requests all debug output to be
printed. Smaller levels reduce verbosity. Values greater than 4
- enable libusb debugging (if available). Example: export
+ enable libusb debugging (if available). Example: export
SANE_DEBUG_SANEI_USB=4.
@@ -216,7 +222,7 @@
AUTHOR
Henning Meier-Geinitz
-sane-backends 1.0.13 27 Nov 2002 sane-usb(5)
+sane-backends 1.0.14-cvs 8 Mar 2004 sane-usb(5)
diff --git a/man/sane-v4l.5.html b/man/sane-v4l.5.html
index 5d5a6299..43561408 100644
--- a/man/sane-v4l.5.html
+++ b/man/sane-v4l.5.html
@@ -105,7 +105,7 @@
SEE ALSO
sane(7), xcam(1).
-sane-backends 1.0.13 28 Aug 2002 sane-v4l(5)
+sane-backends 1.0.14-cvs 28 Aug 2002 sane-v4l(5)
diff --git a/man/sane.7.html b/man/sane.7.html
index 1ff932c0..44cb70f3 100644
--- a/man/sane.7.html
+++ b/man/sane.7.html
@@ -59,10 +59,10 @@
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.13/sane.tex' are references to text files that
- were copied to the SANE documentation directory
- (/usr/local/doc/sane-1.0.13/) during installation. Everything else is a
- URL to a resource on the web.
+ `/usr/local/doc/sane-1.0.14-cvs/sane.tex' are references to text files
+ that were copied to the SANE documentation directory
+ (/usr/local/doc/sane-1.0.14-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
@@ -76,30 +76,30 @@
CAN YOU HELP SANE for details. There are lists for specific releases
of SANE, for the current development version and a search engine:
http://www.sane-project.org/sane-supported-devices.html. The lists
- are also installed on your system at /usr/local/doc/sane-1.0.13/.
+ are also installed on your system at /usr/local/doc/sane-1.0.14-cvs/.
SANE mailing list
- There is a mailing list for the purpose of discussing the SANE stan-
+ There is a mailing list for the purpose of discussing the SANE stan-
dard and its implementations: sane-devel. Despite its name, the list
- is not only intended for developers, but also for users. Since this
+ is not only intended for developers, but also for users. Since this
is currently the only mailing list devoted to SANE, it's perfectly OK
- to ask questions that are not strictly related to SANE development.
- How to subscribe and unsubscribe: http://www.sane-project.org/mail-
+ to ask questions that are not strictly related to SANE development.
+ How to subscribe and unsubscribe: http://www.sane-project.org/mail-
ing-lists.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.
+ 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.13/README and the os-dependent README
- files for information about compiling and installing SANE.
+ Look at /usr/local/doc/sane-1.0.14-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
+ For information about various systems and SCSI controllers see
sane-scsi(5).
USB configuration
@@ -116,10 +116,10 @@
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
+ 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,
+ Also, have a look at the sane-frontends package (including xscanimage,
xcam, and scanadf) and the frontend information page at
http://www.sane-project.org/sane-frontends.html.
@@ -128,52 +128,52 @@
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,
+ (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
+ 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
+ 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.
+ 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
+ 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-
+ 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.
+ 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.
+ 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-
+ 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
+ The canon_pp backend supports the CanoScan FB330P, FB630P, N340P and
N640P parallel port scanners. See sane-canon_pp(5) for details.
coolscan
@@ -181,7 +181,7 @@
sane-coolscan(5) for details.
coolscan2
- This is a SANE backend for Nikon Coolscan film-scanners. See
+ This is a SANE backend for Nikon Coolscan film-scanners. See
sane-coolscan2(5) or http://coolscan2.sourceforge.net for details.
epson
@@ -193,148 +193,143 @@
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,
+ 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-
+ 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
+ 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
+ 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
+ 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.
ma1509
- The ma1509 backend supports the Mustek BearPaw 1200F USB flatbed
+ 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
+ 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
+ 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
+ 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.
+ 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.
mustek_pp
The mustek_pp backend provides access to Mustek parallel port flatbed
- scanners with a CIS sensor. See sane-mustek_pp(5) for details.
-
- mustek_pp_ccd
- The mustek_pp_ccd backend provides access to Mustek parallel port
- flatbed scanners with a CCD sensor. See sane-mustek_pp_ccd(5) for
- details.
+ scannersr. 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
+ 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)
+ 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 USB flatbed scanners that use the
+ The SANE plustek backend supports USB flatbed scanners that use the
National Semiconductor LM983[1/2/3]-chipset aka Merlin. Scanners
using this LM983x chips include some models from Plustek, KYE/Genius,
- Hewlett-Packard, Mustek, Umax, Epson, and Canon. See sane-plustek(5)
+ Hewlett-Packard, Mustek, Umax, Epson, and Canon. See sane-plustek(5)
for details.
plustek_pp
- The SANE plustek_pp backend supports Plustek parallel port flatbed
+ The SANE plustek_pp backend supports Plustek parallel port flatbed
scanners. Scanners using the Plustek ASIC P96001, P96003, P98001 and
- P98003 include some models from Plustek, KYE/Genius, Primax. See
+ P98003 include some models from Plustek, KYE/Genius, Primax. See
sane-plustek_pp(5) for details.
ricoh
- The ricoh backend provides access to the following Ricoh flatbed
+ The ricoh backend provides access to the following Ricoh flatbed
scanners: IS50 and IS60. See sane-ricoh(5) for details.
s9036
- The s9036 backend provides access to Siemens 9036 flatbed scanners.
+ 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
+ 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
+ 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
+ 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
+ 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-
+ 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.
+ 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-
+ 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,
+ 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
+ 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
+ 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
+ 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.13/PROJECTS.
+ projects in /usr/local/doc/sane-1.0.14-cvs/PROJECTS.
@@ -349,91 +344,92 @@
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
- sane-gphoto2(5).
+ (See http://www.gphoto.org for more information and a list of
+ supported cameras.) Gphoto2 supports over 140 different camera mod-
+ els. However, please note that more development and testing is
+ needed before all of these cameras will be supported by 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
+ 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.13/PROJECTS.
+ projects in /usr/local/doc/sane-1.0.14-cvs/PROJECTS.
MISCELLANEOUS BACKENDS
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
+ 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-
+ 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
+ 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
+ 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
+ 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.13/PROJECTS.
+ projects in /usr/local/doc/sane-1.0.14-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
+ 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 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.13/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).
+ 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.14-cvs/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.13/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.13/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.
+ /usr/local/doc/sane-1.0.14-cvs/backend-writing.txt. Most of the inter-
+ nal 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.14-cvs/PROJECTS for projects that are planned
+ or not yet included into the SANE distribution 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-
ner: http://www.meier-geinitz.de/sane/misc/develop.html.
@@ -455,7 +451,7 @@
The shared libraries implementing the backends (present on sys-
tems that support dynamic loading).
- /usr/local/doc/sane-1.0.13/*
+ /usr/local/doc/sane-1.0.14-cvs/*
SANE documentation: The standard, READMEs, text files for back-
ends etc.
@@ -545,7 +541,7 @@
For reporting bugs or requesting new features, please use our bug-
tracking system: 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.13/AUTHORS file or the
+ can be found in the /usr/local/doc/sane-1.0.14-cvs/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).
@@ -560,26 +556,26 @@
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_pp_ccd(5), sane-mustek_usb(5),
- sane-nec(5), sane-net(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-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)
+ sane-hp5400(5) sane-ibm(5), sane-leo(5), sane-ma1509(5),
+ sane-matsushita(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-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)
AUTHOR
David Mosberger-Tang and many many more (see
- /usr/local/doc/sane-1.0.13/AUTHORS for details). This man page was
+ /usr/local/doc/sane-1.0.14-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.13 3 Oct 2003 sane(7)
+sane-backends 1.0.14-cvs 06 Jan 2004 sane(7)
diff --git a/man/saned.1.html b/man/saned.1.html
index 19013924..4d1c72a4 100644
--- a/man/saned.1.html
+++ b/man/saned.1.html
@@ -175,7 +175,7 @@
AUTHOR
David Mosberger
-sane-backends 1.0.13 29 Oct 2003 saned(1)
+sane-backends 1.0.14-cvs 29 Oct 2003 saned(1)
diff --git a/man/scanimage.1.html b/man/scanimage.1.html
index 96393348..757d90ee 100644
--- a/man/scanimage.1.html
+++ b/man/scanimage.1.html
@@ -109,7 +109,9 @@
incremented by. Generally this is used when you are scanning double-
sided documents on a single-sided document feeder. A specific command
is provided to aid this: --batch-double will automatically set the
- increment to 2.
+ increment to 2. --batch-prompt will ask for pressing RETURN before
+ scanning a page. This can be used for scanning multiple pages without
+ an automatic document feeder.
The --accept-md5-only option only accepts user authorization requests
that support MD5 security. The SANE network daemon (saned) is capable
@@ -142,8 +144,8 @@
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:
+ To see the options for a device named dev, invoke scanimage via a
+ command-line of the form:
scanimage --help --device-name dev
@@ -272,7 +274,7 @@
For vector options, the help output currently has no indication as to
how many elements a vector-value should have.
-sane-backends 1.0.13 15 Apr 2003 scanimage(1)
+sane-backends 1.0.14-cvs 22 Feb 2004 scanimage(1)