Prev: Unable to Pend IRP on ISO Read (IN) pipe
Next: read from virtual comport
From: turambar n-nospam on 28 Apr 2008 08:14
"Don Burn" wrote:

> Your DLL is using Win32 calls, you cannot use these in the kernel. You
> need to redesign things to not use functions not supported in the kernel.
>
>
Can I write instead my driver in user-mode ? or at least a part in user-mode
that can have access to my dll, so my driver will inderectly have access to
Win32 calls that can make my dll work ?
From: Don Burn on 28 Apr 2008 08:23
You can create a helper application that sends IOCTL's down to the driver,
which pends them and then releases them with a request for the DLL to do
something this is known as an inverted call. What does your DLL do is the
real question?


--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply



"turambar <n-nospam(a)free.fr>"
<turambarnnospamfreefr(a)discussions.microsoft.com> wrote in message
news:972845DB-7A56-4AEE-A882-0B8DF4069D17(a)microsoft.com...
> "Don Burn" wrote:
>
>> Your DLL is using Win32 calls, you cannot use these in the kernel. You
>> need to redesign things to not use functions not supported in the kernel.
>>
>>
> Can I write instead my driver in user-mode ? or at least a part in
> user-mode
> that can have access to my dll, so my driver will inderectly have access
> to
> Win32 calls that can make my dll work ?


 | 
Pages: 1
Prev: Unable to Pend IRP on ISO Read (IN) pipe
Next: read from virtual comport