with ppdev (linux only)
When you have the ppdev character device available, you may run the backend as normal user, if the '/dev/parport*' devices have the correct read/write permissions.
without ppdev (linux only)Then the current implementation of the backend will use 'ioperm()' to allow direct access to i/o ports, you will then need to run the following commands as root. Or you'll have to install all as root then set the suid bit (chmod a+s) of the frontend you use (note that most recent GTK+ doesn't like suid bit any longer...) .
with the ppi device (*BSD only)
When you have the ppi device available, you may run the backend as normal user, if the '/dev/ppi*' devices have the correct read/write permissions.
OS/2You'll have to add (or change) 'IOPL=YES' in config.sys, and reboot.
Detecting the scanner
For the first tests, it is recommended that you switch off any other device attached to the pass-trough port of the scanner.
Then if the scanner is on, we can try to detect it with the 'umax_pp' command line utility which is the 'tools' subdirectory. You can probe the scanner with the '-p' option, a trace level of 1 '-t 1' shows the results:
You should get the following output with ppdev, revision, EPP mode and model may vary:
You should get the following output with direct harware access, revision, EPP mode and model may vary:
In case you don't have the same kind of result, especially if there are
messages about registers holding unexpected values and no scanner is
detected, try to reset the scanner by plugging/unplugging cables as explained here:
First scanOnce the scanner has been correctly detected, you can do a color preview with the following:
this produces a 'out.pnm' file which holds the result of the scan.
Checking SANE install
Now that the scanner is working, we can now check the SANE install with:
scanimage -Lwhich should output:
device `pnm:0' is a Noname PNM file reader virtual device
Note that the current patch comment out any other backend in dll.conf to avoid possible conflicts with other scanners. You'll have to edit it to get back any other backend allready installed.
This behaviour will be changed when the backend will leave beta status...
If you successfully went through the previous steps, you can now launch xsane or xscanimage. They should show a list of devices where 'umax_pp:0xXYZ' should appear. Select it, then go ...
As a shortcut, you can launch it by 'xsane umax_pp:0xXYZ'.
If something goes wrong with the backend, try to reproduce it with the umax_pp test program in the tools subdirectory. Then do 'umax_pp -t 255 -p 2>probe.log' if you have a detection problem, or 'umax_pp -t 255 -s 2>scan.log' if you have scan problems. Then send me stefdev the log files and all the 'dump00*.*' files created in the current directory.
|download||install||use||bugs and issues||troubleshooting||links||lists||changelog|