Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!think!mintaka!bloom-beacon!bu.edu!bu-cs!dartvax!eleazar.dartmouth.edu!isle
From: isle@eleazar.dartmouth.edu (Ken Hancock)
Newsgroups: comp.sys.mac
Subject: Re: Some Human Interface (was: System Error = 03)
Message-ID: <19253@dartvax.Dartmouth.EDU>
Date: 9 Feb 90 04:27:23 GMT
References: <33777@news.Think.COM> <5415@bgsuvax.UUCP>
Sender: news@dartvax.Dartmouth.EDU
Organization: Computer Resource Center, Dartmouth College
Lines: 26

In article <5415@bgsuvax.UUCP> denbeste@bgsuvax.UUCP (William C. DenBesten) writes:
>I think that the average user would find it helpful if the follwing
>ones (for example) were reported textually.
>
>	Memory Corupted  	id=28	DSStkNHeapHeap

Ok, I'll bite.  "Uh-oh...the memory in my computer is bad.  Does that
mean I have to have my Mac repaired."
(Don't laugh...that's exactly what some people would thing...)

>	Memory Full	 	id=25	DSMemFullErr
>	Application Damaged	id=16	DSBadLaunch
>	Application Damaged	id=15	DSLoadErr

These errors, as with most, can be generated by other things going wrong
so that the System really doesn't know what's going on... in many cases
the ID of the System Error is completely irrelevant as to why it happened.

Ken


--
Ken Hancock '90            | DISCLAIMER: I'm graduating and looking for
Consultant                 |             a job, so I'll stand by my words.
Computer Resource Center   |==============================================
Dartmouth College          | EMAIL: isle@eleazar.dartmouth.edu