CreateNamedPipe... someone got any idea?

Hi The OnlineDocumentation says the path to the pipe has to be
\\.\pipe\pipename (for using a constant within C/C++
\\\\.\\pipe\\pipename)
if it is not a typo you have
 \\\\.¡\\pipe\\mypipe
and that is wrong as the docs says
Hope that helps

Norbert

Yes that's what documentation said. But one should be aware that specifying special character in a string you must use \ and then the character you want in your string. Therefore \\ in a string means \. This was also my first mistake. I debugged the app and saw the string I want is in memory just as it should be. there has to be seomething else.

Character after dot is a mistake. Ignore it.

Have you tried using GetLastError() to see what the error is?  You should always try that first.

To use VC's memory debugging features you use the procedure _CrtSetDbgFlg().  with the _CRTDBG_LEAK_CHECK_DF flag.  (Or this flag in with the existing flags.  This will report memory block overruns and blocks that weren't deleted when the program terminates.  To make it really effective, though you need to overload the new operator so that it stores with each block the source code file name and line number from which thr block was allocated.  Then when you gets these errors reported, you can doubleclick the error message and it will show you the line of code that allocated the block.  This is all documented in the VC help.

Woops.  Got posted to the wrong question!  sorry.

Feel free to reject this because it is a shot in the dark, but named pipes can only be created on NT. Is your test machine an NT?

Yes. I use NT 4.0 Server. That's the whole  point. Since it didn't work I ran both apps on Windows 95 machine because I suspected something could be wrong with network implementation.
NT machine is just as is, no SP3 or alike have been installed.
I read all docs I could find on that topic and haven't found a statement that would imply named or annonymous pipes won't work on Windows 95.

Perhaps someone could pass an alternative?

Promising solution will get double points!!!

On Win95, only the client side of named pipes is implemented. So your client app should work on win95 and on NT, not your server.

What exactly is your problem? Does "CreateNamedPipe" return an invalid handle? If not, does connectnamedpipe return you an instance or is your client just failing?

Is your server app a service?

I have a working program with named pipes for a server and programs from NT and 95 can connect to it...

Bingo!!!

Yes I appologize that I didn't supply as much data as needed but you gave me an extra edge with that article. It solved a few other things too. Thx abesoft.