Skip to Content

Unsanity urges customers to make sure APE is current before upgrading to Leopard

Not all Leopard upgrades have gone as smoothly as hoped, which is not unexpected (and why we always back up before upgrading, right? Right.) and not necessarily cause for enormous alarm. One frequent alert, however, has been the implication of Unsanity's Application Enhancer (APE) framework in some upgrade problems. APE has a long and sometimes controversial history, with some developers swearing BY it (Audio Hijack, for example, uses APE to enable the "Instant Hijack" functionality) and other developers swearing AT it (APE's ability to modify other applications at runtime, necessary to enable some tools, can also make app debugging more difficult).

We relayed an early warning on APE (8:31 pm Friday) as part of Scott's liveblog of his Leopard upgrade, but without confirmation from the developer there wasn't much more to say... until now. Rosyna of Unsanity sent out an urgent email alert to mailing list subscribers (reproduced in whole below) recommending that APE be updated to the current version (2.03) prior to upgrading to Leopard, lest badness ensue. Note that v2.03 of APE still won't actually do anything under Leopard, which knocks out a large slice of utility functionality, but it won't crash either.

In general, if you are doing an upgrade install, I recommend an AppFresh or VersionTracker pass to make sure that all your bits and pieces are as current as they can be. Plus, that backup... don't skip it. Really.

Thanks Laurie!
---- from Unsanity's customer mailing list ---

We wanted to send out some information to our mailing list subscribers about Mac OS X 10.5 and Unsanity's Application Enhancer.

First and formost. *Before* you install Mac OS X 10.5, make sure you have Application Enhancer (APE) 2.0.3 or later installed. You can download it from http://www.unsanity.net/ape-203.dmg (the webpage is at http://unsanity.com/haxies/ape ).

Make *sure* you have APE 2.0.3 or later installed *before* you install Mac OS X 10.5. If you have an earlier version of APE installed before you install 10.5, you may exhibit one of the following symptoms upon booting into Mac OS X 10.5:

- Your goldfish may die.
- A strange dog might bite you on the street.
- A friend may punch you.
- Your computer may catch fire.
- Your loved one may leave you.

All of these things are really bad. So we urge everyone to make sure they have APE 2.0.3 or later installed. If you aren't sure, install APE 2.0.3 or later from the link above. APE 2.0.3 was released on March 14th, 2007. And please, always keep your software up to date.

A note about 10.5 and haxies:

As long as you have APE 2.0.3, nothing bad will happen in 10.5. Well, nothing we can control. However, none of your APE Modules will work either.

Developers in Apple's Mac OS X developer program (ADC) got the final 10.5 GM yesterday. We are still downloading the huge 6.66GB image and as soon as the downloads finish for our developers, we will be hard at work on making our software work on 10.5.

You can keep up to date with the status of haxies and 10.5 by viewing http://unsanity.com/products/compatibility/ and we will post more information as we have it on our blog at http://unsanity.org/ . Mac OS X 10.5 compatibility is currently our number one priority.

"If APE doesn't work in 10.5, shouldn't I just uninstall it?"

No, you should not. Just make sure you have APE 2.0.3 or later. A lot of third party (and Unsanity made) utilities depend on the APE framework itself being there. As it has some extremely useful functions. Removing it may cause these Applications and/or preference panes to stop launching.

For more information on Unsanity haxies, please visit:

http://www.unsanity.com/haxies/


Unsanity LLC is the creator of other popular haxies such as WindowShade X, ShapeShifter, FontCard, Mighty Mouse, Menu Master, FruitMenu, Xounds, Dock Detox, and Silk. Unsanity is dedicated to providing quality software for the Macintosh community.


-Rosyna of the Unsanity Team
Always needs a hug

Categories

Leopard

