Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!usc!bloom-beacon!bu-cs!bucsb!bear From: bear@bucsb.UUCP (Blair M. Burtan) Newsgroups: comp.sys.amiga Subject: Guru explanation needed Message-ID: <3142@bucsb.UUCP> Date: 19 Aug 89 17:50:03 GMT Reply-To: bear@bucsb.UUCP (Blair M. Burtan) Organization: Boston Univ Comp. Sci. Lines: 31 I need some guru number explanations. 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. I'm assuming that GOMF doesn't catch these because I've got low-vector checking off. But what I want to know is why the system crashes in the first place and why I get a guru AFTER a reset. -- ------------------------ Signature Version 0.4 ------------------------------ "He's showing signs of pressure-induced psychosis and he has a nuclear weapon." "Raise your hand if you thought that was a 'Russian water tentacle'." - The Abyss Blair "Bear" Burtan, Boston University's Resident Amiga Expert which isn't saying much. My opinions blah blah blah... bear@bucsb.bu.edu bear@bucsf.bu.edu bear@buengf.bu.edu bear@bu-pub.bu.edu enge05c@buacca.bu.edu -----------------------------------------------------------------------------