Bolo Crashing on Mac Classic

Any version of Bolo that I try to run on my recapped Mac Classic crashes in the tutorial (address error), and Internet Bolo Buddy crashes immediately (unimplemented trap) and will not start. Things I've tried:
  • I installed MacsBug and that allowed me to somewhat get past the crashing in Bolo by continuing program execution every time it happened, but it didn't help with the Bolo Buddy.
  • I've tried it with minimal 6.0.8, and also 7.1 and 7.5.5 with extensions. Same result in every OS.
  • I've tried the versions of the game included with MacPack (0.99.2, 0.99.7bv, Plus Pack 1.0) and also a fresh download of Plus Pack 1.0 copied over from another volume.
  • I installed the AppleTalk driver included with 0.99.2.
I have not installed any additional brains. Other games from MacPack have been running just fine. I'm using BlueSCSI v2 with the latest firmware to load my files and run my OS.
Anyone have any ideas at all?
Edit: forgot to mention I've got 4MB of RAM.
 
Last edited:
When you drop to MacsBug, what's the error that halts execution? Since I've had no issues with Bolo on other hardware, I suspect you've got some sort of niggling hardware error, and the crash report might shed light on what it is.
 
Never had an issue, either. With an address error, is it possible that you have some bad RAM, or at the least an iffy connection to some of the built-in RAM? Any other issues at all with any other applications?
 
When you drop to MacsBug, what's the error that halts execution? Since I've had no issues with Bolo on other hardware, I suspect you've got some sort of niggling hardware error, and the crash report might shed light on what it is.
In a coincidence, I just saw your post on the Garden >2 years ago under the Bolo page, and I actually do have a compiled version of the bolorama UNIX executable that I use to host a server.
 
When you drop to MacsBug, what's the error that halts execution? Since I've had no issues with Bolo on other hardware, I suspect you've got some sort of niggling hardware error, and the crash report might shed light on what it is.
I'll take a picture when I'm home tonight.
Never had an issue, either. With an address error, is it possible that you have some bad RAM, or at the least an iffy connection to some of the built-in RAM? Any other issues at all with any other applications?
I've tested my RAM using some Apple diagnostic tool and it came back OK.
 
I'll take a picture when I'm home tonight.

I've tested my RAM using some Apple diagnostic tool and it came back OK.
The other question I’d ask is are there any extensions you are running in common between the systems that mess with the RAM at any sort of way?
 
It is supported on the Plus and up, so it should work without issue as you are saying.
Although I would note that even though it's supported, the Classic is NOT the platform for a serious Bolo player! We used to have LAN parties, playing Bolo until 3:00am and my poor Classic had a hard time keeping up with faster Macs. Way too much lag for a truly competitive Bolo player!
 
Although I would note that even though it's supported, the Classic is NOT the platform for a serious Bolo player! We used to have LAN parties, playing Bolo until 3:00am and my poor Classic had a hard time keeping up with faster Macs. Way too much lag for a truly competitive Bolo player!
Hah... we used to have Mac Plus LAN parties where running the slower hardware was part of the challenge! Then there'd be someone on the LAN with a faster Mac and larger screen acting as the spectator's lounge so that those who'd already lost could watch the rest of the game in more comfort.
 
Phht, adespoton…. Sure I used to try to pedal my bike to turn a dynamo to run my Classic to keep up with my pals, who had fast Macs AND actual mains electricity. Occasionally, lightning would strike and I could even see what was going on on the Classic! Otherwise, I’d never have known that I had lost.

(We all need a laugh — thanks.)
 
Playing Bolo on a 9" screen was an art form -- limiting everyone to a small visible playing field tended to affect strategy quite a bit. A lot more sneaking up through the forest happened; personally, I found it more enjoyable than everyone on 24" colour monitors with brains aware of everything, where it was just an all-out fight and a race to see who moved in the right direction soonest.
 
Playing Bolo on a 9" screen was an art form -- limiting everyone to a small visible playing field tended to affect strategy quite a bit. A lot more sneaking up through the forest happened; personally, I found it more enjoyable than everyone on 24" colour monitors with brains aware of everything, where it was just an all-out fight and a race to see who moved in the right direction soonest.
What version of Bolo were you playing? I don't recall being able to see more of the map - I just booted my LC575 and SE/30 side by side and they show the same game area. It would be a pretty unfair advantage to be able to see more.
 
What version of Bolo were you playing? I don't recall being able to see more of the map - I just booted my LC575 and SE/30 side by side and they show the same game area. It would be a pretty unfair advantage to be able to see more.
Yes, regardless of what machine you play on, the game window is always the same size. It would have been pretty cheap had it been otherwise.

Now, with a larger screen, you likely could have had the overview map AND the game window open simultaneously without one blocking the other...that may be what he he referring to.
 
Back
Top