CS> parameters. But there is a problem -- the documentation
 CS> does not agree on the order of the parameters!

 MS> but not the bsedos.h file!!!  Even in the toolkit2.1
 MS> bsedos.h header files, the order was : inbufsize,
 MS> outbufsize. Now (with tlkt30) the docs and the header
 MS> files agree. This was not the case under tlkt21.

 MS> Toolkit 3.0 BSEDOS.H
 MS>    APIRET APIENTRY  DosCreateNPipe(PCSZ  pszName,
 MS>                                    PHPIPE pHpipe,
 MS>                                    ULONG openmode,
 MS>                                    ULONG pipemode,
 MS>                                    ULONG cbInbuf,
 MS>                                    ULONG cbOutbuf,
 MS>                                    ULONG msec);

Based on the results of DosQueryNPipeInfo(), it looks to me that the
cbInbuf and cbOutbuf parameters are reversed from what they should be.
Either that, or the PIPEINFO structure has its corresponding fields
reversed.

So it looks to me that IBM managed to get BOTH the documentation and the
header file wrong for the OS/2 3.0 toolkit.

By the way, what are these functions in BSEDOS.H supposed to do and why
aren't they documented in the toolkit? :

   APIRET APIENTRY  DosRawReadNPipe( PCSZ   pszName,
                                     ULONG  cb,
                                     PULONG pLen,
                                     PVOID  pBuf);

   APIRET APIENTRY  DosRawWriteNPipe( PCSZ  pszName,
                                      ULONG cb);

I'm going to post another message to you about the problems I'm having with
named pipes.  At the moment, I'm wondering why other people are not having
so much trouble with them.


--- Maximus/2 2.01wb