Warning: 10.5.3 breaks Starcraft on non-Penryn Intel processors

[Petey05]

I posted already in the StarCraft thread, but then I saw this in the Diablo thread:

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.

This is incorrect. Starcraft on Penryn has been broken for awhile, but 10.5.3 broke StarCraft on my 2.2 GHz blackbook. I almost restored from Time Machine when I found out but it would have been too much trouble. Here's hoping they patch soon. Just wanted to warn other people.

 

[thatinkjar]

Yep

I have a MacBook Pro SR, and Starcraft was working perfectly on 10.5.2. Since updating to 10.5.3, it simply crashes on startup.

I have a horrible feeling that we might be waiting a long time for a fix, too.

 

[Tom B.]

This is incorrect. Starcraft on Penryn has been broken for awhile, but 10.5.3 broke StarCraft on my 2.2 GHz blackbook. I almost restored from Time Machine when I found out but it would have been too much trouble. Here's hoping they patch soon. Just wanted to warn other people.

Sorry about that, I admit I was completely wrong, and I did change my post before I saw yours:

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.

 

[temna]

I posted already in the StarCraft thread, but then I saw this in the Diablo thread:



This is incorrect. Starcraft on Penryn has been broken for awhile, but 10.5.3 broke StarCraft on my 2.2 GHz blackbook. I almost restored from Time Machine when I found out but it would have been too much trouble. Here's hoping they patch soon. Just wanted to warn other people.

This is not true either, I installed and played Starcraft yesterday before the 10.5.3 update on my Blackbook 2.4 and it worked fine. Now it appears broken. I think I will try reinstalling.

 

[CJM]

Just had a try, and it works fine on my Core2Duo iMac.

 

[johnny_b]

Broken

Broken on my Mac Pro 2008 with Nvidia GeForce 8800. Happend yesterday after 10.5.3.

 

[rbarris]

Affected users should notify Apple that they are having this problem.

We will try to repro it here and file a bug.

 

[johnny_b]

How? By using the Apple Forum or?

 

[MongoTheGeek]

How? By using the Apple Forum or?

Apple reads their forums but I don't think they allocate developer time to fix problems reported there.

A better way is

https://bugreport.apple.com/

You have to be a registered developer to use it (Free developer account works)

 

[Petey05]

This is not true either, I installed and played Starcraft yesterday before the 10.5.3 update on my Blackbook 2.4 and it worked fine. Now it appears broken.

That's actually exactly what I wrote.

 

[Petey05]

Affected users should notify Apple that they are having this problem.

We will try to repro it here and file a bug.

Done.

Do you have any idea when/if this might be fixed? I don't want to have to regress to 10.5.2....then again, I don't think I can wait until SC2 to ever play SC again...

 

[chickenninja]

im running 10.5.2 and i can testify that starcraft has worked pretty well since leopard came out, does anyone else have a green cursor burned into the top right corner of their starcraft screen? has anyone gotten SC to work on 10.5.3 yet?

 

[eXan]

BW works fine on my MacBook rev. B under .5.3, as well as on my iMac G5.

 

[QCassidy352]

yikes, I think I'll just stick with 10.5.2. Everything's running fine, and I don't want any part of these problems!

 

[johnny_b]

Done reporting. I have a student developer account. Hopefully Apple or Blizzard will fix this very soon.

 

[JezC]

im running 10.5.2 and i can testify that starcraft has worked pretty well since leopard came out, does anyone else have a green cursor burned into the top right corner of their starcraft screen? has anyone gotten SC to work on 10.5.3 yet?

Got 10.5.3 and StarCraft (not expansion) working with Blizzard Update 1.15.2 on a Mac/Mini. Has a green static cursor image in top left - same as in 10.5.2.

Got 10.5.3 and StarCraft (not expansion) *NOT* working on a new MB Pro 17. The initial loader comes up (with display selection, etc), but fails to proceed after clicking OK. Tried with original (1.0.4, IIRC) CD binary and the Blizzard Mac OS X Installer. Applied update 1.15.2 and it still failed silently after the selection window. Haven't traced the execution to see where the failure point is, or compared with the Mac Mini image, yet.

 

[aeg722]

im running 10.5.2 and i can testify that starcraft has worked pretty well since leopard came out, does anyone else have a green cursor burned into the top right corner of their starcraft screen? has anyone gotten SC to work on 10.5.3 yet?

I have the green cursor as well forever burned at the top left of my screen, or at least had it until I unsuspectingly downloaded 10.5.3. Now it won't load up, how long till you think Blizzard updates or Mac fixes the issue?

 

[oratowsky]

Crash report

Hi, I'm having the same problem.

