benswets
Newbie
RE Dimage Scan Dual IV on Windows XP Pro. My film scanner has chronic blinking light and won’t start. 5 years ago when I first bought this new scanner and installed it, this same problem occurred. The instructions warned me against unplugging it while green light blinked. I tried not to, however there was no way the scanner would turn off without unplugging. So I unplugged it. The Konica/Minolta staff told me on the phone that since I had unplugged it whilst blinking, the only way to fix it was to mail it to the factory. They sent it back to me in perfect working order. I presume it was the same unit.
Two years later the same problem occurred. I fixed it myself without mailing it in. I have no idea how I fixed it, but I did not remove any files from the registry. I performed an aggressive uninstall or an aggressive install or some such thing which I can not recall today. The scanner has worked well for years.
Today I have read many web viewers’ posts regarding their chronic blinking Dimage Film Scanners. Some posts recommend removing the scanner from the registry. I feel quite certain that today’s problem is the one I solved twice in the past – once via the factory.
I am writing to ask this question- Uninstalling from the registry would imply that the “poison” that foiles my scanner is within my tower. When the scanner was fully repaired by the factory, that implied that the “poison” was removed from my physical scanner more than from my hard drive. If the latter is true, and if today’s problem is the same as in the past, is there any good reason for me to uninstall my scanner from my computer’s registry, to solve my chronic blinking problem? Can uninstalling anything from the tower, registry or other-where’s, somehow remove bad files or “poison” from the actual scanner’s guts?
To restate my question, was my creative self-fashioned solution 3 years ago (upon the second advent of this frustrating blinking light) which was performed by some keyboard / USB cable / device manager / shut down dance (for example) -- was that solution in fact performed more on the hard drive than on the scanner itself? Or, is there a way that my keyboard / tower work actually was withdrawing unwanted files or otherwise healing the physical scanner itself more than healing the tower? Ie, this seems to be the same situation that the factory could fix by receiving my film scanner-unit via Federal Express. If so, is there value in exploring my registry?
I have, by the way, downloaded the new update from Konica-minolta’s web site. My computer will not accept it, claiming the original software is not installed, which it is for the fifth or sixth time, but will not start.
Another piece of evidence that implies the problem is in the physical scanner itself is this. I have two computers. One had the scanner plugged in and working fine a few days ago. I decided to do some scanning to my other computer’s hard drive yesterday, on which the scanner had worked well months ago. It was on this second computer that my blinking conflicts began. After much struggle to get it working on computer number two, I gave up and plugged the scanner back into computer number one where it had, a few days ago, been working fine. But the exact same symptoms now exist with the scanner plugged back into computer number one. Should I clean the registry in computer numb two?
Two years later the same problem occurred. I fixed it myself without mailing it in. I have no idea how I fixed it, but I did not remove any files from the registry. I performed an aggressive uninstall or an aggressive install or some such thing which I can not recall today. The scanner has worked well for years.
Today I have read many web viewers’ posts regarding their chronic blinking Dimage Film Scanners. Some posts recommend removing the scanner from the registry. I feel quite certain that today’s problem is the one I solved twice in the past – once via the factory.
I am writing to ask this question- Uninstalling from the registry would imply that the “poison” that foiles my scanner is within my tower. When the scanner was fully repaired by the factory, that implied that the “poison” was removed from my physical scanner more than from my hard drive. If the latter is true, and if today’s problem is the same as in the past, is there any good reason for me to uninstall my scanner from my computer’s registry, to solve my chronic blinking problem? Can uninstalling anything from the tower, registry or other-where’s, somehow remove bad files or “poison” from the actual scanner’s guts?
To restate my question, was my creative self-fashioned solution 3 years ago (upon the second advent of this frustrating blinking light) which was performed by some keyboard / USB cable / device manager / shut down dance (for example) -- was that solution in fact performed more on the hard drive than on the scanner itself? Or, is there a way that my keyboard / tower work actually was withdrawing unwanted files or otherwise healing the physical scanner itself more than healing the tower? Ie, this seems to be the same situation that the factory could fix by receiving my film scanner-unit via Federal Express. If so, is there value in exploring my registry?
I have, by the way, downloaded the new update from Konica-minolta’s web site. My computer will not accept it, claiming the original software is not installed, which it is for the fifth or sixth time, but will not start.
Another piece of evidence that implies the problem is in the physical scanner itself is this. I have two computers. One had the scanner plugged in and working fine a few days ago. I decided to do some scanning to my other computer’s hard drive yesterday, on which the scanner had worked well months ago. It was on this second computer that my blinking conflicts began. After much struggle to get it working on computer number two, I gave up and plugged the scanner back into computer number one where it had, a few days ago, been working fine. But the exact same symptoms now exist with the scanner plugged back into computer number one. Should I clean the registry in computer numb two?
Last edited:
