Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!decwrl!sgi!cdp!jeff
From: jeff@cdp.UUCP
Newsgroups: comp.windows.ms.programmer
Subject: Re: Windows, Exec, Subprogram
Message-ID: <1266500005@cdp>
Date: 11 Apr 91 05:43:00 GMT
References: <1997375683@1991Apr10.170742.799@bellcore.be>
Lines: 13
Nf-ID: #R:1991Apr10.170742.799@bellcore.be:1997375683:cdp:1266500005:000:497
Nf-From: cdp.UUCP!jeff    Apr 10 22:43:00 1991


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