Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Re: strange results in Win10 from CreateProcess due to MajorVersion etc PE headers
27 views
Skip to first unread message
Dex
Dec 14, 2014, 4:22:12 AM12/14/14
to
Sorry, I was wrong in regards to x64 possibly ignoring the version values.
Just to clarify, im actually getting the same results from the 64bit exe as
well as the 32bit exe...
ie. it doesnt matter what the Major/MinorOperatingSystemVersion is, but if
the Subsystem is 6.3 or 6.4, regardless of whether its 32 or 64bit, it
returns weirdly... (CreateProcess claims success, yet the return code is the
invalid return code you'd normally get when CreateProcess fails)
--- news://freenews.netfront.net/ - complaints: ne...@netfront.net ---
Just to clarify, im actually getting the same results from the 64bit exe as
well as the 32bit exe...
ie. it doesnt matter what the Major/MinorOperatingSystemVersion is, but if
the Subsystem is 6.3 or 6.4, regardless of whether its 32 or 64bit, it
returns weirdly... (CreateProcess claims success, yet the return code is the
invalid return code you'd normally get when CreateProcess fails)
--- news://freenews.netfront.net/ - complaints: ne...@netfront.net ---
Dex
Dec 14, 2014, 5:16:24 AM12/14/14
to
Ive uploaded some sample 32 and 64bit exes with the appropriate PE header
values...
10kbs .zip:
https://www.sendspace.com/file/yhbuzp
All the executable does is return 69696969 as an ExitProcess return code.
Under Windows 10 i get the following results:
---
C:\>runproc c:\xtest\64\0.0.6.2.exe
CreateProcess = 1. GetExitCodeProcess=1, ReturnCode= 69696969/0x4277DC9
C:\>runproc c:\xtest\64\0.0.6.3.exe
CreateProcess = 1. GetExitCodeProcess=1, ReturnCode=-1073741701/0xC000007B
C:\>runproc c:\xtest\64\0.0.6.4.exe
CreateProcess = 1. GetExitCodeProcess=1, ReturnCode=-1073741701/0xC000007B
C:\>runproc c:\xtest\64\0.0.6.5.exe
CreateProcess = 0 (FAIL)
GetExitCodeProcess=0, ReturnCode= 0/0x0
C:\>runproc c:\xtest\64\0.0.6.6.exe
CreateProcess = 0 (FAIL)
GetExitCodeProcess=0, ReturnCode= 0/0x0
values...
10kbs .zip:
https://www.sendspace.com/file/yhbuzp
All the executable does is return 69696969 as an ExitProcess return code.
Under Windows 10 i get the following results:
---
C:\>runproc c:\xtest\64\0.0.6.2.exe
CreateProcess = 1. GetExitCodeProcess=1, ReturnCode= 69696969/0x4277DC9
C:\>runproc c:\xtest\64\0.0.6.3.exe
CreateProcess = 1. GetExitCodeProcess=1, ReturnCode=-1073741701/0xC000007B
C:\>runproc c:\xtest\64\0.0.6.4.exe
CreateProcess = 1. GetExitCodeProcess=1, ReturnCode=-1073741701/0xC000007B
C:\>runproc c:\xtest\64\0.0.6.5.exe
CreateProcess = 0 (FAIL)
GetExitCodeProcess=0, ReturnCode= 0/0x0
C:\>runproc c:\xtest\64\0.0.6.6.exe
CreateProcess = 0 (FAIL)
GetExitCodeProcess=0, ReturnCode= 0/0x0
Message has been deleted
Paul
Dec 14, 2014, 3:38:38 PM12/14/14
to
else mentioned it.
http://connect.microsoft.com/
Paul
Dex
Dec 14, 2014, 4:41:01 PM12/14/14
to
Thanks for your..... oh, wait.
Dex
Dec 14, 2014, 4:48:16 PM12/14/14
to
btw, one of the reasons MS releases pre-production releases is to help find
such gremlins... but ok, I'll zip my lips and wait for the production
release, it'll be better to let customers face the issue first right ;)
Anyway Mr Morgan no need to get your pantyhose in a twist, this
issue/bug/whatever found me, I didn't go looking for it, so you can relax.
such gremlins... but ok, I'll zip my lips and wait for the production
release, it'll be better to let customers face the issue first right ;)
Anyway Mr Morgan no need to get your pantyhose in a twist, this
issue/bug/whatever found me, I didn't go looking for it, so you can relax.
rvint...@intelliarts.com
Jan 12, 2016, 11:25:33 AM1/12/16
to
Hi Dex, have you found solution for this behavior?
0 new messages