Article View: comp.windows.ms.programmer
Article #2045Re: Windows, Exec, Subprogram
From: Aaron Akman
Date: Thu, 11 Apr 1991 16:13
Date: Thu, 11 Apr 1991 16:13
24 lines
1524 bytes
1524 bytes
In article <1266500005@cdp>, jeff@cdp.UUCP writes: > > You can use WinExec(), which is closer to system() than to execv(). > Even for a short program, Windows will switch to the full screen > (or a window, if you're using a PIF file and have specified > windowed mode). File I/O is the easiest way to communicate, but > there are definitely better ways, e.g., a shared block of memory. > > By the way, note that WinExec() is asynchronous, and will probably > return before the requested program has completed. > > Jeff Dean > jeff@cdp.igc.org > uunet!pyramid!cdp!jeff If the WinExec()'ed program is a regular DOS program (with a PIF to make it popup in a window) that does modem stuff, will everything else stop until it finishes? Do regular DOS apps ever get multitasked? Off int 28h, or something? ___________________________ Aaron Akman aaron@backyard.bellcore.com 908-699-8019
Technical Details
Message-ID:
<1991Apr11.161356.20694@bellcore.bellcore.com>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!sun-barr!rutgers!bellcore!backyard!aaronReferences:
<1997375683@1991Apr10.170742.799@bellcore.be> <1266500005@cdp>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!sun-barr!rutgers!bellcore!backyard!aaron From: aaron@backyard.bae.bellcore.com (Aaron Akman) Newsgroups: comp.windows.ms.programmer Subject: Re: Windows, Exec, Subprogram Message-ID: <1991Apr11.161356.20694@bellcore.bellcore.com> Date: 11 Apr 91 16:13:56 GMT References: <1997375683@1991Apr10.170742.799@bellcore.be> <1266500005@cdp> Sender: usenet@bellcore.bellcore.com (Poster of News) Reply-To: aaron@backyard.bae.bellcore.com (Aaron Akman) Organization: Bell Communications Research Lines: 24