I have a network protocol driver which can be installed in windows 2000. I
am using the snetcfg.exe sample from the Windows 2000 DDK. There may be
cases where the driver will be upgraded or downgraded. For example, perhaps
a version of driver which is newer (thus having a newer .INF file) installed
on the system shall be uninstalled and then re-installed with an older inf
and driver. It seems as though windows 2000 has a mind of its own and will
not let this happen. Is there any way to delete the old files (.inf and
.pcf and .sys) and then tell windows 2000 to forget it ever had that
software installed. Then install the older driver. Windows 2000 seems to
retain the label of the newer driver even though it has been uninstalled.
Thanks,
Dominick Cafarelli
> I have a network protocol driver which can be installed in
windows 2000. I
am using the snetcfg.exe sample from the Windows 2000 DDK.
There may be
cases where the driver will be upgraded or downgraded. For
example, perhaps
a version of driver which is newer (thus having a newer .INF
file) installed
on the system shall be uninstalled and then re-installed with
an older inf
and driver. It seems as though windows 2000 has a mind of
its own and will
not let this happen. Is there any way to delete the old
files (.inf and
.pcf and .sys) and then tell windows 2000 to forget it ever had that
software installed. Then install the older driver. Windows
2000 seems to
retain the label of the newer driver even though it has been
uninstalled.
I don’t know if it’s “legal”, but I seem to be getting away with
deleting the OEM*.INF and OEM*.PNF files in the \WINNT\INF directory
(after uninstalling the device with the device manager).
Patrick Klos
Network Software Engineer
NuMega Lab / Compuware Corporation