Sys 7.5 Finder Error:"No Coprocessor"
Paul Banks
Billy Lee Myers, Jr. <ifz...@mcl.cc.utexas.edu> wrote:
>This is a strange one. I know three people who are getting this error
>with just-installed System 7.5:
>
>"Sorry, a Finder error occured. Floating point processor not found."
>
>Then the system crashes.
> ................
>Is there some step in the setup process that we are overlooking? Has
>anyone else had this problem?
>
I have had a similar problem on my 7100 when I went from 7.1.2 to 7.5.
Everytime I started ClarisWorks by holding down whatever key it is to
open an old document on startup and opened a commuications file I had,
I would get the no fpu error (ClarisWorks does not need an fpu). If I
let ClarisWorks come normally and then use cmd-O to open the file, no
problem. (Either way worked w/o problem under 7.1.2). It wasn't im-
portant enough to me to do much more about it. I used the system update
option to install 7.5 in my old system folder so that may have some-
thing to do with it.
BTW, my version of ClarisWorks is the native version and so my 7100
does have an fpu. Any other comments?
Paul Banks
pba...@llnl.gov
Simon Kidd
Billy Lee Myers, Jr. <ifz...@mcl.cc.utexas.edu> wrote:
>This is a strange one. I know three people who are getting this error
>with just-installed System 7.5:
>
>"Sorry, a Finder error occured. Floating point processor not found."
>
>Then the system crashes.
>
>and they don't have any control panels or inits except what came from
>Apple. Since we are all getting the same errors, quite often, I'm
>assuming other folks on the net are having the same trouble. Obviously,
>none of these machine have a coprocessor.
>
>Is there some step in the setup process that we are overlooking? Has
>anyone else had this problem?
>
>
>Billy
>
>
>-----
>Billy Lee Myers, Jr.
>Austin, Tx
>
I have seen the same thing with a PB180 which does have a coprocessor. It
was suggested that I have some crappy software or to zap the pram 3x.
I did the later but used TechTool. Things seem to have calmed down.
Simon
Pete Resnick
ifz...@mcl.cc.utexas.edu (Billy Lee Myers, Jr.) wrote:
> This is a strange one. I know three people who are getting this error
> with just-installed System 7.5:
>
> "Sorry, a Finder error occured. Floating point processor not found."
This is a silly error message. It only means that the currently executing
code in memory looked like a floating point coprocessor instruction and
the 680x0 chip said, "Huh?". That most likely means that the machine
starting executing some garbage in memory because of some broken system
extension and this is the best error message the system could come up
with.
As far as I know, nothing in 7.5 needs an FPU.
pr
--
Pete Resnick (...so what is a mojo, and why would one be rising?)
Doctoral Student - Philosophy Department, Gregory Hall, UIUC
System manager - Cognitive Science Group, Beckman Institute, UIUC
Internet: res...@uiuc.edu
John W. Baxter
(David Alcocer) wrote:
> res...@uiuc.edu (Pete Resnick) writes:
> >This is a silly error message. It only means that the currently executing
> >code in memory looked like a floating point coprocessor instruction and
> >the 680x0 chip said, "Huh?".
>
> I've seen this error occur on several PowerMacs--including my own. I've
> also seen an extension called "SoftFPC" (or something like that) that, by
> somehow "faking" the presence of a coprocessor, eliminates the problem. I
> used it on a 7100 this summer and those errors disappeared.
You're not "eliminating" the problem, you're masking it. The problem, in
turn, is not that Finder needs an FPU (it doesn't), but that some bogus
code (probably an old INIT) is scrambling memory, or otherwise causing
execution to wander into arbitrary memory. When the high-order byte of
the next "instruction" happens to be hex FF, you get the complaint about
needing an FPU.
--John
--
John Baxter Port Ludlow, WA, USA [West shore, Puget Sound]
Sorry...clever signatures require cleverness, not found here.
jwba...@pt.olympus.net
Billy Lee Myers, Jr.
with just-installed System 7.5:
"Sorry, a Finder error occured. Floating point processor not found."
Then the system crashes.
Pierre Fortin
In article <1994Oct18.125854.1258@rockyd> Simon Kidd,
ki...@rockyj.rockefeller.edu writes:
>In article <ifzb362-1710...@slip-b-9.ots.utexas.edu>,
>Billy Lee Myers, Jr. <ifz...@mcl.cc.utexas.edu> wrote:
>>This is a strange one. I know three people who are getting this error
>>with just-installed System 7.5:
>>
>>"Sorry, a Finder error occured. Floating point processor not found."
>>
>>Then the system crashes.
Well, you can add me to the list. Worse yet: the other day I got this
message every time I tried to boot up. Trying to boot without Extensions
resulted in a Line-F crash... So, no way to boot up my PB170 <SIGH>!!!
I booted from floppy and figuring 7.5 was damaged, I re-installed 7.5...
Surprise! NO CHANGE... Booting from the HD after removing ALL
Extensions and Control Panels still bombed... Then I removed everything
from the Preferences folder; now I could boot from the HD...(???)
>>One is a Powerbook 140, the others are LCIIs. They all have 8 megs of
ram
>>and they don't have any control panels or inits except what came from
>>Apple. Since we are all getting the same errors, quite often, I'm
>>assuming other folks on the net are having the same trouble. Obviously,
>>none of these machine have a coprocessor.
I also have 8M. What really hurts me is that I can not reliably run with
RAM Doubler; I get lots of random crashes... :^( I did not have these
problems with 7.1 Pro...
Before installing 7.5, I regularly went a week or more without rebooting.
I would only put the PB to sleep and take it home or to the office and
un-sleep... Since installing 7.5, I have suffered more crashes than I
have in the previous TWO YEARS. Needless to say, I am very pissed and
have contacted SOS-APPL for instructions on backing out to 7.1 Pro; I'll
be doing this shortly...
Just before heading out on a trip on Monday, I had 6 random
crashes/lockups in under one hour... :^(
Other problems include a message that "HP PrintMonitor" needs to be in
the System Folder; but that's PRECISELY WHERE IT IS!! <arghhhhh!!!>
This was OK under 7.1 Pro; in fact, after installing 7.5, I had to
re-install the HP drivers.
Trying to use my Dayna SCSI Ethernet adapter now results in missed
packets if the other device is too fast. I don't know if this is a Dayna
problem or 7.5; but I'm working with Dayna while suspecting 7.5... If
the other device responds in less than about 0.4ms (seen on Sniffer), my
PB does not see the packet...
At this point, I see no option but to back out; I can't afford the lost
time and productivity.
>>Is there some step in the setup process that we are overlooking? Has
>>anyone else had this problem?
>>
>>Thanks a million for any help.
>>
>>Billy
>>
>>
>>-----
>>Billy Lee Myers, Jr.
>>Austin, Tx
>>
>
>I have seen the same thing with a PB180 which does have a coprocessor. It
>was suggested that I have some crappy software or to zap the pram 3x.
>I did the later but used TechTool. Things seem to have calmed down.
Methinks the "crappy software" is System 7.5; BUT, as my signature says...
>Simon
Pierre
--
Pierre Fortin
Cisco Systems Inc., Suite 400, 14160 N. Dallas Parkway, Dallas, TX 75240
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Until you've found *and* fixed a problem, you can NOT discount *any*
possibility; what you gratuitously discount will likely be the source
of the problem(s)." Pierre Fortin - 1990
Nilson
NIlson
Simon Kidd (ki...@rockyj.rockefeller.edu) wrote:
: In article <ifzb362-1710...@slip-b-9.ots.utexas.edu>,
Billy Lee Myers, Jr.
> > I've seen this error occur on several PowerMacs--including my own. I've
> > also seen an extension called "SoftFPC" (or something like that) that, by
> > somehow "faking" the presence of a coprocessor, eliminates the problem. I
> > used it on a 7100 this summer and those errors disappeared.
>
> You're not "eliminating" the problem, you're masking it. The problem, in
> turn, is not that Finder needs an FPU (it doesn't), but that some bogus
> code (probably an old INIT) is scrambling memory, or otherwise causing
> execution to wander into arbitrary memory. When the high-order byte of
> the next "instruction" happens to be hex FF, you get the complaint about
> needing an FPU.
John,
Well, I've zapped my pram and withdrawn all inits except the ones from
Apple. No good. I then booted with disk tools and drug all the system
files to the trash and reinstalled Sys 7.5. Now everytime I quit an
application the system freezes.
I've successfully made the situation much worse.
Now a lesser man than myself would just blow off the 7.5 idea and go back
to useing my safe, boring, never-crashing 7.1 which has worked just fine
for me all these many months.
Let me ask you this one question. Would William Travis take the easy way
out? Would Harriette Tubbman loss her nerve? Would Theodore Rosevelt run
from a fair fight?
I don't think so.
That's why I'm going to stay after this until I've got it licked. You
might see my name here in the newsgroup pleading for your help. In the
name of freedom and liberty, I ask for your help.
God bless you, and God bless America!
John Harmon
installed all of the goodies, and everything worked fine. I then installed
StarNine's MailLink, ran the updater, and my Mac crashed every time upon
startup with this same message. In my case, the culprit was an "Installer
Cleanup" extension. What do these things do anyway, and can you delete
them? Well, deleting mine fixed my problem.
--
John Harmon
apl...@crl.com
Bruce Robinson
ifz...@mcl.cc.utexas.edu (Billy Lee Myers, Jr.) wrote:
> Well, I've zapped my pram and withdrawn all inits except the ones from
> Apple. No good. I then booted with disk tools and drug all the system
> files to the trash and reinstalled Sys 7.5. Now everytime I quit an
> application the system freezes.
>
> I've successfully made the situation much worse.
>
I cured this problem on a couple of installations on PB 160's by using the
System 7.5 disk tools to update the disk driver. In one case I ended up
having to reformat the drive, again using the 7.5 disk tools.
Bruce Robinson IT Manager
Graduate School of Business, University of Auckland
voice (64)(09) 373 7599 ext 5351, fax (64)(09) 373 7430
e-mail b.rob...@auckland.ac.nz
--
Distance is no barrier
Billy Lee Myers, Jr.
Banks) wrote:
> >"Sorry, a Finder error occured. Floating point processor not found."
> >
> >Then the system crashes.
---
> I have had a similar problem on my 7100 when I went from 7.1.2 to 7.5.
> Everytime I started ClarisWorks by holding down whatever key it is to
> open an old document on startup and opened a commuications file I had,
> I would get the no fpu error (ClarisWorks does not need an fpu).
> BTW, my version of ClarisWorks is the native version and so my 7100
> does have an fpu. Any other comments?
Paul,
The above error message should read: "Sorry system error "Finder"
Floating point processor not found." I'm thinking that something has
corrupted my finder. I don't know how this could happen, but I'm going to
try to reinstall and see if that helps.
This is very frustrating. I know two other people who are having the same
problem, and are as stumped as I am. We can't *all* have corrupted
Finders, can we? It really seems like an init conflict of some kind, but
I have been unable to isolate the problem to find the culprit.
If you find out any more information, I'd be internally indebted to you.
(I'm off to re-install.)
Billy Lee Myers, Jr.
(Simon Kidd) wrote:
> >"Sorry, a Finder error occured. Floating point processor not found."
> >-----
> >Billy Lee Myers, Jr.
> >Austin, Tx
> >
> I have seen the same thing with a PB180 which does have a coprocessor. It
> was suggested that I have some crappy software or to zap the pram 3x.
> I did the later but used TechTool. Things seem to have calmed down.
Simon,
I'll try anything! Since my problems seem to be Finder-inspired (after
saving or DropStuffing) I'm going to re-install the system. But maybe
I'll zap pram just for fun before going the more drastic route.
Thanks so much for the tip!
Hans-Christian Becker
with a Q840AV and certain programs, and it turned out to be the
disk drivers which were incompatible with SCSI Manager 4.3. I
think 4.3 is in ROM on the AVs and PMacs, and is included in system
7.5 (or does it need special SCSI chips to run on?). Anyway, this
was with system 7.1.2.
Good Luck,
Hans
---
Hans-Christian Becker
Dept. of Physical Chemistry
Chalmers University of Technology
---
If I only knew how to get this #$! signature feature working!
Larry Rosenstein
jwba...@olympus.net (John W. Baxter) wrote:
> In article <382uvp$9...@tuba.cit.cornell.edu>, da...@crux4.cit.cornell.edu
> (David Alcocer) wrote:
>
> > I've seen this error occur on several PowerMacs--including my own. I've
> > also seen an extension called "SoftFPC" (or something like that) that, by
> > somehow "faking" the presence of a coprocessor, eliminates the problem. I
>
> You're not "eliminating" the problem, you're masking it. The problem, in
> turn, is not that Finder needs an FPU (it doesn't), but that some bogus
In fact, you're not even masking the problem in all cases. You can still
get a coprocessor exception even if you have an FPU, since not all
possible words of the form Fxxx are legal FPU instructions.
Unless you know that the program in question uses floating point, the
cause of this error is jumping off into a random part of memory.
--
Larry Rosenstein
Taligent, Inc.