none
NDIS 6.0 Filter Driver Sample - Basics RRS feed

  • Question

  • Hello,

    I'm very new to driver development. 
    I want to deploy, debug and understand the NDIS Filter driver sample. 

    I'm working with 
    OS: Windows 7 
    NDIS ver: NDIS 6.20
    WDK 8 integrated with Visual Studio 2012.

    I read the instruction at 
    http://code.msdn.microsoft.com/windowshardware/NDISLWFSYS-Sample-NDIS-60-42b76875#content 
    to build and install. Following the instructions I built the sample, prepared an installation directory and installed the driver.

    1. Could someone please tell me the next steps to see the working of the sample driver?

    2. I'm trying to install and debug on same computer. The video at 
    http://msdn.microsoft.com/en-us/library/windows/hardware/hh855052.aspx
    shows that the debugger should run on host computer and driver should be installed on target computer. Can I not do using one system? How do I see the kernel debugger in VS 2012?

    3. Right now, I don't want to modify the sample driver, I just want to learn how filter driver works, should I do anything about 'attaching' and 'detaching' the driver? 

    Thank you in Advance.
    Thursday, November 29, 2012 6:28 AM

Answers

  • As Doron said, you'll really want at least two computers to do kernel development.  Anything fewer than that is a terrific waste of your time, since each error means the computer bugchecks and reboots.

    Depending on what kind of networking you're doing, you may need more than two computers (e.g., client + server).  Many of the tests in NDISTest require a minimum of two test machines.

    Once you install the WDK on top of VS 2012, the kernel debugger will be another debug transport for you to use.  There are some great introduction videos from BUILD, like these: 

    http://channel9.msdn.com/Events/Build/BUILD2011/HW-907C 

    http://channel9.msdn.com/Events/Build/BUILD2011/HW-235T

    Thursday, November 29, 2012 8:39 PM

All replies

  • You need a separate machine to install and deploy to.

    d -- This posting is provided "AS IS" with no warranties, and confers no rights.

    Thursday, November 29, 2012 7:58 AM
  • As Doron said, you'll really want at least two computers to do kernel development.  Anything fewer than that is a terrific waste of your time, since each error means the computer bugchecks and reboots.

    Depending on what kind of networking you're doing, you may need more than two computers (e.g., client + server).  Many of the tests in NDISTest require a minimum of two test machines.

    Once you install the WDK on top of VS 2012, the kernel debugger will be another debug transport for you to use.  There are some great introduction videos from BUILD, like these: 

    http://channel9.msdn.com/Events/Build/BUILD2011/HW-907C 

    http://channel9.msdn.com/Events/Build/BUILD2011/HW-235T

    Thursday, November 29, 2012 8:39 PM
  • I've not used VS2012 yet for driver work so I hope you can still do this.

    I tend to use a Virtual Machine on my development PC so I only have to use one device. The PC runs the debugger, the VM has the OS under test running the driver. Then when your development driver bombs its only the VM that you need to restart. If you've done something really bad and your VM keeps rebooting you can attch the VHD to your base PC and remove your driver.

    Monday, December 3, 2012 9:01 AM