Karl Heinz Kremer wrote:
Hi,
> I'm about to receive a Perfection 636S, which uses the same command set as
> the 636U. This means that I can (for the first time) actually debug this
> problem myself. I can assure you that this problem will be fixed in a few
> weeks.
Very good news ! Happy hackin
I'm about to receive a Perfection 636S, which uses the same command set
as
the 636U. This means that I can (for the first time) actually debug this
problem myself. I can assure you that this problem will be fixed in a
few
weeks.
Karl Heinz
On Jul 4, 2004, at 4:03 PM, Julien BLACHE wrote:
> He
Henning Meier-Geinitz wrote:
Hi,
> Anyway, make sure that a line containing only "usb" is in epson.conf.
> If that's the case, show us the complete log. To make the log shorter,
> you can disable everything but "epson" in dll.conf.
Support for the Perfection 636U seems to be kind of broken late
Hi,
On Sun, Jul 04, 2004 at 11:37:05AM -0400, Fritz Lang wrote:
> I have a G3 450Mhz running Panther.3.2 on OEM video card.
That's the interesting part of the log:
> [epson] sane_init: sane-backends 1.0.14
> [sanei_debug] Setting debug level of sanei_usb to 255.
> usb_set_debug: Setting debuggi
I have a G3 450Mhz running Panther.3.2 on OEM video card.
256M RAM
PCI USB 2 port and PCI FW 2 port cards.
Only the Epson 636U scanner is plugged in.
I powered the scanner on first, then plugged into the port.
There are no other apps running that scan, nor do I have any other
apps that scan. N
