Oliver and Allan, Thank you for the help. I have editted the snapscan.conf file so that the path points to the firmware file. I tried again with the debugging level at 255.
Andy-Whelans-Computer:~ andywhelan$ SANE_DEBUG_SNAPSCAN=255 scanimage -L [sanei_debug] Setting debug level of snapscan to 255. [snapscan] sane_snapscan_init [snapscan] sane_snapscan_init: Snapscan backend version 1.4.53 [snapscan] add_usb_device(libusb:002:002-04b8-011f-ff-ff) [snapscan] add_usb_device: Detected (kind of) an USB device [snapscan] snapscani_usb_open(libusb:002:002-04b8-011f-ff-ff) [snapscan] add_usb_device: error opening device libusb:002:002-04b8-011f-ff-ff: Invalid argument [snapscan] sane_snapscan_get_devices (0xbffff830, 0) No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). [snapscan] sane_snapscan_exit Andy On Dec 18, 2007 6:04 AM, Oliver Schwartz <Oliver.Schwartz at gmx.de> wrote: > Hi, > > you also need to specify the path to the firmware file in > snapscan.conf, which is installed in /usr/local/etc/sane.d/ on OS X, > IIRC. > > The firmware file itself (esfw30.bin) should be contained on the > windows driver CD. > > See http://snapscan.sourceforge.net for some additional infos on the > firmware files. Let me know if that doesn't solve your problem. > > Regards, > > Oliver > > > On 18.12.2007, at 05:51, andy whelan wrote: > > > Andy-Whelans-Computer:~ andywhelan$ scanimage -L > > [sanei_debug] Setting debug level of snapscan to 2. > > [snapscan] add_usb_device: error opening device libusb: > > 002:002-04b8-011f-ff-ff: Invalid argument > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20071218/ca67f262/attachment.htm
