Originally posted by The Grimace
How is OS X's failure to 'Force Quit' WarCraft III Blizzards fault? Here I thought under OS X every app ran in a protected memory space, which couldn't touch the OSs' or any other apps space. Golly gee. If this is true, then how is WarCraft III able to bring the ENTIRE OS to a complete and utter standstill? FYI, none of the suggested remedies on Blizzards site worked.
Just because the memory space is protected doesn't mean the application can't access a level of the system that isn't protected. I haven't had any problems with warcraft3. I read the site you posted. http://www.blizzard.com/support/?id=mwr0669p
No where does it say that the *bug* is OS X's fault. It simply tells you to quit all your applications before running wc3 (free up resources). It also says to quit those mouse programs, which probably iterfere with wc3 capturing the location of the mouse on the screen. It says to update card drivers. They probably directly access the video card or something for their graphics, I don't know anything about how blizzards game engine works, but if they have a bug and are accessing low level parts of the system, I wouldn't be surprised if it could cause a crash. Step 4 points out that on some systems there's a carbon library *for developers* http://www.radgametools.com yes you see credits to rad gametools on wc3 and starcraft etc, because blizzard uses their product for audio. then they tell you to reinstall the game. *Obviously* the *bug* is not OS X's fault. Blizzard just needs to figure out what is causing it and release a fix. Please stop bitching and saying that its OS X's fault. I challenge you to find real evidence/data that contradicts what I have just said. Please.