Manipulating ProtocolDriver UI in Network Connections

Hello All

Below is for 2k3/2k8 advanced servers OS’es.

  1. Could you point me to resources where I can find how to disable the (clicking which calls Protocol{Un}bindAdapater/Ex ) checkbox for a protocol driver bound to NIC.

  2. Is there an INF solution to above ?

  3. Also I do not see my protocol driver in non PnP devices when I do show hidden devices in device manager.
    I remember it was showing up initially, not anymore, Not sure what changes I made for that to happen etc…
    Anyways just want to know reason when it shows up and not
    (ofcourse it is installed and always shows up under network connections under the NICs it is bound to etc)

thanks

  1. Search for NCF_HIDDEN and NCF_NOT_USER_REMOVABLE in the WDK & MSDN.

  2. You NetTransport class INF entry has a value “Characteristics” in the NDI
    section which is made of NCF_xxx flag values.

  3. Why do you care (out of curiosity)? You will not be able to hide it from
    ‘regedit’ or the ‘sc’ command so hiding it from DevMgr seems to be (to me) a
    waste of time. As for a reason why, I have no idea.

Good Luck,
Dave Cattley
Consulting Engineer
Systems Software Development

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@yahoo.com
Sent: Monday, September 01, 2008 2:14 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Manipulating ProtocolDriver UI in Network Connections

Hello All

Below is for 2k3/2k8 advanced servers OS’es.

  1. Could you point me to resources where I can find how to disable the
    (clicking which calls Protocol{Un}bindAdapater/Ex ) checkbox for a protocol
    driver bound to NIC.

  2. Is there an INF solution to above ?

  3. Also I do not see my protocol driver in non PnP devices when I do show
    hidden devices in device manager.
    I remember it was showing up initially, not anymore, Not sure what changes I
    made for that to happen etc…
    Anyways just want to know reason when it shows up and not
    (ofcourse it is installed and always shows up under network connections
    under the NICs it is bound to etc)

thanks


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

1 Like

>Also I do not see my protocol driver in non PnP devices when I do show hidden devices

in device manager.

IIRC, everything related to protocol drivers is dealt with by InetCfg , rather than by Device Manager…

Anton Bassov

David/Anton
Thanks.

David

>3) Why do you care (out of curiosity)? You will not be able to hide it from
>‘regedit’ or the ‘sc’ command so hiding it from DevMgr seems to be (to me) a waste of time.
>As for a reason why, I have no idea.
Yes, i asked for myself just out of cuiousity.
Also I expect my test team might soon sometime ask why unlike TCP/IP it does not show up in DeviceManager etc.
When I first started (withe WDK protocol sample INF) it used to show up.
Now I see my characteristics=0, maybe that’s why?

My protocol driver is the lower-edge and upper-edge is KMDF driver, I do not want testers to think unchecking the protocl driver in NC uninstalls it etc. It only unbinds it.
I register the protocol with NDIS when the KMDF virtual bus driver is loaded Bus_EvtDeviceAdd (AddDevice). When the protocol is insyalled it binds
So just want for users/testers to not have option to muck around that NC check-box, Just install and uninstall and abstract away the internal binding/specifics etc for testers/end-users etc.

I changed Characteristics=0x28 ; NCF_HIDDEN | NCF_NOT_USER_REMOVABLE
Hopefully above disables the protocolDriver checkbox in NC rather than not showing up it at all.
Will test and update.

0x28 ; NCF_HIDDEN | NCF_NOT_USER_REMOVABLE
totally disabled the UI. I guess that is obvious.

Re-installing with individual bits (0x20, 0x8, 0x0) did not bring that back either.