From - Thu Oct 30 07:23:54 1997 Path: news.mitre.org!blanket.mitre.org!agate!usenet.INS.CWRU.Edu!vncnews!HSNX.wco.com!hub.org!news.maxwell.syr.edu!ais.net!iagnet.net!usc!newshub.cts.com!newsfeed.cts.com!cmkrnl!jeh From: jeh@cmkrnl.com (Jamie Hanrahan) Newsgroups: comp.os.ms-windows.programmer.nt.kernel-mode Subject: Re: [Q] How to notify applicate when driver I/O Completed Message-ID: <1997Oct29.215728.8282@cmkrnl> Date: 29 Oct 97 21:57:28 PST References: <343e6059.82211512@news.connectnet.com> <3457ce41.106111230@news.connectnet.com> Organization: Kernel Mode Systems, San Diego, CA Lines: 27 In article <3457ce41.106111230@news.connectnet.com>, fdebaca@getntds.com writes: > On 16 Oct 1997 12:57:56 GMT, "dave porter" > wrote: > >>Why "inefficient"? > > I have to keep calling GetOverlappedResult to see if my I/O has > completed. I just want to be notified somehow, that my driver is > done. I've tried using WaitForSingleObject with a time value of > INFINITE but I never get controlled until the I/O completes. While > I'm down in WaitForSingleObject, my application is dead. No, the thread that's waiting is "dead". Simply create some other threads. > I also tried WriteFileEx but my callback function never got called. > Weird! I'll keep farting around with WriteFileEx. Your thread has to be in an alertable wait for the callback to be called. --- Jamie Hanrahan, Kernel Mode Systems, San Diego CA Internet: jeh@cmkrnl.com (JH645) CompuServe: 74140,2055 drivers, internals, networks, applications, and training for VMS and Windows NT NT driver FAQ, links, and other information: http://www.cmkrnl.com/ If you post a reply in news, please don't e-mail it too.