Dispatch routine completing IRP

Discussion in 'Windows Vista Drivers' started by Drew Wurfel, Jul 25, 2005.

  1. Drew Wurfel

    Drew Wurfel Guest

    According to msdn, a driver should be completing various IRPs in its
    dispatch routine. If the major code is not not implemented, our dispatch
    routine sets the status to STATUS_NOT_IMPLEMENTED and completes it, but the
    driver verifier utility sends in IRPS with valid major codes and the invalid
    minor code(0xFF) to test the control paths. Is the minor code(0xFF) the
    only reserved one? what if we wanted to use our own custom minor codes(do we
    have to stay away from 0xFF? Should we be checking all the valid minor codes
    for every major code each time before changing any data in it?
    Drew Wurfel, Jul 25, 2005
    1. Advertisements

  2. Drew Wurfel

    Don Burn Guest

    First not all IRP's care about minor codes, second the minor codes are
    reserved for Microsoft, don't try claiming one. The verifier does send down
    FF for IRP_MJ_PNP, you should not be completing those but instead passing
    them to the lower driver, just like any other minor code you don't
    Don Burn, Jul 25, 2005
    1. Advertisements

  3. it also does this for WMI and power irps. the rules for all 3 types of
    these irps is if you don't support it, you leave it unmodified and send it
    down teh stack.

    Doron Holan [MS], Jul 26, 2005
    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.