Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!cbosgd!osu-eddie!elwell%tut.cis.ohio-state.edu
From: elwell%tut.cis.ohio-state.edu@osu-eddie.UUCP
Newsgroups: comp.sys.mac
Subject: Re: System Error 33
Message-ID: <3785@osu-eddie.UUCP>
Date: Fri, 10-Jul-87 10:55:08 EDT
Article-I.D.: osu-eddi.3785
Posted: Fri Jul 10 10:55:08 1987
Date-Received: Sun, 12-Jul-87 11:15:52 EDT
References:  <3519@ecsvax.UUCP>
Sender: news@osu-eddie.UUCP
Reply-To: elwell%tut.cis.ohio-state.edu@osu-eddie.UUCP (Clayton Elwell)
Organization: The Ohio State University, CIS Dept.
Lines: 26

In article <3519@ecsvax.UUCP> wmcb@ecsvax.UUCP (William C. Bauldry) writes:
>>Stump the Stars: what dis the "DS" in "DSErrCode" originally stand for?
>>
>
>... there's also this thought of D*** S*** that I've
>heard a time or two (or 10^20) whilst programming...
>I've got this land in Florida that I'd like to talk to you about...
>hm?

Well, I dug up my ancient babylonian copy of Inside Mac (you know, the one
that talks about the "new ROMs" being version 7.0--the ones they put in the
Mac 128K).  There is a page, evidently a printout of an assembler header
file, that lists all of the values for DSErrCode.  Sure enough, the list
is headed by the comment "Deep Sh*t Error Alerts".  I can see why the
published version was switched to say "Dire Straits," but I still think the
original was more in the spirit of what you feel when you see a system bomb
while debugging...


-=-

Clayton Elwell

Arpa/CSNet:	Elwell@Ohio-State.ARPA
UUCP:		...!cbosgd!osu-eddie!elwell
Voice:		(614) 292-6546