Duane Clark <[EMAIL PROTECTED]> writes: > One of several problems I see in my patch (obviously I should have > slept on it before submitting) was that it would not return hProcess > when requested. Getting that info appears to me to require an explicit > call to CreateProcess, rather than using WinExec.
True, it does; OTOH returning a valid instance from ShellExecute16 requires a WinExec... another possible solution is to simply implement a completely separate ShellExecute16 by copying the relevant parts of the code. -- Alexandre Julliard [EMAIL PROTECTED]
