Can someone pin numbers on the following codes: STATUS_FILE_IS_A_DIRECTORY STATUS_INVALID_EXECUTABLE_IMAGE At least I think that's what they're called (unfortunately, my book's at home where I can't check it). They're listed in my NT native API book (though that's no guarantee that they exist), but not in the Wine header files, and I don't have a copy of the DDK installed on top of MSDEV. David
David Howells wrote:
Can someone pin numbers on the following codes:
STATUS_FILE_IS_A_DIRECTORY STATUS_INVALID_EXECUTABLE_IMAGE
At least I think that's what they're called (unfortunately, my book's at home where I can't check it).
They're listed in my NT native API book (though that's no guarantee that they exist), but not in the Wine header files, and I don't have a copy of the DDK installed on top of MSDEV.
They're not defined in the MS SDK header files either. -- ======================================================================== Ian Pilcher ian.pilcher(a)home.com ========================================================================
"David Howells" <dhowells(a)cambridge.redhat.com> wrote:
Can someone pin numbers on the following codes:
STATUS_FILE_IS_A_DIRECTORY STATUS_INVALID_EXECUTABLE_IMAGE
At least I think that's what they're called (unfortunately, my book's at home where I can't check it).
They're listed in my NT native API book (though that's no guarantee that they exist), but not in the Wine header files, and I don't have a copy of the DDK installed on top of MSDEV.
nt4 ddk has only one of them: #define STATUS_FILE_IS_A_DIRECTORY ((NTSTATUS)0xC00000BAL) perhaps STATUS_INVALID_EXECUTABLE_IMAGE is defined in the win2000 ddk? neither win98 ddk, nor platform sdk july 2000 edition have them.
participants (3)
-
David Howells -
Dmitry Timoshkov -
Ian Pilcher