<br><br><div class="gmail_quote">On Nov 25, 2007 8:21 PM, m. allan noah <<a href="mailto:kitno455@gmail.com">kitno455@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
it's never completely hopeless, you can get a trace of the windows<br>driver in action, and reverse engineer the protocol. its just a<br>question of how much time you want to spend, and how much C-fu you<br>have. generally, the cheaper the scanner, the more difficult the
<br>driver is to write.</blockquote><div><br>Well, I went to <a href="http://meier-geinitz.de/sane/mustek_a3p1-backend/">http://meier-geinitz.de/sane/mustek_a3p1-backend/</a>, I have grabbed a3p1_0.6.1.2.tar.gz and compiled it (after few trivial changes).
<br><br>right now, when I run scanimage, it crashes and burns on DMARead.<br><br>Could SANE (or at least mildly inSANE) wizards take a look at the log and give a word or two of wisdom on what might be going on (and whether it is SQ11 chip or not).
<br><br><br><br></div></div>