Skip navigation

Rosetta Problems after Security Update 2012-001

9028 Views 67 Replies Latest reply: May 19, 2013 11:21 AM by MlchaelLAX RSS Branched to a new discussion.
  • DoctorYo Level 1 Level 1 (0 points)
    Currently Being Moderated
    Feb 3, 2012 7:52 AM (in response to J.Morris)

    Posted on another site, but if anyone is using Quicken 2007 the Apple update will stop the printer and also block exporting report to Excel file. This fix worked perfectly to cure the problem. Many thanks. Heartrate almost back to normal.

  • pubwvj Level 1 Level 1 (10 points)
    Currently Being Moderated
    Feb 3, 2012 8:05 AM (in response to J.Morris)

    This is a tragedy. Apple is destroying the wealth of data and applications that came before. The modern computers have the hardware processing capacity to continue emulating PPC, 68K, OS9, etc. Even the oldest iPhone or iPodTouch has the power to handle this in emulation. There are a tremendous number of applications for those in the educational and small business fields as well as games. These were never ported to OSX or iOS. Apple should work hard to support this older software. It would expand their market and benefit consumers.

  • R C-R Level 6 Level 6 (13,830 points)
    Currently Being Moderated
    Feb 3, 2012 8:26 AM (in response to pubwvj)

    It isn't a tragedy. It isn't destroying anything. It's just a bug Apple didn't catch before releasing the update. It isn't the first time this has happened nor is it likely to be the last.

     

    J. Morris has confirmed that Apple is working on a fix. It isn't the end of the world or worthy of all the over-the-top drama people are posting about it.

  • Whisper33 Calculating status...

    Thanks for the link.  It has worked for me at least for Office 2004.  Though I had to use google translate to read it. 

  • WZZZ Level 6 Level 6 (11,880 points)
    Currently Being Moderated
    Feb 3, 2012 9:25 AM (in response to R C-R)

    RC-R wrote: It isn't the end of the world or worthy of all the over-the-top drama people are posting about it.

    No, it isn't the Haiti earthquake, but if it happened to you you wouldn't be a happy camper. I didn't get caught by it, since I saw early on what was happening, and if I had I've got clones to restore from. For anyone who did get it right in the face, I think your remarks are insensitive.

     

    It's not the first bug Apple has introduced in an update, but it is astonishing a bug this blatant and big wasn't caught before that update was released. It either shows extraordinarly sloppy and incompetent work or just plain indifference to the base of PPC/Rosetta users. It would appear all it needed was some very basic testing on a few machines running Rosetta to have easily uncovered this mistake.

  • R C-R Level 6 Level 6 (13,830 points)
    Currently Being Moderated
    Feb 3, 2012 9:29 AM (in response to WZZZ)

    It did happen to me. Need I say more about that?

  • WZZZ Level 6 Level 6 (11,880 points)
    Currently Being Moderated
    Feb 3, 2012 9:42 AM (in response to R C-R)

    Yes, you could say more and I would venture to guess probably will. And I'm supposing you easily restored from a TM or Clone? That would make all the difference wouldn't it? If you needed to do a reinstall, which played havoc with your work flow with serious consequences, then I applaud your equanimity. But you may be willing to understand that many others are not so blessed with your admirable stoicism and forgiving nature.

  • revjmark Level 1 Level 1 (0 points)
    Currently Being Moderated
    Feb 3, 2012 10:23 AM (in response to J.Morris)

    Many thanks - your fix did the job for me and restored an early version of Indesign to working order and Word X.

     

    Much relief. Thanks

     

    Mark

  • R C-R Level 6 Level 6 (13,830 points)
    Currently Being Moderated
    Feb 3, 2012 10:30 AM (in response to WZZZ)

    The only point I was trying to make is all the drama is a waste of time that won't fix anything.

  • cathy fasano Level 2 Level 2 (340 points)
    Currently Being Moderated
    Feb 3, 2012 11:07 AM (in response to R C-R)

    If you would like to do something useful while waiting (restoring your clone, reinstalling 10.6, etc.) go to the apple bug reporter and report that Security Update 2012-001 is still up on the Software Update server, and still comes up offering the update on 10.6 machines.

     

    (Heaven help the unsophisticated mac users -- the ones who would never in a gazillion years figure out what to put in google to figure out what has happened to them.  The sort of users who are going to turn off their macs and power up their windows 98 machines.)

  • John CH Calculating status...
    Currently Being Moderated
    Feb 3, 2012 11:56 AM (in response to J.Morris)

    Mr. Morris -- the fix worked for me, thanks!

     

    I use good ol' Adobe ImageReady daily for animated gif production and image slicing because there's nothing better (and is why no Lion for me), but the security update broke saving/exporting files.

     

    C'mon Apple. I've owned Macs since '84 but sheesh.

  • dalstott Level 4 Level 4 (2,455 points)

    I feel sorrow for those who haven't been with Apple/Mac long enough to treat upgrades with the upmost caution. I am always eager to upgrade as soon as something is announced but have learned to wait a minimum of 1 week before jumping in. During that interval I check the forums for problems and solutions. And before installation I always make the bootable clone current. Having a clone is the easiest and most reliable way to regress to a prior state.

     

    The way things are evolving I wonder if in the not too distant future a handheld device will be the hub and the laptop/desktop will be a peripheral appendage.

  • ds store Level 7 Level 7 (30,305 points)
    Currently Being Moderated
    Feb 3, 2012 3:52 PM (in response to J.Morris)

    Security Update 2012-001 v 1.1 is released, hit your software update.

  • FatMac\>MacPro Level 4 Level 4 (2,070 points)
    Currently Being Moderated
    Feb 3, 2012 3:54 PM (in response to J.Morris)

    J.Morris wrote:

     

    My crack team of sys admins and I have devised a method for resolving some of the issues regarding the Security Update 2012-001 and Rosetta.

     

     

    http://www.educate-it.org/content.php?130-Rosetta-Issue-after-Security-Update-20 12-001

     

    Click this link for an Installer that will revert the files necessary for some Rosetta apps to run after the Security Update. This is a band-aid and is only recommended in emergency situations. Apple is currently working on a fix, but until that happens, we are stuck with reverse-engineering their update. I hope this helps those in distress from this update.

    FWIW, Software Update now shows a version 1.1 of the Security Update. As of right now, there does not yet seem to be an updated version on Apple's support website. Since I didn't install the original, I don't know if 1.1 would be offered by Software Update as a fix if the original was installed. And I'm sure not going to try 1.1 to see if the original issue was fixed.

    Mac Pro, Mac OS X (10.6.8), 5,1 6-core 24 GB 5870 27" LED ACD
  • R C-R Level 6 Level 6 (13,830 points)

    cathy fasano wrote:

     

    If you would like to do something useful while waiting (restoring your clone, reinstalling 10.6, etc.) go to the apple bug reporter and report that Security Update 2012-001 is still up on the Software Update server, and still comes up offering the update on 10.6 machines.

    If you send a request like that via bug reporter, it will likely be ignored. Bug reporter is intended be used to report suspected bugs, preferably with as much info about specific misbehaviors & what a user did when one occured as possible.

     

    Roughly equivalent to that is to allow Snow Leopard to automatically send crash reports to Apple, making sure to fill in anything relevant in the comments section you can think of. The crash reports sent this way will include the crash log which, along with any other specific info you can include, will help Apple's engineers verify that the bug exists, the exact conditions that trigger it, & what to do to correct it.

     

    Since AppleWorks 6 consistently produces crashes for me if I try to open a preexisting AW file or print a newly created one, I have sent at least one crash report for each of these actions. Others are reporting slightly different results & hopefully are sending their own commented crash reports.

     

    It all helps.

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.