Re: Driver Verifier interferes with IoCallDriver ?
From: ernie (ernie_at_gmx.net)
Date: 02/02/05
- Next message: Michael Huang: "Accessing large physical memory (128M-1G)"
- Previous message: mridupawan.das_at_gmail.com: "enumeration fails second time"
- In reply to: Mark Roddy: "Re: Driver Verifier interferes with IoCallDriver ?"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 02 Feb 2005 15:14:38 +0100
Ok, I'll change my code accordingly.
thank you :)
Mark Roddy wrote:
>
> The value 4 would pass NT_SUCCESS(Status). Status values have three
> classes: error, warning, success. You should test success using the
> NT_SUCCESS macro. Note that STATUS_PENDING will also pass NT_SUCCESS, so
> you really have to test for STATUS_PENDING first, then success or error.
>
> ernie wrote:
>
>> Hallo,
>> I am verifying my driver with driver verifier, and I've encountered a
>> strange behaviour: I have two drivers which communicate through a well
>> know interface. The driver A prepares a new Irp, fills it with the
>> IRP_MN_QUERY_INTERFACE stuff, and then calls
>> IoCallDriver(B_DevObj, newIrp);
>>
>> The problem is: the dispatch routine in B always fills the interface
>> data and returns STATUS_SUCCESS, but when the Driver Verifier is
>> active the call to IoCallDriver() returns 0x00000004 instead of
>> STATUS_SUCCESS.
>>
>> Has anyone seen this problem before ?
>> What can be the cause ?
>>
>> Thank you.
- Next message: Michael Huang: "Accessing large physical memory (128M-1G)"
- Previous message: mridupawan.das_at_gmail.com: "enumeration fails second time"
- In reply to: Mark Roddy: "Re: Driver Verifier interferes with IoCallDriver ?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
