C
charlie
It is credible: bizarre happens.
If there were only one kind of printer, or at least, only one kind of
interface to a printer, and if there were only one kind of computer
hardware, or at least, only one kind of hardware interface to the
peripherals, and if there were only one operating system, or at least
only one kind of software interface to peripherals, it might not be
problematic. And I left out other considerations, especially the ones I
haven't thought of or don't know about...
Microsoft is in the not so enviable position of herding cats, IMO.
If the printer in question is connected via USB - -
Determine which USB port and controller are used.
Make sure that it's a different controller than that used
by the keyboard and mouse. (Unless you happen to be using a P/S 2 mouse
and keyboard.
The real problem may be to identify which port and controller is used.
One some systems there may be multiple drivers for the same controller,
standard and enhanced.
Basically, the idea is to shutdown the port and controller, and if
necessary, disconnect the drivers for that particular controller.
That should break any of the existing software paths in the drivers to
the USB controller, the port, and the printer driver(s).
With the printer (and drivers) disconnected from the USB port and the
P/C, shutdown and reboot.
What usually happens next is that windows re-installs the USB controller
and port drivers automatically. If not,
You may have to use control panel, device manager, etc. to enable the
controller and ports, and install the USB drivers, etc.
Assuming that this works, it's time to shutdown, and restart.
Then, usually, install the printer driver and the printer.
This is a legacy method. I haven't had to use it with win 7 and my
current printers and P/C. I did use it last with an HP laptop running
Vista. Older printers and legacy based drivers (updated, sort of) for
win 7 may benefit from this method.
Anyway - -