Not all Leopard upgrades have gone as smoothly as hoped, which is not unexpected (and why we always back up before upgrading, right?...
 

Add a Comment

*0 / 3000 Character Maximum

23 Comments

Filter by:
vandlism

Wow, APE. Also known as how to screw up your computer royally. I am so sick of this application and its use. A special big thanks goes to Logitech for relying on this destructive app, and as a result making their own products worthless.

October 29 2007 at 12:05 PM Report abuse rate up rate down Reply
Hone Melgren

@Ape Haters

1) I've never once had a problem with APE or Unsanity problem on any of the macs I've had over the years . I've also paid and registered user. Never one crash caused by APE or Unsanity Stuff

2) The APE Framework uses the same system infrastructure and Apple provided and documented APIs that gdb uses. GDB is an Apple supported debugger engineered by Apple to "work" on OS X. It does not use any shady "unsupported" methods to work neither do they use kernel extensions.

3) The GM release of Leopard was never seeded to developers. They had to download it after launch day and such had changes in it that *broke* a lot of apps. I'm won't be surprised if the security features were one of them

Seriously people the Unsanity developers *love* the mac and will continue to code for macs for years to come (and in safe non system melty ways) . If you want developers that hate mac just choose the people that do Vent - they vermently hate macs ;(

October 29 2007 at 8:30 AM Report abuse rate up rate down Reply
Hone Melgren

Lol anti-APE camp posters come out in droves!

October 29 2007 at 8:23 AM Report abuse rate up rate down Reply
Mark Thomas

Unsanity have about as much integrity as spammers. They insist that they have a right to exist even though their products ultimately bring sorrow and woe to the world.

October 28 2007 at 10:33 PM Report abuse rate up rate down Reply
papichulo

This thing has always been one of the few pieces of malware on the Mac OS. Good riddance APEsh*t!!!!!

October 28 2007 at 8:55 PM Report abuse rate up rate down Reply
Chris

Guys, how is this new and strange?

APE works by intercepting system calls and working with what it thinks are statically assigned libraries and memory allocations. The very security feature of Leopard, randomly assigned memory allocations for libraries, and sandboxing was meant to keep (illicit) applications from doing this. And now APE doesn't work, because the security holes it was exploiting to function aren't there anymore. Of course, since it is a 'legitimately' installed application (it is already in the kext folder, along with proper permissions) not code being executed from a buffer overflow, it is hanging the system.

(And btw, how did they not have a build of 10.5 running and working on their systems, they should have known this wouldn't have worked atleast by september's build, as I doubt apple turned on these security features last minute)

October 28 2007 at 3:32 PM Report abuse rate up rate down Reply
mare

I can't live without WindowShadeX so I actually don't upgrade to Leopard until that works. I bought it (have the T-shirt), have it installed on an external drive but booted only once from it, just to see if it was workable. Having my windows move to my Dock when I minimize them (and I minimize about 6000 times a day) makes it just unworkable for me. In the Dock they are locxated in a semi random order, windowshaded I know where they are. I've never used the Dock and I'm not going to do so now. Besides Tiger works just fine for me. Only when a lot of apps will require Leopard to run, I might upgrade.

October 28 2007 at 12:57 PM Report abuse rate up rate down Reply
Catt

Thanks to Scott's live cast I simply uninstalled APE before upgrading to Leopard. Thus, I was one of the ones that had no issues with my upgrade on account of APE. I can't get the Shapeshifter icon out of my systems preference though... I'm more annoyed that Candybar is not working under Leopard yet the default icons are driving me batty.

October 28 2007 at 12:46 PM Report abuse rate up rate down Reply
Lee Patterson

follow this is you find yourself stuck with a blue screen after update install
http://docs.info.apple.com/article.html?artnum=306857

October 28 2007 at 12:17 PM Report abuse rate up rate down Reply
Hard Nard

In my case i got the blue screen and soent half a day trying to figure what went wrong. Turns out the Logitech mouse software installs APE. I re-ran the installation using Archive and install and everything was fine. All I needed to re-install was my printer driver and my Logitech software.

October 28 2007 at 11:16 AM Report abuse rate up rate down Reply
Buy an ad here

Hot Apps on TUAW

Tweets

© 2012 AOL Inc. All Rights Reserved.