From: gti4ever on
Oops,

there is a typo in my previous post, the correct DeviceIoControl code should
be:

DeviceIoControl((HANDLE) handle,
IOCTL_VENDOR_REQUEST_EX,
(LPVOID) vr, // Ptr to InBuffer
dwInSize, // Length of InBuffer
NULL, // Ptr to OutBuffer
0, // Length of OutBuffer
(LPDWORD) &nBytesRead,
0);



From: gti4ever on
Doron, you are the man! I checked my code and found I did forget to return
the proper size when calling WdfRequestCompleteWithInformation().

Thank you Doron and Don for the answers and helps, my new driver is up and
running now.

I am still curious to see how UMDF handles METHOD_NEITHER, but that is low
priority now.

G.

"Doron Holan [MSFT]" wrote:

> how are you calling WdfRequestComplete? are you passing the sizse of the
> structure as the information? are you passing the buffer here as an input
> or output buffer to the KMDF driver?
>
> d
>
> --
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>

From: Doron Holan [MSFT] on
method neither is not supported by UMDF at all

d

--

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


"gti4ever" <gti4ever(a)discussions.microsoft.com> wrote in message
news:C9C82D72-9A83-456E-9149-522A08859BFC(a)microsoft.com...
> Doron, you are the man! I checked my code and found I did forget to return
> the proper size when calling WdfRequestCompleteWithInformation().
>
> Thank you Doron and Don for the answers and helps, my new driver is up and
> running now.
>
> I am still curious to see how UMDF handles METHOD_NEITHER, but that is low
> priority now.
>
> G.
>
> "Doron Holan [MSFT]" wrote:
>
>> how are you calling WdfRequestComplete? are you passing the sizse of the
>> structure as the information? are you passing the buffer here as an
>> input
>> or output buffer to the KMDF driver?
>>
>> d
>>
>> --
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>
>