Did some digging around and found this crash report:
Process: Starcraft (Carbon) [312]
Path: /Users/orenratowsky/Downloads/Brood War v1.15.2 OSX/Starcraft (Carbon)
Identifier: com.blizzard.Starcraft
Version: 1.11 (1.1.1)
Code Type: PPC (Translated)
Parent Process: launchd [122]

Date/Time: 2008-06-03 17:32:19.788 -0700
OS Version: Mac OS X 10.5.3 (9D34)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000060
Crashed Thread: 0

Thread 0 Crashed:
0 translate 0xb80bcd58 0xb8000000 + 773464
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 0 crashed with X86 Thread State (32-bit):
eax: 0x00000060 ebx: 0xb80bcd30 ecx: 0x00000000 edx: 0x00000003
edi: 0x00000060 esi: 0x80303820 ebp: 0xb7fffa08 esp: 0xb7fff9d0
ss: 0x0000001f efl: 0x00010206 eip: 0xb80bcd58 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0x00000060

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/orenratowsky/Downloads/Brood War v1.15.2 OSX/Starcraft (Carbon)
Exception: EXC_BAD_ACCESS (0x0001)

Thread 0: (0xb009a83c, 0xb81529ef)
0xa0298e44: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore : _gThreadMgrNewbornLock + 0
0x916530d4: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore : _CooperativeThread + 184
0x96d85e8c: /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: 0x00000000 lr: 0x96cfb360 ctr: 0x96cf4430
r00: 0xffffffe1 r01: 0xf0080dc0 r02: 0xa0cdf924 r03: 0xf0080e6c
r04: 0x00000002 r05: 0x00000000 r06: 0x00000020 r07: 0x00004307
r08: 0x00000000 r09: 0x00000000 r10: 0xa0d17d94 r11: 0xa0ce45f4
r12: 0x96cf4430 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0x00000000 r22: 0x00000000 r23: 0x00000000
r24: 0xf0080e6c r25: 0x00000020 r26: 0x00004307 r27: 0x00000000
r28: 0x00000000 r29: 0x00000002 r30: 0x00000002 r31: 0x91653024

Thread 1: Crashed (0xb7fff9d0, 0xb80bcd58)
0x851cb524: No symbol
0x851d3cc8: No symbol
0x851d35d8: No symbol
0x8531087c: No symbol
0x853108cc: No symbol
0x852d8bac: No symbol
0x853be024: No symbol
0x853be090: No symbol
0x853cae14: No symbol

PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x851cd7f4 ctr: 0x851cb544
r00: 0x00000000 r01: 0xbfffed40 r02: 0x005c9000 r03: 0x00000000
r04: 0x00000000 r05: 0x00000001 r06: 0x00000000 r07: 0x00001a03
r08: 0x00000000 r09: 0x915f9ac8 r10: 0x00000000 r11: 0xa0ce45f4
r12: 0xa02a3d00 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0xffffffff
r20: 0xbffff6f0 r21: 0xbffff548 r22: 0x00000001 r23: 0x00000409
r24: 0x00000006 r25: 0x00000000 r26: 0x00000001 r27: 0x00000000
r28: 0x00000006 r29: 0x00000000 r30: 0xbffff0cc r31: 0x00000010

I'm on a 2.2 ghz 2 gb ram Macbook Pro using 10.5.3. I don't know if anybody has submitted something like this to Apple or Blizzard but could be helpful. Awaiting a fix for this!!

 

[MongoTheGeek]

I submitted a similar bug against Diablo ii. Blizzard says its Apple's problem but they are working with Apple to Fix it. Apple says they already have the bug filed under a different number.

I saw get a free developer account and file the bug with Apple. The more people report it, the higher priority.

 

[johnny_b]

The issue is that they removed support for 256 colors in 8800 and 8600.

 

[Sijmen]

The issue is that they removed support for 256 colors in 8800 and 8600.

Well that makes clear why my ATi-equiped iMac has no problems

 

[Tom B.]

The issue is that they removed support for 256 colors in 8800 and 8600.

What about the GMA X3100?

 

[eXan]

The issue is that they removed support for 256 colors in 8800 and 8600.

I've tried to launch Starcraft on a 2.4 GHz 24" iMac (in XP) and it couldn't load. It turned out the computer didn't support 640x480 resolution - the minimum was 800x600...

Can somebody confirm this with their 24" iMac? Does 20" have the same issue? It would really su©k if it does.........

 

[tianuk3]

What about the GMA X3100?

Yeh its messed it for the GMA X3100, looks like Apple just decided to remove 256 colours and pretty much any backcompatibility in the update...

seriously they need to fix this now! Now 3 of my games have completely stopped working, Fallout, Fallout 2 and Diablo 2.... Lets all complain..and let them know what we think about their "update"

 

[johnny_b]

My guess is that Apple will never fix this. To bad Hopefully Blizzard can do something about it.