Path: utzoo!utgpu!watserv1!watmath!att!pacbell!pacbell.com!decwrl!mips!apple!claris!wombat From: wombat@claris.com (Scott Lindsey) Newsgroups: comp.sys.apple2 Subject: Re: Appleworks GS Questions Keywords: insure, emphysematous, renown, conjoint Message-ID: Date: 8 Sep 90 21:19:19 GMT References: <9008291701.AA17270@apple.com> <13176@netcom.UUCP> Sender: wombat@claris.com Organization: Claris Corporation, Santa Clara, CA Lines: 28 In-reply-to: avery@netcom.UUCP's message of 4 Sep 90 01:16:46 GMT Subversive: fissionable In article <13176@netcom.UUCP> avery@netcom.UUCP (Avery Colter) writes: > > and then, after pressing the dialog button, we get another dialog box > > with the message "A serious system error has occurred" and the machine > > has to be rebooted. > Did the machine give you an error number? The described dialog will never give you an error number. It gets displayed when AWGS hits a BRK or COP instruction and there's no handler previously installed (like a debugger). In fact, it's not really a dialog but a call to TLMountVolume. It was simply deemed friendlier than crashing into the monitor for the average user, especially when the monitor is on the text screen and the SHR is up. At least the user knows he's crashed. As for the bug that's causing the crash... I can't help you immediately, but I've forwarded the info (that I deleted from this message :-) about DB reports to someone who'll have a better idea than I about what might be happening. Additional note: if you **really** want to get into the monitor from the aforementioned dialog, hold down the option and apple keys when you hit the restart button (or hit return). I can't guarantee whether all the registers are valid, because I use FWEntry to get back to the monitor. -- Scott Lindsey | I dig iguana in their outer space duds Claris Corp. | saying, "Aren't you glad we only eat bugs?" ames!claris!wombat| DISCLAIMER: These are not the opinions of Claris, Apple, wombat@claris.com | StyleWare, the author, or anyone else living or Dead.