CRITICAL ERROR ROUTINE ARGS

Article View: comp.sys.atari.st

Article #41576

#41576

From: cs325ec
Date: Tue, 06 Mar 1990 01:41

22 lines
769 bytes


	OK, now I can trap errors by setting 0x404 to point to one
	of my own subroutines...  But...  What sort of arguments
	should my routine accept?  

	I tried

	int criterr(void)
		{
		}


	and long criterr(void)
		{
		}

	but I am just guessing... and they don't work.  Can someone
		tell me what to expect from the 0x404 jump?

		Thanks.
				-- Greg

Technical Details

Message-ID: <16000020@ux1.cso.uiuc.edu>

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!ux1.cso.uiuc.edu!ux1.cso.uiuc.edu!cs325ec

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!ux1.cso.uiuc.edu!ux1.cso.uiuc.edu!cs325ec
From: cs325ec@ux1.cso.uiuc.edu
Newsgroups: comp.sys.atari.st
Subject: CRITICAL ERROR ROUTINE ARGS
Message-ID: <16000020@ux1.cso.uiuc.edu>
Date: 6 Mar 90 01:41:56 GMT
Lines: 22
Nf-ID: #N:ux1.cso.uiuc.edu:16000020:000:351
Nf-From: ux1.cso.uiuc.edu!cs325ec    Mar  5 14:46:00 1990