• Updated 2023-07-12: Hello, Guest! Welcome back, and be sure to check out this follow-up post about our outage a week or so ago.

Bomb error messages

cjtmacclassic

Well-known member
hi all

ever since i got my Macintosh classic, i have noticed that if i leave it on and don't move any thing, it will go into screensaver mode. when i move the mouse it stops the screensaver and it displays a bomb window that says "coprocessor not installed". then, it asks me to restart. how do i fix this, and if i can't fix it, is there any way to continue without restarting?

-CT

 

Mac128

Well-known member
how do i fix this, and if i can't fix it, is there any way to continue without restarting?
You will save a lot of time if you provide as much detailed information as possible. First, there is no way to continue without restarting so you must fix this.

Second. There is an incompatibility with the System, Screen Saver software, or other "extensions" depending on the System version you are running. The only way to help you is for you to give a detailed list of items installed running in your Classic System and what ScreenSaver you are trying to run. The most likely answer, and one you don't want to hear is that the System you want to run is incompatible with the Screen Saver which most likely requires an older or newer System version. Alternatively you may be able to find a more compatible version of the screen saver software.

 

porter

Well-known member
Did you do a complete install of OS from scratch or are you running gods knows what from god knows where?

 

Bunsen

Admin-Witchfinder-General
Turn the screensaver off or remove it. Then investigate other, compatible screensavers.

 

cjtmacclassic

Well-known member
well, i tried removing the screensaver, and even if it's running something like MS word and the mouse is moved, it still does it.

Tech specs:

moire screensaver, system 7.1, 40 mb hd, 1.4mb superdrive,, 4mb ram

 

Scott Baret

Well-known member
Since you're running System 7 there is an easy way to see if an extension or control panel (sometimes referred to as INITs and cdevs by old-timers) is causing a conflict. Start up with the shift key down. You'll want to press it shortly before the Happy Mac appears and keep holding it down until the "Welcome to Macintosh" screen displays. The screen will display a message stating that extensions are off.

If it works fine without extensions, re-introduce each one one at a time until you can pinpoint the cause. When you find the suspect, move it out of the system folder and keep it out, adding the rest back to the system folder (although I'd still recommend the one at a time approach just in case there are two extensions causing problems). Keep in mind that two extensions may also be conflicting with each other, so if you have some extra time it may be worth starting up with different extension sets (which is possible with some of the INIT managers out there, such as Ricardo Batista's Extensions Manager).

If the problem persists without extensions, try booting up from another disk or the Classic's ROM disk (hold down COMMAND-OPTION-X-O while starting up). This will let you know if your system file is corrupt. If it is, find your install disks and re-install the system. If you don't have install disks, Apple provides 7.0.1 and 6.0.8 on their website free of charge. (They also have 7.5.3, but I don't recommend it for a Classic I).

If all else fails, there's a chance it may be a faulty logic board (and if it is, chances are it's capacitor-related). I had a Classic that would intermittently freeze but once I replaced the logic board with a donor from a machine with a bad analog board everything worked fine. (I'm going to re-cap the old one or at least clean it in a dishwasher sometime).

I should also mention that the Moire screen saver is not a "suspect" cdev by any means. It was widely regarded as the best shareware screen saver during its day and I have yet to hear a report of any problems caused by it.

 
Top