-ETHICS 1.01-

This directory contains information on how to stop a debugger from
single stepping through your program. You may, or may not, want to
do this.  If you do, consider the ramifications of data destruction
and your responsibilties in that regard. Locking up a debugger has
the potential to crash a disk cache or worse, causing lost clusters
and eventually cross-linking files...

If data is lost, any data, do you want people saying your program did
it?  Would your *lawyer* want people saying that?

If you use the ideas here, strive for a clean exit. Reserve the lockup
routines for determined crackers, if at all. By no means delete any
files- it would be unprofessional and your reputation may suffer for it.