[sane-devel] Snapscan on Mac OS X 10.3

2003-12-07 Thread Rémi Zara
Hi, More findings: scanimage -L fails in usb_claim_interface (sanei_usb.c:603), because=20 the systems tells us the device is already taken by another process. This might be due to the fact that we do an open (sanei_usb: 541)=20 before a claim. Now the fun thing is if I do a printf just before t

[sane-devel] Snapscan on Mac OS X 10.3

2003-12-06 Thread Rémi Zara
--Apple-Mail-2-82248232 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=ISO-8859-1; format=flowed Le 6 d=E9c. 03, =E0 12:19, Henning Meier-Geinitz a =E9crit : > Hi, > > On Sun, Nov 30, 2003 at 01:46:37PM +0100, R=E9mi Zara wrote: >>> Environment vari

[sane-devel] Snapscan on Mac OS X 10.3

2003-12-06 Thread Henning Meier-Geinitz
Hi, On Sun, Nov 30, 2003 at 01:46:37PM +0100, Rémi Zara wrote: > >Environment variable: SANE_DEBUG_SANEI_SOMETHING, e.g. > >SANE_DEBUG_SANEI_USB=255 or SANE_DEBUG_SANEI_SCSI=255. > > This is very interresting ! > With SANE_DEBUG_SANEI_USB=255, scanimage -L finds my snapscan e40 ! > Set it back to

[sane-devel] Snapscan on Mac OS X 10.3

2003-12-01 Thread Oliver Schwartz
=2DBEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, > Some more informations: > scanimage starts to see the scanner at SANE_DEBUG_SANEI_USB=3D8. > With this setting, I was able to scan an image successfully. no idea why this should happen. My best guess is a timing issue, but=20 I'm just clutchi

[sane-devel] Snapscan on Mac OS X 10.3

2003-11-30 Thread Rémi Zara
Hi, Some more informations: scanimage starts to see the scanner at SANE_DEBUG_SANEI_USB=3D8. With this setting, I was able to scan an image successfully. regards, R=E9mi Zara -- R=E9mi Zara http://www.remi-zara.net/ Le 30 nov. 03, =E0 13:46, R=E9mi Zara a =E9crit : >> Environment variable: SANE

[sane-devel] Snapscan on Mac OS X 10.3

2003-11-30 Thread Rémi Zara
> Environment variable: SANE_DEBUG_SANEI_SOMETHING, e.g. > SANE_DEBUG_SANEI_USB=3D255 or SANE_DEBUG_SANEI_SCSI=3D255. This is very interresting ! With SANE_DEBUG_SANEI_USB=3D255, scanimage -L finds my snapscan e40 ! Set it back to 0, and it does not find it anymore. Set it back to 255, and here it

[sane-devel] Snapscan on Mac OS X 10.3

2003-11-30 Thread Henning Meier-Geinitz
Hi, On Sun, Nov 30, 2003 at 12:43:51PM +0100, Rémi Zara wrote: > My next question is how do I enable debug output in sanei ? Is there an > environnement variable, or is this a compile time option ? Environment variable: SANE_DEBUG_SANEI_SOMETHING, e.g. SANE_DEBUG_SANEI_USB=255 or SANE_DEBUG_SAN

[sane-devel] Snapscan on Mac OS X 10.3

2003-11-30 Thread Rémi Zara
Hi, There's no device file for USB on OS X (I think) I tried as a privileged user and the result was the same: lundi:~ rzara$ sudo scanimage -L [sanei_debug] Setting debug level of snapscan to 255. [snapscan] sane_snapscan_init [snapscan] sane_snapscan_init: Snapscan backend version 1.4.35 [snaps

[sane-devel] Snapscan on Mac OS X 10.3

2003-11-29 Thread Oliver Schwartz
=2DBEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, > sane-find-scanner says: > found USB scanner (vendor=3D0x06bd [AGFA], product=3D0x208d [ SNAPSCAN > e40 ]) at libusb:008:008 > > but : > lundi:~/Documents/Projets/sane/sane-backends/include/sane rzara$ > scanimage -L > [sanei_debug] Setting deb

[sane-devel] Snapscan on Mac OS X 10.3

2003-11-29 Thread Rémi Zara
Hi, I'm trying to use my snapscan e40 on Mac OS X 10.3.1. I compiled sane-backends by defining OSX_ONLY_10_2_API sane-find-scanner says: found USB scanner (vendor=3D0x06bd [AGFA], product=3D0x208d [ SNAPSCAN = e40 =20 ]) at libusb:008:008 but : lundi:~/Documents/Projets/sane/sane-backends/incl