Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!rpi!clarkson!grape.ecs.clarkson.edu!levericw From: levericw@cheetah.ece.clarkson.edu (Walden Leverich) Newsgroups: comp.os.msdos.programmer Subject: Re: cntl-alt-del trap Message-ID: Date: 25 Jan 91 22:06:59 GMT References: <24752@grebyn.com> Sender: @grape.ecs.clarkson.edu Distribution: na Organization: /home/cheetah.ece/levericw/.organization Lines: 29 In-Reply-To: valley@uchicago's message of 25 Jan 91 17:55:21 GMT > My $.02 worth. I always thought this was a dumb idea. I mean all you > do is force the pern to find the reset switch when (N.B., not "if"!) the > machine locks up. Worse, if they don't have a reset switch, they gotta > turn the damn thing off wait 15 seconds then power back up. I always > thought this idea of trapping it was just programmer ego gone haywire > (Frankenstein mentality: If it can be done, it should be done...) Think about the user who is waiting for a database action. A long one to be specific. If ctl-alt-del is trapped and he/she hits the buttons, a message can be sent telling that the operation is still running, or the operation can be closed down in an orderly maner. If the buttons are not trapped you can have a serious mess. The same argument applies to some network functions, not to mention disk cache programs. It may not be needed at all times, but trapping ctl-alt-del does have its uses. -Walden -- --------------------------------------------------------------------------- Walden H. Leverich III | Inet: levericw@clutx.clarkson.edu ECE Dept. | CServ: 73237,2212 <- checked weekly Clarkson University | SnailMail: Software Solutions | PO Box 763 | Potsdam, NY 13676-0763 #include --------------------------------------------------------------------------