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

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!

Eh?  If it trapped like that, it should just kill that one task,
no?  That's what the protection is all about.  I have "AUTOFAIL"
in my config.sys as well, so that it just fails and keeps going
instead of waiting for user-input.  That's so that my BBS can
run successfully after Binkley used to trap.  BFN.  Paul.
@EOT:

---