The macosxhints Forums - How to tell if Rosetta is installed

The macosxhints Forums (http://hintsforums.macworld.com/index.php)

- Applications (http://hintsforums.macworld.com/forumdisplay.php?f=5)

- - How to tell if Rosetta is installed (http://hintsforums.macworld.com/showthread.php?t=105756)

Okay, figured it out as I was going to dinner. "Open using Rosetta" is dependent upon having "Open in 32-bit mode" checked first. That's not immediately obvious based on the way it's visually represented in "Get Info", especially because "Locked" is directly beneath the two, and that option is not dependent on either of the above having been checked.

Glad that mystery has been solved.

I'm guessing that the app I want to run simply does not run in Snow Leopard (it's from the Panther days), and that's okay, but why would I not even get an option to try and run it in Rosetta? Perhaps it's so old that the system doesn't know what to do with it.

Quote:

Originally Posted by benwiggy (Post 689855)

May be they are crashing for some other, non-Rosetta reason?

What does the crash log indicate?

In a nutshell:

Code:

Code Type:       PPC (Translated)

Parent Process:  launchd [109]



Date/Time:       2012-06-26 18:42:16.483 +0700

OS Version:      Mac OS X 10.6.8 (10K549)

Report Version:  6



Exception Type:  EXC_CRASH (SIGTRAP)

Exception Codes: 0x0000000000000000, 0x0000000000000000

Crashed Thread:  0  Dispatch queue: com.apple.main-thread



Thread 0 Crashed:  Dispatch queue: com.apple.main-thread

0   libSystem.B.dylib                     0x80239236 __pthread_kill + 10

1   libSystem.B.dylib                     0x80238ad7 pthread_kill + 95

2   com.aspyr.thps4                       0xb80bfb30 0xb8000000 + 785200

3   com.aspyr.thps4                       0xb80c0037 0xb8000000 + 786487

4   com.aspyr.thps4                       0xb80dd8e8 0xb8000000 + 907496

5   com.aspyr.thps4                       0xb8145397 spin_lock_wrapper + 1791

6   com.aspyr.thps4                       0xb801ceb7 0xb8000000 + 118455



Thread 1:

0   libSystem.B.dylib                     0x80142afa mach_msg_trap + 10

1   libSystem.B.dylib                     0x80143267 mach_msg + 68

2   com.aspyr.thps4                       0xb819440f CallPPCFunctionAtAddressInt + 206231

3   libSystem.B.dylib                     0x80170259 _pthread_start + 345

4   libSystem.B.dylib                     0x801700de thread_start + 34



Thread 0 crashed with X86 Thread State (32-bit):

  eax: 0x00000000  ebx: 0x802fc540  ecx: 0xb7fff9ac  edx: 0x80239236

  edi: 0xb8211640  esi: 0x00000005  ebp: 0xb7fff9d8  esp: 0xb7fff9ac

   ss: 0x00000023  efl: 0x00000286  eip: 0x80239236   cs: 0x0000000b

   ds: 0x00000023   es: 0x00000023   fs: 0x00000000   gs: 0x0000000f

By the way, if anybody at Aspyr is reading this, Feral is "The Greatest Mac publisher on Earth, ever."

…actually, it kind of varies based on where Brad Oliver is working at the moment.

Ha Ha.

Quote:

Originally Posted by acme.mail.order (Post 689856)

According to my receipts folder Rosetta is not installed. Yet various PPC programs run fine.

Digging deeper, the core program seems to be /usr/libexec/oah/translate ?

I also see Rosetta listed within /Library/Receipts/InstallHistory.plist (Snow Leopard). Not sure about Lion.

Can you tell us what app that you are really interested in?
You cut off the line near the top of the log that tells what app actually crashed.

And, doesn't really matter what you'll find about rosetta in Lion. There's no support in Lion for rosetta, so PPC apps have no chance of running in any case.

Quote:

Originally Posted by ThreeBKK (Post 689849)

3) Yes, 10.6.8, but running on my Mac mini which is "Lion-only" according to Apple. Used instadmg to build it. That whole process can be found in another thread, if anyone is interested.

Then you're off in uncharted territory. Just because you've managed to trick the installer into installing something it didn't want to install doesn't mean it'll work. The installer may have had very good reasons for telling you "no" when you asked it straight up. "Working" is not an all or nothing thing. It may be that some things work and others don't. The installer would have said "no" if it knows that not everything works; you may have just found one of the things that doesn't.

And "the web told me it'll work" doesn't mean it'll work.

The rule I follow is: Never lie to your computer. Bad things tend to happen when you do.

Didn't really have to trick the installer. Just built the image with instadmg, mostly because I have only 1 Mac, and cloned it onto a partition. It booted up fine, and has run well for the past few days / weeks, but as you noted, it's not all or nothing.

Found some hardware performance problem areas which I'm going to address in separate threads, one of which has already been solved, but overall, very happy to have access to Snow Leopard again. Too many things in Lion which irk me, and I would be loath to make it my home.

Really a shame that Apple seem to have changed their tactics with regard to OS releases and hardware compatibility. Cutting off Snow Leopard so abruptly, I think, was a mistake.