> FileIOCompletionRoutine is always zero, but I see my defined time out
error
code (0x60040026) in the Internal field of the overlapped structure. In
this
I’m sure you also have lots of “RTL: no valid Win32 error mapping” or
similar debug traces.
Looks like inventing your own NTSTATUS codes is not so good - I personally
ended with using the standard NTSTATUS values (with valid Win32 error
mappings) in very unusual semantics. The user mode code was also written
to match this semantics.
Max