KMDF's NONPNP sample question.

Discussion in 'Windows Vista Drivers' started by Kim, Heejune, Aug 30, 2006.

  1. Kim, Heejune

    Kim, Heejune Guest

    Hello.

    when I was building and debugging with NONPNP sample from KMDF, I found a
    little bit odd behavior. The NONPNP sample driver defined its symbolic links
    name as "L"\\DosDevices\\NONPNP". So I thought I should use device name
    "\\\\.\\NONPNP" to open nonpnp sample driver from application, but the idea
    was wrong.

    Why does nonpnp sample (user mode) application open its driver with
    "\\\\.\\NONPNP\\nonpnpsamp.log", not "\\\\.\\NONPNP"
    Did I miss something?

    I tried to use TraceView to debug, but I wasn't able to choose any
    Provider(PDB file, CTL file...) from Provider Control GUID Setup window.

    Thanks.
     
    Kim, Heejune, Aug 30, 2006
    #1
    1. Advertisements

  2. Kim, Heejune

    Don Burn Guest

    Look at what the sample driver does, it utilizes the file name to open a
    file based with ZwCreateFile. One of the purposes of this sample is to show
    how driver namespaces work.

    Don Burn (MVP, Windows DDK)
    Windows 2k/XP/2k3 Filesystem and Driver Consulting
    http://www.windrvr.com
    Remove StopSpam from the email to reply
     
    Don Burn, Aug 30, 2006
    #2
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.