Mountain Lion – Notification Center Shortcut

Posted on July 27th, 2012 by Luke Sheldrick.
Categories: IT / Tech.
Tags: , , , , , , , .

27 07 2012

Just a quick one. Have been using Mountain Lion for just over a day, but noticed there wasn’t a quick way to see the notification center

Seems there is a shortcut available in the keyboard preferences, it’s just not set. So just assign your preferred shortcut, as below.

 

 

0 comments.

Mountain Lion

Posted on July 26th, 2012 by Luke Sheldrick.
Categories: IT / Tech.
Tags: , , , , , , , , , , .

26 07 2012

So, Mountain Lion came out yesterday. I bought Apple’s new Macbook Pro with Retina, so am entitled to a free upgrade.

Applied for the redemption code, had to give a load of info, like purchase date, serial number..etc (not quite sure why, surely Apple can check this against my AppleID). Anyhow, they send you out a password and a password protected PDF in separate mails. Received mine within the hour, go to use it, and it informs me the code has already been used. Took a look on twitter, and seems everyone was in the same boat. According to numerous reports, Apple Support are saying to wait 72 hours, when a new code will automatically be issued.

I’m sorry, but that just sucks. I buy their top of the range laptop (well as well as most other things), and now I have to wait for the new shiny! Boo. I have a MacMini I use in my home office, which I’ve read mixed reports if the upgrade code would work for, so decided to just pay for the upgrade, as I’ll probably have to anyway for the MacMini, and I can use that on multiple machines.

Upgrade was pretty painless, a few things are broken, whilst developers update their code (and more importantly, make it work within the App Sandbox). I was reading up on PowerNap, as this is one feature that I think is really cool. My MBP will update, backup..etc when in standby. The default is to have this disabled when on battery power – however I wanted to ensure that was the case. According to the Apple KB, it’s in Power settings, and then in the Battery tab. I don’t have that. OK, so I need a SMC update before I can enable PowerNap. Great – for their latest, flagship MacBook, it’s ‘coming soon’.

WHAT?

Noticed a few things are broken so far:
TruePreview – Stops mails being marked as read in Mail. Manual Fix Here.
GPGMail – PGP/GPG for Mail. Broken at current – devs say to follow their twitter.
Hal9000 Screensaver – As it says on the tin.

0 comments.

GlobalSAN Fail

Posted on November 14th, 2011 by Luke Sheldrick.
Categories: Fail, IT / Tech.
Tags: , , , , .

14 11 2011

I bought a MacMini the other day to replace my old nettop at home. Until I get the new storage for it, I figured I’d quickly setup a LUN on my NAS for it. It seems OS X, even Lion, still doesn’t include an iSCSI initiator (wtf, really?). Anyway the typical freebie that you’d use on Leopard/Snow Leopard was GlobalSAN’s free initiator. However seems that as of version 5, it’s not a freebie.

I gave it a try, and went through their process (read giving them my details twice – once to download, then again to get a trial key)… tried it out, and didn’t rate it. So using their provided uninstall script I see the below:

WTF is that all about? Their uninstaller is trying to delet / . .. /sbin ..etc, someone really hasn’t QA’ed their code.

Have emailed them to see what they say about it. Poor show.

0 comments.

10.6.7 + Aperture 3 + Final Cut Express 3 = fail

Posted on April 9th, 2011 by Luke Sheldrick.
Categories: IT / Tech.
Tags: , , , , , .

9 04 2011

Yesterday, my flatmate looked like he was going to pull all of his hair out. He was on the phone to Apple, who kept fobbing him off. So I thought I’d be nice and help out.

Problem

He had bought Aperture 3 from the Mac AppStore, and was working fine. The 10.6.7 update came out, and he’d updated to that too. Still all fine. He’d then bought and installed Final Cut Express 3. After this Aperture panic’s when it opens with something like

Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: no suitable image found. Did find:
/Library/Frameworks/PluginManager.framework/Versions/B/PluginManager: no matching architecture in universal wrapper

Attempted fixes

He’d tried un-installing and re-installing both Final Cut Express, and Aperture in all sorts of combinations. Nothing was working. He then called Apple who pointed him towards this article. However that was for 10.6.6, and he was now on 10.6.7, so couldn’t apply that update.

I took a look, and indeed with any combinations of re-installing, and even re-applying the 10.6.7 update didn’t fix the issue.

Looking at various forums, such as the Apple discussion forums, there were plenty of people having the issue. Reading those, and various blog entries, there were a number of suggestions, from applying the 10.6.6 update, to re-installing OSX (yeah, sure that would probably fix it, but not the best approach), there was even a suggestion to run Aperture in 32bit mode. Nothing worked.

My Fix

So I decided to give up on the forums and t’internets, and try my own method of tracking down the issue. I got my MacBookAir, and took a manual backup with TimeMachine (which backs up to my Solaris SAN). This meant I had a clean backup, if anything went wrong. I am also at patch level 10.6.7. I had a look in /Library/Frameworks and I had the folder PluginManager.framework.

I installed Aperture 3, and all worked. Folder was still there. I then proceeded to install Final Cut Express, and when the installer had finished the folder had been deleted. Wasn’t in the trash or anything. Interesting.

This naturally broke Aperture, as it did on my flatmate’s MBP. Just to see if I could resolve this, in a more methodical fashion, I un-installed Aperture and Final Cut, and then re-applied the 10.6.7 update. Still PluginManager.framework was missing.

I had a good copy of PluginManager.framework so decided to install Aperture and Final Cut, then copy PluginManager.framework back to /Library/Frameworks. After this everything worked as expected.

My flatemate doesn’t have any backups, so I scp’ed my PluginManager.framework folder to his MBP, and indeed, all worked.

Solution

So ignore the forums, they’re just going to have you running around in circles.

Restore PluginManager.framework from your backups, after installing Aperture and Final Cut Express.

If you’ve not installed Final Cut Express yet, make sure you take a copy of PluginManager.framework.

If you’ve already installed, and don’t take backups. Then well, that’s just silly. If you want a copy of my PluginManager.framework folder, leave a comment, and I’ll get a copy over to you. In my tests, going from a MBA, to a MBP, it all worked fine. Not 100% sure if it will work on say a MacPro or iMac, but I would have thought it would, OSX isn’t _that_ much different between machines, except for drivers.

Hope this helps someone else out there.

4 comments.

1 of 11

Templatesbrowser.com