1.
Error Codes: Win32 vs. HRESULT vs. NTSTATUS « JP’s Blog Aug 20, 2007 ... 3 As long as you have a ‘real’ HRESULT (i.e. not one from HRESULT_FROM_WIN32) and want to get a ‘real’ Win32 error code (i.e. not a ...
2.
Error Codes: Win32 vs. HRESULT vs. NTSTATUS « JP’s Blog Aug 20, 2007 ... NTSTATUS* and Win32 error codes share the same definition: // // Values are 32 bit values layed out as follows: // // 3 3 2 2 2 2 2 2 2 2 2 ...
3.
Error Codes: Win32 vs. HRESULT vs. NTSTATUS « JP’s Blog Aug 20, 2007 ... However, due to compatibility reasons, all common error codes defined in winerror.h (such as ERROR_FILE_NOT_FOUND, 0×2) do not quite adhere ...
4.
JP’s Blog The Windows kernel maintains two types of threads — Non-GUI threads, ..... 0:000> lsa Leak!wmain+0x00000044 33: } 34: 35: int __cdecl wmain() 36: { > 37: ...
5.
Error Codes: Win32 vs. HRESULT vs. NTSTATUS « JP’s Blog Aug 20, 2007 ... 2 Holds for ‘real’ Win32 error codes. For compatibility error codes, use HRESULT_FROM_WIN32 3 As long as you have a ‘real’ HRESULT (i.e. not ...
6.
Error Codes: Win32 vs. HRESULT vs. NTSTATUS « JP’s Blog Aug 20, 2007 ... NTSTATUS* and Win32 error codes share the same definition: ... 1 1 1 1 1 1 1 1 1 1 // 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 ...
7.
Error Codes: Win32 vs. HRESULT vs. NTSTATUS « JP’s Blog Aug 20, 2007 ... HRESULTs are 32 bit values layed out as follows: // // 3 3 2 2 2 2 2 2 2 ... #define FACILITY_DEBUGGER 0x1 #define FACILITY_RPC_RUNTIME 0x2 ...
8.
Error Codes: Win32 vs. HRESULT vs. NTSTATUS « JP’s Blog Aug 20, 2007 ... Even the other way round, assigning HRESULT values to NTSTATUS variables seems to be ok, given that the R, C, N and r bits of HRESULTS are ...
9.
Error Codes: Win32 vs. HRESULT vs. NTSTATUS « JP’s Blog Aug 20, 2007 ... It turns out that the NTSTATUS documentation in the DDK contradicts the definition in ntstatus.h (3790): According to winerror.h, ...
10.
Error Codes: Win32 vs. HRESULT vs. NTSTATUS « JP’s Blog Aug 20, 2007 ... 3 As long as you have a ‘real’ HRESULT (i.e. not one from HRESULT_FROM_WIN32) and want to get a ‘real’ Win32 error code (i.e. not a ...
|