Bonjour,
Sujet: MANDRIVA et SANE avec Scanner // plustek
Ayant remplacé MANDRAKE par MANDRIVA, je n'arrive plus a configurer mon scanner plustek opticpro 4830p sur port // avec mandriva Limited Edition 2005 j'ai respecté la procédure (ajout package SANE et SCANNER) auparavant cela avait fonctionné sans problème avec mandrake 10.1 community,
- j'ai réessayé avec mandrake 10.1 community puis avec mandriva Limited Edition 2005 version DVD et CD,
- sur ce port // est branché le scanner puis sur le scanner une imprimante HP Deskjet qui fonctionne bien.
- Avec win98 mon scanner marche bien (donc pas de pb cable ou matériel)
- ci dessous copie de mon fichier etc/sane.d/plustek_pp.conf si quelqu'un y comprend qqchose
puis fichier manuel sane
avez-vous des solutions ?
Merci
------------------------------------------------------
FICHIER etc/sane.d/plustek_pp.conf
------------------------------------------------------
# Plustek-PP SANE Backend configuration file
# For use with Plustek parallel-port scanners
#
#
# user either [direct] or [kernel] to access the scanner
# when using [kernel], device specifies the device-node, which is created
# by the kernel-module loader (applies only to Linux)
# when using [direct], device is used to set the parallel-port base address
# or a device-name suitable for libieee1284, i.e. parport0
#
[direct]
device 0x378
#
# leave the default values as specified in /etc/modules.conf
fichier plustek_pp.conf
#
option warmup -1
option lOffOnEnd -1
option lampOff -1
# model override switch, mostly for cosmetic changes, if the autodetection
# does not work or could not work correctly
#option mov 7
#
# example for accessing the scanner via libieee1284
#
device parport0
#
# example for accessing the scanner via the kernel module
#
#[kernel]
#device /dev/pt_drv
#
#option warmup -1
#option lOffOnEnd -1
#option lampOff -1
-------------------------------------------------------
MANUEL SANE
-------------------------------------------------------
sane-plustek_pp(5) SANE Scanner Access Now Easy sane-plustek_pp(5)
c
NAME
sane-plustek_pp - SANE backend for Plustek parallel port flatbed scan-
ners
DESCRIPTION
The sane-plustek_pp library implements a SANE (Scanner Access Now Easy)
backend that provides access to Plustek ASIC 9600[1/3] and P9800[1/3]
based parallel port flatbed scanners. The access of the scanner is
either done directly by the backend or via kernel module, called pt_drv
which can be created out of the plustek_pp backend code - see also sec-
tion BUILDING THE KERNEL MODULE for further information.
SUPPORTED DEVICES
At present, ***spam*** scanners should work with this backend and/or
the kernel module:
PLUSTEK SCANNERS
Parallelport Model: ASIC: Properties:
---------------------- ----- ------------------------
OpticPro 4830P/FBIII 96003 300x600 dpi 30bit 32Kb
DEVICE NAMES
This backend works in two modes, the so called "direct-mode" and the
"kernel-mode". In direct-mode, the user-space backend is used, in ker-
nel-mode, you should have a kernel-module named pt_drv loaded. This
backends default device is:
0x378
This "default device" will be used, if no configuration file can be
found. It is rather the base address of the parallel port on i386
machines.
As the backend supports up to four devices, it is possible to specify
them in the configuration file
/etc/sane.d/plustek_pp.conf
See this file for examples.
CONFIGURATION
This section decribes the backends' configuration file entries. The
file is located at:
/etc/sane.d/plustek_pp.conf
For a proper setup, you will need at least two entries:
[direct]
device 0x378
or
Model: Remarks:
--------------------------- ----------------------------
BrightScan OpticPro OpticPro P12
DEVICE NAMES
This backend works in two modes, the so called "direct-mode" and the
"kernel-mode". In direct-mode, the user-space backend is used, in ker-
nel-mode, you should have a kernel-module named pt_drv loaded. This
backends default device is:
0x378
This "default device" will be used, if no configuration file can be
found. It is rather the base address of the parallel port on i386
machines.
As the backend supports up to four devices, it is possible to specify
them in the configuration file
/etc/sane.d/plustek_pp.conf
See this file for examples.
CONFIGURATION
This section decribes the backends' configuration file entries. The
file is located at:
/etc/sane.d/plustek_pp.conf
For a proper setup, you will need at least two entries:
[direct]
device 0x378
or
Model: Remarks:
--------------------------- ----------------------------
BrightScan OpticPro OpticPro P12
DEVICE NAMES
This backend works in two modes, the so called "direct-mode" and the
"kernel-mode". In direct-mode, the user-space backend is used, in ker-
nel-mode, you should have a kernel-module named pt_drv loaded. This
backends default device is:
0x378
This "default device" will be used, if no configuration file can be
found. It is rather the base address of the parallel port on i386
machines.
As the backend supports up to four devices, it is possible to specify
them in the configuration file
/etc/sane.d/plustek_pp.conf
See this file for examples.
CONFIGURATION
This section decribes the backends' configuration file entries. The
file is located at:
/etc/sane.d/plustek_pp.conf
For a proper setup, you will need at least two entries:
[direct]
device 0x378
or
[kernel]
device /dev/pt_drv
direct tells the backend, that ***spam*** 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.
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 script called:
MakeModule.sh
Now if your Linux kernelsources are installed correctly, it should be
possible to build, install and load the module pt_drv. Please note,
that the kernelsources need to be configured correctly. Refer to your
distributions manual on how this is done. As root user, try
./MakeModule.sh
the script will try and get all necessary information about your run-
ning kernel and will lead you through the whole installation process.
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/modules.conf (kernel < 2.6.x) or /etc/mod-
probe.conf (kernel >= 2.6.x)
The Options:
lampoff=lll
The value lll tells the driver, after how many seconds to
switch-off the lamp(s). The default value is 180. 0 will dis-
able this feature.
HINT: Do not use a value that is too small, because often
switching on/off the lamps will reduce their lifetime.
port=ppp
ppp specifies the port base address, where the scanner is con-
nected to. The default value is 0x378 which normaly is standard.
warmup=www
www specifies the time in seconds, how long a lamp has to be on,
until the driver will start to scan. The default value is 30.
lOffonEnd=e
e specifies the behaviour when unloading the driver, 1 -->
switch lamps off, 0 --> do not change lamp status
slowIO=s
s specifies which I/O functions the driver should use, 1 --> use
delayed functions, 0 --> use the non-delayed ones
forceMode=fm
fm specifies port mode which should be used, 0 --> autodetec-
tion, 1 --> use SPP mode and 2 --> use EPP mode
mov=m
m =0 - default: no override
m =1 - OpticPro 9630PL override (works if OP9630
has been detected) forces legal size (14")
m =2 - Primax 4800Direct override (works if OP600
has been detected) swaps red/green color
m =3 - OpticPro 9636 override (works if OP9636 has
been detected) disables backends
transparency/negativ capabilities
m =4 - OpticPro 9636P override (works if OP9636 has
been detected) disables backends
transparency/negativ capabilities
m =5 - OpticPro A3I override (works if OP12000 has
been detected) enables A3 scanning
m =6 - OpticPro 4800P override (works if OP600
has been detected) swaps red/green color
m =7 - Primax 4800Direct 30bit override (works if
OP4830 has been detected)
Sample entry for file /etc/modules.conf :
alias char-major-40 pt_drv
pre-install pt_drv modprobe -k parport
options pt_drv lampoff=180 warmup=15 port=0x378 lOffonEnd=0 mov=0
slowIO=0 forceMode=0
For multidevice support, simply add values separated by commas to the
different options
options pt_drv port=0x378,0x278 mov=0,4 slowIO=0,1 forceMode=0,1
Remember to call depmod after changing /etc/conf.modules.
PARALLEL PORT MODES
The current driver works best, when the parallel port
has been set to EPP-mode. When detecting any other mode such as
ECP or PS/2 the driver tries to set to a faster, supported mode.
If this fails, it will use the SPP mode, as this mode should
work with all Linux supported parallel ports. If in doubt, enter
your BIOS and set it to any mode except ECP.
Former Plustek scanner models (4830, 9630) supplied a ISA parallel port
adapter card. This card is not supported by the driver.
The ASIC 96001/3 based models have sometimes trouble with high resolu-
tion modes. If you encounter sporadic corrupted images (parts dupli-
cated or shifted horizontally) kill all other applications before scan-
ning and (if sufficient memory available) disable swapping.
See the plustek_pp.conf file for examples.
FILES
/etc/sane.d/plustek_pp.conf
The backend configuration file
/usr/lib/sane/libsane-plustek_pp.a
lines 244-285
The static library implementing this backend.
/usr/lib/sane/libsane-plustek_pp.so
The shared library implementing this backend (present on systems
that support dynamic loading).
/lib/modules/<Kernel-Version>/kernel/drivers/parport/pt_drv.o
The Linux kernelmodule for kernels < 2.6.x.
/lib/modules/<Kernel-Version>/kernel/drivers/parport/pt_drv.ko
The Linux kernelmodule for kernels >= 2.6.x.
ENVIRONMENT
SANE_CONFIG_DIR
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in /etc/sane.d. If the
value of the environment variable ends with the directory sepa-
rator character, then the default directories are searched after
the explicitly specified directories. For example, setting
SANE_CONFIG_DIR to "/tmp/config:" would result in directories
"tmp/config", ".", and "/etc/sane.d" being searched (in this
order).
SANE_DEBUG_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/doc/sane-1.0.15/plustek/Plustek-PARPORT.changes
http://www.gjaeger.de/scanner/plustek_pp/
lines 286-326
ONTACT 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/plustek_pp/
To obtain debug messages from the backend, please set the environment-
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.
KNOWN BUGS & RESTRICTIONS
* The Halftoning works, but the quality is poor
* Printers (especially HP models) will start to
print during scanning. This in fact is a problem
to other printers too, using bidirectional protocol
(see www.plustek.com (TAIWAN) page for further details)
* The driver does not support these manic scalings up
to 16 times the physical resolution. The only scaling
is done on resolutions between the physical resolution
of the CDD-sensor and the stepper motor i.e. you have a
600x1200 dpi scanner and you are scanning using 800dpi,
so scaling is necesary, because the sensor only delivers
600dpi but the motor is capable to perform 800dpi steps.
* On some devices, the pictures seems to be bluished
ASIC 98001 based models:
* The 300dpi transparency and negative mode does not work
correctly.
* There is currently no way to distinguish a model with
To obtain debug messages from the backend, please set the environment-
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.
KNOWN BUGS & RESTRICTIONS
* The Halftoning works, but the quality is poor
* Printers (especially HP models) will start to
print during scanning. This in fact is a problem
to other printers too, using bidirectional protocol
(see www.plustek.com (TAIWAN) page for further details)
* The driver does not support these manic scalings up
to 16 times the physical resolution. The only scaling
is done on resolutions between the physical resolution
of the CDD-sensor and the stepper motor i.e. you have a
600x1200 dpi scanner and you are scanning using 800dpi,
so scaling is necesary, because the sensor only delivers
600dpi but the motor is capable to perform 800dpi steps.
* On some devices, the pictures seems to be bluished
ASIC 98001 based models:
* The 300dpi transparency and negative mode does not work
correctly.
* There is currently no way to distinguish a model with
and without transpareny unit.
* The scanned images seem to be too dark (P9636T)
ASIC 96003/1 based models:
* 30bit mode is currently not supported.
* On low-end systems and under heavy system load, the
driver will loose data, this might causes the sensor
to hit the scan-bed and/or the picture is corrupted.
* The scanspeed on 600x1200 dpi models is slow.
* The scanquality of the A3I is poor
sane-backends 1.0.15
Sujet: MANDRIVA et SANE avec Scanner // plustek
Ayant remplacé MANDRAKE par MANDRIVA, je n'arrive plus a configurer mon scanner plustek opticpro 4830p sur port // avec mandriva Limited Edition 2005 j'ai respecté la procédure (ajout package SANE et SCANNER) auparavant cela avait fonctionné sans problème avec mandrake 10.1 community,
- j'ai réessayé avec mandrake 10.1 community puis avec mandriva Limited Edition 2005 version DVD et CD,
- sur ce port // est branché le scanner puis sur le scanner une imprimante HP Deskjet qui fonctionne bien.
- Avec win98 mon scanner marche bien (donc pas de pb cable ou matériel)
- ci dessous copie de mon fichier etc/sane.d/plustek_pp.conf si quelqu'un y comprend qqchose
puis fichier manuel sane
avez-vous des solutions ?
Merci
------------------------------------------------------
FICHIER etc/sane.d/plustek_pp.conf
------------------------------------------------------
# Plustek-PP SANE Backend configuration file
# For use with Plustek parallel-port scanners
#
#
# user either [direct] or [kernel] to access the scanner
# when using [kernel], device specifies the device-node, which is created
# by the kernel-module loader (applies only to Linux)
# when using [direct], device is used to set the parallel-port base address
# or a device-name suitable for libieee1284, i.e. parport0
#
[direct]
device 0x378
#
# leave the default values as specified in /etc/modules.conf
fichier plustek_pp.conf
#
option warmup -1
option lOffOnEnd -1
option lampOff -1
# model override switch, mostly for cosmetic changes, if the autodetection
# does not work or could not work correctly
#option mov 7
#
# example for accessing the scanner via libieee1284
#
device parport0
#
# example for accessing the scanner via the kernel module
#
#[kernel]
#device /dev/pt_drv
#
#option warmup -1
#option lOffOnEnd -1
#option lampOff -1
-------------------------------------------------------
MANUEL SANE
-------------------------------------------------------
sane-plustek_pp(5) SANE Scanner Access Now Easy sane-plustek_pp(5)
c
NAME
sane-plustek_pp - SANE backend for Plustek parallel port flatbed scan-
ners
DESCRIPTION
The sane-plustek_pp library implements a SANE (Scanner Access Now Easy)
backend that provides access to Plustek ASIC 9600[1/3] and P9800[1/3]
based parallel port flatbed scanners. The access of the scanner is
either done directly by the backend or via kernel module, called pt_drv
which can be created out of the plustek_pp backend code - see also sec-
tion BUILDING THE KERNEL MODULE for further information.
SUPPORTED DEVICES
At present, ***spam*** scanners should work with this backend and/or
the kernel module:
PLUSTEK SCANNERS
Parallelport Model: ASIC: Properties:
---------------------- ----- ------------------------
OpticPro 4830P/FBIII 96003 300x600 dpi 30bit 32Kb
DEVICE NAMES
This backend works in two modes, the so called "direct-mode" and the
"kernel-mode". In direct-mode, the user-space backend is used, in ker-
nel-mode, you should have a kernel-module named pt_drv loaded. This
backends default device is:
0x378
This "default device" will be used, if no configuration file can be
found. It is rather the base address of the parallel port on i386
machines.
As the backend supports up to four devices, it is possible to specify
them in the configuration file
/etc/sane.d/plustek_pp.conf
See this file for examples.
CONFIGURATION
This section decribes the backends' configuration file entries. The
file is located at:
/etc/sane.d/plustek_pp.conf
For a proper setup, you will need at least two entries:
[direct]
device 0x378
or
Model: Remarks:
--------------------------- ----------------------------
BrightScan OpticPro OpticPro P12
DEVICE NAMES
This backend works in two modes, the so called "direct-mode" and the
"kernel-mode". In direct-mode, the user-space backend is used, in ker-
nel-mode, you should have a kernel-module named pt_drv loaded. This
backends default device is:
0x378
This "default device" will be used, if no configuration file can be
found. It is rather the base address of the parallel port on i386
machines.
As the backend supports up to four devices, it is possible to specify
them in the configuration file
/etc/sane.d/plustek_pp.conf
See this file for examples.
CONFIGURATION
This section decribes the backends' configuration file entries. The
file is located at:
/etc/sane.d/plustek_pp.conf
For a proper setup, you will need at least two entries:
[direct]
device 0x378
or
Model: Remarks:
--------------------------- ----------------------------
BrightScan OpticPro OpticPro P12
DEVICE NAMES
This backend works in two modes, the so called "direct-mode" and the
"kernel-mode". In direct-mode, the user-space backend is used, in ker-
nel-mode, you should have a kernel-module named pt_drv loaded. This
backends default device is:
0x378
This "default device" will be used, if no configuration file can be
found. It is rather the base address of the parallel port on i386
machines.
As the backend supports up to four devices, it is possible to specify
them in the configuration file
/etc/sane.d/plustek_pp.conf
See this file for examples.
CONFIGURATION
This section decribes the backends' configuration file entries. The
file is located at:
/etc/sane.d/plustek_pp.conf
For a proper setup, you will need at least two entries:
[direct]
device 0x378
or
[kernel]
device /dev/pt_drv
direct tells the backend, that ***spam*** 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.
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 script called:
MakeModule.sh
Now if your Linux kernelsources are installed correctly, it should be
possible to build, install and load the module pt_drv. Please note,
that the kernelsources need to be configured correctly. Refer to your
distributions manual on how this is done. As root user, try
./MakeModule.sh
the script will try and get all necessary information about your run-
ning kernel and will lead you through the whole installation process.
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/modules.conf (kernel < 2.6.x) or /etc/mod-
probe.conf (kernel >= 2.6.x)
The Options:
lampoff=lll
The value lll tells the driver, after how many seconds to
switch-off the lamp(s). The default value is 180. 0 will dis-
able this feature.
HINT: Do not use a value that is too small, because often
switching on/off the lamps will reduce their lifetime.
port=ppp
ppp specifies the port base address, where the scanner is con-
nected to. The default value is 0x378 which normaly is standard.
warmup=www
www specifies the time in seconds, how long a lamp has to be on,
until the driver will start to scan. The default value is 30.
lOffonEnd=e
e specifies the behaviour when unloading the driver, 1 -->
switch lamps off, 0 --> do not change lamp status
slowIO=s
s specifies which I/O functions the driver should use, 1 --> use
delayed functions, 0 --> use the non-delayed ones
forceMode=fm
fm specifies port mode which should be used, 0 --> autodetec-
tion, 1 --> use SPP mode and 2 --> use EPP mode
mov=m
m =0 - default: no override
m =1 - OpticPro 9630PL override (works if OP9630
has been detected) forces legal size (14")
m =2 - Primax 4800Direct override (works if OP600
has been detected) swaps red/green color
m =3 - OpticPro 9636 override (works if OP9636 has
been detected) disables backends
transparency/negativ capabilities
m =4 - OpticPro 9636P override (works if OP9636 has
been detected) disables backends
transparency/negativ capabilities
m =5 - OpticPro A3I override (works if OP12000 has
been detected) enables A3 scanning
m =6 - OpticPro 4800P override (works if OP600
has been detected) swaps red/green color
m =7 - Primax 4800Direct 30bit override (works if
OP4830 has been detected)
Sample entry for file /etc/modules.conf :
alias char-major-40 pt_drv
pre-install pt_drv modprobe -k parport
options pt_drv lampoff=180 warmup=15 port=0x378 lOffonEnd=0 mov=0
slowIO=0 forceMode=0
For multidevice support, simply add values separated by commas to the
different options
options pt_drv port=0x378,0x278 mov=0,4 slowIO=0,1 forceMode=0,1
Remember to call depmod after changing /etc/conf.modules.
PARALLEL PORT MODES
The current driver works best, when the parallel port
has been set to EPP-mode. When detecting any other mode such as
ECP or PS/2 the driver tries to set to a faster, supported mode.
If this fails, it will use the SPP mode, as this mode should
work with all Linux supported parallel ports. If in doubt, enter
your BIOS and set it to any mode except ECP.
Former Plustek scanner models (4830, 9630) supplied a ISA parallel port
adapter card. This card is not supported by the driver.
The ASIC 96001/3 based models have sometimes trouble with high resolu-
tion modes. If you encounter sporadic corrupted images (parts dupli-
cated or shifted horizontally) kill all other applications before scan-
ning and (if sufficient memory available) disable swapping.
See the plustek_pp.conf file for examples.
FILES
/etc/sane.d/plustek_pp.conf
The backend configuration file
/usr/lib/sane/libsane-plustek_pp.a
lines 244-285
The static library implementing this backend.
/usr/lib/sane/libsane-plustek_pp.so
The shared library implementing this backend (present on systems
that support dynamic loading).
/lib/modules/<Kernel-Version>/kernel/drivers/parport/pt_drv.o
The Linux kernelmodule for kernels < 2.6.x.
/lib/modules/<Kernel-Version>/kernel/drivers/parport/pt_drv.ko
The Linux kernelmodule for kernels >= 2.6.x.
ENVIRONMENT
SANE_CONFIG_DIR
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in /etc/sane.d. If the
value of the environment variable ends with the directory sepa-
rator character, then the default directories are searched after
the explicitly specified directories. For example, setting
SANE_CONFIG_DIR to "/tmp/config:" would result in directories
"tmp/config", ".", and "/etc/sane.d" being searched (in this
order).
SANE_DEBUG_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/doc/sane-1.0.15/plustek/Plustek-PARPORT.changes
http://www.gjaeger.de/scanner/plustek_pp/
lines 286-326
ONTACT 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/plustek_pp/
To obtain debug messages from the backend, please set the environment-
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.
KNOWN BUGS & RESTRICTIONS
* The Halftoning works, but the quality is poor
* Printers (especially HP models) will start to
print during scanning. This in fact is a problem
to other printers too, using bidirectional protocol
(see www.plustek.com (TAIWAN) page for further details)
* The driver does not support these manic scalings up
to 16 times the physical resolution. The only scaling
is done on resolutions between the physical resolution
of the CDD-sensor and the stepper motor i.e. you have a
600x1200 dpi scanner and you are scanning using 800dpi,
so scaling is necesary, because the sensor only delivers
600dpi but the motor is capable to perform 800dpi steps.
* On some devices, the pictures seems to be bluished
ASIC 98001 based models:
* The 300dpi transparency and negative mode does not work
correctly.
* There is currently no way to distinguish a model with
To obtain debug messages from the backend, please set the environment-
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.
KNOWN BUGS & RESTRICTIONS
* The Halftoning works, but the quality is poor
* Printers (especially HP models) will start to
print during scanning. This in fact is a problem
to other printers too, using bidirectional protocol
(see www.plustek.com (TAIWAN) page for further details)
* The driver does not support these manic scalings up
to 16 times the physical resolution. The only scaling
is done on resolutions between the physical resolution
of the CDD-sensor and the stepper motor i.e. you have a
600x1200 dpi scanner and you are scanning using 800dpi,
so scaling is necesary, because the sensor only delivers
600dpi but the motor is capable to perform 800dpi steps.
* On some devices, the pictures seems to be bluished
ASIC 98001 based models:
* The 300dpi transparency and negative mode does not work
correctly.
* There is currently no way to distinguish a model with
and without transpareny unit.
* The scanned images seem to be too dark (P9636T)
ASIC 96003/1 based models:
* 30bit mode is currently not supported.
* On low-end systems and under heavy system load, the
driver will loose data, this might causes the sensor
to hit the scan-bed and/or the picture is corrupted.
* The scanspeed on 600x1200 dpi models is slow.
* The scanquality of the A3I is poor
sane-backends 1.0.15
-
sub13
- Messages : 360
- Géo : Bouches du Rhône
