home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #20 / NN_1992_20.iso / spool / comp / os / mswindo / programm / misc / 1725 < prev    next >
Encoding:
Internet Message Format  |  1992-09-08  |  1.2 KB
  1. Path: sparky!uunet!ogicse!emory!swrinde!cs.utexas.edu!tamsun.tamu.edu!lstar31.tamu.edu!rjsparks
  2. From: rjsparks@lstar31.tamu.edu (Robert Sparks)
  3. Newsgroups: comp.os.ms-windows.programmer.misc
  4. Subject: Re: WinExec return useful?
  5. Message-ID: <1992Sep8.150425.9484@tamsun.tamu.edu>
  6. Date: 8 Sep 92 15:04:25 GMT
  7. Article-I.D.: tamsun.1992Sep8.150425.9484
  8. References: <dobbins.271.715550243@lan.ccit.arizona.edu> <1992Sep8.111436.10411@bohra.cpg.oz.au>
  9. Sender: news@tamsun.tamu.edu (Read News)
  10. Distribution: usa,world
  11. Organization: none
  12. Lines: 12
  13.  
  14. In article <1992Sep8.111436.10411@bohra.cpg.oz.au>, daavid@bohra.cpg.oz.au (Daavid Turnbull) writes:
  15. |> A problem that I am currently trying to solve (I have been successfully
  16. |> putting it off so far), is how to obtain information about the exit code
  17. |> of a dos app.  I know that I can set up the dos app to write a file etc.
  18. |> but I would much rather not have to resort to suc a messy solution.  The
  19. |> real problem is that the exit code of the app becomes part of the 
  20. |> enviroment which In my case is essentially lost when the app terminates.
  21.  
  22. How about any non-file-based transfer mechanism from a DOS app kicked off
  23. with WinExec?
  24.  
  25. RjS
  26.