On Sunday, 96/04/28, Leslie Rhorer wrote to David Noon about "Named
Pipes" as follows:

LR>  DN> I had loads of problems using named pipes using a Borland C/C++
LR>  DN> compiler.
LR> 
LR>         I'm using a DOS compiler, not an OS/2 compiler.

Precisely. I was using BCAF 3.1 when I was having the problems. The
programs wouldn't work in a VDM or a VMB.

LR>         Since these use the raw API, and they *DON'T* work, 
LR> the API must not be working, No?  And since these problems 
LR> exist WITHOUT using any compile of mine, it can't be my 
LR> compiler, can it?

If these are being used inside a VDM you might not be running the FAPI
versions of TYPE and MORE supplied with OS/2, and therefore not using
the API directly. The reason I say this is because the virtualised
COMMAND.COM is assigning the pipe correctly to the redirected STDIN:
device, so the pipe seems to be accessible at that level. You might be
inadvertantly using older, real DOS versions of TYPE and MORE.

Do you have a PATH statement in the VDM's AUTOEXEC.BAT that places a
real DOS system directory (C:\DOS, perhaps) ahead of the x:\OS2 and
x:\OS2\MDOS directories?

Regards

Dave


 * KWQ/2 1.2i * If you can't fix it, call it a feature!
--- Maximus/2 3.01