RE: re-installing test driver (NDSI 5.0 Miniport - Win 20- 00)

Just delete the oem?.?nf files first, then update the driver. It should
overwrite your binary, at least it does when I do this to my ATAPI SCSI
miniport. I don’t know the syntax, but you can have your inf specifically
copy itself to a name you assign, instead of the oem? default the OS uses.

The behavior of ignoring the date when it isn’t signed is by design, and has
been discussed here before. I won’t pass on my personal view of that
particular design decision for a developer. :frowning:

Phil

-----Original Message-----
From: vikas [mailto:xxxxx@yahoo.com]
Sent: Monday, April 30, 2001 1:11 PM
To: NT Developers Interest List
Subject: [ntdev] re-installing test driver (NDSI 5.0 Miniport - Win
2000)

Hi,

I am writing a miniport NIC driver (NDIS 5.0) for Win 2000. I have to
frequently re-install it on the target m/c. I tried using ‘update driver’
from ‘Device Manager->Network adapters->(card properties)’. Win2K does not
use the latest INF file that I provide in the install disk. Instead it
always uses the ‘oem?.inf / oem?.pnf’ files in ‘winnt\inf’ that it creates
when the driver was first installed. So I have to uninstall the driver,
delete the oem?.?nf files and then reinstall the driver.

Is there any way I can reinstall the driver using the latest INF from the
install disk, without all this work around?

NOTE: Since my driver not signed, Win2k seems to ignore the date in the
‘DriverVer’ entry in the install section of INF. And it always considers its
own copy of INF to be the latest.

tia,
vikas


You are currently subscribed to ntdev as: xxxxx@intel.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