[sane-devel] Problems with libusb and Snapscan 1236U (maybe similar to others): USB dump

2004-03-04 Thread D. Winkler
Hello to all, > > is there any way for a backend to tell what the current status of the > > toggle is, before closing the connection? > > With libusb? I don't think so. But counting packets works fine. I've > implemented it in the mustek_usb backend now and (at least for me) > there are no more

[sane-devel] New Boeder Slimscan issue

2004-03-04 Thread Henning Meier-Geinitz
Hi, On Wed, Mar 03, 2004 at 09:00:12PM -, Jim George wrote: > Scans appear to arrive with the first third of the scan a light colour and > the remaining two-thirds a darker colour. Can you put an example on a webpage? Try a low resolution and width so the image doesn't get too big. > Could t

[sane-devel] Re Genesys backend and other backends

2004-03-04 Thread Henning Meier-Geinitz
Hi, On Thu, Mar 04, 2004 at 04:16:33PM +0530, Sanjay Chigurupati wrote: > I looked at Henning's page. I was looking at Genesys backend as reference > for understanding on how to write backend. Better use a backend that is already finished. For understanding how a backend works in principle, you c

[sane-devel] Question on Genesys backend

2004-03-04 Thread Henning Meier-Geinitz
Hi, On Thu, Mar 04, 2004 at 10:16:45AM +0530, Sanjay Chigurupati wrote: > 3) genesys.c is the high level implementation for the scanner with > genesys.h being the header for it. genesys.c mostly contains the SANE API and calls the hardware-related functions in genesys_low.c. It's mostly copied fr

[sane-devel] mustek_usb backend: scanning only once problem fixed

2004-03-04 Thread Henning Meier-Geinitz
Hi, On Wed, Mar 03, 2004 at 08:56:09PM -, Jim George wrote: > is this related to the recent problem that Eddy deGrief and I had with the > Mustek Parallel Port back-end? I don't think so. The reason for the work-around is a bug in the USB protocol of the Mustek chips (I think). It should only

[sane-devel] Re Genesys backend and other backends

2004-03-04 Thread Sanjay Chigurupati
Hi, I looked at Henning's page. I was looking at Genesys backend as reference for understanding on how to write backend. Which of the usb backends on that page would serve as a good example to write a backend? I read the status, but I am confused. I guess I need to set cvs up on my home machine

[sane-devel] Sane, Microtek ScanMaker II and Mac OS X SCSI

2004-03-04 Thread Matto Marjanovic
... >So the first thing that fails is the first scsi command being sent that >has the isWrite set to 0: > >[microtek] .get_scan_status 0... >[sanei_scsi] cmd2: cmd_size:6 src_size:0 dst_size:6 isWrite:0 >[sanei_scsi] isRead dst_size:6 >[sanei_scsi] Executing command >[sanei_scsi] ExecuteTa

[sane-devel] hp2300c

2004-03-04 Thread Julien TIERNY
Hi all, I have a HP Scanjet 2400. Having a look at USB traces (benoit papillault's sniffer) made me realize = its=20 protocol is very close to HP 3300's one. =09 Le jeudi 4 Mars 2004 00:13, Frank Zago a =E9crit : > Sanjay Chigurupati wrote: > > Does that mean HP 2400c and HP 230

[sane-devel] hp2300c

2004-03-04 Thread Sanjay Chigurupati
Does that mean the Genesys backend is incomplete? regards, sanjay Frank Zago

[sane-devel] Question on Genesys backend

2004-03-04 Thread Sanjay Chigurupati
Hi, Please correct me if I am wrong. This is my understanding: 1) genesys.conf defines the vendor id and , (usb address ?) 2) genesys_low.c is the low level implementation for the scanner with genesys_low.c being the header file for it 3) genesys.c is the high level implementation for the scanne

[sane-devel] hp2300c

2004-03-04 Thread Sanjay Chigurupati
Does that mean HP 2400c and HP 2300c are supported by the latest cvs version of Sane? HP 3670 and HP 2400 seem similar except for HP 3670 having an additional function button . Atleast thats what it looks like from windows driver. Would have to check on that. Its been a while since I had a look a

[sane-devel] Visioneer Strobe XP100 (need help)

2004-03-04 Thread Gerhard Jaeger
Hi, On Wednesday 03 March 2004 22:21, G. Naik wrote: > I have a created a few logs with USB snoopy and the newer USB sniff, > but they are very large in size. I'm going to try and sort through > them and find the relevant URBs. Okay, probably you find some URBs which address the registers, size