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 had
 RI> 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().

Then you should thank Cset for finding what is clearly a bug in your code!


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

Search for a program like killem.zip.



--- Maximus/2 3.00