PS> Yeah, I read about that. But each process will be 
 PS> separate, I will simply 
 PS> startx several instances of on EXE. Prefarably without any multi-process 
 PS> implementation. Each process shouldn't have to know if 
 PS> it's "alone" or if 
 PS> there are 123 other instances of itself. But as I 
 PS> understand it, a named pipe 
 PS> can only exist as one pipe, serverclient. But can 
 PS> however allow multiple 
 PS> clients access the same pipe, but not multiple 
 PS> servers. 

You've been lead a little astray.

With one pipe name:

 - one server process can serve multiple clients.  Each pipe is
   distinct;  with its own handle.

 - You can start multiple servers (using the same pipe name)
   to serve multiple clients.  One server per client is just fine.

   The only concern is the very first program that calls
   DosCreateNPipe() -- that decides how many pipes can be created with
   that name.   Subsequent calls can pass a number,  but it will
   be ignored.


 PS> Is it at all possbile to achive the possibility to 
 PS> create multiple instances 
 PS> of one pipe that is 100% separate when the clients/servers are concerned?

Yes -- but it is not "one pipe".  Each pipe is distinct -- but
they can all use the same pipe name.


 PS> I wanna save as much CPU as possible. And to modify

Then you should try to have only one server (start a new thread as each
client connects)...


--- Maximus/2 3.00