Minolta Scan Dual IV With Vuescan under Linux

[Leonard Evens]

I am using Fedora Core 2 Linux. Using a post by Jack Frillman, I
managed to get the Scan Dual IV working under my OS using Vuescan. The
secret was to add the following entry to the file
/etc/hotplug/usb/libsane.usermap

# Konica Minolta|Scan Dual IV
libusbscanner 0x0003 0x132b 0x000a 0x4000 0x0000
0x00 0x00 0x00 0x00 0x00
0x00 0x00000000

This just copies the previous entry for the Dual Scan III but changes
the Vendor ID (0x132b) and the Product ID (0x000a).

So far everything works fine, but there are some peculiarities. I've
posted a question about that separately.

 

[Xiaotian Sun]

I am using Fedora Core 2 Linux. Using a post by Jack Frillman, I
managed to get the Scan Dual IV working under my OS using Vuescan. The
secret was to add the following entry to the file
/etc/hotplug/usb/libsane.usermap

# Konica Minolta|Scan Dual IV
libusbscanner 0x0003 0x132b 0x000a 0x4000
0x0000
0x00 0x00 0x00 0x00 0x00
0x00 0x00000000

This just copies the previous entry for the Dual Scan III but changes
the Vendor ID (0x132b) and the Product ID (0x000a).

So far everything works fine, but there are some peculiarities. I've
posted a question about that separately.

A similar approach was actually documented (linked) in the Vuescan
Release Note. This line is needed only if you don't want to run vuscan
as root. You actually doesn't need to do anything except turning on SD4
first and running vuescan as root for vuescan to find the scanner. But
of course any Linux user knows using root for regular tasks is a bad
behavior.

So what's your question?

Xiaotian

 

[Leonard Evens]

A similar approach was actually documented (linked) in the Vuescan
Release Note. This line is needed only if you don't want to run vuscan
as root. You actually doesn't need to do anything except turning on SD4
first and running vuescan as root for vuescan to find the scanner. But
of course any Linux user knows using root for regular tasks is a bad
behavior.

So what's your question?

In some circumstances it asks me to remove the film, and close the door.
It then calibrates. It does this despite the fact that I've already
calibrated. But I think that may have stopped now that I've set the
scan resolution to 3200.

Also, when I start, before Vuescan loads, it asks me to shut the door,
despite the fact that it is shut. I don't think it makes any difference
whether I open and shut the door or just click okay. It may even make
no difference if I click cancel instead. In any case, Vuescan seems to
work differently in these respects than the Minolta software under XP.

Finally, I'm not sure, but Vuescan may be taking longer to focus than
the Minolta software does under XP.

 

[Leonard Evens]

A similar approach was actually documented (linked) in the Vuescan
Release Note. This line is needed only if you don't want to run vuscan
as root.

Right. I only needed it to be able for Vuescan to recognize the scanner
without my being root. As root I could run it without any changes.

If you look at the entry I posted, you will see that there is one other
difference from what is recommended at the libusb website. There is
says that all the other entries after the Product ID should be zero.
But the entry for the SD III has a 0x4000 there, so that is what I used.
I looked at the documentation in the file and that field is supposed
to be bcdDevice_lo. I don't know what that is for or if it makes any
difference.

 

[Pasi Savolainen]

Also, when I start, before Vuescan loads, it asks me to shut the door,
despite the fact that it is shut. I don't think it makes any difference
whether I open and shut the door or just click okay.

I think there's no way to detect the state of the door, so it's just a
reminder. Door should be closed for duration of scanner calibration.
At least for SD2 on linux calibration is performed one time when vuescan
is started.

 

[Xiaotian Sun]

In some circumstances it asks me to remove the film, and close the door.
It then calibrates. It does this despite the fact that I've already
calibrated. But I think that may have stopped now that I've set the
scan resolution to 3200.

I don't know the reason for this behavior, but I kind of remember
sometimes Minolta software asks me to do so too under Win XP.

Also, when I start, before Vuescan loads, it asks me to shut the door,
despite the fact that it is shut. I don't think it makes any difference
whether I open and shut the door or just click okay. It may even make
no difference if I click cancel instead. In any case, Vuescan seems to
work differently in these respects than the Minolta software under XP.

I guess it's just a reminder. I never tried to calibrate with door open
or cancel the calibration. But I kind of remember (you know, I have bad
memory ) that Minolta software can detect the status of the door.

Finally, I'm not sure, but Vuescan may be taking longer to focus than
the Minolta software does under XP.

Since you pointed this out, it seems so to me too. Then there are other
users on this group reporting vuescan won't properly focus their SD4
(under Windows?).

 

[Xiaotian Sun]

Right. I only needed it to be able for Vuescan to recognize the scanner
without my being root. As root I could run it without any changes.

If you look at the entry I posted, you will see that there is one other
difference from what is recommended at the libusb website. There is
says that all the other entries after the Product ID should be zero. But
the entry for the SD III has a 0x4000 there, so that is what I used. I
looked at the documentation in the file and that field is supposed to be
bcdDevice_lo. I don't know what that is for or if it makes any difference.

I don't know what this bcdDevice_lo does. But I set up following the
link and everything seems working fine. So I guess it makes no
difference.

 

[Xiaotian Sun]

I don't know what this bcdDevice_lo does. But I set up following the
link and everything seems working fine. So I guess it makes no difference.

After some extensive search, I fount at one webpage

http://lumumba.luc.ac.be/~cheezy/misc/unusual_devs.html

that bcdDevice_lo and bcdDevice_hi is for the range of the firmware
revision number, so multiple versions of the device can use the same
setup.