I don't know if this is the proper forum to bring this up, but I thought
I would try at the very least.
I am converting one of my machines from a Win98/Photoshop base to a
Linux/GIMP base for graphical design and development. The scanner I
have is a Microtek SlimScan C3, a reasonable choice for a Windows base,
perhaps, but a lot of trouble in Linux. But this isn't stopping me from
trying to get it to work, but I am at my wits end. The number one
reason is that the scanner is parallel but appears to have a
SCSI component to it.
The first thing I did was download the ppSCSI suite drivers and
installed them. (http://www.torque.net/parport/ppscsi.html) and the
patch went in well with RH 6.0 (2.2.9). The protocol I decided to try,
based on the presumption I have seen on other Mustek scanners, is onscsi
(for OnSpec 90c26). After insmoding the various packages (insmod sg,
insmod ppscsi, and insmod onscsi), the systems on the parallel chain
"initialized".
find-scanner produced:
---[root@dilophosaurus sane.d]# find-scanner find-scanner: found scanner " scanner 330CS 1.34" at device /dev/scanner find-scanner: found scanner " scanner 330CS 1.34" at device /dev/sg0 find-scanner: found scanner " scanner 330CS 1.34" at device /dev/sga
---Not exactly very specific. But at least it's something! The best news I had gotten in 24 hours while configuring everything.
Next step:
---[root@dilophosaurus sane.d]# scanimage -d microtek2:/dev/scanner scanimage: open of device microtek2:/dev/scanner failed: Error during device I/O [root@dilophosaurus sane.d]# scanimage -d microtek:/dev/scanner scanimage: open of device microtek:/dev/scanner failed: Invalid argument
---To mock me, the green light on the scanner during both attempts, gave a blink. Something was going on.
---[root@dilophosaurus scsi]# ls -l total 0 dr-xr-xr-x 2 root root 0 Oct 31 18:48 onscsi -rw-r--r-- 1 root root 0 Oct 31 18:48 scsi [root@dilophosaurus scsi]# ls -l onscsi total 0 -rw-r--r-- 1 root root 0 Oct 31 18:48 0
----
Mmm. Again, interesting.
My question is: Does this mean that SANE, which can at least touch the scanner, is infact incompatible with it? Is there any development along these lines and if I am not doing something extremely dumb and overlooking a obvious thing .... if it happens that this device is not yet supported, is there anyway I can contribute information or data so that one can be developed?
Oh, just one more thing...
----
[root@dilophosaurus scsi]# scanimage -L device `pnm:0' is a Noname PNM file reader virtual device device `pnm:1' is a Noname PNM file reader virtual device
----
Not there. Not surprisingly.
Anyone have any ideas? Thanks and sorry for the lengthy and detailed message.
Jason
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com