Prev: difference between \\\\.\\%c:" & "\\\\.\\PHYSICALDRIVE%d"
Next: installing DLL file in system32 folder
From: Uv on 8 May 2008 04:16
You've got cause and effect reversed, I think:
The completion routine needs to signal the event on which KeWait is
waiting.
There is no code internal to Windows that will signal the event for
you.

You need to set the completion routine, set the context to pass to it
(probably a pointer to an on-stack event) and write the completion
routine to signal the event.
Only then will KeWait ever wake up.

On May 7, 4:57 am, qwert <qw...(a)discussions.microsoft.com> wrote:
> I used IoSkipCurrentIrpStackLocation.
> I thought that I need not provide completion routine.
> I wnated to implement synchronous call only.
> completion routine gets executed when the kewait.... gets signalled,if I am
> right.
> but here the signalling itself is not happening.
>
> "Don Burn" wrote:
> > Where are you setting up a completion routine to signal the event? This
> > looks like half of a common implementation of a sychronous call to a lower
> > driver.
>
> > --
> > 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
>
First  |  Prev  | 
Pages: 1 2
Prev: difference between \\\\.\\%c:" & "\\\\.\\PHYSICALDRIVE%d"
Next: installing DLL file in system32 folder