Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!oliveb!felix!kehr
From: kehr@felix.UUCP (Shirley Kehr)
Newsgroups: comp.sys.mac
Subject: Re: MS Word died in strange disease!
Message-ID: <75410@felix.UUCP>
Date: 19 Dec 88 14:48:08 GMT
References: <425@tekn01.chalmers.se>
Sender: daemon@felix.UUCP
Reply-To: kehr@felix.UUCP (Shirley Kehr)
Organization: FileNet Corp., Costa Mesa, CA
Lines: 33

In article <425@tekn01.chalmers.se> d83_sven_a@tekn01.chalmers.se (Sven (Sciz) Axelsson) writes:
 
<My MS Word 3.02 has suddenly died for me! It all started last week when it
<started to beep just after displaying its startup alert. After that it worked
<normally.
<Well, I thought I could live with this but when I tried it today
<it bombed (ID 02) at the same point in its startup. What has happened??
 
<Has anyone but me been struck by this strange behaviour? If so, please
<let me know of a cure...
 
<Sven Axelsson			d83_sven_a@tekn01.chalmers.se

I'm running MS Word 3.02 with Suitcase II at work with no problems, but I
got this same ID=2 last night. It wasn't a bomb, just the Microsoft Word
has unexpectedly quit message. I do run in multifinder on System 6.0.2, so
maybe that's the difference.

I don't know if this ID is the same as the bomb ID, which is an out of
range memory request, but just for a test I gave Word more memory (425
instead of 384). After that I had no problems, but I didn't run Word
all that long.

Another disclaimer: My Mac was just back from the repair shop where they've
been trying to track down the excessive bombs in the Levco Monster Mac
logic board. I was just trying to see how long it would run before bombing
again. 

When running MS Word, make sure that it is the first application you start
so it gets all of its memory from the first megabyte. This is one of Word's
most serious problems for me.

Shirley Kehr]