Anyone noticing any issues with Diablo 2 LOD and Leopard 10.5.3?

Discussion in 'Mac and PC Games' started by lindstrom, May 29, 2008.

  1. macrumors member

    Joined:
    Sep 13, 2006
    #1
    Just saw in another thread that someone reported that 10.5.3 broke Starcraft (in what way was not described, but I assume that it won't load).

    Is there any cause for concern regarding Diablo?

    These two might be completely unrelated but the thought crossed my mind.

    I just recently started with D2 again, and I have not had the time to update Leopard as I am still at work.

    Can anyone confirm that D2 LOD is still working properly after the update?
     
  2. macrumors 65816

    Tom B.

    Joined:
    Mar 22, 2006
    Location:
    London
    #2
    I think that whoever it was in that other thread simply meant that StarCraft still doesn't work (on Penryn MacBooks and MacBook Pros), rather than it suddenly stopped working after installing 10.5.3.

    As for Diablo II, I will try it out when I get home (in 5 hours), as well as StarCraft and WarCraft III, but I'm sure there will be no problems.
     
  3. macrumors newbie

    Joined:
    Oct 19, 2007
    #3
    Yes, there is an issue! Diablo 2 LoD will not start anymore on an Intel Mac with 10.5.3. This is true for all MacBooks and some iMac versions. :( Hopefully Blizzard will give us another patch!
     
  4. thread starter macrumors member

    Joined:
    Sep 13, 2006
    #4
    Thanks mate, I really appreciate your help. I was not aware that StarCraft did not work earlier, my bad.

    Very much looking forward to hear what you discover when you test this out. I won't be home to try this myself for another 8+ hours so it will be very interesting to watch this thread in the meantime.
     
  5. macrumors newbie

    Joined:
    Mar 12, 2008
    #5

    I can confirm that too.. my LOD fails to start.

    Code:
    Process:         Diablo II (Carbon) [2242]
    Path:            /Users/xxx/Games/Diablo II Folder/Diablo II (Carbon)
    Identifier:      com.blizzard.Diablo2
    Version:         1.10 (1.10)
    Code Type:       PPC (Translated)
    Parent Process:  launchd [199]
    
    Date/Time:       2008-05-29 15:27:36.372 +0100
    OS Version:      Mac OS X 10.5.3 (9D34)
    Report Version:  6
    
    Exception Type:  EXC_BAD_ACCESS (SIGBUS)
    Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
    Crashed Thread:  0
    
    Thread 0 Crashed:
    0   translate                     	0xb80bc688 0xb8000000 + 771720
    1   translate                     	0xb80b7007 0xb8000000 + 749575
    2   translate                     	0xb80d49c0 0xb8000000 + 870848
    3   translate                     	0xb813ce79 spin_lock_wrapper + 1981
    
    Thread 1:
    0   ???                           	0x800bc4a6 0 + 2148254886
    1   ???                           	0x800c3c9c 0 + 2148285596
    2   translate                     	0xb818b6ea CallPPCFunctionAtAddressInt + 202886
    3   ???                           	0x800ed6f5 0 + 2148456181
    4   ???                           	0x800ed5b2 0 + 2148455858
    
    Thread 2:
    0   translate                     	0xb81529ef spin_lock_wrapper + 90931
    1   translate                     	0xb8183633 CallPPCFunctionAtAddressInt + 169935
    2   translate                     	0xb81861e2 CallPPCFunctionAtAddressInt + 181118
    3   translate                     	0xb80dfb0b 0xb8000000 + 916235
    
    Thread 3:
    0   translate                     	0xb815289e spin_lock_wrapper + 90594
    1   translate                     	0xb816e8a7 CallPPCFunctionAtAddressInt + 84547
    2   translate                     	0xb80dfb0b 0xb8000000 + 916235
    
    Thread 4:
    0   translate                     	0xb81529ef spin_lock_wrapper + 90931
    1   translate                     	0xb8183633 CallPPCFunctionAtAddressInt + 169935
    2   translate                     	0xb81861e2 CallPPCFunctionAtAddressInt + 181118
    3   translate                     	0xb80dfb0b 0xb8000000 + 916235
    
    Thread 0 crashed with X86 Thread State (32-bit):
      eax: 0x00000000  ebx: 0xb80b6c78  ecx: 0x00000000  edx: 0x00000000
      edi: 0x80303848  esi: 0x8080d180  ebp: 0xb7fffa08  esp: 0xb7fffa00
       ss: 0x0000001f  efl: 0x00010206  eip: 0xb80bc688   cs: 0x00000017
       ds: 0x0000001f   es: 0x0000001f   fs: 0x00000000   gs: 0x00000037
      cr2: 0x00000000
    
    Binary Images:
    0xb8000000 - 0xb81d7fe7  translate ??? (???) /usr/libexec/oah/translate
    
    Translated Code Information:
    Rosetta Version:  21.03
    Args:  	/System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp /Users/xxx/Games/Diablo II Folder/Diablo II (Carbon) 
    Exception: EXC_BAD_ACCESS (0x0001)
    
    Thread 0: (0xb019e83c, 0xb81529ef)
    0x84fa4624: No symbol
    0x949c2f4c: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore : _YieldToThread + 532 
    0x949c8328: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore : _SetThreadState + 172 
    0x85339f08: No symbol
    0x8533a514: No symbol
    0x8535d810: No symbol
    0x8525aab8: No symbol
    0x8525b998: No symbol
    0x8525adf4: No symbol
    0x8535e294: No symbol
    0x85339828: No symbol
    0x949c8178: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore : _CooperativeThread + 348 
    0x93fb1e8c: /usr/lib/libSystem.B.dylib : __pthread_body + 40 
    0x00000000: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp :   + 0 
    
    PPC Thread State
    srr0: 0x00000000	srr1: 0x00000000		             vrsave: 0x00000000
    cr:  0xXXXXXXXX		xer: 0x20000000		 lr: 0x93f27360		ctr: 0x93f20430
    r00: 0xffffffe1 	r01: 0xf0182610 	r02: 0x00000013 	r03: 0xf01826bc 	
    r04: 0x00000003 	r05: 0x00000018 	r06: 0x00000020 	r07: 0x00006503 	
    r08: 0x00000000 	r09: 0x00000000 	r10: 0x00000000 	r11: 0xa07e05f4 	
    r12: 0x93f20430 	r13: 0x00000000 	r14: 0x00000000 	r15: 0x00000000 	
    r16: 0x00000000 	r17: 0x00000000 	r18: 0x00000000 	r19: 0x00000000 	
    r20: 0x00000000 	r21: 0x00000000 	r22: 0x00000000 	r23: 0x00000018 	
    r24: 0xf01826bc 	r25: 0x00000020 	r26: 0x00006503 	r27: 0x00000000 	
    r28: 0x00000000 	r29: 0x00000003 	r30: 0x00000003 	r31: 0x949c2d40 	
    
    Thread 1: (0xb009a83c, 0xb81529ef)
    0xf0080cf8: No symbol
    0x949c2f4c: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore : _YieldToThread + 532 
    0x8533a358: No symbol
    0x85339758: No symbol
    0x85339828: No symbol
    0x949c8178: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore : _CooperativeThread + 348 
    0x93fb1e8c: /usr/lib/libSystem.B.dylib : __pthread_body + 40 
    0x00000000: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp :   + 0 
    
    PPC Thread State
    srr0: 0x00000000	srr1: 0x00000000		             vrsave: 0x00000000
    cr:  0xXXXXXXXX		xer: 0x20000000		 lr: 0x93f27360		ctr: 0x93f20430
    r00: 0xffffffe1 	r01: 0xf0080c70 	r02: 0x00000013 	r03: 0xf0080d1c 	
    r04: 0x00000003 	r05: 0x00000018 	r06: 0x00000020 	r07: 0x00004307 	
    r08: 0x00000000 	r09: 0x00000000 	r10: 0x00000000 	r11: 0xa07e05f4 	
    r12: 0x93f20430 	r13: 0x00000000 	r14: 0x00000000 	r15: 0x00000000 	
    r16: 0x00000000 	r17: 0x00000000 	r18: 0x00000000 	r19: 0x00000000 	
    r20: 0x00000000 	r21: 0x00000000 	r22: 0x00000000 	r23: 0x00000018 	
    r24: 0xf0080d1c 	r25: 0x00000020 	r26: 0x00004307 	r27: 0x00000000 	
    r28: 0x00000000 	r29: 0x00000003 	r30: 0x00000003 	r31: 0x949c2d40 	
    
    Thread 2: Crashed (0xb7fffa00, 0xb80bc688)
    0x84e77ddc: No symbol
    0x84e768c4: No symbol
    0x84e71b50: No symbol
    0x84e6b0e8: No symbol
    0x84e6a50c: No symbol
    0x84e6a350: No symbol
    0x84e6d3f4: No symbol
    0x84e6ba48: No symbol
    0x84e6ddcc: No symbol
    0x84e69118: No symbol
    
    PPC Thread State
    srr0: 0x00000000	srr1: 0x00000000		             vrsave: 0x00000000
    cr:  0xXXXXXXXX		xer: 0x00000000		 lr: 0x84e77ddc		ctr: 0x93f20e80
    r00: 0x84e77ddc 	r01: 0xbfffeaf0 	r02: 0x003f6000 	r03: 0x00000000 	
    r04: 0x000001e0 	r05: 0x0000000c 	r06: 0x00000000 	r07: 0x00000000 	
    r08: 0x00454d30 	r09: 0x00000000 	r10: 0x00000020 	r11: 0xa09e117c 	
    r12: 0x93f20e80 	r13: 0x00000000 	r14: 0x00000000 	r15: 0x00000000 	
    r16: 0x00000000 	r17: 0x00456448 	r18: 0x00456438 	r19: 0x00456444 	
    r20: 0x00456440 	r21: 0x8527532c 	r22: 0x85275334 	r23: 0x00454d30 	
    r24: 0x00454d30 	r25: 0x0045643c 	r26: 0x00000026 	r27: 0x00126680 	
    r28: 0x00000026 	r29: 0x001269b0 	r30: 0x00000000 	r31: 0x004549f0 	
    
    Thread 3: (0xb011ce20, 0xb815289e)
    0x93f638c0: /usr/lib/libSystem.B.dylib : __pthread_cond_wait + 1260 
    0x94973ea0: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore : _TSWaitOnConditionTimedRelative + 244 
    0x94973c74: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore : _TSWaitOnSemaphoreCommon + 432 
    0x94973938: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore : AsyncFileThread(void*) + 68 
    0x93fb1e8c: /usr/lib/libSystem.B.dylib : __pthread_body + 40 
    0x00000000: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp :   + 0 
    
    PPC Thread State
    srr0: 0x00000000	srr1: 0x00000000		             vrsave: 0x00000000
    cr:  0xXXXXXXXX		xer: 0x20000000		 lr: 0x93f63900		ctr: 0x93f204b0
    r00: 0xffffffd9 	r01: 0xf0101cb0 	r02: 0xa07db924 	r03: 0x00004803 	
    r04: 0x00004903 	r05: 0x0000003c 	r06: 0x00000000 	r07: 0x00000000 	
    r08: 0x00000000 	r09: 0x00000001 	r10: 0xf0101e68 	r11: 0xa07e09dc 	
    r12: 0x93f204b0 	r13: 0x00000000 	r14: 0x00000000 	r15: 0x00000000 	
    r16: 0x00000000 	r17: 0x00000000 	r18: 0x00000000 	r19: 0x00000000 	
    r20: 0x00000000 	r21: 0x94a53acc 	r22: 0x94a53acc 	r23: 0x00000000 	
    r24: 0x00000000 	r25: 0x00000001 	r26: 0xf0101e68 	r27: 0xa07e33e8 	
    r28: 0xa0929a1c 	r29: 0xa07db924 	r30: 0xa0929a50 	r31: 0x93f633e8 	
    
    
     
  6. macrumors 68040

    MongoTheGeek

    Joined:
    Sep 13, 2003
    Location:
    Its not so much where you are as when you are.
    #6
    Mine too. Crap.

    Executing a null pointer. joy.
     
  7. macrumors 65816

    Tom B.

    Joined:
    Mar 22, 2006
    Location:
    London
    #7
    Ok, sorry, I was wrong in my other post. :(

    Diablo II: Lord of Destruction unexpectedly quits straight away every time, and StarCraft II: Brood War just bounces a few times then does absolutely nothing.

    But the good news is that WarCraft III: Reign of Chaos and The Frozen Throne both work completely fine.
     
  8. macrumors 6502

    Joined:
    Oct 28, 2003
    Location:
    Irvine CA
    #8
    Sorry, we have no way of releasing patches to OS X. That would be Apple's department.
     
  9. macrumors 68020

    kkat69

    Joined:
    Aug 30, 2007
    Location:
    Atlanta, Ga
    #9
    Works on my iMac. Just ran it up, graphics and all still works.

    Starcraft still works too.

    Going to check this and starcraft on my wife's SR MB.

    Starcraft won't start but LOD works.

    Since we don't play these anymore, not bothering to re-install to see if that helps. Just deleting all the files now.
     
  10. macrumors 68040

    MongoTheGeek

    Joined:
    Sep 13, 2003
    Location:
    Its not so much where you are as when you are.
    #10
    True but you can patch your program which is crashing.

    /Admittedly in code being executed in Rosetta.
    //Did you at least file a bug?
     
  11. macrumors 6502

    Joined:
    Oct 28, 2003
    Location:
    Irvine CA
    #11
    We did file a Radar on this today.

    It is not clear what patch we could provide which would address this - and the app as-is works correctly from OS X 10.3.9 through 10.5.2, so this looks like a regression in OS X plain and simple.
     
  12. macrumors 68030

    Catfish_Man

    Joined:
    Sep 13, 2001
    Location:
    Portland, OR
    #12
    Runs fine here as long as I don't turn on OpenGL mode (which has been true all along on Intel Macs afaik).
     
  13. macrumors 68040

    MongoTheGeek

    Joined:
    Sep 13, 2003
    Location:
    Its not so much where you are as when you are.
    #13
    I didn't mean to seem to snarky. Fighting my own bugs.

    I just filed RDAR://5973763 against it as well.

    The crash is in Rosetta and it is probably a timing problem with Apple being too clever in optimization of what gets loaded/converted when.
     
  14. macrumors 68020

    kkat69

    Joined:
    Aug 30, 2007
    Location:
    Atlanta, Ga
    #14
    Ditto, both MB and iMac run LOD on 10.5.3.
     
  15. macrumors 6502

    Joined:
    Oct 28, 2003
    Location:
    Irvine CA
    #15
    In the "good news" dept. we have a fix for the OpenGL issue in final testing internally. I do not have a schedule for its release but the coding to fix it is done.
     
  16. macrumors 68030

    Catfish_Man

    Joined:
    Sep 13, 2001
    Location:
    Portland, OR
    #16
    Oh nice :) Glad to hear it. Good luck with the 10.5.3 issues.
     
  17. thread starter macrumors member

    Joined:
    Sep 13, 2006
    #17
    Okay, talk about mixed messages, glad I asked about this =).

    Will have to ponder on this upgrade for a little I think.

    Wow, that is really nice to hear. Great work mate!
     
  18. macrumors 68040

    MongoTheGeek

    Joined:
    Sep 13, 2003
    Location:
    Its not so much where you are as when you are.
    #18
    Cool. Glad to see that there is still development on the game even though its so far into the "long tail"

    Side question: Will you be among the Blizzard contingent at WWDC?
     
  19. macrumors 604

    thejadedmonkey

    Joined:
    May 28, 2005
    Location:
    Pa
    #19
    They (SC & D2: LoD) both work fine for me (MBP C2D w/ ATI x1600)

    I don't have brood war.
     
  20. macrumors 6502a

    Joined:
    Jul 26, 2005
    #20
    As always, I want to thank rbarris & Blizzard for being on top of these things. I don't have an Intel Mac or 10.5.3 (yet), but I think responsiveness - in a non-company forum, no less - and continuing support for years-old games is the standard every company should aspire to, and I applaud them for it.
     
  21. macrumors newbie

    Joined:
    Mar 12, 2008
    #21
    I sent an email to Blizzard's support team today. I just got a reply from them,


    And if anyone wants to keep updated, here's a sticky mod thread on blizzard's support forum

    http://www.battle.net/forums/thread.aspx?fn=support&t=535843&p=1&#post535843
     
  22. macrumors newbie

    Joined:
    Jan 18, 2007
    #22
    Hi rbarris. I just bought Diablo2 battle chest (new) today. I have the most recent revision of Macbook Pro. After installing (using the OSX installer from blizzard's website), the game crashes immediately on launch saying it "quit unexpectedly."

    Here's the punchline: I am using OSX 10.5.2, not 10.5.3. So maybe this is not a problem with 10.5.3 after all?

    --Sirlin
     
  23. macrumors 6502

    Joined:
    Apr 9, 2006
    Location:
    Boston, MA
    #23
    That is awesome, thanks to the entire blizzard team for still updating 7 year old games.

    And Diablo II:LoD (& Starcraft w/o the expansion) is working fine on my 10.5.3 MacBook, at least once I got it installed, but that took awhile. The OSX installer started, but did nothing, no screen or anything, so I had to install it on a different computer and then transfer the files to my MacBooks, but it has worked fine once I did that.
     
  24. macrumors 603

    Joined:
    Mar 29, 2008
    Location:
    Seattle
    #24
    New patch out today. Game still crashes immediately on my MacBook Pro 10.5.3. Great.
     
  25. macrumors regular

    Joined:
    Jul 6, 2003
    #25
    Still crashing for me too. I'm on a MacBook Pro running 10.5.3. Since I recently temporarily moved to Hawaii, I bought my 2nd copy of the game this week since I had the urge.

    Oh well, I'd still like to thank rbarris and the whole Blizzard and mac team for updating these ancient games. It is a testament to the quality of the support and the creators that the game still has players and a staff that updates it.
     

Share This Page