[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wine-devel
Subject:    Re: ntdll: Map ESPIPE to STATUS_ILLEGAL_FUNCTION
From:       "Dmitry Timoshkov" <dmitry () codeweavers ! com>
Date:       2006-12-31 11:21:35
Message-ID: 001001c72ccd$d99e3350$0100a8c0 () DMITRY
[Download RAW message or body]

"Andreas Mohr" <andi@rhlx01.fht-esslingen.de> wrote:

> The STATUS_ILLEGAL_FUNCTION name was rather misleading to me since it doesn't
> indicate at all that it's supposed to be pipe-related
> (however it's within the numeric range of many other pipe status codes!).
> So, given that this is mainly a pipe status code after all I'd say that's
> the best we can achieve right now.

I haven't found anything more close is the PSDK.

> Of course, what really matters is what the receiving Win32 side *usually*
> expects after we encountered ESPIPE, and this might turn out to differ
> from your conversion ;).
> (is there any indication that RedAlert checks for a specific status code??)

Looks like that my change didn't actually affected RedAlert at all, at least
it was still functioning in my limited test session.

-- 
Dmitry.


[prev in list] [next in list] [prev in thread] [next in thread]