DN> Since you are not running SES, it would seem that any security issues
 DN> would arise from Lantastic. Does the author run Lantastic too?

        No, and neither do I on the machine which handles the application. 
Lantastic was installed on that machine, but wouldn't work for other
reasons.  I removed all the Lantastic drivers and IFS from Config.Sys on
that machine.  Is it possible the installation routine de-classified some
object or that a related DLL is interfering?

 DN> Here is a quick and dirty REXX exec that will behave like TYPE but use
 DN> the pipe directly rather than inherit the handle from the command
 DN> shell by redirection.

        It behaves exactly like TYPE and MORE.  No errors, but no strings,
either.  Obviously it is able to open the pipe.  It errors if run before
the pipe is in place, or after it is closed, or if the Rexx process is
interrupted by a  and run again.  If the pipe is terminated
normally by closing the parent app, control is returned to the command line
with no comment.

 DN> If this reads the pipe and TYPE still doesn't then it looks very much
 DN> like an inheritance problem.

        Nope.  This opens the pipe, but doesn't read it.

                                                                Les

--- FLAME v1.1