device driver installation application in XP and Win9x

I need to write an application to install my WDM device driver. The user
will insert installation media before he plugs in the device. So when he
plugs in the device for the first time, the device installation will be
completely "silent".

1. For Windows XP, I followed the instructions in DDK. I use
"SetupCopyOEMInf" function to copy my INF file to %windir%\inf foler, and a
PNF file is generated too. However, when I plug in the device, the "New
Device Found Dialog" still pops up. According to DDK, this should not happen
if the PNF file is alreday generated. Is this because my driver is not
digitally signed?

2. For Windows 98 SE, the "SetupCopyOEMInf" dosen't work. Is there a way to
write a device driver installation program for Win9x/Me to install the
driver before the device is plugged in?


Thanks,

Zhen

bburgin
Sat Nov 15 20:55:30 CST 2003

------=_NextPart_0001_53E0CC31
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

1. In Windows XP, if a driver is not signed, the driver package is elevated
to the rank of untrusted drivers. In such cases, the Found New Hardware
Wizard will always appear. See the DDK on how Windows XP selects a driver
for more information. This is different from your unsigned driver policy
(allow, block, warn). Also, if your driver is in the untrusted rank and
SetupApi finds another signed driver that is less of a perfect match, it
will favor the signed driver.

2. SetupCopyOEMInf is not supported in 98/ME.

HTH,

The testing process will ensure that your device works properly with the
Microsoft-supplied and Windows XP in-box RNDIS drivers.



Bryan S. Burgin
bburgin@microsoft.com

This posting is provided "AS IS" with no warranties, and confers no rights.

------=_NextPart_0001_53E0CC31
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20 1. In Windows XP, if a driver is not signed, the driver package is elevated to the rank of untrusted drivers. In such cases, the Found New Hardware Wizard will always appear. See the DDK on how Windows XP selects a driver for more information. This is different from your unsigned driver policy (allow, block, warn). Also, if your driver is in the untrusted rank and SetupApi finds another signed driver that is less of a perfect match, it will favor the signed driver.
\par
\par 2. SetupCopyOEMInf is not supported in 98/ME.
\par
\par HTH,
\par
\par The testing process will ensure that your device works properly with the Microsoft-supplied and Windows XP in-box RNDIS drivers.
\par
\par
\par
\par Bryan S. Burgin
\par bburgin@microsoft.com
\par
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par
\par }
------=_NextPart_0001_53E0CC31--

Zhen
Sun Nov 16 00:06:28 CST 2003

Thanks for your help.

Is there any way in 98/Me that I can write a "silent" device driver
installer program?

Zhen

""Bryan S. Burgin [MSFT]"" <bburgin@online.microsoft.com> wrote in message
news:OWvfZ0#qDHA.2464@cpmsftngxa06.phx.gbl...
> 1. In Windows XP, if a driver is not signed, the driver package is
elevated
> to the rank of untrusted drivers. In such cases, the Found New Hardware
> Wizard will always appear. See the DDK on how Windows XP selects a driver
> for more information. This is different from your unsigned driver policy
> (allow, block, warn). Also, if your driver is in the untrusted rank and
> SetupApi finds another signed driver that is less of a perfect match, it
> will favor the signed driver.
>
> 2. SetupCopyOEMInf is not supported in 98/ME.
>
> HTH,
>
> The testing process will ensure that your device works properly with the
> Microsoft-supplied and Windows XP in-box RNDIS drivers.
>
>
>
> Bryan S. Burgin
> bburgin@microsoft.com
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>