The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
I am working on a WDI model Windows sample driver.
Two different paths available in driver for WDI Oids & Standard 802.11 OIDs.
I have used IOCTL_NDIS_QUERY_GLOBAL_STATS in DeviceIOControl() API, whatever the custom non-WDI OID i have implemented in test app is not reaching to the driver.
Tried registering custom non-WDI OIDs with NDIS by following this
"call GenerateWdiGetAdapterCapabilities with WDI_GET_ADAPTER_CAPABILITIES_PARAMETERS::InterfaceAttributes::NonWdiOidsList"
Added Custom non-WDI oids implementation at standard 802.11 OID's place in WDI driver.
OID communication from test app to WDI driver is not working in this trial also.
Please share information if any way is there to implement the OID communication between test app & WDI driver.
|Upcoming OSR Seminars|
|OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!|
|Writing WDF Drivers||12 September 2022||Live, Online|
|Internals & Software Drivers||23 October 2022||Live, Online|
|Kernel Debugging||14 November 2022||Live, Online|
|Developing Minifilters||5 December 2022||Live, Online|