Thanks Oliver, this sounds more like it; except the only thing that has changed is my commenting out.
I had to assume a firmware update was as everything I read suggested it would be and not having discovered any info that said otherwise. Also I don't really know what that involves so simply copied snape20.bin off the e20 driver CD and into a likely directory - /usr/local/etc/sane.d for what it's worth. Is there a chance I've got/had a conflict with some other firmware in another location. As you can see I'm just stumbling around having fun! Don't forget that at this point in time everything seems to be working fine, and it wasn't before! Regards, Alisdair Oliver Schwartz wrote: > Hi, > > >>I think I'm using libusb, but I've not checked. > > > It shouldn't matter which driver you use. > > >>Between my posting and your response it's possible I've solved the >>problem by commenting out all the details listed for other scanners >>in snapscan.config. > > > If you're referring to the "usb" statements: These values are only > used for queries on the usb layer. They do not even result in > commands send to the scanner. Whether you have 1 query or 100 won't > change the data transfer to and from the scanner. > > >>A couple of reboots and starting Xsane each time has produced a >>perfectly uneventful start for the scanner. > > > In most cases this is a firmware file issue. Are you sure you had the > correct firmware file in snapscan.conf when the noises occured? > > Regards, > > Oliver > _______________________________________________ > Sane-devel mailing list > sane-de...@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel > > . >
