Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!wrdis01!gatech!purdue!haven!umd5!vbob
From: vbob@umd5.umd.edu (Bob Shields)
Newsgroups: comp.sys.mac.apps
Subject: Re: Excel on LC
Summary: ver 2.2a works fine
Message-ID: <8455@umd5.umd.edu>
Date: 19 Apr 91 23:35:07 GMT
References: <71577@eerie.acsu.Buffalo.EDU> <1991Apr18.071839.27937@news.iastate.edu> <1991Apr19.163343.28788@planck.uucp>
Reply-To: vbob@umd5.umd.edu (Bob Shields)
Organization: University of Maryland, College Park
Lines: 24

In article <...> westley@orion.uucp (Terry J. Westley) writes:
>  [previous articles deleted...]
>
>Is it only later versions of Excel which require the coprocessor?  I
>have an SE on which I run an earlier version, perhaps 1.05.  Will I have
>to trash or upgrade my SE if I get the upgrade to Excel that I was
>considering?
>
>-- 
>Terry J. Westley 
>Calspan Corporation, P.O. Box 400, Buffalo, NY 14225
>westley%planck.uucp@acsu.buffalo.edu | "planck!hercules!westley"@acsu.buffalo.edu

No, no, no...  Excel never "required" a FPU to run.  The problem excountered
on IIsi and LC machines was that Excel mistakenly assumed they had a FPU,
and therefore blew up when it tried to execute floating-point code.  This
has been fixed in version 2.2a (note the 'a').  Excel can work fine on
non-FPU equipped machines, it just needs to know there isn't an FPU!

Bob Shields
vbob@umd5.umd.edu

-- 
Bob Shields		 vbob@umd5.umd.edu