PowerPC apps not executing

Hello,
Recently, I've ran into a problem with all of my PowerPC applications not launching. At first I thought it was just an issue with Microsoft Word, however I soon found that it's ALL of my PowerPC applications. I've tried to run some Universal programs with Rosetta, and unfortunately they ran fine. So I'm unsure what the problem is.
Any ideas?
Thanks

Jeramy,
Any chance you've run something like Monolingual to remove extraneous language files? I recently made that mistake to find out that the program also removed all my cocoa framework files (and others) that stopped Rosetta from properly handling PPC apps.
Other than that I would check your log files using console to see if anything is kicking any error messages out to logs, that may give us some clue as to what's going on. Try that and let u know if you see any log or error messages.
Short of that you're going to have to either restore a backup or reinstall Tiger.
(beleive me, things like this have led me to practice taking "clones" of my HD a couple of times a week to a firewire drive. Its a fairly cheap alternative to spending hours trying to figure out what we did wrong.)
let us know what your log files have to say...
HTH,
Peter

Similar Messages

Mac app store wont load, error "powerpc Apps not supported"

mac app store wont load, error "powerpc Apps not supported"
Im running a 2008 intel i mac with ios 10.7.5 all updates done. Have previously used the store ok.
Help please.

You're using 10.7 but Rosetta is no longer available on that build. So you can't get PowerPC emulation to run anymore. Sorry but that's been stripped out.
But I am puzzled as to why this would prevent Mac App Store from loading.
Could you show us a screenshot of this error, and your screen in its entirey here? Thanks.

Should Dreamweaver 8 work on OS 10.9 and if so how do I stop PowerPc apps not working error message...?

And is there any email contact for Adobe?

KarynRY wrote:
Thanks Nancy, from the description it looked like it was just for mobile apps but maybe not? If not, will give it a trial...
Quite the opposite.
Most of Adobe's best selling desktop apps are now only available via the Adobe Creative Cloud (for rent via monthly payments, not for sale). Adobe is betting the house on it.
Software available via the Cloud
Explore Adobe desktop apps | Adobe Creative Cloud

My imac is running mountain lion and last night i downloaded maverick. in midst of installing it it said a powerPC app microsoft word would not work so i canceled the install for the time being. my questions is if i choose to finish installing maverick

my imac is running mountain lion and last night i downloaded maverick. in midst of installing it, it said a powerPC app microsoft word would not work so i canceled the install for the time being. my questions is if i choose to finish installing maverick does that mean i will nevver be able to access word documents stored on my desktop? or do the word docs automatically convert to pages or what? i am so confused. would i be better off just sticking with mountain lion and send the maverick install to the trash? hoping someone will be able to answer my question though i am afraid the response is likely to be just stick with mountain lion so you can keep using word. i had been looking forward to maverick but it seems pretty drastic to not have access to microsoft word anymore by switching to maverick. hope someone has an answer so i can have the best of both worlds so to speak!

thanks for your response Csound1 on the peninsula ... if i go ahead and install maverick and then download LibreOffice or OpenOffice will i then be able to access old microsoft word saved documents on my deskstop through those two free alternatives? i am not that knowledgeable about these things so i am not sure if you are saying i will just be able to use libreoffice or openoffice for creating new documents or whether i can access the saved microsoft docs? are they transferred to OO or LO or what and if editing of the old word docs is needed can i do that through the OO and LO programs or apps (see i am not even sure if i am using the correct vocabulary!) hope you can answer this as quick as the first question, so i can decide to stick with mountain lion and trash the maverick install or proceed with maverick install and hoppe that my microsoft word docs are still accessible through OO or LO or adding to myquestion will pages on maverick be able to open the old word documents? thanks again!

When I touch my iPad screen to execute an app, the screen goes dark then the app icon reappears. The app does not execute.

When I touch my iPad screen to execute an app, then the screen goes dark then the app icon reappears. The app does not execute. Any thoughts?

