More Proof that Apple Will Win
Originally posted 2007-08-21 17:17:22
Last year I built a computer with parts ordered from newegg.com. Over time, and because of its faster processor, larger hard drives, and buckets more memory, my home-built computer has replaced my aging iBook G4 as my principal away-from-work computer. It runs Ubuntu 7.04 (64-bit), and Compiz Fusion amazes everyone that happens by. I realize that building my own PC separates me from Grandma Myrtle, Joe Sixpack, or whatever other metaphorical average computer user you favor, but I’m no Jeff Atwood. I got recommendations from my then local LUG president for which parts to buy. When my new machine wouldn’t power on, I sought the help of my local office alpha geek, who directed me to check my power cables to the motherboard (I had ’em backwards). Without them, I’d have had to get a Dell, dude. In other words, I’m a former developer who’s now in management.
A few days ago, Ubuntu notified me of some updated software available for download, including some kernel updates. I downloaded the updates and restarted my computer. The machine wouldn’t POST. The BIOS screen appeared, directing me to press F2 for setup and informing me that it was using dual memory mode, waited about five seconds, then recursed into a reboot. I stared dumbly at the screen for a few cycles, tried pressing F2 when so directed, tried mashing F2 repeatedly as if I were playing Track and Field back in the day, tried powering the machine all the way off and all the way back on, and tried throwing books at the wall and shouting oaths I’d reprimand my children for, but could not stem the abbreviated-POST-and-reboot cycle. For awhile I blamed those stupid kernel updates for corrupting the kernel, until I realized that the BIOS wasn’t seeing the hard drives to even try booting the new kernel. Eureka! The hard drives must have spun loose from their cables by a particularly jarring kernel update! Did I mention I’m in management? I laid the machine’s innards bare, detached and reattached all cables leading to the hard drives, removed and reseated the RAM since I was in there anyway, and hopefully powered the machine back on (I did know enough to power it off–a smoked CD-ROM drive from my distant past testifies that I haven’t always been that bright). No change. I did notice, however, a strange sequence of letters in the lower right of the screen–something like 6B3E0 (I’m making that up, but it was some sequence that’s just a little too long to name a Star Wars droid and a little too short to be a sysadmin’s password)–that had presumably been there since the moment of the first reboot.
Exhilarated, I leapt to my motherboard manual, cracked it open, and found no error code reference. Undaunted, I googled the error code, and found a few threads on a couple of discussion forums complaining of the same symptom. Salvation at last! Each thread, however, admonished the sufferer to pursue the same remedy: return the under-warranty motherboard to its manufacturer and demand a refund. I’m about 17 months into this motherboard, so returning for a refund didn’t sound likely. I nearly punted at that point and ordered a Dell, but I clicked that one more Google link that offered a possible solution: completely unplug the computer and plug it back in. RIIIIIGHT. Expecting Allen Funt to pop out of my closet at any moment to reveal that I was on Candid Camera, I disconnected the power cord from the power supply, reconnected it, turned on the machine . . . and up it came, complete with updated kernel.
You EE majors are now giggling uncontrollably, gasping, \”Of course, you idiot, you have a bug in your BIOS, and you just had to reset it! You should flash your BIOS at your next opportunity!\” Let me just say that I don’t even do email in my underwear, let alone flash my BIOS, and I resent that something so simple could end my anguish. Telling someone to fix a computer problem by unplugging it and plugging it back in sounds an awful lot like sending someone on a snipe hunt or calling a grocery to store to ask if they have Prince Albert in a can. I’m embarrassed for engineers everywhere that it worked.
Why does this prove that Apple will (eventually) win? They’ll win because the control the hardware, they control the software, they control the BIOS, which is actually EFI, and they would never make me stoop to unplugging my computer and plugging it back in to get it to boot up. Now, if they would just port Compiz Fusion to Mac OS X . . . .