|
#9
| ||||
| ||||
| It's Classic. You won't get it to run under Leopard. Rosetta is there to translate PPC Mac OS X code to run on an Intel Mac. PPC Classic code is not going to work. |
|
#10
| |||
| |||
| Wouldn't a classic app be listed as a classic app in the Get Info window? This game is listed in the info as an Application (PowerPC) Got any proof it's really a Classic app?
__________________ Serendipity is a lucky guess ! |
|
#11
| ||||
| ||||
| Well it's an OS X native game, which I assume meant, in terms of Classic/Carbon/Cocoa, that it would be one of the latter two. It certainly is PowerPC, but I don't think it's considered Classic. |
|
#12
| ||||
| ||||
| Best thing you can do is to send an email to Macplay and ask them if it is supported. I don't think it will be, since its originally released for 10.0 and then was later patched to run on 10.1. Lots of change went on internally in OS X during the move from 10.1 -> 10.2 -> 10.3 which meant that a lot of software broke. |
|
#13
| ||||
| ||||
| Ah, that would make sense as to why it worked on a previous Mac OS X version and not this one. I'll contact MacPlay and ask about it. Also, just to follow up, I did try it on another user account that I created and had no better luck. Thank you both for your help! |
|
#14
| |||
| |||
| I'm having the same problem. It just opens and then closes right away with that stupid error message. Although, check this out. It appears on the MacForums site that someone was able to install and run Giants on Leopard 10.5.2 with no problems at all once he fixed a resolution problem! We need to find out what he is doing differently! I miss playing Giants too!!! LINK: http://forums.macrumors.com/showthread.php?t=488642 |
|
#15
| ||||
| ||||
| Mate, if he did it successfully you should be asking him. Or email Macplay and ask them about it. Though it appears that someone in that other thread has already emailed Macplay and got a response. You might need to switch off a processor to get it working. So follow the instructions contained in that Macplay email and you'll be fine, assuming of course that the problem is caused by you having two processors running ![]() |