[sane-devel] NEC Petiscan driver for MacOSX possible?

2004-06-10 Thread Mattias Ellert
This is a cryptographically signed message in MIME format. --ms070607030900050808020401 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Allan Kaplan wrote: > Hi Mattias, > > I am happy to report a little progress. Once I installed the proper

[sane-devel] RE: sane-devel digest, Vol 1 #365 - 11 msgs

2004-06-10 Thread David Neary
Hi, Keith Clayton wrote: > What sort of steps are availble for me to take debugging-wise on the > windows end? > > If xsane is started from the command prompt, are there any swithces > available to generate debugging output at the command prompt? As Henning said, you just need to set your enviro

[sane-devel] Timeouts: usb_reset seems necessary to avoid bulk timeouts.

2004-06-10 Thread Tom Schutzer-Weissmann
On Thu, 10 Jun 2004 05:36:52 -0400 Karl Heinz Kremer wrote: > I'm also reading sane-devel, so no need to take a detour with > any Epson backend related information :-) > I've never experienced any of the problem you describe, and I've > been running a 2.6.x kernel for some time now (SuSE 9.1 beta

[sane-devel] Oops . . here's the logs (xsane-win32/saned + epson 1650 prob)

2004-06-10 Thread Oliver Rauch
For windows you can not enable a debug output - at least I do not know a way with the published binaries because they are compiled as GUI. BTW. Did you ever test xsane-0.94-win32? Oliver Am Don, 2004-06-10 um 16.09 schrieb Keith Clayton: > What sort of steps are availble for me to take debugging

[sane-devel] Oops . . here's the logs (xsane-win32/saned + epson 1650 prob)

2004-06-10 Thread Henning Meier-Geinitz
Hi, On Thu, Jun 10, 2004 at 07:09:36AM -0700, Keith Clayton wrote: > What sort of steps are availble for me to take debugging-wise on the > windows end? > > If xsane is started from the command prompt, are there any swithces > available to generate debugging output at the command prompt? I don't

[sane-devel] Oops . . here's the logs (xsane-win32/saned + epson 1650 prob)

2004-06-10 Thread Henning Meier-Geinitz
Hi, On Wed, Jun 09, 2004 at 09:18:11PM -0700, Keith Clayton wrote: > Hate when I do that . . here's the xsane logs described in my previous > email Ok, let's look at the second log. The preview scan looks ok (but I don't know the details of the plustek backend). The real scan also starts fine and

[sane-devel] Question About Mustek 600CP scanner on Suse 9.1

2004-06-10 Thread Neal Gamradt
Hello All, First off I would like to thank you all for the the work you have put into scanner support for Linux, I have a Mustek 600CP and historically I have never had much trouble setting it up thanks to the great work you have done. I recently upgraded from Suse 8.2 to Suse 9.1. Currently I a

[sane-devel] Timeouts: usb_reset seems necessary to avoid bulk timeouts.

2004-06-10 Thread Olaf Meeuwissen
Hi Tom, I am the lead developer of iscan and the sane-epkowa backend that comes with it. Farideh has also contacted me about your issue, but I think that my reply is better sent to sane-devel (at least it'll be archived :-). Tom Schutzer-Weissmann writes: > I had problems using the Epkowa libr

[sane-devel] Re: How to configure sane, xsane, etc.

2004-06-10 Thread Olaf Meeuwissen
Henning Meier-Geinitz writes: > On Wed, Jun 09, 2004 at 10:08:32AM +0200, Fran=E7ois Patte wrote: > >> and to wait about 10/15 minutes for the research of >> peripherics > > That shouldn't happen. Which version of sane do you use > (scanimage --version)? The scan takes about 1 to5 seconds at

[sane-devel] Fwd: [canon630u] read_byte(fd, 0x01, &result); /* got 00 */

2004-06-10 Thread Henning Meier-Geinitz
Hi, On Wed, Jun 09, 2004 at 08:15:01PM +0200, ins...@piments.com wrote: > As you can see communication seems to go quite well at first but then gets > stuck in a loop with no apparent timeout. I have had a quick look at the sourcecode and think the loop happens at backend/canon630u-common.c, li

[sane-devel] saned + win32-xsane problem

2004-06-10 Thread Henning Meier-Geinitz
Hi, On Wed, Jun 09, 2004 at 09:16:13PM -0700, Keith Clayton wrote: > I re-did my tests. Nice. But it looks like you forgot to attach the results :-) > 2nd test: used xsane to do a remote preview scan then attempt a regular > scan once the preview has completed and the scanner head returned to >

[sane-devel] Oops . . here's the logs (xsane-win32/saned + epson 1650 prob)

2004-06-10 Thread Keith Clayton
No, still running 0.90 on the windows box. I upgraded to 0.94 on the linux box and looked for windows binaries at the same time. Didn't see them. Did I miss it? K On Thu, 10 Jun 2004, Oliver Rauch wrote: > For windows you can not enable a debug output - at least I do not know > a way with the

[sane-devel] Oops . . here's the logs (xsane-win32/saned + epson 1650 prob)

2004-06-10 Thread Keith Clayton
I don't know much about windows side either. Guess I'll plug away a bit and see if I can coax some debug output out of xsane Cheers, Keith On Thu, 10 Jun 2004, Henning Meier-Geinitz wrote: > Hi, > > On Thu, Jun 10, 2004 at 07:09:36AM -0700, Keith Clayton wrote: > > What sort of steps are availb

[sane-devel] Oops . . here's the logs (xsane-win32/saned + epson 1650 prob)

2004-06-10 Thread Keith Clayton
What sort of steps are availble for me to take debugging-wise on the windows end? If xsane is started from the command prompt, are there any swithces available to generate debugging output at the command prompt? K On Thu, 10 Jun 2004, Henning Meier-Geinitz wrote: > Hi, > > On Wed, Jun 09, 200

[sane-devel] Timeouts: usb_reset seems necessary to avoid bulk timeouts.

2004-06-10 Thread Karl Heinz Kremer
I'm also reading sane-devel, so no need to take a detour with any Epson backend related information :-) I've never experienced any of the problem you describe, and I've been running a 2.6.x kernel for some time now (SuSE 9.1 beta versions and the final SuSE 9.1). I've tried this with two differen