Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!uupsi!sunic!liuida!isy!lysator.liu.se!mabac From: mabac@lysator.liu.se (Mattias Backen) Newsgroups: comp.sys.amiga.programmer Subject: Re: Unknown GURU numbers Message-ID: <537@lysator.liu.se> Date: 17 Mar 91 03:25:23 GMT References: <1991Mar10.072019.15764@zorch.SF-Bay.ORG> <18d1cfcc.ARN0b7a@swinjm.UUCP> Sender: news@isy.liu.se (Lord of the News) Organization: Lysator Computer Club, Linkoping University, Sweden Lines: 23 forgeas@swinjm.UUCP (Jean-Michel Forgeas) writes: >In article , Kenneth Yarnall writes: >> In article <1991Mar10.072019.15764@zorch.SF-Bay.ORG> mike@zorch.SF-Bay.ORG (Mike Smithwick) writes: >> >[] >> > >> >Is there a more complete source of GURU numbers than alerts.h? I'm always >> >getting ones which aren't listed. Just what the heck is 0x00000003 and >> >0x0000000B? >> >> _Mapping the Amiga_ by Anderson and Thompson (Compute Books, 1990, ISBN >> 0-87455-195-1) has a bunch on them in an appendix (well, all the ones I've >> ever gotten, anyway :). It lists 00000003 as implying an Adderss error (a CPU >> exception, and 0000000B as Op code 1111. I had some trouble knowing what the gurunumber meant too before, but not anymore :') There's a PDprogram called "guru" which gives you a very short explanation of any gurunumber. Short but it's better than nothing and usually enough. Unfortunately I don't know which Fish it's on, but if you can't find it, mail me and maybe I can fix it. -- Mattias Backen. mabac@Nanny.Lysator.LiU.SE