JP> UO> Just write a program that uses a named pipe to communicate
  > UO> with the PM session.  You can then send debugging trace
  > UO> strings from the PM session.  Instant debugger!  There's a
  > UO> program, PMPRINTF, that does all this, but it is 16-bit.

JP>   FWIW, the Borland IDE includes such a facility (the
  >Transcript window), and BCOS2 even comes with a few filters
  >(w/source) so some of their utilities can use it.

But the Transcript window can ONLY be used during compile, not
run-time...  So it wouldn't do you much good.  Unless you know something
I don't, in which case tell me... 

UO, I never thought of using a named PIPE to comunicate for debugging
purposes.  I think I'm going to have to work on something like that!!
'SPECIALLY SINCE -=BORLAND=- CAN'T SEEM TO WRITE A DEBUGGER THAT
-=W=O=R=K=S=-! 

Michael Douglass
___
 .Mike's Mail Internet:   MICHAEL.DOUGLASS{at}LCHANCE.SAT.TX.US

--- Maximus/2 2.01wb