I tried all these ids’s. It does not install through DevCon
Can anyone tell me which (psuedo) ID I should use or what ID I should use so that I can install my protocol driver from cmd-line without going to network-connections etc.
For the same INF, going to net-connections and installing protocol, works.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-303706- xxxxx@lists.osr.com] On Behalf Of xxxxx@yahoo.com
Sent: Friday, October 19, 2007 9:48 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Using Devcon for installing a protocol driver
All
My stack contains a root enumerated virtual driver.
For that I am able to use DevCon to do the install.
But for my protocol driver I am not able to use it. When I do “devcon
hwdis *”.
It shows below for my protocol driver
ROOT\LEGACY_MYPROT\0000
Name: My Protocol Driver
No hardware/compatible ID’s available for this device.
My INF looks like below
[version]
Class = NetTrans
…
I tried all these ids’s. It does not install through DevCon
Can anyone tell me which (psuedo) ID I should use or what ID I should
use so that I can install my protocol driver from cmd-line without
going to network-connections etc.
For the same INF, going to net-connections and installing protocol,
works.