Juanito


Group: Members
Posts: 1601
Joined: Sep. 2005 |
 |
Posted: April 06 2008,05:14 |
 |
Quote | Your sane.uci detects my umax scanner fine using sane-find-scanner, but that is as far as I can go, being spoiled by xsane no doubt. I am not too familiar with scanning at the command line, and my xsane.dsl does not work with this extension. |
Thanks for trying it out - I'm not too sure what you mean by xsane - the sane.uci extension has scanimage (command line) and xscanimage (gui).
Quote | Since it finds my scanner, I am sure it is just a pebkac/configuration issue on my part. |
I believe that if "sane-find-scanner"/"scanimage -L" find your scanner, it is just a question (how easy that is to say) of adding a suitable .conf file to /etc/sane.d/ and then scanimage and xscanimage should work.
|