Shirt Pocket Watch

Apple can sometimes make small changes that have unexpected consequences.

Take Partition Schemes, for example.

This is the kind of thing most Mac users never think about. You buy a drive, plug it in, drive comes up, things work.

Done.

What you probably don't know is that most drives came partitioned and formatted for Windows, even when the drive is listed as "Mac Compatible", typically using Master Boot Record as the partition scheme and FAT32 as the format.

Before OSX 10.4.6 or so, this wasn't a big deal, at least for SuperDuper! Since FAT32 isn't appropriate for storing Mac files with full fidelity (and has various other issues, like file size limits, etc), we would instruct the user to erase the drive, using HFS+ (Mac OS Extended) as the format. Disk Utility wouldn't allow HFS+ volumes to be hosted on Master Boot Record partitioned drives, and so the user would need to select the drive, rather than the volume, and erase that way. No big deal.

Then, the Intel Macs came out, and with them, 10.4.6.

To help with something-or-other (probably to allow HFS+ and FAT32 volumes to be hosted on the same drive in separate partitions for Boot Camp users), Apple decided to change Disk Utility so that it allows HFS+ volumes to be hosted on Master Boot Record partitioned disks. Which I'm sure didn't seem like a big deal: in fact, it's quite convenient, and had probably been requested as a feature over the years.

All that's great, except for one thing: Macs don't support starting up from Master Boot Record volumes.

This is clearly not a big deal for most users. But, for SuperDuper! users (and, I'm sure, for those who use similar applications) it's been a big problem: drives that look like they should act as startup volumes won't, and the reason is really obscure.

Suddenly, users who used to use Disk Utility to erase a drive now have to head to the Partition tab (which doesn't even appear if you select the volume instead of the hosting drive), click Options, understand the 3 partition types, and partition their drive appropriately.

So, this one small change -- allow HFS+ volumes on Master Boot Record partitioned drives -- ends up having a pretty big impact on users with external drives. This is mostly due to its implementation (and lack of documentation).

Worse, users aren't steered to the right choice by Disk Utility. In fact, the default is to do the absolutely wrong thing for most: retain a Windows partition scheme.

This probably hasn't had much of an impact on Apple's support, but it's sure hurt here!

I've listened to This American Life for years on NPR: it's a great radio show. And now, they've managed to add a TV version to their portfolio. It's on Showtime, and is both new and remarkably faithful to the original vision.

Showtime has been good enough to put the first show up for free on their web site.

Enjoy!

I've just heard that Rich and Kerri have lost Rufus, their nearly 14-year old dog.

Buddy was 13. He'd had a very good run. (Most of it through the water!) He was, hands-down, the best dog I ever knew, or had even heard of. He was fun and playful, loved everyone, and was immensely obedient...for most of his adult life, he never even needed a leash. He never ran away (except to sneak a couple of houses away to my mother's to mooch cookies), he never bit anyone, he never even jumped on people...he always came when you called him. He brought the paper in every morning -- he'd even do his level best with the Sunday paper. He brought me bottles of water when I was laid up with a broken ankle. He let kids pet him and let babies pull his ears and tail and fur, and never once complained. Oh, and that bark -- he sounded awfully scary, protecting his family like a sentry. Never had a problem with his hips, his eyes, his elbows...nothing.

Everyone who met Buddy loved him. I'm really going to miss him.

(Kerri, on her blog.)

Zabeth and I know this all too well -- our thoughts and love are with them.

tv is in the house -- two of them, actually -- and, well, it's good!

I'm not using it for music much -- my library is much too large for this device, and navigation of large collections, as has been said elsewhere, is quite lacking.

That said, for video material -- movies, tv shows, etc -- it works great. Playback starts quickly, even when streamed, and looks quite good. It's lacking in the audio department (it's really too bad that so much of this material, both movies and TV, encoded with Dolby Digital in full 5.1 or 7.1 surround, are reduced to ancient Dolby Surround playback, with no LFE channel, no split surrounds... much less impact), but visually things look quite reasonable.

It works great with netTunes, too, as you'd expect. As I've said many times, I run with a headless server, and it contains all my music and other content. With netTunes, it's trivial to connect to the server using a laptop while seated on the couch, and "pair" the tv with the server, change the synchronization information, purchase TV shows to be viewed -- all remotely.

I'm happy that the approach I took years ago -- truly remote controlling iTunes with its own interface -- continues to work with new versions of iTunes, and continues to prove it was the right way to go, moving forward with iTunes as iTunes itself changes.

Anyway, great stuff.

