Name Pipe to TCP/IP utility

There are three parts
First part is the Named Pipe Server.  This piece of software acts in place
or the ReactOS server, simplifying starting stopping and developing messages
for testing.  Program is called MS_Pipe_Server.exe

Second part is the Middle_Man.  Middle_Man is where all the work is done.
The Middle_Man contains a winsock TCP/IP server and a Named Pipe Client.
This is also where significant work needs to be done to handle communications.
Multiple threads will be needed to really make it work fully.


Third part is the terminal program DTelnet, or other.

How to run it.
There is a timing issue so things need to be ready to go in order to work.
Sometimes several tries are needed - but it does work.

1) Start DTelnet but don't click connect yet.  host 127.0.0.1 Port 27015 

2) Start the Named Pipe Server MS_Pipe_Server

3) Now get ready to start the Middle_Man and immediately connect DTelnet
   and send a character.  If timing is good the three screens will appear
   like the image attached, and you can press key in DTelnet and have 
   the response back from the Named Pipe.  Not sure why the timing is
   sensitive on the start up.  If need to try again both Middle_Man and 
   MS_Pipe_Server need to be closed before starting over.
   
Like I said this is just proof of concept.  Code pieces from Microsoft.
For a fully functioning bridge much more refinement needs to be done which
would include a separate threads for the communications, better buffer controls,
error checking, retries, etc.

Init_Pipe_Connect.c and MS_Server_winsock.c get complied together to make Middle_Man.exe
MS_Pipe_Server.c get compiled to make the Named Pipe Server in place of ReactOS

The ppj files can be opened with a text editor to see the compile and link conditions