RS> is no command or status information on a pipe, the DosRead()-call blocks
RS> until something is written to the pipe.

 DG>     In looking under remarks on DosRead, I see there is a
 DG> call     DosPeekNPipe that you can use to determine if there
 DG> is something     there to read before issuing the DosRead
 DG> function.

I have seen this call also, but it is only for named pipes (at least the
documentation says so, I haven't tried it).

Regards, Ruud 

--- timEd/2 1.00