NetNews Usenet Archive 1992 #20/NN_1992_20.iso/spool/comp/os/mswindo/programm/misc/1723

Internet Message Format | 1992-09-08 | 1.6 KB

Path: sparky!uunet!munnari.oz.au!mel.dit.csiro.au!yarra!bohra.cpg.oz.au!daavid
From: [e-mail] (Daavid Turnbull)
Newsgroups: comp.os.ms-windows.programmer.misc
Subject: Re: WinExec return useful?
Message-ID: <[e-mail]>
Date: 8 Sep 92 11:14:36 GMT
References: <[e-mail]>
Distribution: usa,world
Organization: Computer Power Software
Lines: 26

In article <[e-mail]> [e-mail] (Gary Dobbins) writes:
> When an app calls WinExec, the return value is described somewhat vaguely
> in the SDK as a task handle, which I presume is an instance handle. (?)
This might be the case for a windows program but it is certainly not the
case when WinExec()ing a vanilla dos app, ie a .pif file.  Because WinExec()
is essentially a fork there is little that WinExec() can return apart from
an instance handle and in the case of a vanilla dos app all it really can
return is success or failure to start the app.

A problem that I am currently trying to solve (I have been successfully
putting it off so far), is how to obtain information about the exit code
of a dos app.  I know that I can set up the dos app to write a file etc.
but I would much rather not have to resort to suc a messy solution.  The
real problem is that the exit code of the app becomes part of the
enviroment which In my case is essentially lost when the app terminates.

Any suggestions ?

Thanks in advance, daavid


--
    Daavid Turnbull
    [e-mail]   [phone]    (fax) [phone]
    uunet!munnari!bohra.cpg.oz!daavid
    CP Software Export Pty Ltd                   ACN 006 640 133