--=.Ck,JUCF/u'4.N7
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Hi,
some remarks on the Parallel Port sections:
Interface Types -> Parallel Port Devices:
Jonathan's page is really very outdated for some time now. It's
better (also for the other scanner types) to check the supported
scanners list on sane.informatik.uni-freiburg.de/cgi-bin/driver.pl
Kernel Support -> Parallel Port Scanners:
Not all scanner drivers need kernel level support. Some are using
directio (this needs to be enabled in configure) You're also mixing
dmesg and lsmod a little (lsmod is in bold, but a dmesg output is
shown). You could also note that you might have to enabled certain
transfer modes in the BIOS
Making and Accessing the Scanner Devices -> Manually creating ...
crw------- 1 root root 99, 0 Jun 24 13:47 parport0
crw------- 1 root root 99, 1 Jun 24 13:47 parport1
crw------- 1 root root 99, 2 Jun 24 13:47 parport2
crw------- 1 root root 99, 3 Jun 24 13:47 parport3
crw-r----- 1 root root 1, 4 Jan 1 1970 port
if a scanner doesn't use the kernel drivers, it normally needs the
port number as device name.
Making and... -> Groups and Permissions:
If a scanner doesn't use the kernel drivers, you have to use the
sane daemon (saned) to let non-root users access the scanner
Configuring SANE:
Parallel port backends often need libieee1284 installed or directio
enabled.
You could also stress the point a little more that an old SANE
installation is the reason #1 why self compiled SANE version don't
work (as you'd expect)
The network setup is missing the (x)inetd setup and doesn't mention
the possibility of using passwords
Testing your scanner:
There's an option --test for scanimage
that's it :)
regards
-- jochen
--=.Ck,JUCF/u'4.N7
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE++VrK8OF76YrreuMRArQTAKCReMsOr0kGL5l1uJpYK4DAbf9PvwCePze4
ZaxTEK0r7jeQMKdlfptoHP4=
=ca9K
-----END PGP SIGNATURE-----
--=.Ck,JUCF/u'4.N7--
