Hi,
On Wed, Jan 23, 2002 at 10:49:16PM +0100, Rainer Hofmann wrote:
> After installing "gimp-devel-1.2.1-31" ./configure produces following output:
> ...
> checking for libgimp/gimp.h... (cached) no
> checking for libgimp/gimpfeatures.h... (cached) no
Beware of the "(cached)" :-)
Do "rm config.c
Hi,
> After installing "gimp-devel-1.2.1-31" ./configure produces following
> output: ...
> checking for libgimp/gimp.h... (cached) no
> checking for libgimp/gimpfeatures.h... (cached) no
> gimp.h and gimpfeatures.h can be found at /usr/include/libgimp/. I even
> placed this path into /etc/ld.so.
Jody Hay wrote:
>
> I have been having an infrequent problem scanning
> with my Artec AM12S. Usually within the first ten
> scans after a reboot, something seems to lock up
> the computer.
>
> Here are some details:
> Debian "testing" distribution
Hi Oliver,
> After installation of the header files you have to run "configure", "make"
> and "make install" again for the sane frontends. Watch the output of
> "configure" for messages about gimp support.
After installing "gimp-devel-1.2.1-31" ./configure produces following output:
...
checking
--2mNuWrpDTYoom6W8
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Jan 23, 2002 at 09:43:35PM +0100, Henning Meier-Geinitz wrote:
> This is with gcc-3.x? I don't get them with gcc 2.95.4.
Yes.
> > They
> > are for things
Hi,
On Wed, Jan 23, 2002 at 09:55:55AM +, Tim Waugh wrote:
> I get these warnings when compiling sane-backends-1.0.7-beta1.
This is with gcc-3.x? I don't get them with gcc 2.95.4.
> They
> are for things like:
>
> bit = ++bit % 8;
>
> which are indeed undefined.
Because it's not cl
Hi,
> Upgrading to last version of sane,
> my Snapscan e20 USB scanner is no longer detected by
> scanimage.
please send me a debug log ("export SANE_DEBUG_SAPSCAN=255", then
"scanimage -L 2>debug.log").
Regards,
Oliver
Hi,
On Wed, Jan 23, 2002 at 02:19:10AM -0800, Andrei B. wrote:
> I looked at them and I'll try them this evening.
> A glance at the kernel source (g_NCR5380.c) tells a lot :
> USLEEP_POLL = 1
> USLEEP_SLEEP = 20
> USLEEP_WAITLONG = 500
>
> I'll try to play with them a bit.
Be carefull. I
Hello Andre,
I am working on a suggestion for several well known options.
It is not published yet but I suggest you start with the
option names I list here, although they might change if
necessary.
Andre Herms wrote:
> 1. Scan modes
> What are the default names for RGB, greyscale, and this 1 bit
Carlos,
> any plans to incorporate the SUPER COOLSCAN 4000 ED film scanner into the
> line-up of SANE supported scanners in the near future? This would capture
> a lot of high-end photographers.
Support is basically there. Please look under
http://coolscan2.sourceforge.net/
where you can fin
Carlos,
> any plans to incorporate the SUPER COOLSCAN 4000 ED film scanner into the
> line-up of SANE supported scanners in the near future? This would capture
> a lot of high-end photographers.
Support is basically there. Please look under
http://coolscan2.sourceforge.net/
where you can fin
Oliver Rauch writes:
> xsane-0.84 is available on
>
> http.//www.xsane.org
[...]
here is a packager request :)
we are now switching to png icons in menu and elsewhere. thus it is possible
to include them in xsane/src with the traditionnal xpm ones.
An 16x16 icon will be very appreciated too.
t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
As I had to recognise the sane standard is not up to date with the actually
used standard. There are some well-known options that are not well known but
only by some developers. So I have no choice but asking for them.
1. Scan modes
What are
--YhFoJY/gx7awiIuK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
I get these warnings when compiling sane-backends-1.0.7-beta1. They
are for things like:
bit = ++bit % 8;
which are indeed undefined.
Tim.
*/
microtek2.c:8054: warning: operation on `bit' may be
I have been having an infrequent problem scanning
with my Artec AM12S. Usually within the first ten
scans after a reboot, something seems to lock up
the computer.
Here are some details:
Debian "testing" distribution
custom 2.4.16 ke
Hi,
Upgrading to last version of sane,
my Snapscan e20 USB scanner is no longer detected by
scanimage.
sane-find-scanner found it:
sane-find-scanner: found USB scanner (vendor = 0x06bd,
product = 0x2091) at device /dev/usb/scanner0
It's listed in USB devices :
T: Bus=02 Lev=01 Prnt=01 Port=01 C
any plans to incorporate the SUPER COOLSCAN 4000 ED film scanner into the
line-up of SANE supported scanners in the near future? This would capture
a lot of high-end photographers.
NOTE: this scanner only supports IEEE1394 ("Fire-wire") and I don't know
if current Linux supports firewire.
Thank
--- Henning Meier-Geinitz wrote:
> There are some tricks that may or may not help a little bit. Some of
> them are
> summarized at http://www.meier-geinitz.de/sane/docu.html#SCSI . They
> are
> related to Mustek scanners but they use the same SCSI adapters.
I looked at them and I'll try them thi
xsane-0.84 is available on
http.//www.xsane.org
- if xsane-license.txt is not file when it shall be displayed then xsane does
print an error message and behaves like when the user did not accept the
license.
- if xsane-startimage.pnm is not found then an image of the size 1x1 pixel is
Hi,
> I've tried to register xscanimage as a plugin for gimp-1.2. But when
> starting gimp I get the message: ~/gimp-1.2/plugins/xscanimage: Gimp
> support missing. The plugin doesn't turn up in XTNS-Menue.
>
> I've installed the sane-frontends-1.0.6 package.
>
> I can start xscanimage without pro
20 matches
Mail list logo
