Have you tried to use devcon.exe to install virtual nic driver? I would do
that first to make sure you are not making any mistakes in your install app.

Here is another trick I use on Vista to make sure whether my INF is well
written. I try preinstalling the driver package using pnputil.exe (inbox
utility) and see if that runs sucsessfully.

If you have any errors in your INF, you will see the failure when you add
the package to the system. It's easier this way to differentiate whether the
problem is in adding the package or actualling in installing the device.

For example:

pnputil.exe -a a:\usbcam\USBCAM.INF -> Add package specified by
USBCAM.INF

pnputil.exe -i -a a:\usbcam\USBCAM.INF -> Add and install driver package

-Eliyas

What is the error code you see in the device manager?


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

Eliyas,

I do not exactly know how to answer you....

I do not see an "error" in the device manager... I get the following from
DiInstallService when trying to install programmatically:

bRet = (pDiInstallDevice)(NULL, hDevInfo, &DevInfoData,
&DrvInfoData, DIIDFLAG_INSTALLNULLDRIVER, FALSE);

bRet = 0 and GetLastError() = 0xe0000219

When I try to start the associated service - I get the following:
Error 1075: The dependency service does not exist or has been marked for
deletion...

Comments?

Lynda


The log states:
! dvi: Installing NULL driver!
! dvi: A NULL driver installation is not allowed for this
type of device!
!!! dvi: Cleaning up failed installation (e0000219)
!!! dvi: Default installer: failed!
!!! dvi: Error 0xe0000219: The installation failed because a
function driver was not specified for this device instance.
dvi: {DIF_INSTALLDEVICE - exit(0xe0000219)} 14:32:20.784
dvi: {DIF_DESTROYPRIVATEDATA} 14:32:20.799



"Eliyas Yakub [MSFT]" <eliyasy@online.microsoft.com> wrote in message
news:%23y86guO8HHA.5360@TK2MSFTNGP03.phx.gbl...

Here is another idea. There is a virtual ndis miniport sample in the WDK
called vnetmini. Try that out. If that one installs fine then find out the
difference between your INF and the sample inf. Next suggestion would be to
run chkinf utility from the WDK tools directory and see if that shows any
errors.

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

"Lynda Bowen" <lbowen02@harris.com> wrote in message
news:OfxNKVV8HHA.5504@TK2MSFTNGP02.phx.gbl...