Sorry, this is my fault. The snapscan backend added in 0.70 complains about
not finding an AGFA snapscan at initialization if there isn't one.
Does the umax backend still find your scanner, or does xscanimage stop after
these messages get printed? The message problem will be fixed in the
snapscan backend this evening, and a patch will be available. In the
meantime, the messages should go away if you command out the "snapscan"
line in <sane installation root>/etc/sane.d/dll.conf.
Sorry for any inconvenience.
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