On 8/26/06, aliensrcooluk at yahoo.co.uk <aliensrcooluk at yahoo.co.uk> wrote: I think what the OP meant was functionally like a blue screen on an MS OS, not visually identical to one, in this case, the answer is, "sorta-kinda-mostly", at least from the standpoint that it was the last thing you get to see before resetting the machine. In any case, the entire screen may or may not be black, depending on the nature and severity of the cause - with some errors, the entire screen was slid down enough to make room for the Guru Meditation box, which had a blinking red border and red text inside (red it fatal, yellow if not, but that was rare). There _could be_ a "Software Failure" requester box with "press mouse button to reset", but that was _prior_ to a Guru Meditation screen, not the Guru Meditation itself. Those are examples of 68000 trap error codes... 80000003 in particular happens to be the odd address trap that started things off (it was rather common, especially if your code went off into the weeds and tried to execute an instruction on an odd-byte boundary). There were also _lots_ of error codes that could tell you specifics about what really went wrong, but unless you had the Rom Kernel Manual (RKM) handy or did a lot of development, people ignored the numbers. Either "HELP" in ASCII (0x48454C50) or the address of the process that was running when the machine puked. It was only useful if you were a developer and used it to fire up ROMWack (an internal debugger) to sift through the remains of your process to see what it was doing when something went wrong. Mostly, though, the second number wasn't particularly helpful. Yeah.... typically, if you got a recoverable error, something was likely to happen shortly thereafter that wasn't recoverable. -ethan