This is a multi-part message in MIME format.
--050502060805010409020200
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Hi Susan,
I had a look into your fstab and compared it with mine. Maybe you like
to try the different versions of lines I
--Boundary-00=_FiuxBU6nitX3pWR
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Hi,
I guess we are some steps closer.
> > [sanei_debug] Setting debug level of snapscan to 2.
> > device `snapscan:libusb:001:007' is a Acer FlatbedScanner4
On Sun, 2004-12-19 at 21:54 +0100, Peter Ankerstål wrote:
> It seems that windows get much better results scanning negatives.
> Is it just me or could this be true? (smaller pixels, sharper results)
The main reason is that scanning negatives requires a lot more post
processing on the PC than scann
Hello,
On Dec 20 07:40 Karl Heinz Kremer wrote (shortened):
> NNO :-)
Grtt :-))
>the epson.conf file:
> usb 0x4b8 0x80e
>
> Once the scanner is recognized, the backend will talk to the scanner and
> find out it's capabilities automatically.
...
Hello,
On Dec 17 20:20 Karl Heinz Kremer wrote (shortened):
> Thanks, I'll add the CX-3650, the 6400 is already supported.
>
> On Dec 17, 2004, at 9:11 PM, Till Kamppeter wrote:
> > here are some device IDs, both are MF devices which work with the "epson"
> > backend:
> >
> > epson cx 6400: 0x04
NNO :-)
You don't have to recompile the backend just because you want to add
a new product ID to the EPSON backend.
To recognize a new scanner, the system has to do two things:
1. The hotplug system needs to know what to do with the new device. This
is the reasy why you ne
