| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 40414 | 2003-12-07 09:34:00 | Sudden Scanner s/w Failure - Any ideas? | Perry (4966) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 198120 | 2003-12-07 09:34:00 | I have a Microtek 4600 scanner that has suddenly stopped relating to my PC. I've reinstalled the scanner s/ware: no change. I have several programs that use the scanner, the result is always the same: Windows 98SE falls over! Fatal exception 0028:C002B21C VXD NTKERN(01) + 00009620. Even the scanner test utility that comes with said flatbed machine causes Windows to fall over. It's been OK for nearly two years - then bang! I have tried most of the 'usual' things, but, nothing seems to resolve the problem. Seems like a s/w file failure somewhere, but the resident Windows system file verifier says all is OK! I use the scanner frequently. The 'all-of-a-sudden' nature of the problem is perplexing. Does anyone have any clues, please? |
Perry (4966) | ||
| 198121 | 2003-12-07 10:34:00 | It certainly appears to be scanner specific from your description. That error does not appear to show up anywhere. You say you have "reinstalled the scanner s/ware". "Reinstallation" will not always replace system files if they already exist. Similarly the scanner specific files may not be verified by SFC either. You need to fully uninstall the scanner, disconnect it, reboot and reinstall it according to the manual. No guarantee it will fix it, but it would be the next logical step. While the message suggests its the main Windows kernal file erroring, its quite likely a scanner system file is calling it inappropriately. |
godfather (25) | ||
| 198122 | 2003-12-07 10:42:00 | Godfather has some good points, I would like to just suggest also that a visit to the manufacturer website maybe useful. There maybe updated drivers there | beama (111) | ||
| 198123 | 2003-12-07 10:48:00 | Beama raises a good point, is it possible a Windows Update has been applied in between "working" and "broken" states? Or any software added or updated? If so, driver updates may be in order. Otherwise nothing should have changed, and a corrupt driver would still be in the frame. |
godfather (25) | ||
| 198124 | 2003-12-08 20:46:00 | I've just come across the same problem with a freinds wee USB powered Canon scanner. Working great for months then bang! dead as a dodo. Communication tests failed, uninstalling & reinstalling drivers & software didn't fix it. I did some digging & found a "twain" removal utility on the manufacturers website, ran that, removed all software then installed the latest versions of drivers & software form the site. Now runs sweet as. Apparently an uninstall/reinstall of the software won't repair a corrupted twain driver. Might be worth a try. |
45South (4769) | ||
| 198125 | 2003-12-08 21:14:00 | files can get corrupted thru power failures uninstalling or installing other progs updates , not properly shutting down the PC etc Which is why it is important to keep a image or backup of your whole C: drive in perfect working order with the drivers software etc installed rthen its simply a matter of restoring the image takes me about 15 mins on my 98SE system using drive image 2002 . |
kiwibeat (304) | ||
| 198126 | 2003-12-10 03:10:00 | >Apparently an uninstall/reinstall of the software won't repair >a corrupted twain driver. Might be worth a try. Sounds very similar to my problem. The scanner "initialies" at boot up, and "initialises" again when a program that uses the scanner is run. However, once the SCAN button is pressed - it's all over! Back to the power-off button, scan disk @ startup, ad nauseum. Since the earlier comments and ansers, I have talked to Imaging Technology support and been right through the remove s/ware, h/ware, etc. then re-installed. No change. Somehow, I don't see how the lastest scanner s/ware version as a likely fix-up prospect. The corrupt Twain driver seems like the way to go. I'll check with Imaging Tech to see if they're got a remove driver utility. In response to some points: No significant "environment" changes, s/ware, h/ware install/uninstall, or the like were undertaken. At least none can be recalled. A big "thank you" to everyone who has proffered comments. |
Perry (4966) | ||
| 198127 | 2003-12-11 21:11:00 | The NZ Microtek people said that their scanner interface is different to Canon's, so the twain driver "fix" was not a likely solution. I was then told to download the latest version of their ScanWiz s/ware, dump all existing s/ware and h/ware, reboot with the USB cable disconnected, then plug it back in after Windows finished loading. And it worked. And I haven't the faintest idea why! So my scanner is now talking to my PC. No wonder computers frustrate the hell out of people! | Perry (4966) | ||
| 198128 | 2004-01-12 09:29:00 | Long time ago, I said that it worked. Well, it did, but not quite. The scanner and PC starting talking to one another, but the acquired image was garbled: more phone calls to Imaging Technology. Eventually, it was decided that the CCD was kaput. Yes - you guessed it, the scanner was a few months out of warranty. "Please send us $135 and we'll send you a replacement." And so it was. The new one communicates faster than the old one, but whether that's because of the hardware and/or the new software is a moot point. Thanks again to those who offered suggestions and ideas. My next question (which will be a separate thread when I get to it) will be about caller display s/ware, TAPI compliant modems, Telecom, and setting up a PC to monitor telephone calls and use the speakers to announce inwards calls. With my initial (h/ware, connections, etc) inquiries, it almost seemed as if I was asking folks about a slice of rock from Mars!?! |
Perry (4966) | ||
| 198129 | 2004-01-12 23:03:00 | I've almost given up on scanners and use a digital camera instead. | antmannz (28) | ||
| 1 2 | |||||