When I uninstall my PCI Ndis device from Device Mangler on Windows 2000,
the driver is left in %WINDIR%\system32\drivers and a copy of the
install file is left in %WINDIR%\inf\oem0.inf.
From a comment in the DDK Chapter 6 “Writing a Custom Device Installation
Application” which says - "In the uninstall program, do not delete the
installed driver files off of (sic) the system, even if their hardware has
been removed. " one can infer that this is intended behaviour.
When I scan for hardware changes the Found New Hardware Wizard
‘search for a suitable driver’ option finds the oem0.inf, even
if I specify a location. This becomes a problem when I change the
.inf file to add some registry settings, etc.
How do I coerce windows into seeing the new .inf?
Can I do anything automated, or do I have to manually delete oem0.inf?
This would be a major problem on a system with other oem?.inf files,
as you need to decide which to delete and which to keep.
Have I missed something? I can find no advice in the DDK.
Has anyone any idea how one should perform an upgrade?
Regards and TIA,
Evan
xxxxx@nsine.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
During development and testing, you can manually find the oem?.* and delete
it. In the real production environment, when you make changes to your driver
or INF file, you advise the user to use the Update driver option in the
Driver tab of the device manager to update to new package. In whistler this
option has been moved to the right-click menu.
-----Original Message-----
From: xxxxx@nsine.com [mailto:xxxxx@nsine.com]
Sent: Monday, March 05, 2001 5:01 PM
To: NT Developers Interest List
Subject: [ntdev] Update problem with .inf
When I uninstall my PCI Ndis device from Device Mangler on Windows 2000,
the driver is left in %WINDIR%\system32\drivers and a copy of the
install file is left in %WINDIR%\inf\oem0.inf.
From a comment in the DDK Chapter 6 “Writing a Custom Device Installation
Application” which says - "In the uninstall program, do not delete the
installed driver files off of (sic) the system, even if their hardware has
been removed. " one can infer that this is intended behaviour.
When I scan for hardware changes the Found New Hardware Wizard
‘search for a suitable driver’ option finds the oem0.inf, even
if I specify a location. This becomes a problem when I change the
.inf file to add some registry settings, etc.
How do I coerce windows into seeing the new .inf?
Can I do anything automated, or do I have to manually delete oem0.inf?
This would be a major problem on a system with other oem?.inf files,
as you need to decide which to delete and which to keep.
Have I missed something? I can find no advice in the DDK.
Has anyone any idea how one should perform an upgrade?
Regards and TIA,
Evan
xxxxx@nsine.com
You are currently subscribed to ntdev as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
However, the update driver option in the driver tab only does driver
update, and it will not change the property values that you find in the
Advance Tab. For example, the oem?.inf has the property name Promiscuous
Support which set it to NO for NIC,and my revised INF file want to set this
field to YES. However, choose update driver will not change this field,
and I am struggling to figure this out too. Please help!!
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com