Hi René,
Many thanks for your fast patch. 32-bit is compiling now.
Cheers,
Rolf
Am 15.03.2015 um 00:21 schrieb René Rebe:
Hi,
thanks for the pointer, should be fixed in git:HEAD now. Let hem know if
you find more ,-)
René
On Mar 14, 2015, at 21:40, Rolf Bensch r...@bensch-online.de
On 15/03/15 07:43, Stef wrote:
what is needed is a log recorded when doing a preview when running
windows O/S. The log tool to use is usbpcap http://desowin.org/usbpcap/ .
Would a Wireshark log help, while running Windows in VirtualBox?
I have such a log, however, am not able to generate
On 14/03/2015 18:12, Jochen wrote:
Hi Stef, I understand you're asking for a log from somebody with a LiDE
120 doing a preview. Me, I'd be happy to see my LiDE 120 supported by
SANE. So if you tell me what to do and how to even make my LiDE 120 do
anything loggable, I'll see if I can provide
Hi Stef, I understand you're asking for a log from somebody with a LiDE
120 doing a preview. Me, I'd be happy to see my LiDE 120 supported by
SANE. So if you tell me what to do and how to even make my LiDE 120 do
anything loggable, I'll see if I can provide that. Unfortunately, I am
not much of a
hmm- I have never actually seen an fi-65f, I only have user reports
from my patches. However, the initial development was done with
firmware 65f_0A01.nal Can you try to extract that version (or later)
from the Fujitsu windows drivers? You might have to get the latest
version from their website.
Wireshark is fine, but this log does not contain the calibration step,
which is where sane seems to fail. Can you unplug and replug the
device while wireshark is running, and get a log of the initialization
process? I'm not sure if wireshark can do that.
allan
On Sun, Mar 15, 2015 at 6:01 PM,
I think this should cover it, started capture before plugging in, then
initialization and then a full page scan:
https://www.dropbox.com/s/y0mz0by18r1uti5/fi65_3.pcap?dl=0
-Jonas
On Sun, 15 Mar 2015 15:39:16 -0700 m. allan noahkitno...@gmail.com wrote
Wireshark is fine, but this
Hmm- perhaps you can try scanimage again, but at resolution 300? Also
increase the epjitsu debug level to 25, and don't set the dll debug
level, it is not helpful.
I see a couple possible differences that have never been important
with prior scanners, but perhaps are important with yours.
allan
I see, installing that driver on Windows adds both a 65f_.nal in C:\Windows
and a 65f_0A01.nal in C:\Windows\twain_32\fjscan32. I had missed that latter
last time.
Unfortunately, still no change in behavior. The output remains effectively
same, but just in case I'm missing something, below
I also have a Canon LiDE 120 that I hope SANE will support soon.
If there's any other log/capture files that you need I'd be happy to
provide them.
Thanks,
Steven
--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Hi All,
Any idea on this?
From: sane-devel
[mailto:sane-devel-bounces+arielramonito.edera=ddp.kyocera@lists.alioth.debian.org]
On Behalf Of Ariel Ramonito Edera
Sent: Friday, March 13, 2015 5:41 PM
To: sane-devel@lists.alioth.debian.org
Subject: [sane-devel] xsane crashes using Acquire
On 15/03/2015 12:23, Mr. Kraus wrote:
Hello,
what is needed is a log recorded when doing a preview when running
windows O/S. The log tool to use is usbpcap http://desowin.org/usbpcap/ .
Regards,
Stef
Hi, here you go! To be complete, I added the log of an actual scan, as well:
12 matches
Mail list logo
