[audio:http://media.libsyn.com/media/maccast/MC20090408.mp3]
Download today’s show here! 
MC20090408.mp3 [35.9MB 01:18:20 64kbps]
A podcast about all things Macintosh. For Mac geeks, by Mac geeks. Show 262. Apple releases 2nd iPhone 3.0 Beta. Snow Leopard closer to being on the prowl. Shuffles shake up some sales. XServe’s go Nehalem. AT&T TOS blocks Sling, then doesn’t. Rumors paint next gen iPhone picture. HD Rentals now in iTunes with 8.1.1. iTunes goes all DRM free and variable. Follow-up on Macbook cracked case repairs. More Appleworks discussions. My opinions on Applecare for the iPhone. Migrating data to a new Mac from backups. Matching Memory. Leopard USB Disk formatting mystery. Using iTunes codes to bypass region control.
Special thanks to our sponsors:
Faronics Deep Freeze
RCP Tones – Sophisticated Ringtones for iPhone 3G. Business Rings, Sleek Melodic Alerts, Beeps, Chimes, Alarm Sounds & more. No hidden fees or subscriptions. No DRM.
New music, Shadow of Me by Mr. Jason (iTunes)
It’s a dangerous business going out your front door — J. R. R. Tolkien (1892 – 1973), “The Fellowship of the Ring”
Subscribe to the Podcast Feed or Get the MP3 or AAC (enhanced)
I just ordered on the those Steve Jobs plush doll last week, should be in a few days. I found it out via iJustine.
Hi Adam,
re: TimeMachine backups & how OS X identifies “different” computer/TM-backup combinations:
A month or two ago my MacBookPro (3,1 June07) succumbed to the legendary nVidia 8600 GPU failure. Took it to my local Apple Store & they replaced the motherboard. When I got it back, Time Machine wouldn’t recognise the TM db already on my Drobo (& nor would AppleTV show up in iTunes anymore – I had to delete the iTunes pairing & re-sync it from scratch).
After a lengthy call with Apple Care, it turns out that OS X identifies a TM backup destination with not just the hard-drive’s UUID as you suggested (which in my case had NOT changed) but also the wired ethernet NIC’s MAC address, which is also a unique identifier. Although the few terminal commands to fix this were simple, there was a complication with syntax because my Mac’s ‘computer name’ has both a space & an apostrophy in it & the tech had to check the syntax a couple of time with a colleague, and then me re-type them each time, hence the length of the call, otherwise it would have been much quicker. After doing that the existing TM db on my Drobo was recognised OK. The next TM backup took ages, but after that it was all back to normal.
However, I would be a little wary of doing this in a scenario where you simply change/upgrade your Mac & wish to maintain your TimeMachine backup ‘history’. While this should be OK for user data, I suspect that subtle differences between system files on one Mac model vs. another *could* cause problems if you were to attempt to restore system files, or especially an entire system partition – you could, as just 1 example, go replacing multi-touch-pad-aware system files with non-aware system files that came from your *previous* Mac’s backup. I’m also aware of other ‘customisations’ to OS X apps for specific Mac models, like iTunes/Quicktime (if i remember right??) on the MacBook Air (who knows why..). Not fun!