sane-project-website/old-archive/1997-07/0126.html

113 wiersze
5.3 KiB
HTML

<!-- received="Wed Jul 23 15:31:05 1997 MST" -->
<!-- sent="Wed, 23 Jul 1997 14:57:44 -0700" -->
<!-- name="David Mosberger-Tang" -->
<!-- email="davidm@azstarnet.com" -->
<!-- subject="Re: More on Mustek 8000SP adventures..." -->
<!-- id="199707232157.OAA18160@panda.mosberger" -->
<!-- inreplyto="Pine.LNX.3.93.970723141923.31011A-100000@ispol.com" -->
<title>sane-devel: Re: More on Mustek 8000SP adventures...</title>
<h1>Re: More on Mustek 8000SP adventures...</h1>
<b>David Mosberger-Tang</b> (<a href="mailto:davidm@azstarnet.com"><i>davidm@azstarnet.com</i></a>)<br>
<i>Wed, 23 Jul 1997 14:57:44 -0700</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#126">[ date ]</a><a href="index.html#126">[ thread ]</a><a href="subject.html#126">[ subject ]</a><a href="author.html#126">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0127.html">Jonathan A. Buzzard: "Re: UMAX Astra 600p"</a>
<li> <b>Previous message:</b> <a href="0125.html">Michael K. Johnson: "Re: UMAX Astra 600p"</a>
<!-- nextthread="start" -->
<li> <b>Next in thread:</b> <a href="0131.html">Rogier Wolff: "Re: More on Mustek 8000SP adventures..."</a>
<li> <b>Reply:</b> <a href="0131.html">Rogier Wolff: "Re: More on Mustek 8000SP adventures..."</a>
<!-- reply="end" -->
</ul>
<!-- body="start" -->
<i>&gt;&gt;&gt;&gt;&gt; On Wed, 23 Jul 1997 14:35:16 -0400 (EDT), Gregory Trubetskoy &lt;grisha@ispol</i><br>
.com&gt; said:<br>
<p>
Gregory&gt; I am not stupid, I do read man pages, I know what RTFM is,<br>
Gregory&gt; all this - and yet, I did exactly the same thing that the<br>
Gregory&gt; man page describes below, only I figured it out myself. Had<br>
Gregory&gt; this been in the README file, it'd save me about 3 hours. (<br>
Gregory&gt; The README doesn't say "go read scsi-sane(5) man page. )<br>
<p>
I updated the info in the README a bit. I appended the updated<br>
section below.<br>
<p>
Gregory&gt; There need to be better installation, and more importantly<br>
Gregory&gt; *testing* instructions. ( E.g. run this command, then try<br>
Gregory&gt; to open the resulting file with xv or something )<br>
<p>
Sounds like a good idea. I probably won't have time for this anytime<br>
soon, but if somebody wants to put together some instructions, I'd be<br>
glad to incorporate them. Both a SANE tutorial and a SANE backend<br>
programming tutorial would probably be useful as well. I have written<br>
a SANE article for Linux Journal, but it just barely scratches the<br>
surface and says hardly anything about SANE programming.<br>
<p>
--david<br>
<pre>
--
* Installation and Configuration
<p>
Once 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.
<p>
For information on configuring and trouble-shooting the various SANE
components, please refer to the manual pages listed below:
<p>
Regarding: Read:
----------------- ------------------------------------------
scanimage scanimage(1)
xscanimage xscanimage(1)
saned saned(1)
xcam no man-page---see frontend/xcam.README
<p>
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)
<p>
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/.
<p>
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:
<p>
scanimage -d mustek:/dev/scanner -h
<p>
If this works, you could try to acquire an image with:
<p>
scanimage -d mustek:/dev/scanner &gt;t.pnm
<p>
<pre>
--
Source code, list archive, and docs: <a href="http://www.azstarnet.com/~axplinux/sane/">http://www.azstarnet.com/~axplinux/sane/</a>
To unsubscribe: mail -s unsubscribe <a href="mailto:sane-devel-request@listserv.azstarnet.com">sane-devel-request@listserv.azstarnet.com</a>
</pre>
<!-- body="end" -->
<p>
<ul>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0127.html">Jonathan A. Buzzard: "Re: UMAX Astra 600p"</a>
<li> <b>Previous message:</b> <a href="0125.html">Michael K. Johnson: "Re: UMAX Astra 600p"</a>
<!-- nextthread="start" -->
<li> <b>Next in thread:</b> <a href="0131.html">Rogier Wolff: "Re: More on Mustek 8000SP adventures..."</a>
<li> <b>Reply:</b> <a href="0131.html">Rogier Wolff: "Re: More on Mustek 8000SP adventures..."</a>
<!-- reply="end" -->
</ul>