Try a Reset...
Press and hold the Sleep/Wake button and the Home button at the same time for at least ten seconds, until the Apple logo appears. Release the Buttons.
Basic troubleshooting
From Here
http://www.apple.com/support/ipad/basics/

App Builder produces "Not Executable" error with Strictly Typed VI Refs

There is a very frustrating problem with the app builder in LV 8.0.1. Certain VIs compile and run fine in labview, but the app builder
refuses to make them into applications.
The error message is very long and ends with something like "The VI is not
executable". Standard advice for this problem is to force LV to recompile
everything you're building by either mass compiling or ctrl-shift clicking the
run arrow, but this hasn't worked for me in two separate cases (completely
different projects).
It seems that this problem is caused by wiring a strictly typed VI reference to
an invoke node with the FP.open method selected. In both cases I resolved
the issue by changing the Static VI Reference to be weakly typed (right-click
the static vi reference and make sure "Strictly Typed VI Reference"
is unchecked). After that, the project build successfully.
This is very hard for a user to track down for several reasons:
- The error message in the application builder does not give any
indication as to what the real problem is
- The app builder reports that the top-level VI is broken, even when the
strictly typed reference and invoke node may occur in a sub VI
- Nothing (that I can
find at least) in the documentation suggests that strictly typed references
won't work with the Open.FP method.
There is a page that says "some of the properties and methods do
not work when you configure this function to output a strictly typed VI
reference," but no indication is given of which methods fail
Note that in one case I was also able to make the project
build by deleting an instance of "IMAQ Create.vi" from the top-level
VI. I
have no explanation for this.
Hopefully this post will save some other users the trouble
of tracking this down and maybe even get NI to correct the issue for future
versions.
Adam Brewster

Hello Adam,
Thank you for sharing your experience and insight. Your post was well thought-out and offered a
good description of the problem as well as some possible workarounds. I believe that the issue has been filed and
is under investigation (3TU8T8V9). Feel
free to post back after the next LabVIEW release and inquire as to its status.
Thanks again,
Travis M
LabVIEW R&D
National Instruments

I recently upgraded to Mavericks from Snow Leopard. Does Snow Leopard still exist on my Mac? If so, is it possible to restart under Snow Leopard in order to run PowerPC apps? If not, is there an OS available in 64 bit that supports PowerPC apps? Mav ***.

I recently upgraded to Mavericks from Snow Leopard. Does Snow Leopard still exist on my Mac? If so, is it possible to restart under Snow Leopard in order to run PowerPC apps? If not, is there an OS available in 64 bit that supports PowerPC apps? Mav ***.

The only reason I upgraded to Mavericks was because my Snow Leopard OS was 32 bit, which I was told would support only 4GB of RAM.
That wasn't quite right. You can put in as much RAM as your Mac's hardware supports. The division is in the apps themselves. A 32 bit app can't use more than 4 GB or RAM. A 64 bit app can use much more.
For example, as a 32 bit only version, Photoshop CS3 can't use more 4GB of RAM, no matter how much you actually have installed. CS4 or later can use all the RAM you want to throw at it.

"vi is not executable" built app - product feature request

OK, here's what I want for the next version of LabVIEW. Forget a real implementation of OO. Forget about making XControls so that you don't need a PhD to program them. Forget about a real polymorphic control (down all you who say "variant!"). Here's what I want for the next feature of LabVIEW.
I want the run-time engine to give me a better idea of why a built application won't run. The generic "This VI is not executable. The full development version of LabVIEW is required to fix the errors..." is meaningless. If the VI works just fine in the development environment, and it builds without errors, why does it not run? If there's so many reasons, how is one supposed to track it down?
I've been using LabVIEW since version 2 on a Mac, so I like to think that I know what I'm doing with it. Yet, whenever I run into this I feel helpless because I have NO information! This is frustrating beyond my ability to put into words. And please don't tell me to look at this article or this other article in your KnowledgeBase. Been there, done that. In one situation I tracked the problem down to a VI. Couldn't find ANYTHING wrong with it. So, I created a new VI, copied the block diagram over, and saved the new VI over it. Rebuilt the app, and presto, the app worked. Do you know how long it took me to track it down to that VI? About half a day. Was there ANYTHING that gave me a clue as to the problem? Can you say rhetorical question?
I'm posting this here in the hopes that enough people get my grief, and head over to the Product Suggestion Form to hopefully make this pipe dream a reality. Power to the people!
Now, back to figuring out why my latest built application won't run. Guess what I'll be doing for the next half-day or so.

