Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!brutus.cs.uiuc.edu!apple!bridge2!3comvax!tymix!tardis!jms
From: jms@tardis.Tymnet.COM (Joe Smith)
Newsgroups: comp.sys.amiga
Subject: Re: Guru explanation needed
Summary: Beware of booby-trapped 'cracker' disks.
Message-ID: <540@tardis.Tymnet.COM>
Date: 25 Aug 89 06:57:29 GMT
References: <3142@bucsb.UUCP>
Reply-To: jms@tardis.Tymnet.COM (Joe Smith)
Organization: McDonnell Douglas Field Service Co, San Jose CA
Lines: 23

In article <3142@bucsb.UUCP> bear@bucsb.UUCP (Blair M. Burtan) writes:
>Here's the scenario:  I'm playing w/ my 2 meg A1000 shuffling between CLI
>and WB to look at the several dozen PD disks I have.  I'd pop in a disk in
>df1:  look at it in WB for nifty things, then in CLI for non-WB programs,
>eject the disk, put in a new one and double-click it.  POOF.  The power
>light flashes.  I reset the machine and I get a guru number like
>00000004.002292A0 or 9030 or 9250.  Now, I'm running GOMF3.0.

Someone else already mentioned the interaction between LESS 1.3 vs GOMF 3.0.
Here is an additional possible cause of a GURU from inserting a disk.

A year ago I received a floppy full of disk copying programs that was booby
trapped.  You could run the programs if you booted from that floppy and knew
what to type at its CLI.  (Typing DIR or LIST produced "This is not a
workbench disk, dummy!".)  Typing "DF1:C/DIR DF0:" produced an instant GURU.
If I rebooted from a disk that did a LOADWB and then inserted that disk,
Workbench went looking for .info files and triggered the guru.  I reformatted
that disk.
-- 
Joe Smith (408)922-6220 | SMTP: JMS@F74.TYMNET.COM or jms@tymix.tymnet.com
McDonnell Douglas FSCO  | UUCP: ...!{ames,pyramid}!oliveb!tymix!tardis!jms
PO Box 49019, MS-D21    | PDP-10 support: My car's license plate is "POPJ P,"
San Jose, CA 95161-9019 | narrator.device: "I didn't say that, my Amiga did!"