When I wrote my last post about Vista and the 4GB error, I forgot all about one of the best programs out there: vLite. This little program can slipstream and configure your Vista installs, so for those of you getting the ol’ 0×0000007E error when installing Vista, use vLite to make a slipstreamed DVD. And now for something completely not quite so different…
I rebooted my computer last night and as it came back up it ran a CheckDisk on my C: drive. I wasn’t too concerned at first as this does sometimes happen, but is nothing to worry about. Imagine my surprise when it started to throw up a shit load of errors relating to corrupt files and indexes. I sat there chewing on my fingers for a good 10 minutes before it finished and rebooted my machine. It has restarted ok and hasn’t done it again since, but it was enough to worry me. I’m pretty sure I can hear the disk starting to struggle and boot seems to be a fair amount slower than it used to be. Also, the drive is at least a couple of years old (bought back when it was £100 for 300GB), so whilst the computer is still working I ordered another hard drive.
The issue I had when ordering a new drive, was space Vs. speed. My current disk is a 300GB Seagate drive (I have a second identical one in the computer for all the junk I download), but I fancied giving the WD Raptor drives a go. The biggest Raptor drive available is 150GB, so exactly 1/2 my current space, and I tend to use a fair proportion of the space with games (I like me driving sims!). Also, the cost of the Raptor is currently about £120, whereas I could get a 1TB drive for £150. In the end I decided to go with the Raptor, just for the giggles of having a 10,000 rpm drive.
Now I have a new drive on the way, I had to upgrade my version of Acronis True Image to the latest version (11). For those that don’t know, Acronis is disk imaging software, in the same vein as Norton Ghost, but a whole deal easier to use and much more robust. I use it in my current workplace for making images of standard builds which I can then sysprep and distribute as needed. Which brings me nicely onto one more thing: the Sysprep tool.
For those people who have never heard of it, Sysprep is a tool included with Windows to make distributing images of disks “real simple like”. What it does is strip the hardware id’s out of the install of Windows you’re running, allowing you to create a hardware neutral image with your 3rd party imaging software. Its a really great and powerful tool, which allows you to build a system once, with all the software you need on it, without having to worry about making a separate image for each hardware variant you might possibly have. For example, here I have a CADS machine build, a Project Management build and then a couple of test builds. There are a few restrictions (at least on the Windows 2000/XP version. I’ve not done my reading on the Vista version yet) which means you have to have the same number of processors in each machine, and the drive interface has to be the same, i.e. IDE or SCSI. Although having said that, I have successfully installed an IDE image on a SATA interface and it seems happy.