Roadmap for Developing NDIS Intermediate Drivers
To create a Network Driver Interface Specification (NDIS) intermediate driver package, follow these steps:
Step 1: Learn about Windows architecture and drivers.
You must understand the fundamentals of how drivers work in Windows operating systems. Knowing the fundamentals will help you make appropriate design decisions and let you streamline your development process. For more information about driver fundamentals, see Concepts for all driver developers.
Step 2: Learn about NDIS.
For general information about NDIS and NDIS drivers, see the following topics:
Step 3: Determine additional Windows driver design decisions.
Step 4: Learn about the Windows driver build, test, and debug processes and tools.
Building a driver differs from building a user-mode application. For more information about Windows driver build, debug, and test processes, driver signing, and Windows Hardware Certification Kit (HCK) testing, see Building, Debugging, and Testing Drivers. For more information about building, testing, verifying, and debugging tools, see Driver Development Tools.
- Step 5: Read the intermediate driver, miniport driver, and protocol driver introduction topics.
Step 6: Read the writing intermediate drivers section.
Intermediate drivers use a combination of protocol driver and miniport driver interfaces in addition to some intermediate driver specific interfaces. As an option, you can also read the miniport driver and protocol driver design guides.
Step 8: Develop (or port), build, test, and debug your NDIS driver.
See the porting guides if you are porting an existing driver:
- Porting NDIS 5.x Drivers to NDIS 6.0
- Porting NDIS 6.x Drivers to NDIS 6.20
- Porting NDIS 6.x Drivers to NDIS 6.30
For more information about iterative building, testing, and debugging, see Overview of Build, Debug, and Test Process. This process will help ensure that you build a driver that works.
Step 9: Create a driver package for your driver.
Step 10: Sign and distribute your driver.
The final step is to sign (optional) and distribute the driver. If your driver meets the quality standards that are defined for the Windows Hardware Certification Kit (HCK), you can distribute it through the Microsoft Windows Update program. For more information about how to distribute a driver, see Distributing a Driver.
These are the basic steps. Additional steps might be necessary based on the needs of your individual driver.