Tweets for the Week
- Bummed to learn the NFL Experience isn't running this year. Worked on it from XXVII – XXXIV. Always got a kick seeing my work on pre-games. #
- What are u more psyched for w the Superbowl? (via @eastd) Definitely the game. Should be a good one (finally). #
- Any #Quickbooks and #FileMaker gurus know the best format to have someone export from QB for importing into a FM solution? Options needed? #
- Just discovered {less} http://lesscss.org/ OMG. I'll never write CSS the same again… ever… #
- Got a boiler-room head hunter type call looking to fill other positions at day job. Probably time to set my LinkedIn profile semi-private. #
- Just received $25 "donation" (the max possible) for my humble little Mac utility. Always stuns me when someone chooses to be that generous. #
Secure Virtual Memory on OS X
Since the purchase of my 2009 MacBook Pro, I’ve had a nagging issue of anytime the machine sleeps for an extended amount of time (30 minutes or more), when I woke it, it would freak out and apps that ran fine before putting it to sleep suddenly start crashing on launch. The system would become so unstable that a full restart was required to get back on track. I’ve always chalked it up to a flakey machine, and that it was something I would have to live with.
Last night, when I cracked the MBP open, I was greeted with a nasty kernel panic which lead to a whole array of disk errors that could only be repaired using DiskWarrior (a huge shout out to Steve Basile (@xebrawerx) for the reminder on Twitter — this saved my bacon last night).
After rebuilding the disk directory, I decided to see if I could get to the bottom of the flakiness once and for all. I started off by disabling every “add-on” utility I had: Growl, TextExpander, Hazel, Default Folder X, etc. Then I got to digging around in the Apple control panels to see if there as a setting I was missing somehow.
When I got to the Security system preference, the “Use secure virtual memory” was selected. It got me thinking that if the VM was being encrypted, and when the machine is put to sleep that maybe something in memory (RAM) or on the hibernation disc image is changing which doesn’t match the encrypted VM somehow on wake, thus causing the machine to not know what’s where in RAM. It’s a stretch, but worth a try I figured.
So far, by turning off the “Use secure virtual memory” option — which I’d enabled in Leopard 10.5 without issue — the machine seems quite stable, waking without issue. As a (possible) added bonus, performance seems to have increased a touch since the virtual memory isn’t having to be encrypted on the fly.
More to follow if there’s anything worth noting — as in I was wrong in my assumption and my MBP is really a MBL (MacBook Lemon).
UPDATE: Nope. That didn’t fix it. Back to the drawing board. Thinking Genius Bar visit is in order for this weekend. Maybe bad RAM?
UPDATE 2: Decided to completely wipe the machine and do a fresh install of Snow Leopard, along with fresh installs of all applications. A pain in the backside, but the only real way to be sure it’s software related instead of hardware. More to follow…
Tweets for the Week
- Just gave blood at Red Cross. Busy as heck, but always worth the wait to help the newborn littles with my special blood type. #
- Using Chrome as my default browser for the past week. There are some things that bug me about it, but it could be the Safari killer for me. #
- Toyota fleet manager called to buy my 2006 Tundra since they can't sell new models. Gave them ridiculous terms. Doubt I'll hear back again. #
Tweets for the Week
- Yasu 2.6.6 Released http://bit.ly/clrN9Y (via @yasumac) #
- Don't see the fascination w/ the #iPad Too small (underpowered) for serious tasks. Too bulky for other mobile uses. Can't dog-ear a page. #
- Bad news from the Doctor today. All those numbers that are supposed to be good to live long and prosper? Well, they aren't. #notakidanymore #
- Found 38 updates waiting for Windows Server 2003 I updated about a month ago. 90% of them are Security updates. Hrmmm… #
- An auspicious day. About to send day job #FileMaker 6 solution off for conversion by @Excelisys. It only took 5 years to get done too! #
Yasu 2.6.6 Released
Yasu 2.6.6 has been released which addresses the “error 2″ error issue that some users have been reporting. It’s a recommended update for all users. Please visit the Yasu page to download the latest version.
-
Search
Flickr
