UpdateDriverForPlugAndPlayDevices does not call AddDevice in Windows 2000

Using the UpdateDriverForPlugAndPlayDevices appears to work fine for the
installation of an initial multifunction device in Windows 2000. However,
when used to install subsequent devices, there is no call made to may
AddDevice function. As a result, when my DIF_NEWDEVICEWIZARD_FINISHINSTALL
function attempts to pass it's information to my driver, there is not
extension into which the driver can store it. This is failure to call my
AddDevice function for subsequent devices is true regardless of whether I
use the INSTALLFLAG_FORCE or not.

Does anyone know why UpdateDriverForPlugAndPlayDevices fails to call my
AddDevice function in Windows 2000 but works fine in Windows XP and 2003
Server?

Eliyas
Wed Feb 04 11:41:16 CST 2004

It seems to me that subsequent devices are not installed for some reason.
Does UpdateDriverForPlugAndPlayDevices return any error? Why don't you turn
on verbose tracing in setupapi and also in PNP manager and see what's going
on?

ed nt!PnpEnumDebugLevel 2


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




"Del Fredricks" <im.sick.of.spam@ask.i.might.tell> wrote in message
news:e6ZuBxm6DHA.2488@TK2MSFTNGP09.phx.gbl...
>
> Using the UpdateDriverForPlugAndPlayDevices appears to work fine for the
> installation of an initial multifunction device in Windows 2000. However,
> when used to install subsequent devices, there is no call made to may
> AddDevice function. As a result, when my
DIF_NEWDEVICEWIZARD_FINISHINSTALL
> function attempts to pass it's information to my driver, there is not
> extension into which the driver can store it. This is failure to call my
> AddDevice function for subsequent devices is true regardless of whether I
> use the INSTALLFLAG_FORCE or not.
>
> Does anyone know why UpdateDriverForPlugAndPlayDevices fails to call my
> AddDevice function in Windows 2000 but works fine in Windows XP and 2003
> Server?
>
>