RI>
  > While porting a program from unix to CSet/2 I found out the original
  > code did a fopen().. then later performed a fclose() and called a
  > routine which did fprintf() to that fopen FILE pointer.. the original
  > unix code worked fine, another team porting to NT with Visual C also had
  > no problem.. Cset created an exception.
RI>

  From the ISO C Standard, 7.9.3 :

     "[...] The value of a pointer to a FILE object is indeterminate
      after the associated file is closed (including the standard text
      streams). [...]"

  Don't blame your tools for the fact that you had bad code.

  In fact, be grateful to the tool that revealed the problem to you.

RI>
  > Is there a way to really kill a process/session?
RI>

  DosStopSession and DosKillProcess

  The "Program Execution Control" section of your Toolkit 2.x and 3.x
  Control Program Guide and Reference (supplied as standard with all of
  the commercial C++ compilers for OS/2) documents all of the calls
  relating to sessions, processes, and threads.

  > JdeBP <
___
 X MegaMail 2.10 #0:

--- Maximus/2 3.00