Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results
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/
The documentation I've found discourages use of CFH/Reset starting in 6.83, but doesn't recommend any replacement strategy.
If I need to reset my miniport driver due to an underlying hardware condition how do I tell NDIS that something is wrong and I need reset? Do I need to to maintain separate implementations based on NDIS version or is there a preferred single solution?
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 | 7 Dec 2020 | LIVE ONLINE |
Internals & Software Drivers | 25 Jan 2021 | LIVE ONLINE |
Developing Minifilters | 8 March 2021 | LIVE ONLINE |
Comments
Call NdisMResetMiniport, if you can repair the problem. If you can't repair the problem, you can coordinate with the bus driver to get a surprise removal. The details depend on the bus. For example, USB provides IOCTL_INTERNAL_USB_CYCLE_PORT (which you'd use only as a last resort, after resetting the pipe fails).