wrong path for pipes

[krishty]

https://docs.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-createnamedpipea (CreateNamedPipeA function)

Parameters -> lpName says: "The unique pipe name. This string must have the following form: \.\pipepipename"

Wrong. The string must have the form \\.\pipe\pipename, that is two backslashes - dot - backslash - pipe - backslash - pipename.

[welcome]

Thank you for creating the issue! One of our team members will get back to you shortly with additional information. If this is a product issue, please close this and contact the particular product's support instead (see https://support.microsoft.com/allproducts for the list of support websites).

[ryanmajidi]

@GrantMeStrength Can you please take a look at this issue?

[krishty]

Same issue with TransactNamedPipe function (https://docs.microsoft.com/en-us/windows/win32/api/namedpipeapi/nf-namedpipeapi-transactnamedpipe), twice in the Remarks section. The Windows 10, version 1709 hint at the end gets it almost right, a backslash is missing.

Refer to ConnectNamedPipe function (https://docs.microsoft.com/en-us/windows/win32/api/namedpipeapi/nf-namedpipeapi-connectnamedpipe), Windows 10 hint at the end of the Remarks section for the correct syntax. Throughout that article, however, the links to CreateFile and OVERLAPPED are 404.

[GrantMeStrength]

Thank you - the formatting was messed up, and hopefully it is now correct. Thanks for reporting and saving someone a lot of confusion!

[krishty]

Great! CreateNamedPipeA is indeed fixed, and so are the links in ConnectNamedPipe.
The three paths in the Remarks section of https://docs.microsoft.com/en-us/windows/win32/api/namedpipeapi/nf-namedpipeapi-transactnamedpipe are still wrong; should I create a new issue for them?