Julien BLACHE j...@jblache.org writes:
Oliver Schwartz oliver.schwa...@gmx.de wrote:
I've reduced the size for the 2480 since I currently can't distinguish
between 2480 and 2580. The original size may cause damages on a 2580
since the scanner bumps into the rear end of the transparency
Julien BLACHE j...@jblache.org writes:
Simon Munton si...@munton.demon.co.uk wrote:
EPSON GT-F500 1.16
Thu Oct 28 2004 17:57
Mine is version 1.14, dated 20040402, according to the end of the
firmware file.
Used to work fine for transparencies with 1.0.15.
iscan 1.15.0 has
Here's the identifier from my file:
EPSON GT-F500 1.14.8
Friday Apr 2 2004 15:47
Simon Munton Sent me his firmware file and it has the following signature:
EPSON GT-F500 1.16 P
Thu Oct 28 2004 17:57 EPSON
Simon reports that his file appears to give good scans of both flatbed
materials and
Olaf Meeuwissen o...@member.fsf.org wrote:
Maybe Olaf could help here ?
Not much as I'm bound by a NDA :-(
Well, at least you can confirm the uneducated guess ;)
That not withstanding, the snapscan backend sources show that a fair
bit of the structure of the INQUIRY command's reply is
Olaf Meeuwissen o...@member.fsf.org wrote:
iscan 1.15.0 has version 1.16, dated 20041028. Not tested.
That's the only version iscan ever had.
TBH, I didn't bother checking the previous versions ;)
I can't seem to find any reference to the hardware Ken is using, but
if not ix86 could this
Ken Ramey ramey@gmail.com wrote:
Here's the identifier from my file:
EPSON GT-F500 1.14.8
Friday Apr 2 2004 15:47
Julien Blache's file seems to have the same signature as mine. It's
not clear to me if he is seeing the color banding problem or not.
Julien?
Works for me with
Hi,
I'm a proud owner of Lexmark All-In-One P6250 multifunction device. I've
submitted its scanner information as an unsupported scanner, and I'm
wondering, if there's any development on writing a sane backend to it. Do you
have any information on such efforts? Thanks.
--
(Man) tries to live
Hi,
Finally my request for the NDA was accepted by Nikon i was told (took 3
months because i didn't request it under a company hood) so i should
get the specs soon. I also have the scanner so i hope to be able to
get it working ;-) (hope is the last thing you should loose, right?
;-) But
Hi Paul,
On Tuesday 09 August 2005 12:27, Paul Smedley wrote:
Oh I forgot to mention - in the logs that 'beep' there's a return code
(32772) from usbbulkread that says 'less data than requested returned'.
In this case, 1 byte was requested and 0 returned. log excerpt
below shows
Hi Gerhard,
Gerhard Jaeger wrote:
Hi Paul,
On Tuesday 09 August 2005 12:27, Paul Smedley wrote:
Oh I forgot to mention - in the logs that 'beep' there's a return code
(32772) from usbbulkread that says 'less data than requested returned'.
In this case, 1 byte was requested and 0
Hi all,
That not withstanding, the snapscan backend sources show that a
fair bit of the structure of the INQUIRY command's reply is already
known. This is the command I would expect to show different replies
for both models.
They do, but up to now I only have the data of three different
Hi,
Mine is version 1.14, dated 20040402, according to the end of the
firmware file.
Used to work fine for transparencies with 1.0.15.
I've got the 1.14/20040402 as well, that is not working for me with the 1.0.15
backend.
I just downloaded the 1.0.16 sources, and hope to get it compiled
=
=LvpK
-END PGP SIGNATURE-
-- next part --
A non-text attachment was scrubbed...
Name: yuri.vcf
Type: text/x-vcard
Size: 400 bytes
Desc: not available
Url :
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20050815/cfcde9e3/yuri.vcf
From henn...@meier
Hi,
the code is in CVS now. Please try it and let me know if it works for
you.
I currently don't have any information on the firmware filename.
Usually there is only one supplied with the windows driver. Look for
any *.bin file in the twain32 directory.
/Oliver
Hi,
maybe there is something beyond versions to make the transpareny
unit work (or not work), I have the scanner connected via an USB
hub, having only two USB-ports (USB 1.1), that might have some
influence as well?
Well, it shouldn't, but I've seen stranger things happen. If the
scanner is
/x-log
Size: 8655 bytes
Desc: not available
Url :
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20050815/610ec3cb/usbsnoop.bin
From sp...@siriush.com Mon Aug 15 19:08:52 2005
From: sp...@siriush.com (Spiro Angeli)
Date: Mon Aug 15 19:09:03 2005
Subject: [sane-devel] Nikon LS 5000
Hi,
On Mon, Aug 15, 2005 at 09:01:11PM +0200, serja wrote:
I've downloaded some tools and tried out the SniffUSB. The log file I've got
after scanning was incredible big (65 - 110 mb),
Often big files are created by continous probes for buttons.
How big was the scan you did? Usually you
17 matches
Mail list logo