smercurio, i can't help you, but i'm with you, maybe that makes you feel better.
i upgraded a LV-app i created originally with 7.1 (this was the best LV ever, in my opinion) to 8.20. i was forced to do that because of the 64bit feature of ms tickers. it took me about 4hrs to create a project to generate an executable, after several LV-crashes during editing. finally i managed to get the project working (compiling took about 10 mins, with the 7.1 app builder about 1 min!! same code!!!), and then there was this error message: "error blabla in VI blubblub", and the VI was part of the vi.lib! so what to do?
KB: no answer!
discussion forum: no hits!
i found a post in the forum about another error code, but the same scenario. workaround was to disable the "remove as much as possible" option in the advanced project settings.
result: size of executable increased about 100%, while execution speed decreased about 50% compared to the 7.1 version, though all of the "code enhancement features" of 8.20.
now i'm thinking of switching back to 7.1 and to workaround the limits of long execution times with 32bit tickers.
i'm a big fan of LV, and i'm dealing with it since 1998, not for fun, but as a professional programmer. but 8.2 is a real step backwards in quality in my opinion. i think this has to be said to make 9.0 better!
Best regards
chris
CL(A)Dly bending G-Force with LabVIEW
famous last words: "oh my god, it is full of stars!"

I upgraded my iMac to Mountain Lion and now my Canon Pixima MP500 will not open because PowerPC apps are no longer supported! Has anyone experience this problem?

I upgraded my iMac to Mountain Lion and now my Canon Pixima MP500 will not open because PowerPC apps are no longer supported! Has anyone experience this problem?

Correct. Applications designed to run on the old PPC Macs (which Apple stopped making in 2005) cannot run on Mountain Lion.
You need to update your printer driver:
Printer and Scanner software available for download:
http://support.apple.com/kb/HT3669?viewlocale=en_US

Upgraded to 10.8, now Quicken 2006 not working because PowerPC apps are no longer supported? What should I do?

I upgraded my computer to 10.8, and now PowerPC applications won't work. I have Quicken 2006, and I need a way to run it. Is there a software or anything that I can run it with? Or can I find the files on my computer somewhere and put them into a newer version of Quicken, such as 2013?

You can install Snow Leopard on an external disk, then boot to that to use your PowerPC apps.
Or, you can upgrade the Apps to versions that are Intel or Universal. Quicken 2007 was recently updated to a Universal version--it only took them about five years.

Why don't powerpc apps work?

Lion OX is not nice... why is it that I cant it support powerpc apps????

Lion doesn't have Rosetta. Rosetta was removed deliberately from Lion because the PowerPC has been declared obsolete by Apple. You might not think that is nice but Apple felt that supporting PowerPC for 6 years was enough. Without Rosetta, Lion is unable to execute PowerPC code.
Allan

I have recently purchased MacBook Pro with Mac OSX 10.7.3 Lion and I would like to install Final Cut Pro 6 Studio2, and it came up with this error: 'you can't open application FinalCutProStudio.mpkg because PowerPc apps are no longer supported..pls advise

I have recently purchased MacBook Pro with Mac OSX 10.7.3 Lion and I would like to install Final Cut Pro 6 Studio2, and it came up with this error: 'you can't open application FinalCutProStudio.mpkg because PowerPc apps are no longer supported......Is there a way to run FCP6 on lion withoput this error? Any help would be appreciated.....

