Hi!
First of all, I am not a hardware expert, and my English is not that
good :-) I have found some weird bahaviour, and it might be a bug, but I
am not knowledgable enough to know for sure. I am really hoping that
someone on this mailing list can provide some feedback and/or hints. I
have
Hi,
On Sun, Oct 02, 2005 at 12:09:28AM +0200, Frank Zago wrote:
The idea is to keep the SANE and Windows driver as close as possible
to eachother to enable the Mustek people to add more scanners easier.
On the other hand I already had to change a lot of stuff like their
split in separate
Hi,
the behaviour you describe is perfectly normal, as far as the ID of
the scanner is concerned. Initially the scanner identifies itself as
FlatbedScanner_13. After downloading the firmware (which seems to
work only in windows in your case) the scanner identifies itself as
FlatbedScanner_21.
I took the snapshots from http://www.sane-project.org/snapshots/
which were:
sane-backends-2005-10-02.tar.gz
sane-frontends-2005-10-02.tar.gz
I also grabbed libusb-0.1.10a.tar.gz from sourceforge and isnatlled
that. Though it installs as 0.1, which seems a strange numbering
scheme:
# ls
Hi,
On Sun, Oct 02, 2005 at 10:58:52PM +1000, Luke Kendall wrote:
I took the snapshots from http://www.sane-project.org/snapshots/
which were:
sane-backends-2005-10-02.tar.gz
sane-frontends-2005-10-02.tar.gz
I also grabbed libusb-0.1.10a.tar.gz from sourceforge and isnatlled
that.
Hi,
On Sunday 02 October 2005 14:58, Luke Kendall wrote:
I took the snapshots from http://www.sane-project.org/snapshots/
which were:
sane-backends-2005-10-02.tar.gz
sane-frontends-2005-10-02.tar.gz
I also grabbed libusb-0.1.10a.tar.gz from sourceforge and isnatlled
that. Though
Hi Ariel,
great news I hear.
Thank you for working on this. Please let me/us know when you are almost done.
I cannot wait to get this scanner to work, so that I can start my project.
Good work!
Spiro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Haag wrote:
Hi
I just found this ini file by accident.
http://mibix.de/projects/md6190/hardware.ini
it provides view comments assigned to some numbers (thought default
values), maybe that helps to analyse the log files.
Some
