• 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.

Need assistance with interpretation of Macsbugs error

retrobecanes

Active member
In a separate thread I have reported intermittent startup issues with my SE/30 (freezes at the welcome screen).  I have since installed Macsbugs 6.6.3 and when the freeze occurred again I pressed the interrupt button to invoke Macsbugs.  Macsbug reported the following error "the ROM symbol file could not be read due to an OS or memory issue".  Since I have been able to replicate the same intermittent issue with several different clean OS installs (7.1, 7.5.3 and 7.5.5), I tend to think that this is not due to an OS error.  On the other hand, extensive RAM tests with tools such as Snooper and MacTest Pro did not show any problem.  Could RAM still be responsible for this intermittent error (I have 32MB onboard) or could it be ROM?  Any assistance is greatly appreciated.

 

techfury90

Well-known member
No, it just means that you don't have a ROM symbol table file installed and configured for MacsBug. You don't need it to use MacsBug, it just assigns names to various locations within the system ROM. It's handy for debugging sometimes, but MacsBug doesn't need it.

It might also be that the OS is so frozen up that it can't service the request from MacsBug to load the symbol table properly.

 
Last edited by a moderator:
Top