by Craig Anderton
What do the Mac's Snow Leopard and Microsoft's Windows 7 operating systems have in common? Answer: both came out over three years ago. I'm not sure what that is in dog years, but it's about 60 in computer years. And whether you like it or not, at some point you'll have to upgrade if you want to run particular programs that are available only on the latest and (hopefully) greatest operating system.
But there's more to the story, because sometimes you'll need to re-install an existing operating system. You'll know you need to do it because one day, you might be unlucky enough to turn on your computer to boot up your DAW or play a soft synth, and get an error message that goes something like:
0234890 Bad F-Line Trap KernalSanders 0002:VX:RTFM:BURP:666
Translated into English, this means:
This type of catastrophe tends to be more of a problem with Windows operating systems thanks to the legacy of DOS (acronym for “Dumb Operating System”), where the phenomenon is known as the “Blue Screen of Death.” For the Mac, the equivalent is the multilanguage gray screen that tells you that you're hosed, you need to reset, and you probably lost some data.
Without getting into a Windows vs. Mac debate (remember, I use and love/hate both), my experience is that my Mac OS X machine crashes/freezes more often than my Windows 7 machine, but Windows is more likely to die a slow death that renders a computer useless. (For those brave enough to have upgraded to Windows 8, we'll see how that holds up over time.)
Most of my serious Mac problems have been hardware-related (although I’ve had to do the ever-popular “clean install” a couple times), but Windows can go psychotic from software glitches. This is because Mac developers operate under a fairly strict set of standards imposed by the Mac OS, which runs only on Mac hardware. With Windows, there are so many possible hardware/OS combinations that programs that work fine with one set of hardware and software can have unpredictable operation with others.
Someday you’ll install a new OS or re-install and old one, for any one of several reasons:
When you do change operating systems, it will be a major pain to re-create your previous environment – particularly if a long time has elapsed since you first installed the system, and a zillion updates and tweaks have occurred since then. But there are some ways to make the process go a lot more smoothly.
The best time to prepare for installing a new OS is well before you need (or want) to do the install.
I strongly recommend hedging your bets, particularly if your existing setup is working, and you want to move over to a new OS. You’ll often find that certain programs aren’t compatible with the new OS for some reason, or need a fix that hasn’t been released yet. There are two main options for dealing with this.
With the Mac, you can just change the Startup disk and boot from that. Nice. With Windows, you can set up dual-boot systems. For example, you can install Windows 8 and start migrating programs over to that; if you run into snags, then boot into your existing OS instead. Dual-booting is a common procedure, and it's not hard to find programs designed for partitioning and dual-booting.
Another option is to install a removable drive bay so you can just swap out hard drives as needed. If your previous OS and suite of programs was working okay, everything will remain on the disk, and you can just plug that disk into the bay should you need to access it again (always make sure power is off when swapping drives – they are not hot-swappable). You can even create different boot drives optimized for different work environments and situations.
But there’s one problem with multiple drives: copy protection routines that require “authorizing” a single hard drive. Because I use only legal software, during a recent OS flush I had a crash course on which types of copy protection were easiest to deal with.
If you’ve been diligent about organizing your distribution discs and downloaded programs/updates, entering a serial number or inserting the original distribution disc is not a problem. And although some people really don’t like hardware dongles, I've been won over - they can be a transparent solution that's neither computer- nor drive-specific, and allows you to back up your program.
In some cases, you'll need to request a re-authorization from the manufacturer. Usually they err on the side of the customer, assuming you’ve registered your software and don’t request re-authorizations too often.
Acronis and Norton offer programs that can image your main drive. Once you've installed your operating system, image the drive. After installing your main programs and verifying that eeverything works properly, image it again. In fact, it's a good idea to image your drive periodically when your computer is happy and working well, because they you can always rreturn to that state.
And here’s one final piece of advice: Allow plenty of time to re-create your system. This is another reason to keep your old system around, whether via removable drive or dual booting. That way you can get Real Work done as you debug your new OS. Good luck!
Craig Anderton is Editor Emeritus of Harmony Central. He has played on, mixed, or produced over 20 major label releases (as well as mastered over a hundred tracks for various musicians), and written over a thousand articles for magazines like Guitar Player, Keyboard, Sound on Sound (UK), and Sound + Recording (Germany). He has also lectured on technology and the arts in 38 states, 10 countries, and three languages.