[jellybeanboy1]

When I click to go to the multiplayer mode, Halo unexpectedly quits and dumps me back into the Finder. I had been playing online for a while and quit, came back, opened Halo back up, and it now refuses to allow me to play multiplayer. I reinstalled it but it still happened, so I installed it on my other iMac; eventually the same thing happened. What now?
This is the top-ish section of the crash.log for any of you Apple Genius Bar types out there.

OS Version: 10.2.8 (Build 6R73)

Command: Halo
PID: 559

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000010

[beeblebrox]

Indeed I have the same problem only it happened from the first time I ran the game. It works fine on my dual 1.25 G4 but not on my son's identical machine.

Same problem under Panther or Jag. Pulled all the RAM but the original 256 stick (normally it runs with another 3 512mb sticks). No difference, still crashes when selecting MP.

-B

[Camali]

I had the same problems with Halo. I had installed on my G5 (Radeon 9800) and then copied my Halo file which contained all the levels I had already passed and when I loaded that up on an iMac (17-1.25G4) it crashed. Nothing I did seemed to fix until I realized that it could have just been that moving a 'preference' for Halo which expected a Radeon 9800 with whatever settings I used on the G5 (high textures, high res models, etc) could not be handled by the iMacs NVidia chip.

OR

That I had set the program to run at Full screen and later changed it to run in a window.

So you might want to change the settings (in the window that pops up before Halo runs) to see if that helps.

I hope it helps, while Halo is a nice, it just seemed a little short, but I just wish we didn't have to wait so long for it!

[jellybeanboy1]

Thanks. I've tried changing settings around and deleting the prefs, but it just seems to be a glitch. It won't let me into multiplayer just to spite me and I can't get back in until it "cools down." I'd guess all thats to be done is report it and wait for a patch?

[11011001]

This isn't really useful, but that console stuff looks like Halo tried to access memory it didn't own.

[aeneas07]

it has to do with the shaders option on the startup options screen. Try using vertical shaders only or no shaders and it should fix the problem. If you checked the box to not show that options screen again you can trash the prefs file and it will come back, you will need to input your product key again though.

[NeXTLoop]

In my case my video card doesn't support shaders, and it still crashes. So I'm not sure that's the solution.

[NeXTLoop]

Here's the solution:

In the initial dialog box that shows up when you start Halo, input your I.P. address in the I.P. address field. That should take care of it.

[beeblebrox]

Originally posted by NeXTLoop:
Here's the solution:

In the initial dialog box that shows up when you start Halo, input your I.P. address in the I.P. address field. That should take care of it.

Matt- You're a genius. After trying every trick in the book (swapping graphics cards, taking out ram, reinstalling the OS, etc.) this is the solution that works!

What is odd is that the lack of an IP address does not affect that many people (I know of three Macs that work fine with Halo w/o the IP field being filled in. Weird.

Thanks for the solution!


-B

[NeXTLoop]

Wish I could take credit. I actually saw somebody recommend this on the MacAddict game forums, and thought I'd pass it along.

Glad it worked for you too.