Hi,
Version 1.0.11 of the test backend can be dowloaded from
http://www.meier-geinitz.de/sane/test-backend/ .
Changes:
- Bugfixes
- different return stati for sane_read()
- man page
- it's beta now
I would like to include the test backend into sane-backends so I'm
interested in any bug reports
Johan Bengtsson wrote:
>
> Hi,
>
> We're running Gimp 1.0.4 & xsane 0.79 and we have two workstations with
> scanners, one with an Umax scanner and the other one with an Epson
> scanner. The problem is that if one first uses the Epson scanner, gimp
> will create a pluginrc file which points to th
Hello,
Reading the Microtek backend web page at "http://www.mir.com/mtek"; I
noticed a way to get debug info displayed. So I did this and re-ran xsane:
262 craig@lios #> setenv SANE_DEBUG_MICROTEK 128
263 craig@lios #> xsane microtek:/dev/scsi/scanner/c6t6d0
[sanei_debug] Setting debug le
On Tue, 9 Apr 2002, Karsten Festag wrote:
> Hi Craig,
>
> The 'scsi * * scanner' line is for autodetecting every scanner on the
> scsi subsystem. It is not neccessary if you specify the device file and
> I don't know if the autodetection works on Solaris.
>
> Hope that helps, otherwise please foll
Hi,
We're running Gimp 1.0.4 & xsane 0.79 and we have two workstations with
scanners, one with an Umax scanner and the other one with an Epson
scanner. The problem is that if one first uses the Epson scanner, gimp
will create a pluginrc file which points to the Epson driver and
device. If one late
Hi,
On Tue, Apr 09, 2002 at 08:50:04PM +1000, Craig Dewick wrote:
> Reading the Microtek backend web page at "http://www.mir.com/mtek"; I
> noticed a way to get debug info displayed.
I have mentioned this in my first response to your email.
> [microtek] sane_init: config- /dev/scsi/scanner/c6t6
Hi,
On Tue, Apr 09, 2002 at 07:40:31PM +1000, Craig Dewick wrote:
> No, it didn't change anything. However, what I have noticed is that
> running sane-find-scanner with no device name specified, but using the -v
> option, produces a whole list of device names which do not even exist on
> my system
Hi,
On Mon, Apr 08, 2002 at 01:55:14PM -0700, paul beard wrote:
> >[...ers/paul/src/sane-backends-1.0.7/backend]:: make
> cc -c -g -O2 -W -Wall -DHAVE_CONFIG_H -I. -I. -I../include
> -I../include -D_GNU_SOURCE
> -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d
> -DPATH_SANE_DATA_DIR=/usr/local/shar
Hello
You are listed as the current maintainer of the coolscan backend in
SANE. I tested the current CVS version on Solaris, and got several
warnings. I think several of these are plain typos (the semicolon
after functions for instance), and severals are just signed/unsigned
typos. You should c
Hello
You are listed as the current maintainer of the bh backend in SANE. I
tested the current CVS version on Solaris, and got this warning:
"../../backend/bh.c", line 1923: warning: end-of-loop code not reached
The last line in the for loop is a return statement. This code seemed
a bit stra
On Mon, 8 Apr 2002, Karsten Festag wrote:
> Hi Craig,
>
> do you have an entry like
>
> /dev/scsi/scanner/c6t6d0
>
> in the microtek.conf file?
Yes. I modified microtek.conf and dll.conf in /usr/local/etc/sane.d. The
first file looks like this:
# Uncomment following line to disable "real calibr
--=-yvdinyCrqjV5yxlSVHFa
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
On Tue, 2002-04-09 at 04:42, paul beard wrote:
> SANE builds OK, but then we get this with xsane.
>=20
> cc -c -DHAVE_CONFIG_H -DLOCALEDIR=3D/usr/local/share/locale -I. -I.=20
> -I../include -I../include
Hi Craig,
The 'scsi * * scanner' line is for autodetecting every scanner on the
scsi subsystem. It is not neccessary if you specify the device file and
I don't know if the autodetection works on Solaris.
Hope that helps, otherwise please follow Henning's suggestions.
Karsten
Craig Dewick schri
I'm having an odd issue with a sp15c.
It scans fine, but when using the adf it always takes a extra page
after the scan and kicks it out.
Scan one page, eject a second, scan the page, eject a second, etc...
Every other page in the stack is being scanned.
Any suggestions?
--
Ash
"With trembl
The HP 5400c is not supported currently by any
backend. I have a 4400c which, from what I can gather
on HP's website utilizes most of the same command set.
I have made some changes to the HP3300 backend and
gotten the backend to recognize my scanner. However,
without knowledge of the command se
Hi,
OS/2 requires
#include
(because of mode_t)
to get it compiled
Franz
16 matches
Mail list logo