PC Review
Forums
Newsgroups
Hardware
Scanners
Polaroid SprintScan 35 Plus "unable to download microcode data" error
Forums
Newsgroups
Hardware
Scanners
Polaroid SprintScan 35 Plus "unable to download microcode data" error
![]() |
Polaroid SprintScan 35 Plus "unable to download microcode data" error |
|
|
Thread Tools | Rate Thread |
|
|
#1 |
|
Guest
Posts: n/a
|
"Hardware error: Unable to download microcode data."
This error message is persistent when I try to initiate Polacolor Insight. I have been using the SprintScan 35 Plus on Windows 2000 with Polacolor Insight for the last couple of years. The error message occurred while I was scanning a slide as usual. I had already scanned a number of slides during that session, had successfully previewed the slide, clicked the "scan" button and given the file a name. The slide holder moved down and the scanning progress window popped up as usual, but stopped at 1%. Eventually an error message appeared saying: "Hardware error: Unable to download microcode data. Please call Polaroid Technical Support for assistance." The scanner appears to be functioning physically: when I switch it on, the light comes on and the slide holder moves down and up, as normal. When I boot the pc the scanner is recognised as being at SCSI Id 4. I borrowed another SCSI card and cable, removed the original card but seated the new one in a different slot, reloaded the Adaptec driver and Windows popped up the "found new hardware: Polaroid SprintScan 35 Plus" window on rebooting, but the error message is still persistent on initiating Polacolor Insight. I have removed and reloaded Polacolor Insight as well as replacing the lamp, all to no avail. Does anyone have any ideas, or know a place in Cape Town, South Africa where I can take it for repairs? Thanks |
|
|
|
#2 |
|
Guest
Posts: n/a
|
Well, the first thing I try when a "Windows" system
misbehaves is ... Rebooting the complete system. Have you tried that? |
|
|
|
#3 |
|
Guest
Posts: n/a
|
"RSD99" <rsdwla.NOSPAM@gte.net> wrote in message news:<rdj2d.19428$%O5.11619@trnddc07>...
> Well, the first thing I try when a "Windows" system > misbehaves is ... Rebooting the complete system. > > Have you tried that? He already described what it does on boot, so I suspect he's tried that. Another thing to try may be to use Vuescan and see if that helps. It supports that scanner. Mike |
|
![]() |
|
| Thread Tools | |
| Rate This Thread | |
|
|

Main Page 

