Unsanity strikes back!

Leopard-compatible betas released!

Coincidence can be a funny thing.

Just last week, I emailed the folks at Unsanity software, requesting an interview. In case you don't know, Unsanity makes about a dozen popular utilities for Mac OS X. By far, my favorite is WindowShade X. It has long been (together with LaunchBar) one of the first two third-party utilities I install on every new or updated Mac.

The problem has been that virtually none of the Unsanity haxies (as most of their utilities are called) have been updated for Leopard—even though Leopard has now been out for about four months and just about every developer who intends to come out with a Leopard update has already done so. Making matters worse, Unsanity has not exactly been forthcoming in explaining the reason for the delay or when it might be over.

In a blog entry from last October, Unsanity stated, "We have a build internally that works with Mac OS X 10.5... so it's a matter of days for the compatibility update." Unfortunately, the promised update did not appear in the next few days...or weeks...or months. Queries from users—as to what was happening—were met with silence. No further blog entries on the subject were posted. Postings from users began getting increasingly cranky and critical.

It was this backdrop that led to my request for an interview. I hoped they might be willing to sit down for a talk and explain what was going on.

Therein lies the coincidence. I received a reply from Unsanity today, politely declining my request for an interview. Instead, I was directed to a pair of blog entries, posted yesterday, for the answers to my questions: Pragmatic Disillusionment and Enthusiastic Trepidation. I don't flatter myself to imagine that my email triggered the blog entries. As I said, I am sure the timing was just a coincidence.

Still, the entries do provide most of the answers I would have sought.

The main thing is that they announce the release of Leopard-compatible beta versions of much of Unsanity's software. I quickly installed the beta version of WindowShade and — yea! — it works.

[Two troubleshooting notes: (1) Although the installer says that you can either log out or restart to get the software to work, I found that a restart was needed to get the essential Application Enhancer (APE) component to run; (2) After installing the new version of APE, any haxies that are not specifically recognized as compatible with Leopard will be disabled automatically. This includes haxies not made by Unsanity.]

When will these still not 100% complete beta versions be replaced by final released versions? When, if ever, will new versions of Unsanity's remaining software be released? Don't ask. Literally. All Unsanity will tell you is that "it'll be done when it's done." Unsanity adds that any more precise ETA is likely to be wrong and so they won't provide one. If you post comments requesting an ETA, they will be edited or deleted. At least Unsanity offers an apology for the delay in getting these two blog entries (and updated programs) posted, with health problems cited as a primary cause.

Most of the technical details in the remainder of the blog entries are directed at developers. Still, there are several nuggets of more general interest to be found.

The first blog entry (Pragmatic Disillusionment) is entirely devoted to explaining why the existing release versions of Unsanity programs do not work with Leopard. Although this has some bearing on what gets covered in the next entry, there really isn't much value, in my view, in slogging through the details of why haxies and Leopard have not played well together.

The second blog entry starts off by similarly staying in the past. It offers a very lengthy defense for why a version of Application Enhancer may cause a blue screen crash at startup in Leopard (as described here). Noting that it only happened if you were using an out-of-date 2.0.1 version of APE, a version that was updated more than a year before, the blog entry expresses indignation toward people who asked the "loaded question": "Why didn't you test APE 2.0.1 before Leopard was released?" The entry goes on to add that it would have been impossible to test the older version anyway, as the final build of Leopard (which revealed the bug) was not available to developers until the same time it was released to the public.

So, no, Unsanity is not apologizing for any problems caused by APE under Leopard.

At last, the blog entry moves to the present and provides links to the current Leopard-compatible beta versions of its software.

And that's all you are going to get from Unsanity, until they are ready to tell you more. Whenever that is.

P.S. The blog entries, in addition to discussing the status of Unsanity's software, contain several intriguing troubleshooting tidbits.

Most notably, they provide explanations for blue-screen freezes/crashes at startup that have nothing to do with any Unsanity software. For example:

  • An external hard drive that does not mount properly (possibly due to a problem with its bridge board) can cause a hang at startup. Because the mounting problem is typically intermittent (presumably, you would have discarded the hard drive if it never mounted!), the blue screen crash often does not occur at a second restart—even though from the user's perspective nothing has changed.

  • The Mac's inability to make a successful connection to a flaky network can cause a time-out at startup that can last as long as 15 minutes.

  • The blog entries also point out, at least twice, that InputManager software must not be installed in the user's home folder (~/Library/InputManagers) in Leopard, as it will "prevent the InputManager from loading even if the InputManager is installed globally in /Library/InputManagers and meets all the requirements to load." In other words, check your ~/Library/InputManagers folder. If you find anything there, remove it. Doing this at least offers a chance for other InputManager-dependent software to work. While most Unsanity Software does not use the InputManager, two do: Smart Crash Reports and Menu Extra Enabler. These will now install in /Library/InputManagers.