I’m hosting this blog on my home computer. It’s a five year old Dell Optiplex GX270. It originally came with an 80GB hard drive. Of course, at the time, I thought 80GB would be all I would ever need, but it wasn’t long before I added a 120GB SATA drive ( The first was an ATA drive. ) Since then, I’ve added a 320GB and a 500GB Western Digital MyBook external drive.
On Saturday, the 120GB SATA drive began to fail so Wichada and I went to Best Buy where I picked up a new 500GB SATA drive. It cost $117, which I’m sure is less than I paid for the 120GB drive it replaces.
Saturday night I went back to my office and fetched a gizmo that allows you to attach an old drive, externally, by plugging it into a USB drive, so that I could copy the important contents of the old drive to the new drive. But first I had to install Windows XP, and actually, my first order of business was to install RowPro, software that I use for my Concept2 Rowing machine. I’m training to row my own personal marathon, 42,196 simulated meters on my rowing machine. Normally, I would install all of the latest Windows updates, which in this case, included SP3. But because of my rush to get RowPro installed and get going with my long Sunday row, I omitted this step until later. This was to prove to be a big mistake!
By 10am this morning, I finally had XP installed, RowPro installed, last night’s dish’s washed and was ready to do a gruelling 30K training row which I completed in 2 and a half hours. After that, I created and formated a second partition on the new drive to hold my data then hooked up the old drive using the external drive adapter gizmo and began to transfer the data from the old data partition to the new one. To facilitate this task I downloaded the Windows 2003 Resource Tool Kit which contains a command line utility called robocopy which is a full featured and excellent copy and syncing tool. I use this because, if you try to copy by clicking and dragging in windows explorer, you inevitably meet up with copy failures that abort the whole copy process, a feature of explorer which I totally don’t get!
In searching for robocopy on the web, I discovered a gui shell to make it easier to use roboform which has a huge number of switches to choose from. I downloaded and installed that after installing the resource tool kit. The gui proved to be pretty fair and saved me from having to–once again–reading through all of roboform’s switches, to locate the ones best suited to the task at hand.
There was a considerable amount of data to copy so once I started, I could forget about it and go do something else.
It wasn’t until evening that I was finally ready to re-install this blog. I had already copied my old xampp directory to my new c:\ partition so I renamed it to xampp.bak and installed xampp. Once I had xampp installed, I installed another one of my favorite utilities called BeyondCompare. This is a file comparison tool that comes close to being a syncing tool. With this, I copied all the files and directories in my xampp tree that were different from, or additional to, those in the new tree.
After that, I only had to copy my old wordpress directory and then, my old hosts file to c:\windows\system32\drivers\etc\ so that, when I access xampp or wordpress locally, the IP will resolve to the local IP instead of the external IP that I get from my ISP.
I tried xampp before making the last change and I could access it. But, after the change, I could no longer do so. I finally realized that the cause of this was that I hadn’t hard coded my local IP so that, instead of having the one that I had put in my hosts file, I had a different one assigned by DHCP. After I fixed that, everything seemed to work just fine! I was worried that it might not be enough to just sync my new xampp directory with the old one, and that I should have exported the MySQL wordpress data before I rebuilt my system on the new drive. In fact, I actually re-installed the old drive and was able to boot and export that data, but it proved unneccessary.
But after having success with all of this, because of my haste, as I mentioned before, I had not installed the latest windows updates (including SP3) first thing after I was through with the Windows XP installation. Well, yesterday evening (Sunday) I set out to install the updates, but much to my surprise, all updates failed to install. I haven’t had time to troubleshoot this problem. If I can’t figure it out, I’ll have re-install Windows XP!
I did a search on “windows updates won’t install none” and I think I found the answer in this Microsoft article. This article lists several scenarios that can cause the problem. My situation fits in one or, possibly two. Here’s what happened:
After I installed XP I installed drivers from the Dell drivers disk. Again, I was in a hurry so, instead of rebooting between the installation of each driver, I waited until I had installed them all before rebooting. This seemed OK at first, except my audio didn’t work so I re-installed the audio driver and rebooted. But when the system came up, the mouse was unresponsive so I stuck in the XP installation disk and did a repair.
It is actually the repair that the Microsoft article says can prevent updates from installing.
Here’s the scenario that probably applies to my situation:
Scenario 1
| • | You try to update a computer that is running Windows XP. |
| • | You have repaired the Windows XP installation by using the Windows XP CD. |
And here’s the cause:
Scenario 1
This problem occurs because of how the Windows XP repair operation replaces Windows system files. When you repair a Windows installation by using a Windows XP CD, the repair operation performs both of the following operations:
| • | It replaces all the Windows system files with the corresponding files from the CD.
Note This includes the Windows Update files. |
| • | It restores the Windows registry. |
The latest version of Windows Update includes a file that was not available in the release version of Windows XP. This file is named Wups2.dll. Therefore, after the repair operation is complete, the following situation exists:
| • | The Wups2.dll file remains on the computer. |
| • | The registry entries that correspond to this file are missing. |
Because the registry files that correspond to the Wups2.dll file are missing, update installations are unsuccessful.
So the repair didn’t get rid of Wups2.dll but it did get rid of a registry entry necessary for Wups2.dll to do its work. And here is the resolution:
Method 1: Register the Wups2.dll file in Windows
To register the Wups2.dll file in Windows, follow these steps:
| 1. | Stop the Automatic Updates service. To do this, follow these steps:
|
||||
| 2. | Register the Wups2.dll file. To do this, follow these steps:
|
||||
| 3. | Start the Automatic Updates service. To do this, type the following command at the command prompt, and then press ENTER:
net start wuauserv
|
||||
| 4. | Exit the command prompt. To do this type exit, and then press ENTER. |
If that doesn’t work you can re-install the windows update agent. The instructions are in this Microsoft article.
I will try this resolution this evening. I am quite confident that this should be an easy fix.
Tortui 