You will need to delete the old drivers first. HP introduced a new
registry
format with the new driver that is not compatible with the old driver.
Of
course this means you will need to disassociate the old driver from the
printers before deleting them (unless you only have one of these then you
can just delete the printer). We installed a driver for a device we do
not
have on campus, select all the printers that use the old driver, go to
Advance Tab, change the driver, okay, okay...... (we have a bunch of HP
printers around here). Now you get to delete the old driver. The
explorer
process holds onto some of the driver modules so you will need to log off
or
end the explorer.exe process, then restart it. Now delete the driver. I
remember stopping/starting the spooler on at least one of the print
servers.
Great the driver is now gone. All the incompatible registry settings are
gone. Add the updated driver. Multiselect the printers that are using
the
"marker driver", Advanced Tab, change to the new driver, Apply, open
Device
Setting, make the changes for installed options, Advance Tab, configure
the
printer defaults, OK, OK. On to the next printer........
have a beer.
--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
This posting is provided "AS IS" with no warranties, and confers no
rights.
I'm using a HP Laserjet 4350tn trying to install the PS driver. I also
tried
to load the LJ 4300 PS driver as I know that it is compatable with that
printer also with no luck. I've also tried to connect to an HP Deskjet
that
is shared with no luck. All have the same error "unable to install
<Printer
Name> windows 2000 or XP, Intel driver. Operation cannot be completed."
:
What make and model of printer and are you at SP2 level?
--
Cari (MS-MVP)
Windows Technologies - Printing & Imaging
http://www.coribright.com/windows
Hello,
I am getting the exact error message in Windows XP that is described
in
knowledge base article # 835272. However this article only applies
to
Windows
2000. Obviously this bug has carried over to Windows XP. Where can I
get
the
hotfix for this issue that applies to Windows XP?
Sincerely,
Kevin L