Newsgroups: comp.windows.ms.programmer Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!csus.edu!borland.com!sidney From: sidney@borland.com (Sidney Markowitz) Subject: Re: Windows, Exec, Subprogram Message-ID: <1991Apr15.045656.6720@borland.com> Organization: Borland International References: <1991Apr12.211658.28611@netcom.COM> <1991Apr13.010556.25866@borland.com> <1991Apr14.184603.26321@hyper.hyper.com> Date: Mon, 15 Apr 1991 04:56:56 GMT bonneau@hyper.UUCP (Paul Bonneau,,) writes: >sidney@borland.com (Sidney Markowitz) writes: >>WinExec() returns a value >>that is not documented, other than being greater than 31 if successful > ^^^^^^^^^^^^^^^^^^^^^^ >The return value from WinExec() IS documented in the SDK book >"Reference - Volume 1", on page 4-459 under "Return Value" for >WinExec(). The SDK Ref only documents the error codes, which are less than 32. I meant to say that the return value of a successful call is not documented other than being greater than 32. That makes it sound suspiciously like the "module instance handle" returned by LoadModule, and jeff@cdp claimed that they are the same, but the doc doesn't say so. I suppose that Jeff's claim that WinExec just passes back the return value of LoadModule would be easy to check with a debugger, but it still leaves open the question of what it does with a non-Windows app (which LoadModule won't take) and what the return value is for that. Does anyone know? -- sidney markowitz