🚀 go-pugleaf

nather@ut-emx.uucp (Ed Nather) writes:

(DD) >> 
(DD) >> My $.02 worth.  I always thought this was a dumb idea.  I mean all you
(DD) >> do is force the pern to find the reset switch when (N.B., not "if"!) the
(DD) >> machine locks up.  [...]

>You are making an incorrect assumption, that the only time you want to trap
>this combination is when the machine "locks up."  Be aware that people use

I should have been more verbose.  I was hoping people would be able to
read between the lines.  My overall point is that trapping c/a/b is not
a technical issue at all; it is a training issue.  You need to train
your users that there are a few things they shouldn't do when using your
software; the following lists some, but by no means all, of these things:

	1) c/a/b
	2) reset
	3) turning the machine off
	4) unplugging the machine
	5) pouring Coke on the keyboard
	6) dropping the machine
	7) etc...

What trapping c/a/b really does is make it harder for the support
programmer to deal with the machine, while not making it any harder for
the user (intentionally or not) to do something "bad".

(This probably doesn't belong in this [technical] conference at all, but that
is my $0.86 worth)