One expensive but potentially useful tip: you can use a scan converter to convert from Component input to regular Y/C (S-Video) or Composite, should you not have a component/HDMI capable TV. One example is the TV One AVT-3190 ($389). Expensive, but cheaper than replacing your TV...

The other day, I was pushing at the limits of my existing Infrant ReadyNAS NV setup, and needed to increase its size. Normally, this would be a huge project, but with the ReadyNAS it was incredibly easy to do.

You see, the ReadyNAS uses Infrant's proprietary X-RAID. X-RAID basically RAID 6RAID 5 (see comments, below) with the ability to dynamically increase the total size of the RAID as well.

So, not only will the ReadyNAS run with a single drive faiure (and hot-rebuild the drive), it can dynamically increase the size of the RAID set as well. So, all I had to do was:

1. Buy four drives of the appropriate size. I went from four 250GB drives with a total size of about 700GB, to four 500GB drives with a total size of about 1.6TB.

   The reason you don't get "all" the space on the drives is because redundant information is spread across each drive that allows any drive that goes "down" to be replaced and rebuilt with no data loss.

2. With the ReadyNAS on, and in use, pull out the first of the four drives.

   Yeah. Scary. But that's what to do!

3. Unscrew the four screws that attach the SATA drive to the tray from and attach it to the new.

4. Slide the new drive into place.

   At this point, the ReadyNAS will automatically rebuild the data that was on the original drive on this new drive. All of this has been done with the unit on and operating.

5. Wait for the rebuild to complete (it'll send you email when it's done).

6. Repeat with the next drive.

Yeah. That's it. When you're done, you do need to restart the ReadyNAS to get the volume to expand, but that can be postponed until you're ready to do it... and that's the only time the unit is "down".

Pretty cool, eh?

(Yeah, I know I sound like a pitchman for Infrant, but I'm honestly not affiliated with them in any way at all. I just think it's a great product.)

Many of you probably know that, for some reason, iSight cameras can get into a weird state where they start causing serious errors with FireWire drives.

The symptoms usually include a bunch of I/O errors while copying to a FireWire drive: failed copies, flaky behavior, crashes. All of this goes away if you power off, disconnect the iSight, wait a while and power back up.

Sometimes, the iSight stops working with iChat (it says the camera's in use when it's not, or the light comes on, but you don't get any picture), and in it was in that second state today when I had a kernel panic.

No data was lost, I'm happy to say, but I decided that I've had enough of this. Since 10.4.9 supports USB cameras, I've switched to a Logitech QuickCam Ultra Vision. (All they need to do is add Super Deluxe Extreme Edition to the end to make it really cool!)

It's not as elegant as the original iSight (it's fixed focus, horizontal format, a bit gaudy), but it's got a nice wide angle lens, built in microphone, works with any monitor, and seems reliable. Plug the thing in, and it works.

Given that you can't buy "real" iSights any more, and based on direct experience, I give it a thumbs-up.

Sorry, iSight. I'll miss you!

It's really easy to quickly outgrow your internal drive if you've got a substantial iTunes library. And, with all that metadata involved, the last thing you want to do is lose your ratings, comments, whatever.

Don't despair. It's actually really easy to move your iTunes library with iTunes itself. That's right: no Finder, no SuperDuper!, no nothing. And iTunes takes care of all the details!

Here's how:

1. Make sure the drive you want to put the library on is connected. The drive can be a network volume, local volumes, whatever -- just make sure it's mounted and ready to go.

2. Open iTunes and choose iTunes > Preferences. In the Advanced tab, choose the new location for the library.

At this point, you could stop, and all future music/movies/whatever you add to iTunes will be stored in the new location: in essence, your library will be on more then one drive, and you can repeat the above as the new location fills as well.

But, if you want to move your existing music and videos into the new location:

3. Choose Advanced > Consolidate Library. iTunes will copy all of the music from all the various previous locations into the new library location you selected above.

When it's done, make sure you're happy with what you've got. You can then delete the old iTunes Music folder in ~/Music/iTunes. But don't delete the iTunes Library or itunes Music Library.xml files: those must remain where they are.

When the new Airport Extreme Base Station came out, I was happy to see that it had some support for attached USB drives. It's a reasonable (though not perfect) way to share data in a home/SOHO situation, and I figured people would be using it to back up with SuperDuper! So -- to help out...

General Comments

A few things to point out right off the bat:

• As you've likely seen elsewhere, the Airport Disks are not fast. Don't expect blazing speeds: wired, I've seen a maximum of about 1.5MB/s.

