Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!cs.utexas.edu!rutgers!cbmvax!cbmehq!cbmswi!cbmcel!stoller
From: stoller@cbmcel.UUCP (Martin S. Stoller)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Help --> How to prevent the visit from the dreaded guru
Message-ID: <205@cbmcel.UUCP>
Date: 8 Jan 91 12:51:41 GMT
References: <611@caslon.cs.arizona.edu> <1991Jan4.203339.8800@maytag.waterloo.edu> <V2H++Q_@irie.ais.org> <1991Jan7.110218.9448@marlin.jcu.edu.au>
Reply-To: stoller@cbmcel.UUCP (Martin S. Stoller)
Organization: COMMODORE ELECTRONICS LIMITED
Lines: 27

In article <1991Jan7.110218.9448@marlin.jcu.edu.au> glmwc@marlin.jcu.edu.au (Matt Crowd) writes:
>In article <V2H++Q_@irie.ais.org> jph@ais.org (Joseph Hillenburg) writes:
>>Does anyone know how to FORCE a guru through C? What includes, etc, and
>>maybe a ForceGuru() call? I have a program where if you enter an incorrect
>>response, it is supposed to guru. Does anyone have a sure-fire routine?
[CODE DELETED]
>I used this, or something similar once to crash the Amiga when a
>password protection failed.  Takes ages though.  Suggestions
>for a better crash would be appreciated.  Maybe copying the   
>screen bitmap into the Exec structure....
>:-) :-) :-)
>>        Joseph Hillenburg, Secretary, Bloomington Amiga Users Group
>>iuvax!news!valnet!joseph        jph@ais.org          anlhille@iubacs.BITNET
>>       "Only Apple could slow down a 68030 chip" --Computer Shopper
>Colin.

Hmmm... As long as no GURU catchers are watching, then x=5/0; works fine.
Try it.  (If your compiler is SO SMART that it catches that mistake, then use
variables instead...)  This fires off the DIVIDE THRU NULL interuppt.  It works,
most of the time.  Now WHY would anyone want to GURU the AMIGA?  You testing a
new GURU TRAP or somethin'?


-- 

   Regards,
   UUCP: [{(uunet|pyramid|rutgers)!cbmvax}!cbmehq!cbmcel!stoller