Gregory> I am not stupid, I do read man pages, I know what RTFM is,
Gregory> all this - and yet, I did exactly the same thing that the
Gregory> man page describes below, only I figured it out myself. Had
Gregory> this been in the README file, it'd save me about 3 hours. (
Gregory> The README doesn't say "go read scsi-sane(5) man page. )
I updated the info in the README a bit. I appended the updated
section below.
Gregory> There need to be better installation, and more importantly
Gregory> *testing* instructions. ( E.g. run this command, then try
Gregory> to open the resulting file with xv or something )
Sounds like a good idea. I probably won't have time for this anytime
soon, but if somebody wants to put together some instructions, I'd be
glad to incorporate them. Both a SANE tutorial and a SANE backend
programming tutorial would probably be useful as well. I have written
a SANE article for Linux Journal, but it just barely scratches the
surface and says hardly anything about SANE programming.
--david
-- * Installation and ConfigurationOnce the build has finished, install SANE with "make install". By default, this will place the SANE libraries in /usr/local/lib/, the configuration files in /usr/local/etc/sane.d/, and the manual pages in /usr/local/man/. The location of these directories can be overridden with configure options; see "configure --help" for details.
For information on configuring and trouble-shooting the various SANE components, please refer to the manual pages listed below:
Regarding: Read: ----------------- ------------------------------------------ scanimage scanimage(1) xscanimage xscanimage(1) saned saned(1) xcam no man-page---see frontend/xcam.README
Dynamic loading sane-dll(5) Mustek scanners sane-mustek(5) and sane-scsi(5) UMAX scanners sane-umax(5) and sane-scsi(5) HP scanners sane-hp(5) and sane-scsi(5) Networking sane-net(5) and saned(1) PINT scanners sane-pint(5) QuickCam sane-qcam(5)
Please note that the default configuration uses sane-dll as the top-level backend. Hence it is probably a good idea to start with reading sane-dll(5). The top-level backend is determined by the libsane.* symlinks in /usr/local/lib/.
If you encounter any problems with getting your device(s) recognized, try setting the various environment variables that are there to assist in debugging such problems. The environment variables are documented in the relevant manual pages. For example, to get the maximum amount of debug information when testing a Mustek scanner, set environment variables SANE_DEBUG_DLL, SANE_DEBUG_MUSTEK, and SANE_DEBUG_SANEI_SCSI to 128 and then invoke scanimage or whatever program you're trying to debug. For a Mustek scanner at /dev/scanner, you might want to invoke scanimage as follows:
scanimage -d mustek:/dev/scanner -h
If this works, you could try to acquire an image with:
scanimage -d mustek:/dev/scanner >t.pnm
-- Source code, list archive, and docs: http://www.azstarnet.com/~axplinux/sane/ To unsubscribe: mail -s unsubscribe sane-devel-request@listserv.azstarnet.com