Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!brutus.cs.uiuc.edu!apple!bridge2!ngg From: ngg@bridge2.ESD.3Com.COM (Norman Goodger) Newsgroups: comp.sys.mac Subject: Re: Beware: MICROSOFT FLAME Message-ID: <868@bridge2.ESD.3Com.COM> Date: 16 Aug 89 16:57:23 GMT References: <2409@husc6.harvard.edu> Reply-To: ngg@bridge2.3Com.com (Norman Goodger) Organization: 3Com Corp., Mt. View, CA Lines: 23 In article <2409@husc6.harvard.edu> kolodny@husc4.UUCP writes: >To all Microsoft Excel 1.5 users, and concerned citizens: > >I don't usually flame about software companies, but I just had an >experience at the MacWorld Industry Day which really angered me. As a >Microsoft Excel 1.5 owner who just purchased a Mac IIcx, I noticed that my >version of Excel did not print the "running 6888x coprocessor" message >which it prints upon startup on the Mac IIs here at work. I figured that >the version of Excel did not print out the message because it found a 68882 >instead of a 68881, but it used it nonetheless. There is a CDEV called Cache Control I think that includes a way to automatically patch Excel so that it knows about the 882. Not sure specfically how it works, but it appears to. There has also been patches posted that you can do to Excel that will also solve this problem. If someone has those patches somewhere, It might be good to repost them for those that do not want to use 2.2 with 030 machines. -- Norm Goodger SysOp - MacInfo BBS @415-795-8862 3Com Corp. Co-SysOp FreeSoft RT - GEnie. Enterprise Systems Division (I disclaim anything and everything) UUCP: {3comvax,auspex,sun}!bridge2!ngg Internet: ngg@bridge2.ESD.3Com.COM