I'll fix the snapscan backend so it doesn't complain anymore about finding the
wrong scanner unless the debugging level is appropriately set, and make a patch
available.
As for finding your scanner, my understanding is that xscanimage should be
able to find it. Was xscanimage stopping completely when the snapscan
backend generated those messages? If so, there could be a bug in the snapscan
backend that is preventing xscanimage from finding your scanner. (You're
using an HP scanner, right?
Kevin
-- Kevin Charter /\ Grad Studies charter@cs.ualberta.ca /\/ \ Department of Computing Science http://web.cs.ualberta.ca/~charter \ -------- University of Alberta ---------------
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com