Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!mit-eddie!uw-beaver!milton!ogicse!pdxgate!parsely!percy!qiclab!leonard
From: leonard@qiclab.scn.rain.com (Leonard Erickson)
Newsgroups: comp.os.msdos.programmer
Subject: Re: cntl-alt-del trap
Message-ID: <1991Feb15.203348.6157@qiclab.scn.rain.com>
Date: 15 Feb 91 20:33:48 GMT
References: <24752@grebyn.com> <LEVERICW.91Jan17230451@cheetah.ece.clarkson.edu> <valley.664826121@gsbsun> <43301@ut-emx.uucp> <valley.665079050@gsbsun>
Distribution: na
Organization: QIC Laboratories/SCN Research of Tigard Oregon
Lines: 24

valley@uchicago (Doug Dougherty) writes:

>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:

Sorry, but you are assuming that the programmer has any say about the
training of the users! Part of my job is user support, and most of the
problems can be traced to the fact the users *don't* get adequate training.
And management won't listen.

Also, *we* are the support programmers. I can't think of a situation where
trapping ctrl-alt-del during critical portions of a program would be a
support problem to us.  On the other hand, if a user reboots in the middle
of a fileupdate, guess who gets to clean up the mess? And if we complain
that they shouldn't have let someone ignorant enough to do that near the
machine, *we* get in trouble. We are supposed to make the program idiot 
proof. They won't bother trying to keep idiots away from it. <sigh>
-- 
Leonard Erickson			leonard@qiclab.uucp
personal:	CIS: [70465,203]	70465.203@compuserve.com
business:	CIS: [76376,1107]	76376.1107@compuserve.com