Try the following:
Windows 98
In Windows 98, the .INF file is copied to the Windows\Inf directory. After
the initial installation of a device, the information from the .INF file is
added to a driver information database. This database is also found in
Windows\INF as “drvdata.bin” and “drividx.bin”. After the initial
installation, the actual .INF files are not used again unless the device has
been uninstalled (not just unplugged).
Because of this, just deleting, moving, or renaming an INF isn’t enough to
remove it from the Device Manager’s database. So, in addition to removing
the old .INF files, you should delete or rename the driver information
databases (drvdata.bin, drvidx.bin).
The next time you reboot, any references to the unwanted INF file(s) will be
gone and Windows will rebuild any information it needs.
Windows 2000
Windows 2000 doesn’t have a monolithic driver information database. Instead
it creates binary versions of each .INF it uses. These are named the same
as the .INF file, but with a .PNF extension and are kept in the same
WINNT\INF directory. However, the names used in the WINNT\INF directory may
not be the same as the original name of the INF file. Instead the files may
have a new name such as OEMXXX.INF or OEMXXX.PNF.
After uninstalling the device, you should remove or rename any .INF files
that have the same VID/PID as your device and the corresponding .PNF files
in the WINNT\INF directory.
The next time you reboot, any references to the unwanted INF file(s) will be
gone and Windows will rebuild any information it needs.
The next time you install the device, Windows will not find the VID/PID in
its database and will prompt you for the .INF file. It will then copy it to
the INF directory and update its database and continue with the
installation.
See Microsoft’s knowledge base article Q139206, “Hardware List Not Updated
After Installing New .inf File”, for details.
Marc Reinig
System Solutions
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of disasm _
Sent: Friday, May 11, 2001 12:47 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Inf File Problems
I have followed your directions, but it did not seem to have any effect. It
still says that the Win98 driver is the recommended driver. Is there
anything else I can do?
$Windows NT$ NT-based operating systems
$Windows 95$ Windows 9x/Me
$Chicago$ All Windows operating systems
So, if you want a Win 95, Win 98 or Win ME INF that will not be used by Win
2K then use $Windows 95$.
Use $WINDOWS NT$ for your Win 2K only INF.
Use $Chicago$ for a universal INF.
-----Original Message-----
[mailto:xxxxx@lists.osr.com]On Behalf Of disasm _
To: NT Developers Interest List
Subject: [ntdev] Inf File Problems
I have two separate drivers for my device. One for Win2k and the other for
Win98. The problem is that when I plug in the device for the first time on
a
Win2k machine it searches the disk for drivers and tries to use the Win98
driver by default even though the Signature=“$CHICAGO”. On Win98 (actually
WinME) after it finishes searching it pops up a dialog box with all the
compatible drivers that it found. But it lists the Win2k driver first in
the
list and so all the end-users just install the first one listed. What can I
do about this? I suspect that it might be something with the .inf file but
I
have reviewed it and can’t find anything wrong.
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