Weird OS 9 bootup problem
I'm asking for my grandfather, who is having to use 9 for his music notation software (no, switching to a X-friendly tool is not an alternative).
Does anybody have an idea, of why 9 seemingly randomly bombs itself to death stating "Bus-error" on startup? I've seen this problem before, but then it showed up every time I tried, which is not the case of my grandfather, where it sometimes boots up fine, and bombing, varying from 1 out of 4, to every second tries...
Any ideas? Reinstall the whole OS 9 thing?
oh and btw. OS X and OS 9 is installed on separate partitions... on his LCD iMac.
Does anybody have an idea, of why 9 seemingly randomly bombs itself to death stating "Bus-error" on startup? I've seen this problem before, but then it showed up every time I tried, which is not the case of my grandfather, where it sometimes boots up fine, and bombing, varying from 1 out of 4, to every second tries...
Any ideas? Reinstall the whole OS 9 thing?
oh and btw. OS X and OS 9 is installed on separate partitions... on his LCD iMac.
Comments
never been able to fix it...
bbs
- bad or outdated system extension
- extensions conflict
- outdated application using low-level system functions
- corrupted application.
If your Mac throws bombs at you mostly at start-up, this is likely an extension conflict. You are especially lucky if all bus errors occur at the same moment, i.e. when one and the same extension/control panel's icon is the last before the bomb.Otherwise you have to resort to trial and error. During OS 9 start-up hold down the space bar until Extensions Manager shows up. From the pop-up near the top of the window select "Mac OS 9.x Base". Try working with this set a little and rebooting several times until you feel it works fine. Then try the set "Mac OS 9.x All". If it still works without bombs, blame 3rd party extensions. Try adding them one by one and booting a couple of times until you add a conflicting extension. Read more about it. Examine its system requirements. Download the latest version. In most cases all extensions conflicts are well known.
Useful tools are Extension Overload and Conflict Catcher.
I hope this helps.