-=> Quoting Richard Illes to All <=- 

 RI> While porting a program from unix to CSet/2 I found out the original
 RI> code did a fopen().. then later performed a fclose() and called a
 RI> routine which did fprintf() to that fopen FILE pointer.. the original
 RI> unix code worked fine, another team porting to NT with Visual C also
 RI> had no problem.. Cset created an exception.  After doing a debug on the
 RI> code, Visual C zero's out the FILE pointer after a fclose() and any
 RI> further fprintf() to this pointer causes nothing to happen.. CSet just
 RI> leaves the FILE pointer a mess which causes a trap on fprintf().

I do something like this...

fclose(fhandle);
fhandle = 0;

then...

if( fhandle != 0 )
  fprintf(...

 RI> Is there a way to really kill a process/session? Nothing more
 RI> irritating then having a test program hang, and not be able to get rid
 RI> of it other then rebooting the machine!

Install WatchCat 2.0 (WCAT20.ZIP).  It can usually kill a hung program, gets
me out of hangs quite often without rebooting... :-)  WCAT21.ZIP is out, but
I couldn't get it to run, maybe because I run CMD.EXE as my WPS??

         ////
        (o o)
----oOO--(_)--OOo----   phil.crown{at}bluecafe.com | Fido 1:124/6108.2

--- Blue Wave/Max v2.20