I do a lot of beta testing for a variety of companies. I test hardware, software, and peripherals, such as printers, external drives, and USB gadgets. Other times, though, it’s a gadget, such as the StressEraser, which I was involved with in two phases of its testing prior to being released. Most of the stuff, though, is software, which is fine with me.
Playing with software — whether an operating system, an office suite, security programs, utilities, or other types of tools, I love having the chance to check the stuff out before eventually find its way to the marketplace. For the most part, yes, I am interested in the product, as I select the types of products I am willing to beta test.
In doing the beta tests, I get a chance to see, try, test, but most of all, the chance to try breaking the software or hardware before it’s in its final condition.
Because I beta test a lot of software, I re-install my operating system at least seven times a year. Sometimes, though, I have to do an install every two weeks, depending on the beta test.
For the most part, doing the restores are simple enough. What I do before a beta test is roll my computer back to “pristine” condition. By that, what I mean is I roll my computer back to nearly “fresh out of the box” condition.
By “pristine” condition, I mean a fresh install of Windows with all of the software I need and use installed, but without any of the garbage the computer manufacturer felt compelled to install. Garbage such as the “music” tools, the “free” but limited versions of software, and all the “Internet access” deals that bomb you on first boot.
After all that garbage is removed, I hack the registry, remove all the spyware, adware, and whatever other “-ware” registry entries that weren’t removed by the program’s uninstaller, and wonder: why did the manufacturer think they knew more about what I needed and wanted on my machine than the user: me.
Once all the pre-installed garbage is removed, I then knock out the backdoors the computer manufacturer put there for “support” reasons. Sorry, I don’t believe in backdoors for overseas “support,” most of which amounts to little more than a frustrating conversation with “John” in Bangladesh who does not understand the issue after 15 minutes of explanation.
When all that’s done, I use a software tool to make a mirror image of my hard drive. Basically, what it does is takes a picture of my computer’s hard drive at that very moment. It is basically frozen in time.
I save this file as a “clean” backup and restore image for when I do beta tests, but also just for a general re-install for “maintenance” every six months or so. When I do the “maintenance” version, I also go in, install all the updates and patches that Microsoft released during that time, get everything up-to-date, and create a new “clean” backup and restore image.
With this kind of image, I can reinstall Windows any time I want, so it is just like it’s brand-new installation, in about 30 to 40 minutes by opening that file.
Sure, I use that same software tool to make exact copies of my hard drive every day, so in case something really horrible happens, I have a complete backup image of my hard drive. At most, I lost a few hours of work, not months or years of work, photos, and such.
Speeding up fresh WinXP installs
To save time in doing the initial install of Windows, I use a modified copy of the Windows XP CD. It’s called slipstreaming. Until now, the process has been a little shaky at times.
Last week, though, I found a cool utility, AutoSlipstreamer v1.0, a tiny 52KB file, by Brian Hall.
AutoSlipstreamer is freeware, and is really simple to use. It allows you to slipstream a Windows XP install CD with every service pack, hotfix, update, plug, and square knot Microsoft issues for your version of XP. It does, though, require .NET framework be installed on your computer. That’s a freebie from Microsoft, just like the updates, service packs, and patches.
You can do it, too!
Slipstreaming a CD is a simple process. Basically, you create a new folder on your computer, download all the updates and such from the Microsoft update site to that folder for your Windows version, such as Windows XP Pro or Windows XP Home.
Once you have the downloaded stuff out of the way, then comes the easy part. Get out your licensed Windows XP CD, right-click on the CD drive icon, select “Explore,” and copy the contents of the CD to a different folder.
Things are easy from here.
Launch the copy of AutoSlipstreamer you downloaded, find the directory for your files, and click the Start button.
AutoSlipstreamer will combine all those patches, updates, and square knots Microsoft has issued for your version of Windows XP into a new file in the folder where you dragged the contents of the CD.
When AutoSlipstreamer is done, grab a copy of IsoBuster, launch it, and extract the boot image from your licensed WinXP CD.
Use IsoBuster – as Brian Hall says, the free functionality option will work for this, but if you like it, buy it — and make the bootable CD image.
Once the file’s done, you will need to burn the new image to a bootable CD.
No, these aren’t the full instructions for AutoSlipstreamer, nor the instructions Brian supplies on his site or with the tool. These are simply my comments on a great little piece of code. Whether you do beta testing or restore your computer’s operating system only when disaster strikes, be sure to check this out.
Quote of the Day:
While the price of freedom and security is high, it is never too high!
–George W. Bush
(He never had to worry about serving his country in combat, nor about a knock on the door from people in military uniform coming to notify him that his child is a combat casualty.)
You must log in to post a comment.