travels in hypercomputerreality

I’ve just managed to saddle back onto my PC after days of travail, brought on, indirectly, by my new trial-run anti-virus software, PC-cillin, from Trend Micro. At the beginning, after installation, my only serious problem was getting onto the net, which the firewall provided was preventing. I’ve had to switch off the firewall to access the net, but I have to learn I think to configure it more effectively.

The nightmares really began though after PC-cillin ran a ‘vulnerability check’ on my system. Not surprisingly, this uncovered an arm’s length list of vulnerabilities, all displayed in pretty colours, green for ‘hey mate there’s a problem here’, yellow for ‘this is serious mate’, orange for ‘hey, this is getting very serious’, and red for ‘get outa there, the thing’s gonna blow’.

Naturally, I felt it fairly imperative to upgrade to cover these Windows and Office vulnerabilities, though of course I knew precious little of what it all meant.

All the red alerts were Windows vulnerabilities. Underneath the list were two tabs, ‘run Windows update’ and ‘run Office update’. I clicked the Windows tab, followed a prompt or two, and was finally informed that the updates had failed. What to do? I clicked the Office tab, in the hope of at least getting rid of a few oranges and yellows, and if I remember rightly they found some things worth downloading and installing, which I did without any trouble.

But I was worried about those red alerts. Each one came with a code number attached, such as MS06-001, so I got the bright idea of typing those numbers straight into google, and seeing what it came up with. It came up with downloads – patches and such, which I merrily tapped into, downloading and installing in true compunerd fashion. I then restarted the computer, with disastrous results. My fast-flowing (well, at least flowing) PC became an instant glacier.

I won’t describe the emotional mad mouse I’ve been riding while trying to get the problem sorted, but I finally managed to get into safe mode and have a look at add/remove programs in settings. It was a long job. I tried getting rid of the latest Windows 2000 hotfix (KB842773). This had something to do with Background Intelligent Transfer Service (BITS) 2.0 and WinHTTP 5.1, which naturally means nothing to me, but on reading about it I felt that I’d been a bit previous in installing it, because it tends to interfere with the registry (qué?), and that was no doubt the problem.

Getting rid of this took me a while. I was warned that removing it would interfere with the operation of Windows Installer 3.1. I tried checking out what the hell that was. After reading an article on it I was none the wiser, but decided I probably didn’t need it so I uninstalled it. This was after trying to uninstall KB842773 without uninstalling Installer 3.1, which resulted in ‘system error, Windows is about to close’ or something like.

Anyway, I successfully uninstalled KB842773 and felt confident that the problem would be solvered, but no, things were as glacial as before. So I tried the next hotfix up the line, KB835732, and uninstalled that. I noticed that this time the reconfiguration – the deleting and copying files in winsystem32 or wherever it was – took a lot longer, which seemed a good sign. After restarting, everything’s fine again. KB835732 was the culprit. Now to investigate why. And should I reinstall KB842773 and Windows Installer 3.1? Should I try to find out what they’re for?