PRB: WaitNamedPipe and Error 253 in Windows 95

Last reviewed: February 4, 1998
Article ID: Q180222

The information in this article applies to:

Microsoft Windows 95

SYMPTOMS

In Windows 95, when WaitNamedPipe fails due to an invalid pipe name passed as the first parameter, GetLastError returns error 253, which is not listed as a possible error code for this function. When you run the same code on Windows NT 4.0, the error code 161, ERROR_BAD_PATHNAME, appears.

RESOLUTION

To workaround the problem, you can resolve error 253 the same way as error 161, ERROR_BAD_PATHNAME. However, it has to be hard coded. For example:

   if ( !WaitNamedPipe(lpNamedPipeName, NMPWAIT_USE_DEFAULT_WAIT) )
      if (GetLastError() == 253)
         printf ("ERROR: WaitNamedPipe failed due to bad path name.");

STATUS

Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Keywords          : NtwkMisc W32s
Version           : WINDOWS:95
Platform          : WINDOWS
Issue type        : kbprb

================================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 4, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.