Hi Shane,
Just one more quesiton re: this topic, I am looking to get rosetta but do not have Leopard or Snow Leopard...
I read that it is not on Snow Leopard only on Leopard....so do I need to get only Leopard? Can u advise?
Alternatively I do have Mac OS X Tiger so is it on this and can I install it from here?
Please excuse my lack of knowledge here, just trying to get my FCP 6 up and running asap....
Best Rgds.

I get a "vi is not executable" error when building an application.

I have an ongoing project that has worked fine in the past when building an application. I have recently added some report generation toolkit vis(Excel) and get an error for some of the ni vis and some of my own that call lower level excel vis. The error is that he vi is not executable, however they run fine in the development environment. I do not get this error if I save all vi's into one llb with save with options command and then build. However, when I try to run the app, this error re-appears. Also, do I have to add the dynamically loaded vi's that are part of the toolkit in my build script? Could this be the cause of the problem? If so, what's the best way to find all of them? Any suggestions?

You have hit in on the nail! You do need to add the dynamically loaded VIs when you are creating an executable from your VI. You need to add _wordsub.lib and _exclsub.lib as dynamically loaded VIs into your executable. Try this and let us know if you have any more problems with it.
J.R. Allen

Mac OS 10.7 (Lion) won't start After Effects CS5.5 because it's a powerpc app!?

I've had CS 5.5 Master Collection installed on my Mac since it came out. All the CS 5/5.5 apps I've used up to now have worked fine, in 64-bit mode (Photoshop, Illustrator, Acrobat Pro, InDesign). Now I need to use After Effects, but I can't get it to start.
First it said it couldn't rename a Workspaces.xml file in the preferences directory in my home folder. In fact, there was no such file there at all. Nothing to rename. So, I uninstalled After Effects using its uninstaller; then reinstalled it from the install DVDs.
Now, it fails on startup saying the After Effects CS5.5 application cannot be run because PowerPC apps are no longer supported. True: OS X no longer runs apps that require Rosetta. CS 5.5 is does not require Rosetta; it's compatible with Lion. The OS 10.7 Known Issues KB article says nothing about After Effects: http://kb2.adobe.com/cps/905/cpsid_90508.html?promoid=JBQYY
So...what's going on? I need this thing working for a project with a deadline! I don't get it. Anybody seen this before? (I didn't find anything in the discussions about it, nor Google...)

Interesting article, but I knew I was leaving PowerPC apps behind when I moved to OS 10.7, and Adobe claims that After Effects CS 5.5 is fully compatible with Lion. But you must be right about prefs; there's gotta be something causing the Mac OS to think this version of CS is ancient...
Since my initial message, I've tried and failed to find any details about how to select the right prefs to delete. I also ran Disk Utility to repair permissions on my system drive. That got rid of the PowerPC error:) Now on startup AE says mediacore fails to initialize. I can choose to quit or continue on that error, but continuing just results in another error that says dynamiclinkmanager unexpectedly quit, and then AE locks up and I have to force quit it. Not much progress!
No other answers on this so far... Before I uninstall the entire Creative Suite and then delete all Adobe system and hidden files everywhere, any more suggestions? Or a list of the right prefs I should trash?

I have an Epson scanner that is apparently no longer supported because it is a PowerPC app. It's a very good scanner that worked fine until I upgraded to OS Mountain Lion on my MacBook Pro. Any suggestions on how I can continue to use it?

I have an Epson scanner that is apparently no longer supported because it is a PowerPC app. It's a very good scanner that worked fine until I upgraded to OS Mountain Lion on my MacBook Pro. Any suggestions on how I can continue to use it?

For that model, Epson has this information:
ICA Scanner Driver
07/17/12
Description: The latest Mac OS X ICA scanner driver for your Epson product is available only via Apple's Software Update. Here's how to get it:
1. Connect the all-in-one or scanner to your Mac and power it on.
2. Select the  menu, then Software Update.
3. Follow the on-screen instructions to install the available updates.
Note: Software Updates may find multiple updates for your system. You may choose to install all or some of the updates by clicking on Show Details.
Compatible Systems: Mac OS X (v10.8.x)

PowerPC apps not executing

Similar Messages

Maybe you are looking for