At work, I was trying to install the Canon ColorPass 900 on a network by itself.
We couldn't find the win2k drivers for it but we had the old win95 version on cd. Being the smart people that we were, we decided to go through the 'add printer' setup, choose network, located the printer on the network and pointed the 95 driver on the cd as the driver to install. The install went halfway before asking for non-existing .dll files which meant we had to abort.
A few hours later we found the 2k drivers for that printer and we assumed since the previous install didn't complete, it wouldn't be stored in the registry.
But upon going through the same procedure to add a printer, I noticed that it would automatically revert to the win95 driver and install by itself. Of course it wouldn't work so it would prompt us again for those non-existing .dll files and then crap out.
I even tried substituting those .dll files with fake ones just so it would at least finish the install and hopefully i could just update the driver through the properties, that still didn't work.
Basically we can't get the 'add printer' wizard to prompt us again to locate a proper driver without it automatically reverting to the corrupted driver somewhere stored in the registry.
My question is, how can I find/remove this corrupted driver or the path that it points to in the registry without having to reinstall the whole operating system. Please advise, thanks.
daniel
Facebook
Twitter