Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site reed.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!decvax!tektronix!reed!bart
From: bart@reed.UUCP (Bart Massey)
Newsgroups: net.micro.mac
Subject: Re: Error Messages (Re: Could Not Print MacDraw Document)
Message-ID: <2859@reed.UUCP>
Date: Sat, 22-Mar-86 03:00:51 EST
Article-I.D.: reed.2859
Posted: Sat Mar 22 03:00:51 1986
Date-Received: Wed, 26-Mar-86 03:14:57 EST
References: <9647@ucla-cs.ARPA> <4281@dartvax.UUCP>
Organization: Reed College, Portland, Oregon
Lines: 22

> > Instead the error reply was "The print was not successful", or some
> > equally enlightening message.
> > ...
> > Are you listening?  I love your product, but this error message
> > needs more DETAIL.  
> > Arthur Goldberg
> 
> Hell, while you're at it, how about my favourite annoying error message
> from MacWrite:  "MacWrite is unable to print this document."
> ... 
> I have a theory as to why, though.  Both applications are trying to work
> in 128K.  Something has to be sacrificed.
> "A penny for your thoughts, my dear..."              Peter Merchant

No, you'll have to do better than that.  The whole point of the resource
manager is to make things like error messages live on disk until they
need to be paged in.  The only ones that should have to live in memory
are the ones that tell you the resource manager isn't working...  I've
done it -- it's not hard.

						Bart Massey
						..tektronix!reed!bart