Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!caip!nike!cad!ucbvax!hplabs!oliveb!glacier!cascade!leeke
From: leeke@cascade.ARPA (Steven D. Leeke)
Newsgroups: net.micro.mac
Subject: Re: Multiplan 1.1 Update - Problems with Crashes
Message-ID: <113@cascade.ARPA>
Date: Tue, 10-Jun-86 10:23:54 EDT
Article-I.D.: cascade.113
Posted: Tue Jun 10 10:23:54 1986
Date-Received: Sat, 14-Jun-86 04:08:25 EDT
References: <110@cascade.ARPA> <14250@ucbvax.BERKELEY.EDU>
Reply-To: leeke@cascade.UUCP (Steven D. Leeke)
Distribution: net
Organization: Stanford University Computer Systems Laboratory
Lines: 24
Keywords: ID 2, ID 25 errors galore

In article <14250@ucbvax.BERKELEY.EDU> shebanow@ernie.Berkeley.EDU.UUCP (Mike Shebanow) writes:
>
>For, what it is worth, the crashes are NOT Microsoft's fault. The system that
>was shipped with the Multiplan update (3.1, I believe), had a memory
>management bug which would crash Multiplan in exactly the way you described.
>
>To fix this problem, get a copy of Finder 5.2, System 3.1.1, and the companion
>HD20 file, and put them on your Multiplan disk. Better yet, wait a week or two
>for a dealer (or a friend) to get you System 3.2.
>
>Good luck...
>
>Andy

But I AM running system 3.1.1 and Finder 5.2 and the latest HD20 I could find.
If system 3.3 and finder 5.3 will fix things I guess I will have to wait.  I
am running off the Mac 10 and w/ the upgrade Multiplan 1.1 the HD install 
utility means that Multiplan NEVER should see the system it was shipped
with.  The bombs occur w/ the 3.1.1 system.

Still at a loss for a explanation,

Steve Leeke
leeke@cascade.stanford.edu