Xref: utzoo comp.os.os2.misc:589 comp.os.os2.programmer:410
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!rpi!dali.cs.montana.edu!milton!yoda.eecs.wsu.edu!wbonner
From: wbonner@eecs.wsu.edu (Wim Bonner)
Newsgroups: comp.os.os2.misc,comp.os.os2.programmer
Subject: Re: Help with Named Pipes error messages
Summary: problem seems to be fixed
Keywords: named pipes
Message-ID: <1991Jan25.094207.20500@eecs.wsu.edu>
Date: 25 Jan 91 09:42:07 GMT
References: <1991Jan22.110653.3328@eecs.wsu.edu> <1991Jan23.172128.26448@ingres.Ingres.COM>
Reply-To: wbonner@yoda.UUCP (Wim Bonner)
Organization: Washington State University, Pullman
Lines: 32

In article <1991Jan23.172128.26448@ingres.Ingres.COM> seg@ingres.com (scott e garfinkle) writes:
>Are you sure that the server .exe corresponds to the source?  At first
>blow, it sounds to me like the second pipe doesn't have NP_TYPE_MESSAGE
>set, though it dows seem so from your source.
>
>Anyway, why bother to open a second pipe at all?  Why not just keep the
>connection you started with, spawn off a thread to deal with that connection,
>and go make another instance of the named pipe? 

I am writing the program so that there will be multiple clients who want to
talk with the one server.  I am having seperate pipes for each client, but
am having them open a "config" pipe first, and following that, figure out what
pipe they should open permanently.

Anyway, I figured out what my problem was.  

I was actually getting a "PIPE BUSY" message.  The way I was figuring out what
messages I was getting was to use printf statements.  Unfortunately, I was 
printing the pipe name and the open error code using the same printf statement, 
and because the pipe name was pointed to using a PSZ (32 bit pointer) printf
was using the offset correctly and printing the name, but then was using the 
segment to print the error code, instead of the error code.

Now I have taken care of the problem, and hopefully will get the logic of 
the message passing taken care of within the next few days.

Wim.
-- 
|  wbonner@yoda.eecs.wsu.edu  |
| 27313853@wsuvm1.csc.wsu.edu |
|   27313853@Wsuvm1.BITNET    |
|  72561.3135@CompuServe.com  |