> I was expecting the query for OID_GEN_SUPPORTED_GUIDS. But it does not happen.
It does happen. But remember that your filter is detached when the miniport is disabled. When the miniport is re-enabled, the query happens before your filter is reattached. So the sequence is:
- Begin disable miniport
- Detach LWF
- Finish disable miniport
- Begin enable miniport
- Query OID_GEN_SUPPORTED_GUIDS
- Attach LWF
- Finish enable miniport
Fortunately, we have no WHQL requirement that LWFs use WMI. (I’m sure it would come as a great surprise to all the other LWFs in the world if we did). LWFs can pretty much do whatever they want, including IOCTLs. I’d be interested to know which source gave you the impression that LWFs are required to use WMI.
BTW, if you are completely wedded to the idea of WMI, you can always create your own device object and implement IRP_MJ_SYSTEM_CONTROL yourself. NDIS doesn’t do anything *magic* that you can’t do yourself. But frankly that’s a crazy amount of work for almost no gain.
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of vaishali palkar
Sent: Friday, February 18, 2011 10:00 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] OID_GEN_SUPPORTED_GUIDS and LWF
If I?use IOCTLs , because WMI is not working , will I?have any problems with whql certification of my driver ?
?
Thanks
Vaishali
?
From: xxxxx@hotmail.com
To: xxxxx@lists.osr.com
Subject: RE: [ntdev] OID_GEN_SUPPORTED_GUIDS and LWF
Date: Fri, 18 Feb 2011 17:19:22 +0000
Jeffrey ,
?
I have a question.
If?after attaching the filter , I?disable/enable underneath Miniport (NIC) driver , I was expecting the query for OID_GEN_SUPPORTED_GUIDS.
But it does not happen.
In this case , NDIS should query the miniport , right ?
?
Thanks
Vaishali
?
From: xxxxx@microsoft.com
To: xxxxx@lists.osr.com
Subject: RE: [ntdev] OID_GEN_SUPPORTED_GUIDS and LWF
Date: Fri, 18 Feb 2011 04:06:33 +0000
This won’t work reliably. Filter drivers aren’t guaranteed to receive OID_GEN_SUPPORTED_GUIDS.
The problem is that NDIS can issue OID_GEN_SUPPORTED_GUIDS to the miniport before your filter is attached. Once NDIS has gotten the custom GUID list, NDIS caches it and doesn’t requery when a new filter attaches. That explains the intermittent behavior you see – there’s basically a race between WMI registration and attaching your filter.
Unfortunately, I can’t think of any way for your LWF to install its custom GUIDs. Sorry.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@hotmail.com
Sent: Thursday, February 17, 2011 3:41 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] OID_GEN_SUPPORTED_GUIDS and LWF
When I install my lwf driver on windows 7 , I do not get OID_GEN_SUPPORTED_GUIDS.
But if I restart the machine , the stack queries for OID_GEN_SUPPORTED_GUIDS.
It is the same driver.In filterrestart , I am modifying the supported oid list for custom oids.
Does anybody face this problem before ? I am trying to implement WMI in lwf driver.
I still do not know whether it is possible or not (without rebooting the machine)
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
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
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
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