Aperture 2.1.4 & SL -- Any Light at the end of the Tunnel?

Question

On my Macbook, Aperture with SL dies just after the initial screen comes up (the one with the SN, etc). Activity Monitor and Force Quit suggests that it is running, but just not ever getting to the main screen. I've read through the long threads here discussing this and similar problems, replaced the Framework file, and completed all the steps in the Apple Tech support note HT2945, up to and including a database rebuild, removal of pref, presets, etc, and reinstallation. and update. The ONLY way I can get to a working screen now is to delete prefs, start with ALT-CMD, and do the consistency check. It then comes up with a basic screen that lets me navigate projects, etc. The part that seems to consistently kill it involves accessing anything associated with the vault. The screen redraw goes flaky and the whole thing grinds to a halt. I have masters relocated to a network drive -- something that worked fine up until the recent upgrades.
Aperture 2.xx worked like a charm on this Mac up until a couple of months ago. I'm feeling a bit let down by Apple on this. Thirty years of pictures essentially unavailable. Anyone have any suggestions on next steps?

Answer 1

Ben wrote:
Emory wrote:
Are you really trying to say that I should be greatful for getting any email at all on a device sold and marketed for mobile email? You really think they're giving something away for free?
Of course not, its still a business, and business generally like to make money. However the BIS server is designed as a "Consumer" level of service, and isn't targeted towards the business segment. That is after all what BES is designed to do.
IMAP support is a relativly recent addition, and like anything else thats been added in the past, I'm sure its support will be expanded.
The BES is designed to manage, deploy, and enforce policy on mobile devices and enable them to talk to proprietary email services/groupware that they otherwise wouldn't be able to talk to.  
I'm not asking for the world here -- I just want IMAP support to mean that RIM actually supports IMAP.  I'm not an enterprise.  I have no interest in hiring a company to maintain an Exchange infrastructure for me.  And even if I did, I could use ActiveSync with a variety of devices that still wouldn't require a BES.  But that wouldn't be a BlackBerry device, and I'm rather fond of mine.  
While I can appreciate that the BIS is a "Consumer" level of service, that doesn't mean that we're not looking for so-called "Big Business" features like having more than one folder for email.  It means that some consumers don't like flushing money down the toilet to support an architecture like Exchange.  Steering people towards a BES means you're really just steering them away from RIM. 
We're able to do much more, with less resources, relying on open services: Cyrus IMAP, Postfix MTA, and a *wide variety* of MUAs.   Why I would scuttle cost-effectiveness and instead opt to spend around $2800 to get a single-user license for the BES on top of the hardware and software costs of Exchange is completely beyond me.