On Saturday, 96/05/18, Leslie Rhorer wrote to David Noon about "Named
Pipes" as follows:

LR> Is it possible the installation routine de-classified some 
LR> object or that a related DLL is interfering?

Hi Les,

Pipe support is an add-on to the file system. Stuff like WPS classes
won't affect it, since you can use pipes running TSHELL, or even OS/2
1.x.

LR> either.  Obviously it is able to open the pipe.  It errors 

Excellent! We can now eliminate [lack of] handle inheritance as a
cause.

I presume the REXX exec sits there dangling on either the LINES() call
or the LINEIN() call. This would indicate to me that some parameter in
the pipe creation call is causing problems. Here is some code I wrote
for a pipe server address space that creates a pipe that works with the
REXX exec I sent you. You might care to show it to the author of your
program to compare.

#define Buffer_size 4096UL

   APIRET rc;
   HPIPE Pipe;
   static const unsigned short Pipe_instances = 1;

   /* Create the named pipe. */
   rc = DosCreateNPipe("\\PIPE\\DWN_pipe", &Pipe,
        NP_INHERIT|NP_ACCESS_OUTBOUND,
        NP_WAIT|NP_TYPE_BYTE|NP_READMODE_BYTE|Pipe_instances,
        Buffer_size, 0UL, 0UL);

As I see it, the most likely cause of such a problem would be the
omission of NP_READMODE_BYTE, but then again it could really be
anything.

Regards

Dave


 * KWQ/2 1.2i * Windows NT: No Thanks... Not Trusted... Not Today... Not Tomorrow

--- Maximus/2 3.01