• The AEBS gets very, very cranky if you get to a disk full situation. I've seen it crash more than once. Don't do that.

• Remember that HFS+ drives are made available through AFP, and FAT32 through SMB.

  Don't format any drives you're going to use with SuperDuper! as FAT32: use HFS+ (and partition properly for the Mac processor type you're using -- GUID for Intel, Apple Partition Map for Power PC).

• Make sure to connect a power supply to the drive.

• As general advice, please don't cheap out when you get an external drive. Really. Get one with a real Oxford chipset, USB/FireWire if possible in case you want to attach it directly to your Mac.

• Don't expect miracles. This is an inexpensive solution, and it behaves like one. If you want a real NAS, I suggest an Infrant ReadyNAS NV+: it's faster, redundant, recoverable. I'll have another post about the ReadyNAS soon.

• Remember, this is a first generation ("Rev A") product. It's likely to go through teething pains. Don't rely on them as your only backup!

Using Airport Disks with SuperDuper!

You'll note that your Airport Disks don't show up in the SuperDuper! pop-ups. This is by design: we can't currently copy directly to or from a network volume due to authentication/permission/metadata issues.

Instead, you'll follow the steps in Backing up over a network in the SuperDuper! User's Guide (Help > User's Guide), and back up to a read/write sparse image stored on the Airport Disk.

We often get asked why SuperDuper! can't back up directly to a network volume. What most people don't realize is that, for security reasons, you can't directly authenticate as "root" over a network, and that means it's not possible to store files with system ownership on a network drive.

An image, on the other hand, acts as a "local drive", and can be authenticated against, even though it's stored remotely. This ensures that your files are backed up with full fidelity, including proper ownership and permissions. And since it's formatted as HFS+, it avoids various situations that can ensue trying to emulate HFS+ semantics and metadata storage on a non-HFS+ drive, while still storing in a native, non-proprietary, Mac-native format.

I'd suggest doing your first full backup directly to the USB drive, rather than over the network. This'll be a lot faster. You can then connect the drive to the base station, and re-select the image using the "Disk Image..." choice in SuperDuper!'s destination drive pop-up. (Note that although the image will be grey, you can still pick it, and ignore the "overwrite" warning. Yes, I know that UI sucks.)

That should do it: enjoy the base station!

Some time ago, I switched from MarsEdit to ecto. Mostly, I did this because I liked writing posts with "real" formatting -- that is, using the RTF editing view that ecto offered.

At the time, I was only allowing myself 15 minutes per post, and the HTML I was using in MarsEdit simply got in the way of quickly reading the post for content. Too much translation, the Preview didn't really do it for me... and it didn't look like Brent was going to find much time to work on the program (understandable, given his success with NetNewsWire).

Given that set of issues, I switched. Not all upside (the HTML generated by the RTF translator was rather sub-optimal), but overall it worked for me.

With Daniel Jalkut's recent acquisition of MarsEdit (congratulations, Daniel!), and his flurry of activity improving the core and fixing bugs, I've decided to give it another shot. And to get around the readability problem, I'm giving Markdown a try.

I don't know why I didn't use Markdown before -- probably, I didn't want to learn yet another thing. Maybe I just wasn't aware of it. But I'm glad I've finally found it and taken the time to figure it out. Markdown's pretty easy: natural to read and write once you grasp the basics. JG and Aaron Swartz did a good job with the syntax: it's regular, logical, functional, readable.

And it's supported by Expression Engine, too.

So, three posts later, I'm sticking with it. Hopefully with these few changes I'll be able to find a bit more time to blog!

It wasn't that long ago that HP had the absolute worst OSX drivers of any major peripheral developer. Their scanners barely worked, their printers sort of worked, the software they loaded was pretty shamefully buggy, flaky... they just sucked.

So, imagine my surprise when -- after a recent Mac purchase at the Apple Store -- I decided to get a "free" HP C6180 all-in-one printer and... hey! It's been de-suckified!

The thing is well designed, has good drivers, built-in networking, even scans and faxes over the network -- pushing or pulling to multiple "associated" Macs. It's not perfect but what the hell? It's like someone is writing these drivers who actually uses a Mac!

When did that happen? Doesn't HP know they're supposed to have crappy Mac products?

And after that good experience, and reading a number of great reviews, I grabbed an HP B9180 Photosmart Pro Printer, too. Again, a great printer, with good drivers, built-in networking, relatively frugal with inks, good paper handling: and it generates great prints.

This is HP -- "we generate huge dots with expensive ink and our photos look like crap" HP. And -- not.

Wow. I don't know what's going on at HP, but they should definitely keep it up.