Lynn was having issues with her MacBook laptop where she couldn't find our wireless router -- well, that isn't entirely true. It would pick up someone's wireless signal and mistakenly identify it as our wireless signal. So, for a few weeks, she was basically using someone's free wireless signal, thinking it was ours. It was all very strange, but basically it meant that her connection would fade in and out and any sensitive traffic was flowing through the airwaves unencrypted through someone else's router. That's enough to give anyone even slightly paranoid the heebie-jeebies.
After diagnosing her issue for awhile, I could get it to connect to our actual router, but only sporadically; if she ever put her laptop to sleep, it would lose the connection -- not the most ideal situation. So, right around this same time, Leopard came out and I saw in one
very thorough review that the network preferences were upgraded. That was enough to convince us to upgrade to the new OS X.
After going through a pain-less upgrade installation of the new operating system on Lynn's MacBook (the weird wireless issue went away, everything worked great), I decided to update my aging Mac Mini. I tried to do the same upgrade installation that worked so well on Lynn's laptop and I got the dreaded
blue screen of death. I have had my own share of issues upgrading Windows before, so I just shrugged, powered down, and started the upgrade again. Again it hangs before the login screen pops up and I start to panic. So, praise be to Google, I found the
Apple support forum that details the ramblings of lonely Mac geeks and their hypothesis of why this was happening. After reading that it might have to do with the Unsanity's
Application Enhancer product, I realize that I had installed it awhile ago to fix a quirk in an old version of
Parallels that has since been rendered unnecessary by the new version. Cursing my fool-hardy attempt to escape the enclosed system that has been blessed by the Almighty Steve, I grit my teeth and install Leopard using the Archive and Upgrade option and everything was right with the world.
Overall, Leopard is a nice evolutionary step for OS X. The Finder, while not spectacular, is a marked improvement over Tiger's -- less beach-balling, snappier, etc. Spaces is nice, although not anything
revolutionary -- it works well though. Spotlight is greatly improved over Tiger's implementation. Even though I just bought
Launchbar to replace the awesome, yet strangely slow on my machine,
Quiksilver, I am still happy that Spotlight works how it should have worked in the beginning. Time Machine is, uh, sort of weird. Haven't done that much with yet, so I will reserve judgement.
So, even though everything seemed honky-dory, my pain was still palpable. For Parallels continues to not include the one feature that seems like such an easy fix: in full-screen mode, they should not pass keyboard events to the host OS. If I press Ctrl-Arrow Left in Windows, it shouldn't move to another Space. I know I can turn off Spaces, or change the keyboard configuration, but that seems like such a terrible solution. VMWare provides the ability to either pass the keyboard to the host or not, hopefully Parallels will add the ability soon as well. So, because of this one limitation I made a series of somewhat rash decisions:
- I wanted BootCamp, so that I could boot into a real Windows box to code
- I couldn't create a BootCamp partition because my drive was too fragmented
- Backed up all of my data and did a clean install of Leopard
- Installed BootCamp, Windows, Visual Studio 2008, etc
It took me the better part of a weekend, but basically I did a re-install of my entire computer and all of its key systems.
Then,
this weekend I re-installed Windows, Visual Studio 2008, etc on my laptop because somehow Windows became corrupted and hung when logging into the box.
I'm a nerd.