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

Recognize Intel only apps on PowerPC machines System
You can recognize Intel only apps prior to trying to install them. I downloaded the new version of CronniX 3.0.1, which the developer accidently compiled as an Intel-only app, instead of a Universal Binary. After I had mounted the disk image, I saw a white "not usable" sign on the icon of CronniX. I opened the application, and it gave a message stating that this app can't be run on this architecture.

It seems Apple automatically creates some kind of badge on application icons if they're not capable of running on PowerPC machines. I don't think it's the same way on Intel Macs, because they can run PowerPC binaries in Rosetta.

[robg adds: The icon seen here is from the Parallels Desktop Uninstaller tool, which was the only Intel-only app I had handy that showed the "not usable" badge.]
    •    
  • Currently 3.00 / 5
  • 1
  • 2
  • 3
  • 4
  • 5
  (2 votes cast)
 
[11,288 views]  

Recognize Intel only apps on PowerPC machines | 6 comments | Create New Account
Click here to return to the 'Recognize Intel only apps on PowerPC machines' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Recognize Intel only apps on PowerPC machines
Authored by: barryjaylevine on Jun 21, '06 07:41:33AM

"Classic" apps display the same altered icon on Intel Macs. Logical.

---
-----
Two things in this world aren't overrated: Macintosh and Lemon Meringue Pie.



[ Reply to This | # ]
Recognize Intel only apps on PowerPC machines
Authored by: Dirk68 on Jun 21, '06 08:01:51AM

Hello,

you can alway create Intel-only Apps by using "lipo" from the command line to strip unwanted architectures.

But be sure to make a copy beforehand.

Dirk



[ Reply to This | # ]
Recognize Intel only apps on PowerPC machines
Authored by: wgscott on Jun 21, '06 09:03:58AM

use the unix file command, eg:

file Parallels.app/Contents/MacOS/Parallels

returns this: Parallels: Mach-O executable i386

whereas

file Safari.app/Contents/MacOS/Safari

returns this:


Safari.app/Contents/MacOS/Safari: Mach-O universal binary with 2 architectures
Safari.app/Contents/MacOS/Safari (for architecture i386): Mach-O executable i386
Safari.app/Contents/MacOS/Safari (for architecture ppc): Mach-O executable ppc



[ Reply to This | # ]
Recognize Intel only apps on PowerPC machines
Authored by: danieleran on Jun 21, '06 09:39:41AM
Actually there are lots of PowerPC apps that won't run on Intel Macs, even with Rosetta. Anything requiring Classic, G5 specific operations, or dependant upon kernel extensions, JNI libraries or the like.

For example, Microsoft Office apps work, but the AutoUpdater app that ships with it will not launch on Intel, and displays the same crossed out circle badge over the icon. On Intel Macs, you have to download Office updates manually.

PowerPC Macs are still the fastest (and sometimes only) way to run old apps, and will be for a while.

Unraveling The PowerPC Obsolescence Myth
http://www.roughlydrafted.com/RD/Home/F2155356-71C8-4A95-9A0C-3EA63B1EF959.html

- Daniel Eran


[ Reply to This | # ]
Recognize Intel only apps on PowerPC machines
Authored by: jchapman on Jun 21, '06 01:30:21PM

Microsoft AutoUpdate DOES function correctly on an Intel Macintosh; I ran it myself this weekend. Perhaps an earlier version (maybe from Office X?) is a classic application, but certainly the copy installed from the Office 2004 CD works just fine (as does the rest of Office... I have zero complaints about Office speed on my MacBook).



[ Reply to This | # ]
Recognize Intel only apps on PowerPC machines
Authored by: tooki on Jul 13, '06 08:50:39AM

Just a little bit of computer history:

NeXTStep/OpenStep, the direct ancestors of Mac OS X, used a similar mechanism to show that an application lacked the necessary binary -- it grayed out the application icon. (Back then, the architectures were M68K and i386.)

Oddly, though, Mac OS X doesn't use the same method of storing universal binaries. The NeXT way actually just held a separate binary for each architecture, separated by a folder structure inside the application package. That structure now lives on to separate Classic from native OS X binaries inside an application package.

The new Universal Binary system has the advantage that even single-file executables, like UNIX command-line apps, can be universal.

tooki



[ Reply to This | # ]