Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!cbatt!ihnp4!homxb!houxm!mtuxo!mtgzz!rosen
From: rosen@mtgzz.UUCP
Newsgroups: att.sys.pc6300,comp.sys.ibm.pc
Subject: MSC and signal catching
Message-ID: <2681@mtgzz.UUCP>
Date: Mon, 11-May-87 15:14:35 EDT
Article-I.D.: mtgzz.2681
Posted: Mon May 11 15:14:35 1987
Date-Received: Wed, 13-May-87 07:33:46 EDT
Organization: AT&T, Middletown NJ
Lines: 28
Xref: utgpu junk:5115 comp.sys.ibm.pc:3447


Someone wrote me mail asking:

	    I read your response to the guy trying to trap
	 ctrl-C's.  Can the signal() function be used to
	 trap hardware interrupts?  Have you seen any go
	 software to do this (for MSC 4.0)?

I answered:

	According to the MSC manual signal() can only be used to trap for SIGINT
	(ctrl C) or SIGFPE (floating point exception). It seems to me all
	interrupts are the same (hardware and software) so I don't know why
	MSC only handles 2 of them. I suppose to catch other interrupts you 
	can use the type of code the other fellow was writing for ctrl C. That 
	is, replace the interrupt vector or chain to it.

Does anyone else have any opinions/suggestions. I once had to chain to a
hardware interrupt. I wrote some general purpose C routines, and an assembly
program callable from C that will let me chain any C routine to any interrupt
vector. Is there a better way?


-- 
Tom Rosenfeld	 	@ AT&T Information Systems Labs, Middletown, NJ
			(201) 957-5867 	
			UUCP:		{harpo,ihnp4,burl,akgua}!mtgzz!rosen
Disclaimer: I don't claim anything.