[]
> Hello,
>
> I've parsed it a bit, and I must say that you're painting the picture
> darker than it really is for parallel port scanners. Parallel port scanners
> listed in SANE do work. No need to frighten people.
>
> I'm a bit skeptic about favouring ECP mode. It may be w
Hi,
On Freitag, 6. Juni 2003 00:18, Karsten Festag wrote:
[SNIPSNAP]
> Just a remark:
>
> The Microtek2 parport scanners (they use the onscsi parport chip) do no=
t
> work in ECP or ECP/EPP mode (data corruption occurs). EPP is here the o=
nly
> option to get good results.
>
The same applies to t
Hi,
On Thu, Jun 05, 2003 at 08:11:02PM -0700, Philip M Dunton wrote:
> I have an Epson 1650 scanner which worked perfectly with my Redhat 8
> installation. Never a second of grief.
> Now, after switching to RH 9 and the version of Sane which comes with it I
Which version of SANE is that (scani
--fNagykWcDoSVAmSd
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Fri, Jun 06, 2003 at 09:51:20AM +0200, Henning Meier-Geinitz wrote:
> You mean xsane is started when you log into X? Oh well...
That might be the case if he has put it in his GNOME session; it's not
some
On Thu, Jun 05, 2003 at 08:31:52PM +0200, Christoph Bier waffled thusly:
> Henning Meier-Geinitz schrieb:
> > Hi,
> >
> > Some people reported kernel USB timeouts with their gt68xx based
> > scanners, e.g. Plustek 1247 or Mustek BearPaw series. This seems to be
> > caused by the check if the firmw
Hi,
On Fri, Jun 06, 2003 at 09:16:05PM +1000, Michael Fleming wrote:
> I can confirm it now works with my Genius ColorPage Vivid 3XE (USB)
> using libusb 0.1.6 and sane-backends 1.0.12 (on Redhat 9, hand-rolled
> RPM, current RH errata kernel)
Thanks for the report. Any problems in color mode? Th
Hi,
some time ago, there have been reports that it's necessary to comment
out sm3600 in dll.conf on MacOS X because otherwise SANE crashes in
that backend. Is this still the case?
Bye,
Henning
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--enig5F795099F5F25C456C69E563
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi,
I commited the new (and fixed) sanei_pa4s2 to cvs earlier today.
In order to use the mustek_pp backend, you either
Hello.
I've been trying to get my Microtek SlimScan C6 working on my Macintosh
running Mac OS X 10.1.5. After a couple days spent trying to get it to
compile correctly (you can see the details on the mailing list),
everything compiled (including libusb) and I was excited to try my
scanner. It show
Jochen Eisinger wrote:
> What about including libieee1284 into the SANE distribution? I'd
> volunteer on keeping it up to date.
As long as one has the option of using the system's libieee1284, I
won't object. Otherwise you'll hear me scream ;-)
Anyway, libieee1284 is quite small and easy to bui
Hi,
On Fri, Jun 06, 2003 at 09:24:59AM -0700, David Alan Hjelle wrote:
> I've been trying to get my Microtek SlimScan C6 working on my Macintosh
> running Mac OS X 10.1.5.
[...]
> So, I did some research. Apparently, the microtek2 backend only
> supports USB kernel extensions and not libusb? Wha
Hi,
I've moved the list of backends that will be build from
backend/Makefile.in to configure. So we can print more clearly which
backends will be compiled and the tests are all in one place.
The changes are in CVS now. Please test if I broke something.
Configure pronts a warning if a backend is
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--enigC23D0D5E5B47D942DBAEFBFB
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi,
Julien BLACHE wrote:
> As long as one has the option of using the system's libieee1284, I
> won't object. Otherwise
Hi,
There has been some criticism of the current handling of the :status
keywords in the .desc files. These filse are used to create our lists
of scanners and the output of the scanner search engine.
We currently have two sorts of status indicators:
1) The backend status: alpha, beta or stable
2
14 matches
Mail list logo
