home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.programmer.misc
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!wupost!eclnews!swarm.wustl.edu!wilcox
- From: wilcox@swarm.wustl.edu (Don Wilcox)
- Subject: Re: Detecting when a WinExec'd prg term
- Message-ID: <1992Jul23.145405.28920@wuecl.wustl.edu>
- Sender: usenet@wuecl.wustl.edu (Usenet Administrator)
- Nntp-Posting-Host: swarm
- Organization: Washington University in St. Louis, MO
- References: <18014.2a62f9a7@levels.unisa.edu.> <1668700005@igc.org>
- Date: Thu, 23 Jul 1992 14:54:05 GMT
- Lines: 26
-
- In article <1668700005@igc.org> Jeff Dean <jeff@igc.org> writes:
- >
- >>What do you mean unreliable? Do you mean that if I have a notifyregister
- >>callback I don't have to let the message fall through to your program?
- >>This would be very bad programming on somebody's part. On the other
- >>hand I can always nuke your program with TerminateApp() and you
- >>couldn't do anything about that either.
- >
- >The scenario goes like this: I want to WinExec another program, then
- >be notified when it terminates. With NotifyRegister, if another
- >program also requests notification, that program may catch the
- >termination but not pass the information through, leaving me waiting
- >for a notification that will never occur.
- >
- > Jeff Dean
- > jeff@igc.org
- >
-
- Can you kill a DOS app with TerminateApp()? I tried this and managed to get
- Windows to exit (yes, I'm sure I had the right task handle).
-
- Don
- --
- Don Wilcox | "For I am not ashamed of the Gospel of
- Washington University in St. Louis | Christ, for it is the power of salvation
- email: wilcox@swarm.wustl.edu | to all who believe."
-