What you have specified in the INF is the Device ID. This does not really
amount to a specification that the device must be root enumerated.
You get a root enumerated device by (in summary, for details look at devcon
sources):
- Creating a devnode under the root device.
- Telling PnP explicitly to select your driver as the driver for the
DevNode.
- Calling the Class Installer to make nice and install your driver on the
devnode.
So your Device ID could just as easily be SC_ETHERNET, *SC_ETHERNET,
FOOBAR\SC_ETHERNET, etc. Just as long as your device installer (like
devcon) creates the root enumerated devnode and forces it to be ‘matched’ to
your device id (whatever it is).
There are others whom undoubtly can give you a much more precise answer but
that is how I came to understand it.
Good Luck,
Dave Cattley
Consulting Engineer
Systems Software Development
(regards to my friends as sea change)
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@schange.com
Sent: Friday, July 13, 2007 5:38 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] How do I create a root devnode?
I want to create a root devnode. Do I do it this way?
%EthernetPortDesc%=EthernetPort_Inst,Root\SC_ETHERNET
in my models section.
Do I need something else? Do I need it somewhere else?
Is there any other reason why NDIS would not call my initialize routine?
For why, see http://www.osronline.com/showthread.cfm?link=113293
Andy
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer