#WinExec() return is bad
5 messages in this thread
WinExec() always seems to return 0 under win32s. This is supposed to be an
error. If it is successfull, it is supposed to return a value greater than 32.
Is there something wrong with win32s?
KQ
There is 1 Reply.
>>>WinExec() always seems to return 0 under win32s. This is supposed to be
an error. If it is successfull, it is supposed to return a value greater
than 32. Is there something wrong with win32s?
Is it returning 0 even when the requested program has been spawned, or are
the programs never being spawned? Thanks for helping us to track this down.
Lee
There is 1 Reply.
I must appologise. I meant to say that the program is getting executed when I
do WinExec(); however, the return code is 0. This is supposed to indicate a
failure, but the program specified in WinExec() ran just fine.
There are 2 Replies.
>>>I must appologise. I meant to say that the program is getting executed
when I do WinExec(); however, the return code is 0. This is supposed to
indicate a failure, but the program specified in WinExec() ran just fine.
Nice find – you are right. Of course the workaround is to use CreateProcess,
but I'll make sure that this bug is filed.
Lee
>>>I must appologise. I meant to say that the program is getting executed
when I do WinExec(); however, the return code is 0. This is supposed to
indicate a failure, but the program specified in WinExec() ran just fine.
After looking further into the problem, it sounds like you don't really have
Win32s 1.1. This problem was seen on internal builds of Win32s, particularly
ones that were improperly setup. When you get the final update to the Win32
SDK, please change the line "setup=1" to "setup=0" in
<windir>\system\win32s.ini. This will cause the Win32s setup to copy over
*all* files w/o regard to the version information.
Lee