other points of interest,
*mounting the 98.img in linux:
fdisk -l -u -C 592 98.img
echo "512*63" | bc -lq
mount 98.img iso -o loop,offset=32256 -t vfat
* exiting out of qemu focus : alt+ctrl
--
Adam Sulmicki
http://www.eax.com The Supreme Headquarters of the 32 bit registers
Ok, so I got the Microtek ScanMaker 4900 (USB2400) to work under Linux
as follows:
Linux Fedora 8 -> Qemu 0.9.0 -> Windows 98 SE -> Microtek ScanWizard 5
What would be the next step? Any idea?
--
Adam Sulmicki
http://www.eax.com The Supreme Headquarters of the 32 bit registers
What's the procedure to add new code?
In this case it is routine to detect SQ11 chip in sane-find-scanner
--
Adam Sulmicki
http://www.eax.com The Supreme Headquarters of the 32 bit registers
-- next part --
A non-text attachment was scrubbed...
Name: sane.sq11
---
http://www.missl.cs.umd.edu/~adam/sq11/sq11.pgm
--
Adam Sulmicki
http://www.eax.com The Supreme Headquarters of the 32 bit registers
Hello,
I have updated sane-find-scanner to test for what I believe is SQ11 chip.
can anyone else with the same chip try out the patch (sane.sq11.test.diff)
and see if they get the same result?
I have attached full output of run at check-usb-chip-sq11.log.
Below is non-verbose output :
--
On Nov 25, 2007 8:21 PM, m. allan noah wrote:
> it's never completely hopeless, you can get a trace of the windows
> driver in action, and reverse engineer the protocol. its just a
> question of how much time you want to spend, and how much C-fu you
> have. generally, the cheaper the scanner, the
FWIW,
at this point I'm fairly certain that this scanner uses SQ SCAN11 chip.
Since no sane scanner at this point support this chip, I guess it makes the
case pretty hopeless.
data so far :
NAME: "Microtek ScanMaker 4900" aka "USB2400 Scanner" aka "D9"
TYPE:MRS-2400L48U
USB ID: 05da:30d9
, 2007 11:00 PM, Adam Sulmicki wrote:
> Attached is the diff so far...
>
> Does anyone has datascheet for SQ SCAN08 chip?
>
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20071125/c9ba1753/attachment.htm
Is this a conflict? I have
*NAME: Microtek ScanMaker 4900
TYPE:MRS-2400L48U
USB ID: 05da:30d9*
However, in unsuported.desc the entry for 4900 has different USB code (b
instead of d in 30b9). that is :
:model "ScanMaker 4900"
:url "/unsupported/microtek-scanmaker-4900.html"
:interface "USB"
Attached is the diff so far...
Does anyone has datascheet for SQ SCAN08 chip?
-- next part --
A non-text attachment was scrubbed...
Name: sane.microtek.scanmaker.4900.diff
Type: text/x-patch
Size: 2806 bytes
Desc: not available
Url :
http://lists.alioth.debian.org/pipermai
ok
* I got the sane-find-scanner to run, it finds the scanner, but fails
to detect chip.
(I noticed that sane-find-scanner does not seem to look for SCAN08 chip).
I have attached output of the running the program.
* got the scanimage -L to run.
# ./scanimage -L
device `v4l:/dev/video1' is a
Not sure if you care about those stuff. Either way here it goes
(derived from ScanMaker 4800):
# diff /etc/udev/rules.d/60-libsane.rules{-backup,}
833a834,835
> # Microtek ScanMaker 4900
> ATTR{idVendor}=="05da", ATTR{idProduct}=="30d9", SYMLINK+="scanner-%k"
1885a1888,1889
> # Microtek ScanMaker
hello,
how do I explain to sane-scan-find that the following is an usb scanner?
# lsusb
Bus 004 Device 005: ID 05da:30d9 Microtek International, Inc.
I tried something like this, but no go (the goal is to have the
check-usb-chip routine to run).
# cvs diff
Index: backend/sm3840.c
=
13 matches
Mail list logo
