I am using SetupCopyOEMINF, but it adds a new OEM*.INF to the
%systemroot%\inf folder and later the user is presented with a choice
of which driver to select for his device.

I am writing a windows installer custom action to update device drivers
from an original install. These are 1394 devices which can stack so
there may be several present and nonpresent devices.

I am using the DDK's toaster as an example.

I am using SetupCopyOEMINF, but it adds a new OEM*.INF to the
%systemroot%\inf folder and later the user is presented with a choice
of which driver to select for his device.

Later I find all the present or nonpresent devices, update the present
degvices using UpdateDriverForPlugAndPlayDevices and mark the
nonpresent devices for later update.

I have seen driver updaters that do not present the user with this
choice and am wondering if that was because the old OEM*.INF was
removed or overwritten or if there was some other technique for getting
the driver update to recognize the newer driver without asking the
user.

Thanks.
ARGold

ARGold wrote:
[..]
AFAIK, if there is some signed driver/INF file, Windows will
automatically choose this as the preferred driver to install.

If there is more than one signed driver/INF for the same device,
Windows automatically chooses the "latest and greatest".

Is it that all your drivers/INFs are not signed?

Stephan

At present they are not signed.

I didn't write them, but am responsible for this update.

What does it take to sign the drivers?

"ARGold" <argold@isdmg.com> wrote:
Time and money. Your driver is signed after it passes the WHQL validation
process.

Many uninstall/reinstall apps do seek out and remove the old OEM*.INF file,
and the corresponding PNF. That does leave dangling registry entries,
however.
--
- Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.