From: aw AT mail1 DOT bet1 DOT puv DOT fi
Newsgroups: comp.os.msdos.programmer,comp.os.msdos.djgpp
Subject: Re: WARNING: DOS is about to die.
Date: 13 Sep 1999 22:48:39 GMT
Message-ID: <H9X33$uzC@c400>
References: <7quo1t$94k$1 AT solomon DOT cs DOT rose-hulman DOT edu> <37D2EEE8 DOT CF27908C AT a DOT crl DOT com> <37D34350 DOT 2F2EE49B AT videotron DOT ca> <37D3456E DOT 448F01AF AT aol DOT com> <37D3D2E6 DOT 660F1586 AT unb DOT ca> <Pine DOT SUN DOT 3 DOT 91 DOT 990906192019 DOT 12553C-100000 AT is> <7rjobv$42a$1 AT ash DOT prod DOT itd DOT earthlink DOT net>
X-Newsreader: AllNews version 1.33 (Freeware) Build Jan  9 1999
Lines: 11
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

!smentzer AT pacbell DOT net (Steve Mentzer) wrote:
> >
> >For example, did you know you cannot catch SIGINT and SIGFPE on NT?  If 
> >you do, your program crashes, and the DrWatson log file clearly shows 
> >that it's an NT bug.
> 
> And you shouldn't be able to... The only thing that should be handling 
> interrupts are kernel-mode device drivers, not user mode applications.

Catching signals isn't exactly the same thing as handling interrupts.
Any Unix lets you catch signals (except SIGKILL).