Skipped content of type multipart/alternative-------------- next part 
--------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 1856 bytes
Desc: not available
Url : 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060926/df0f0587/attachment.jpe
From [email protected]  Tue Sep 26 23:45:50 2006
From: [email protected] (Olaf Meeuwissen)
Date: Tue Sep 26 23:46:57 2006
Subject: [sane-devel] Re: Problem Scanning with Epson RX520
In-Reply-To: <[email protected]> (Paul Smedley's
        message of "Tue, 26 Sep 2006 10:12:05 +0000 (UTC)")
References: <[email protected]>
        <[email protected]>
        <[email protected]>
Message-ID: <[email protected]>

"Paul Smedley" <[email protected]> writes:

> Hi Olaf,
>
> On Mon, 25 Sep 2006 00:28:16 UTC, Olaf Meeuwissen 
> <[email protected]> wrote:
>
>> "Paul Smedley" <[email protected]> writes:
>> 
>> > Hi Guys,
>> >
>> > I got a report from a user of the OS/2 version of Sane that the Epson 
>> > RX520 isn't working.  Debug log is at http://smedley.ingo/debug.txt
>> 
>> FWIW, the epson backend doesn't claim it's supported in any way.  The
>> epkowa backend does.
> Yep - epkowa backend did it for the user....

Good to know.  So the epkowa backend also works on OS/2.

Looks like some of the changes in the epkowa backend need backporting
to the epson backend.  Unfortunately, I don't really have time at the
moment :-(

>> # Is that URL valid?  Looks like my DNS server doesn't know about
>> # smedley.ingo ...
> Slip of the fingers - should have been http://smedley.info/debug.txt

Had a quick look already but need to get my hands on an RX520 (got one
at home, so that's not the problem) and start digging but there's the
time thingy ...

Hope this helps,
-- 
Olaf Meeuwissen                          EPSON AVASYS Corporation, SE1
FSF Associate Member #1962           sign up at http://member.fsf.org/
GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97  976A 16C7 F27D 6BE3 7D90
Penguin's lib!       -- I hack, therefore I am --               LPIC-2

Reply via email to