JK>
  > Will try it.  What I was trying to say is my VIO programs compile just
  > fine, but when I try to execute them from an OS/2 session, windowed or
  > full screen, the session minimizes while the program runs, then pops
  > open again without showing any of the output from the program.
JK>

  Try this little wheeze :

      TEXTPROGRAM.EXE | MORE

  This is assuming that you have a printf() or use cout in your program.

  If you've accidentally linked your VIO programs as PM programs, then
  when you execute them from a command line the command interpreter
  session will be minimised and you will be switched to the PM session
  for the duration of the process.

  Unlike GUI programs on some operating systems PM programs can quite
  happily use standard input and standard output.   It's just that
  output to the CON device from a process running in a PM session is
  discarded.  If you redirect the output to a file or a pipe, you will
  be able to see it.

  Linking as a VIO program varies from compiler to compiler (Borland
  requires TLINK -ap, for example), so check your compiler documentation.

  TDUMP and EXEHDR will also tell you how you have linked your EXEs.

  > JdeBP <
___
 X MegaMail 2.10 #0:
--- Maximus/2 2.01wb