By Scott M. Fulton, III, Betanews
Download Windows 7 Release Candidate 32-bit from Fileforum now.
Download Windows 7 Release Candidate 64-bit from Fileforum now.
If you're like me...first of all, my apologies. Nevertheless, although you have more than one computer you use every day, you do the majority of your production work on a Windows XP Professional-based system. You could have upgraded to Vista, but you didn't, and it wasn't out of procrastination. It's because you knew the costs involved and the headaches that would ensue, and because you also knew from experience that Vista, in the end, was slower for everyday tasks than XP. Certainly it's more secure, but you have enough access to security software that you can stay vigilant and maintain your systems without serious trouble. Yes, that's if you're like me.
The promise of Windows 7 is that it's the Windows XP upgrade you've been waiting for. The problem with Windows 7 is that it won't upgrade Windows XP, at least not directly. You can make the two-step jump from XP to Win7 through Vista, as we discovered a few months ago, but you need a Vista installation disc to do it. You don't have to register the Vista installation in-between, so you can legitimately borrow one from a friend.
But if you're like me, then what you need to know from the Release Candidate is this: Will the software you use every day be able to survive the jump from XP to Win7 mostly intact, or would you actually sustain fewer headaches by installing Win7 on a fresh PC and reinstalling all your apps? And if the latter is the case, then should you even bother even a test upgrade?
Here's the part where I can start congratulating you for being like me, because you're at least smart enough to know that your desktop production PC should have at least two hard drives, and that your documents and media should be located on the second one (drive D:). You keep your operating system and applications on a smaller, faster hard drive that's easier to maintain and upgrade. I keep XP and its apps on an 80 GB drive -- today, it's almost impossible to find an 80 GB drive new. So now have this option: You can purchase a relatively inexpensive hard drive that can easily hold two copies of your prime partition. A half-terabyte Barracuda costs about sixty-five bucks.
Creating an image backup to an external USB drive is an almost academic process now. I use Acronis True Image as my backup program, and it hasn't failed me once -- you can download it from Fileforum, use it now, and pay for it later. You'll need a good backup program like this to take a snapshot of your C:\ drive that can be recovered later to your new, bigger hard drive without endangering the activation on your XP.
Acronis comes with a recovery system that enables you to boot a special hard disk restoration environment from CD-ROM. You'll actually want to use this to restore XP to two partitions -- one just for using XP normally and doing your regular work, and the other for testing Win7 knowing you have a safety net if all goes wrong.
As an alternative plan, if you have never used the BartPE system recovery environment, you may come to wonder why you haven't let Windows fail more often. You do have to build the recovery CD-ROM yourself, because it requires you to supply Windows XP as the kernel, and BartPE can't supply XP for itself. Once you've booted your system with BartPE in the optical drive and your new hard drive installed, you can use it to create your two partitions.
Although technically you should be able to boot essentially the same operating system (for now) from two partitions, there's a chance you may need to manually edit the BOOT.INI file to ensure that there's two options when you boot from your new hard drive, and that the second option accounts for partition(2). Once that's worked out, you should be able to boot to the partition you've chosen for your Windows 7 test.
We've heard two stories from different sides of Microsoft. Company strategist Mike Nash has been quoted as saying you should treat the RC just as though it were a final release; at the same time, we've heard it might not be desirable to "upgrade" from the RC to Windows 7 RTM once it becomes available. My suggestion is that, while you do go ahead and test your applications in the Windows 7 partition you've created, you do not plan to upgrade from the RC to Windows 7. Instead, make a note of the best practices you've learned from the business with the Win7 partition, and then be prepared to wipe the RC clean and start over with a fresh upgrade...if you take Acer's word for it, once October rolls around. As long as you keep your vital documents and media on a separate drive anyway, you do compensate a bit for all the trouble you're putting yourself through. (That said, you might consider backing up your documents and media anyway before proceeding, for reasons I'll talk about in a bit.)
Next: What should you be testing for?
What should you be testing for?
Although Microsoft has published a handy reviewer's guide specifically for the Windows 7 Release Candidate (Microsoft Word file available here), its purpose is to highlight the new and enhanced features of the operating system. That makes sense if you're installing Win7 on a fresh physical or virtual machine; but if you're testing for usability, there will be a lot more to it. Even if you're just trying a test upgrade from Windows Vista and not XP, you will want to experiment with, and make notes about, the following:
- The integrity of your system folders. As you may know, system folders since Windows XP have been convenient aliases for deeply nested subfolders, especially in the case of personal folders. Vista moved personal documents to the physical location C:\Users\username\Documents, and the fact that Win7 has changed the name of the alias to this location from "Documents" back to "My Documents" (as it was with XP) does not impact this location. However, although Microsoft-brand apps and others should have the least difficulty with handling system folder locations (requesting their targets from the API), other software may encounter difficulties knowing where your personal documents are located even though, physically, they haven't moved.
- The integrity of your MP3 and media files. This is another reason you may want to back up your documents and media as well: We all know that Microsoft is testing some new features in Media Player, some of which are...well, surprises. The other day, I encountered some "album art" in my Windows XP physical directories that I didn't put there myself; it just so happened that Media Player 12 in a virtual Win7, on its whirlwind, clandestine trip around the network, started cataloguing files within their native directories. One side-effect that some users of the earlier Win7 betas encountered was the unexpected lopping off the top of their audio files, by Media Player 12 as it adjusted the metadata of MP3 files...again, without notifying anyone. Supposedly this product was fixed by a Media Player update, but that's not to say something similar won't crop up again.
- The efficiency of your security software. So far, this has been a largely unexplored subject with regard to the Win7 betas: How well will third-party security and anti-malware software work in the new system? Though there are no sweeping kernel changes as there was for Vista (Win7 is actually an in-generation Vista upgrade, like Windows 98 was for Windows 95), changes to system folder aliases and the addition of the new shared libraries feature may necessitate behavioral changes to even Vista-era anti-malware software. What's more, the new Action Center feature of Win7 is supposed to coordinate all types of security activities, including with third-party products; and existing products won't be prepared for such a coordinated effort.
- The connectivity of your network components. The Homegroup Networking feature of Windows 7 is geared to connect networking components and other Win7-based computers to Win7-based networks. But you cannot use a Vista-based computer or older as a homegroup member, at least for now (conceivably, Microsoft could come up with a Vista upgrade, though it may simply choose not to). Win7-based homegroup members are supposed to behave better together than ever before, as well as stay compatible with workplace networks to which they may also belong from time to time. But you can only test this with two Win7-based components. However, if you have two computers, you could conceivably run one copy of Win7 in Virtual PC 2007, hosted by Vista or XP. You could then set up your physical Win7 machine as the nucleus, if you will, of the homegroup, and then set up libraries to be shared between the two. You can also then test Windows Media Center on the physical machine, especially to judge how well homegrouping aids in the promise of steadier streaming, especially over 11g and slower Wi-Fi connections.
- The effectiveness of the revised automated troubleshooting. During the beta phase of a product's testing, companies (especially Microsoft) typically forego completing the documentation process, often leaving pages blank. Some type of automated troubleshooting has existed in Windows since XP; but in Windows 7 and Windows Server 2008 R2, Microsoft's trying an interesting new strategy, which is only barely alluded to in this document: It's enabling third-parties to create troubleshooting packages for known problems, letting others generate PowerShell and other scripts that could effectuate solutions to known and published problems. We may see the first trials of this approach (if someone other than Microsoft is brave enough to take the first steps) during the RC phase of Windows 7 testing.
Essentially, what you should be looking for during the RC phase is the proper transition path between your old operating system and Windows 7. With an easily restorable backup of your old system in place, and a parallel version running in an alternate partition, you should be comfortable to experiment with ideas that might fail -- for instance, removing older-era anti-malware software, or installing old software you've used before and that you wanted to use with Vista but couldn't. Take thorough notes of your process, and make system restore points frequently. When you do encounter problems, consider them discoveries that you're glad you found now rather than later.
Download Windows 7 Release Candidate 32-bit from Fileforum now.
Download Windows 7 Release Candidate 64-bit from Fileforum now.
Copyright Betanews, Inc. 2009