Installed wrong printer driver

[shadylane]

hi All,
I think I accidentally installed the win98 driver for a printer in Win2Kserver. Well, I get the error - "an error occurred during the installation of the device - cannot create a file when the file already exists". The printer is a pre-1999 model NEC printer available only in Japan - I think it's just a rebadged HP though. Anyway it only comes with Windows 98, NT4 & Win 3.1 drivers (already searched the net for W2K drivers to no avail).
I tried deleting all the related dlls from the system32 folder, but I got an access denied message for about 6 of them.
Anyone have a clue what's going on? If I can remove the present plug and play driver, does an NT4 driver usually suffice on W2k?
Cheers
Greg

 

[glman]

i guess you will find the solv in :
try to type regedt32.exe and try to search on printer you will find registery path for the printer you install it try to remove it ok

 

[Ger2111]

a 98 printer driver should work, if not try a search for WDM drivers.

 

[shadylane]

I don't seem to be having any luck here - I removed the registry key under printers and tried again with the same results - I get to the last screen of the add printer wizard where it says - "you have completed the printer set-up wizard successfully" - I hit Finish and then I get the same message that I mentioned in my first post. Also, I don't think I installed the Win98 driver first off now - when I tried specifying the Win98 driver in the setup, a message came up saying there was no information about my device in the inf file - so I guess the NT driver was autodetected when I tried installing it the first time.
Nothing about WDM drivers - it's a fairly obscure model. Although it uses HP cartridges so it could be rebadged.
Could it be because of the language of the OS? I'm installing it on an english system - before I upgraded I was using a Japanese win98 installation. I know there are issues with software like VBA and Visual Studio .NET with installing a certain language's version on a different language OS, but could this be a problem with a driver?!?