Interesting Scan Dual III/VueScan Problem

[Charles Kinghorn]

This problem comes and goes and can be very frustrating (as, I
suspect, are the other Scan Dual III problems described in this news
group).

After doing a number of scans (it can vary from one up to ten in my
experience), VueScan and the Scan Dual III simply stops scanning (it
does not lock up). It happens as follows:

1. Preview is normal.
2. Cropping is normal.
3. The scan step shows the focusing, a short busy indication, and
then, after a pause, the final dimensions and size of the scan. BUT IT
DOES NOT SCAN (OR SAVE).

As I said, it does not lock up and I can continue to try to fix the
problem. Once the condition occurs, it continues for other scans. (I
also occasionally get a lockup, but that is not my current issue.)

I have tried a number of procedures which appear to work at some times
but not others: recalibration, reloading default settings, deleting
the .ini file, deleting the .sd3 file, rebooting, increasing the
allocated memory, deleting other running programs. I am currently
leaving the scanner on all the time, even though Minolta recommends
turning it off when not in use, in the case the problem has to do with
some internal switch expanding and contracting (a very long shot).
There is something very finicky in how VueScan and the scanner talk to
each other. Or in my setup.

I am using an Athlon 1.3GHz with 512 MB memory and Win2K. I have an
Adaptec DuoConnect 3020 card as my USB 2.0 connection (card
recommended by Minolta). I could go to USB 1.1 but would like not to.

I like the Scan Dual III but it can get very frustrating. Judging from
postings in this news group, it has been problematic for others. I
know Ed Hamrick recommends it as an inexpensive film scanner; but it
seems to have caused him some problems as well, since his list of
VueScan changes includes 12 references to this particular scanner.

Any help or suggestions would be much appreciated.

Charles Kinghorn

 

[David C Miers]

I have gotten past this particular issue before by simply changing the input
resolution. As I recall I switched it from Auto at the time to a specific
res. I didn't even have to restart vuescan at the time.

 

[Charles Kinghorn]

Thanks, David, but I always specify the resolution as 2820 when I
scan. But next time it happens, I'll go to Auto, try the scan, and
then reset to 2820. This might do the trick.

Charles

 

[tipicanu]

I have this scanner and use it frequently, and have never had
anything remotely related to this problem (PC version of
Vuescan, winXPpro sp1). Perhaps I have not encountered the
combination of settings that would cause it. Perhaps it is
Windows version related?

Hope you figure it out. Good luck.
-Jeff

 

[David C Miers]

I had the same problems and worse on xp and 2000. I'm wondering if there is
a common denominator with chipsets and processor types. One of the things I
recently did just before vuescan started working again is update my via 4in1
drivers. I wonder how many of us having problems are running AMD vs. Intel
processors. and via chipsets or otherwise vs intel. I have an AMD 2000XP
Athlon with via chipset...I'd have to look up exactly which model
chipset...KT 3 or KT333...something like that. I have an MSI motherboard.
I bought the parts and assembled this machine myself. Or couild it be video
card common? vidieo drivers are one of the most common conflict items