I agree to Oliver, I also think the firmware is the issue. Somewhere in
this list I read about upgrading the firmware but I don't remember for
which scanner model this was. But I think it was at least for a Microtek
scanner. Someone opened his scanner an read out the contens of his
(correct) firmware eprom. Then it is possible to burn eproms for other
The other way would be checking the communication with the Windows driver
and see what they do with this command. Then perhaps it would be possible
to make a workaround for SANE.
Oliver Neukum wrote:
> On Freitag, 9. Februar 2001 18:20, Roy Mathew wrote:
> > Hi Oliver,
> > Where does this leave things? Am I stuck without any resolution?
> > Should I return my scanner or can I hope that there may be
> > a solution soon. (I don't run windows either).
> > Thanks,
> > Roy.
> I don't know. It seems to me that your scanner has a briken firmware.
> A work around may or may not be possible.
> Source code, list archive, and docs: http://www.mostang.com/sane/
> To unsubscribe: echo unsubscribe sane-devel | mail firstname.lastname@example.org
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail email@example.com
This archive was generated by hypermail 2b29 : Sat Feb 10 2001 - 12:12:55 PST