Dan Kegel wrote:
I wrote a humble beginning of a conformance test for named pipes, in hopes of preventing regressions like the one which is currently breaking Installshield installs (or was last I checked).
Later it's going to verify that named pipes like the ones Wine uses internally (e.g. in ole32/rpc.c) actually work, For now I thought I'd just make sure we return the right error code if you pass a bogus filename to CreateNamedPipe. But, um, we don't return any error code; we happily succeed.
Can somebody who has Windows Server run this little test, and tell me what it outputs? You can build it as part of the wine test suite, or standalone with the commands
call \vcvars32.bat cl /D STANDALONE /D _X86_ /D _M_IX86 /D WIN32 /D _WINDOWS pipe.c
Thanks, Dan
Built it standalone, need to add #include <windows.h> above the windef.h header Output was a single line: h FFFFFFFF, err 123
This is on Windows 2000 Professional, but I'm pretty sure (as said before) you don't need Server for named pipes...
David