A Lost Weekend With Windows 7
Dec 14, 2009 6:00 AM PT
This is a story without a happy ending.
For months I, like many others, had been bombarded with fawning reports about the latest edition of Microsoft's operating system, Windows 7. Admittedly, I was skeptical. Then I tried out a new laptop running the OS, and I was sold.
I took to the software's new features like a vampire to blood. Viewing thumbnails of open documents from the task bar was great. Pinning items to it for swift access was terrific, too. Without breaking a sweat, I was shaking windows to clear my desktop and snapping them so they'd appear side by side without going through the hassle of resizing.
This is so good, I thought, I should install it on my own desktop. Sure, my Gateway multimedia monstrosity was 3 years old, but I ran Windows 7 Upgrade Advisor, and it said I was good to go.
Playing It Safe
Nevertheless, I planned to play it safe. I'd install Windows 7 in a partition on my hard drive and create a dual boot system. When I turned on my PC in the morning, I'd have a choice of either using Windows XP or 7. That way, I wouldn't have to totally upset my work routines while breaking in the new OS on my machine.
When casting off on a major project like this, it's always prudent to back up your data. It was at this stage that I should have realized that my mission may be hexed.
I started my backup at 6 p.m. on a Tuesday. After letting my computer cook all night, I thought the measly 100 GB backup would be finished when I checked in at 7 a.m. the next day. It wasn't.
After 21 hours, the backup software said it had finished its task, but a quick check of the external hard disk revealed nothing resembling a backup had been written to it. A review of the device's properties revealed why. There wasn't room to fit a backup on it.
Message From the Gods
Silly me. I thought the backup software would have alerted me to that before it started doing its pseudo backup my data. At the very least, it could have told me the backup failed when it became apparent it couldn't finish it.
Unfortunately, I misinterpreted this sign from the silicon gods. I thought they were telling me it was time to get a new external hard drive. What they were actually saying was something quite different.
Within 48 hours, I had a new terabyte of external storage -- no worries about running out of space on this baby -- and was ready to revive my efforts. This time the backup only took 13 hours.
Now it was time to partition my hard drive. There are lots of commercial partitioning programs out there. Being a cheapskate, I decided to go with a free offering called "Easeus Partition Master Home Edition 4.1.1." The software is easy to use, and the partitioning process is a straightforward one.
Auto Worker Anxiety
After launching Easeus, a window appeared listing the drives on my system and any existing partitions on those drives. I chose to resize the largest partition on my hard drive. The partition is 294GB. I aimed to reset it to 194GB with 100GB for the new Windows 7 partition.
Given its marching orders, Easeus shutdown my computer and rebooted in its own environment. There it began executing batch files to create the resized partitions. Before it could finish the operation, though, it aborted and declared, "Failed to Complete Batch Operations. Unknown Error."
My computer rebooted, and as I waited the five-plus minutes for Windows XP to start running, I began to get as anxious as an auto worker ruminating about job security. Did the software scotch my hard drive when it botched the partition?
Luckily, everything seemed to be running normally. That emboldened me. I dusted off an old copy of Partition Magic, an old commercial program for carving up disk space, and installed it. Maybe it would succeed where Easeus could not.
Back to Command Line
Partition Magic bombed too, but it left a thread of hope. Before the program threw up its hands in surrender, it uttered, "Error 1530 While Executing Batch."
A Google search on Error 1530 suggested that disk errors on my hard drive could be thwarting my attempts to partition it. The suggested remedy was CHKDSK.
There's an old chestnut, I thought. CHKDSK is a DOS utility that runs from the command line, also known as the "C:> prompt." I think the last time I used the C:> prompt, Ronald Reagan was in office, but desperate times call for desperate measures.
My first attempt to run the utility from the Run line in XP failed miserably. An alternative method, however, proved fruitful. I opened up My Computer, selected my C drive, right-clicked on it and chose Properties from the menu that popped up. A tabbed window appeared. I clicked on the tools tab and ran the error-checking option. An hour and a half later CHKDSK reported that it found no errors on my disk. It was apparent my partition scheme wasn't going to work and that I'd have to forestall installing Windows for now. My partitioning efforts had come to the end and so had my weekend.
More to the Story?
My failure to avoid a "clean install" of Windows 7 was disappointing, but it didn't shut the door on upgrading. There are programs, like PCmover from Laplink, that promise a smooth transition to Windows 7 from XP without the hassles of a clean install.
Those hassles include reinstalling all the applications running under XP. On a 3-year-old computer, you can imagine what that would be like.
Then there's the last resort route, the one I took when faced with the harrying task of upgrading my last computer to Windows XP: I shirked the task by buying a new desktop.