One of these days, I’d love to upgrade a computer and have it just work.
The Mac operating system is usually the most painless, and don’t take this as a “This should just work! Die, you stupid ***********!” rant. For every one thing that goes wrong, there are about a hundred things that didn’t. But today was one hell of a day of things going wrong.
I just got a 13” 2.53GHz MacBook Pro last night. Great machine, great specs, plus Snow Leopard. Everything was painless last night—a two-hour session yielding my iTunes and Aperture libraries and all the programs I need. I wake up the next morning and pull open iTunes. “Song could not be located.”
What.
Apparently, half of my songs were still pointing to my external hard drive, although I could have sworn that I had already checked for that last night. But it’s not all of them, just some of them. Completely arbitrary. What do I do? I hit “Locate”, and point to the new file, hoping that iTunes will be smart enough to figure out that that is where all my other iTunes files are. It isn’t. iTunes wants you to go through each one of the songs individually. Screw that, I’m writing a Python script.
I happened to know that iTunes writes out an XML file of its library that you can access with Python’s plistlib. Astute readers will ask, “Hey, Ross, why didn’t you just use ‘Consolidate Library’?” Well, the files were already on my internal hard drive. Everything was copied over correctly; it’s just that the paths were off. I write a script that renames the paths. But now iTunes is complaining that some of the files don’t exist.
What.
Even though the XML file is minutes old, some of the paths in the plist file are just dead wrong. The plist claims there are no track numbers on some of the paths, but the filesystem disagrees. I still don’t get this. However, I dutifully write some logic that checks for these scenarios and finds the correct path. This actually worked for most files, except for a few that I had to correct myself.
The upshot of all this? I still had to rebuild my iTunes library, since I had lost most playlist information, and both my iPods had to be resynced. Ugh.
Later the same day, I need to print something out. I have an HP psc 1350 All-in-one—an average printer from about five years back—that still works great. It is also, unfortunately, one of the few printers that Snow Leopard does not support.
What.
This printer has worked with the default drivers since I’ve had it. My Ubuntu machine can talk to it out-of-the-box, for crying out loud. After much Googling, I find that installing the drivers from HP’s website should work. The drivers from three years ago. Okay, sure. I install them, but find that the damn software keeps popping up a Setup Assistant every time I turn on the computer. How do I make the madness stop?
I find out that in a mislabeled section of HP’s support, there are more recent drivers. I have now downloaded those, and they appear to be working. BLUH.
So the moral of this story is: don’t upgrade optimistically. You will be disappointed. Stay tuned though, because I’m still playing with Snow Leopard’s Grand Central Dispatch, and it’s shaping up to be pretty neat.