Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

10.4: Another fix for non-launching PowerPC apps on Intel System 10.4
The problem: Some PowerPC applications (such as Word) sometimes fail to launch on Intel Macs.

Level 1 solution: There is a root process called translated which seems to be launched with PowerPC programs. If this process is killed, then the application can be launched with no troubles. Note that an administrator password is required. translated can be found by opening up the Activity Monitor. Select the process and click on Quit Process. This was covered in this recent hint.

This solution works, but it is a pain. Read on for some alternative solutions...

Level 2 solution: Automate the termination of the translated process. I wrote an AppleScript program which kills translated and launches Word. The first complication -- translated is not AppleScriptable, so you can't just tell it to quit. The following script uses some Unix shenanigans to find the process id of translated, and then a quit signal is sent to it, before Word is launched.
set pid to do shell script 
 "ps -auxw -U root | grep -i translated | awk '{print $2}'"
if pid ≠ "" then
  do shell script "kill -TERM " & pid 
   with administrator privileges and password
end if
tell application "Microsoft Word" to launch
This solution is better, but what if you want to launch Word with a Word document?

Level 3 solution: Add a run handler. The following script quits translated, whether you are just launching Word or opening a document.
on run
  killtranslated()
  tell application "Microsoft Word" to launch
end run

on open wordfiles
  killtranslated()
  repeat with afile in wordfiles
    try
      tell application "Microsoft Word" to open afile
    end try
  end repeat
end open

on killtranslated()
  set pid to do shell script 
   "ps -auxw -U root | grep -i translated | awk '{print $2}'"
  if pid ≠ "" then
    do shell script "kill -TERM " & pid 
     with administrator privileges and password
  end if
end killtranslated
Save the AppleScript as an droplet (I call it WordLauncher), and if you drop a Word document onto the droplet, it will launch Word and open your document with no problems. The obvious next step is to just allow us to double click Word documents.

Level 4 solution: Let WordLauncher hijack all Word document launches. Usually we could just use Finder's Get Info on a Word document, 'Open with:' WordLauncher, and choose Change All. However, it seems that Script Editor doesn't do all the bundle work that is required. I won't go into the gory details, but essentially I had to add a CFBundleDocumentType for Word documents (I chose to associate W8BN and W6BN).

Bonus step -- add a Word document icns to WordLauncher so Word docs still look like they should.

[robg adds: I haven't tested this one.]
    •    
  • Currently 2.33 / 5
  You rated: 4 / 5 (6 votes cast)
 
[12,802 views]  

10.4: Another fix for non-launching PowerPC apps on Intel | 8 comments | Create New Account
Click here to return to the '10.4: Another fix for non-launching PowerPC apps on Intel' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.4: Another fix for non-launching PowerPC apps on Intel
Authored by: skapplin on Aug 08, '06 11:38:29AM

I have an easier solution that doesn't require a separate Applescript for every Rosetta-run application:

The problem seems only to appear if you have Unsanity's APE and haxies running. If you open APE and add all your PowerPC applications to the Exclude list, then they should all work without needing to kill the translated process. If you have FruitMenu installed, then either uninstall it or use APE to turn it off.

I find this works with all my PowerPC apps without having to kill translated each time I run one.



[ Reply to This | # ]
10.4: Another fix for non-launching PowerPC apps on Intel
Authored by: myrkr on Aug 08, '06 12:06:33PM

I have seen this problem where neither of those programs were installed.



[ Reply to This | # ]
APE
Authored by: rspeed on Aug 08, '06 02:43:13PM
Unsanity said there's a bug in OS X that they need to work around to fix this issue. My guess would be that these errors are fairly rare until APE is installed (especially with ShapeShifter) at which point the issue becomes common.

http://www.unsanity.org/archives/haxies/betatacular.php

[ Reply to This | # ]
10.4: Another fix for non-launching PowerPC apps on Intel
Authored by: SignOfEth on Aug 08, '06 02:29:18PM

This is great! I called AppleCare on Sunday to try and get this very problem diagnosed. And, yes, I have Unsanity's APE and three haxies installed. I'll do the exlude-these-apps thing and see if all is well.



[ Reply to This | # ]
10.4: Another fix for non-launching PowerPC apps on Intel
Authored by: strikeman on Aug 09, '06 03:33:29AM

If I read the Unsanity post correctly they are saying that haxies suffer from the same problem as other Rosetta-dependent programs, not that APE is the source of the problem.

This means that any program that uses Rosetta could have this problem. (In my experience though this varies - for instance, Word is very prone, and Powerpoint is less so).



[ Reply to This | # ]
10.4: Another fix for non-launching PowerPC apps on Intel
Authored by: smeger on Aug 28, '06 04:01:24AM

Unsanity ShapeShifter guy here. This issue is caused by a bug in OS X, but using APE-based haxies can greatly increase the frequency with which this bug is triggered, depending on which haxie is used. To repeat - this bug can occur without APE installed, but is more likely to occur with APE installed. And, unfortunately, the APE Exclude list doesn't help.

The "sudo killall translated" terminal command is a valid work-around, but, of course, it's a pain to run that before every Rosetta launch.

We are hard at work on a fix to APE to get the situation to the point that we're not exacerbating the issue. But currently, the situation I described above is the deal.

This info is current as of APE version 2.0.2b1. Any version newer than that will almost certainly include a fix for this.



[ Reply to This | # ]
Why must you make everything so complicated?
Authored by: rspeed on Aug 08, '06 11:43:43AM
killall translated
Much simpler.

[ Reply to This | # ]
Why must you make everything so complicated?
Authored by: strikeman on Aug 09, '06 03:30:27AM

1) I am automating the killing, so I don't have to go to terminal all the time.
2) translated is a root process, so killall doesn't work anyway as it seems to only match user processes



[ Reply to This | # ]