Forums | MacLife

i recently played it on my dad's 800 mhz powerbook, with some sort of crap 32 mb card and 10.2.8... i didn't run into any problems like that. did a dialog box pop up allowing you to see what kind of error happened? or is that only in 10.3? (where you can send a bug report to apple)

I did a little looking around, and found the halo crash log.  Here's what it looks like, over and over and over and over and over....



Date/Time:  2003-12-20 15:59:32 -0500
OS Version: 10.2.8 (Build 6R73)
Host:       Pamela-Shaws-Computer.local.

Command:    Halo
PID:        492

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

Thread 0 Crashed:
#0   0x00000000 in 0x0
#1   0x90133434 in CFURLCreateWithFileSystemPath
#2   0x90152eb0 in _CFBundleCopyExecutableURLInDirectoryWithAllocator
#3   0x9015ca8c in CFBundleLoadExecutable
#4   0xc00063e4 in __ape_internal
#5   0xc00082d8 in __ape_internal
#6   0x90148464 in __CFRunLoopDoObservers
#7   0x90180f40 in CFRunLoopRunSpecific
#8   0x969a3b70 in RunCurrentEventLoopInMode
#9   0x969b3a78 in ReceiveNextEventCommon
#10  0x969f2b5c in _AcquireNextEvent
#11  0x96ab4cf8 in RunApplicationEventLoop
#12  0x001a0830 in 0x1a0830
#13  0x001a158c in 0x1a158c
#14  0x001a1b50 in 0x1a1b50

Thread 1:
#0   0x90073ba8 in mach_msg_trap
#1   0x90005ed0 in mach_msg
#2   0xc0009190 in __ape_internal
#3   0xc0000efc in __ape_agent
#4   0x90020c28 in _pthread_body

Thread 2:
#0   0x90073ba8 in mach_msg_trap
#1   0x90005ed0 in mach_msg
#2   0x901489f0 in __CFRunLoopRun
#3   0x90180f58 in CFRunLoopRunSpecific
#4   0x9465315c in _ZN10HALRunLoop9OwnThreadEPv
#5   0x946593ac in _ZN9CAPThread5EntryEPS_
#6   0x90020c28 in _pthread_body

PPC Thread State:
  srr0: 0x00000000 srr1: 0x4000f030                vrsave: 0x00000000
   xer: 0x00000000   lr: 0x901335fc  ctr: 0x00000000   mq: 0x00000000
    r0: 0x00000000   r1: 0xbffff460   r2: 0x48802246   r3: 0x901c8fa0
    r4: 0x00077c30   r5: 0x00000000   r6: 0x00000000   r7: 0x00000040
    r8: 0x00000001   r9: 0xa0130938  r10: 0x00051dd0  r11: 0x0000001c
   r12: 0x00000000  r13: 0x00000000  r14: 0x00000000  r15: 0x00000000
   r16: 0x00000000  r17: 0x00000000  r18: 0x00000000  r19: 0x01aebbc0
   r20: 0x00046f30  r21: 0x00000000  r22: 0x00000000  r23: 0x00077da0
   r24: 0x00077df0  r25: 0x00000000  r26: 0xa01303fc  r27: 0x00000000
   r28: 0x00000000  r29: 0xa0131c24  r30: 0x00077c30  r31: 0x90133574

If anyone has any idea what that means, it'd be great

I did repair disk permissions, but it still doesn't work.

Anyway I can preserve my save games, profile, and custom MP settings then?

Sweet!  I looked on the macsoft site, but I guess I missed that one.  My eyes grow weary in my old age

I just checked, and it worked.  You have my eternal thanks for making it work!  HAIL BE TO TRACKS!

::drags limp body of buddy through mud while tracers whip overhead and explosions tear the lush marsh greenery apart::

saved games, keyboard/mouse setup options, etc. are stored in your /home/documents/halo directory, and the prefs file with the cd key in it is in your home/library/preferences

Holy crap, that's awesome! I thought all that stuff was stored in the actual application, since it didn't appear to be anywhere in the halo app folder. Now I'm not so scared of reinstalling.

yeah, i don't know why they even bothered with an installer. you'll notice that it doesn't require an administrator password to install, so (with the exception of the saved game files and prefs) all the game files go in one place. i don't imagine it would be too hard to tell the game to create a directory for the saved games the first time it boots, if it doesn't find one. and *presto* no need for an installer, just drag the folder off and you'd be done.

meh.

saved games, keyboard/mouse setup options, etc. are stored in your /home/documents/halo directory, and the prefs file with the cd key in it is in your home/library/preferences, so deleting your halo install folder won't lose your profile(s), cd key, or saved games.

Yeah, I noticed this too. But is there any way to manipulate these files as if they were ini documents? Has anyone dared to open any of these in a text editor? It would be cool to go more in depth with the graphics tweaking like in UT2K3. I bet a lot of us could squeeze more FPS outta the game just by having a few more advanced options to tweak. Ahh well, we'll see what the next patch has to offer in terms of performance and bug fixes. At the very least it'll cut down on the TKing.

as far as i can tell there aren't any .ini files or any such files we could manipulate... i've tried doing some delving with a package browser, seeing if i could find a file hidden inside the application to mess with, but so far no luck.