I hope y'all aren't too tired of my messes to help me again.
While trying to get IE to download the roots certificates update (discussed in my other thread), I decided to let Windows Update offer again the updates I didn't install the first time, hoping that update would be one of them. It didn't list them all at once – it presented them in dribbles.
In one of the first dribbles was an update for .NET. I decided to install it. Very bad choice!
Problem 1: After the install, I tried to print a document – it wouldn't print. I opened the Printer and Fax folder and found that the update had installed the Microsoft XSS Document Writer and it had ensconced itself as my default printer and my HP printer was no longer working.
I used System Restore to roll back my system prior to installing the .NET update, thinking it would restore my system to its prior state and all would be right with my world again – NOT! It did get rid of the XSS Document Writer, but my Deskjet 682C printer still would not print. In addition to that, I now had
Problem 2: I can't access my ATI Catalyst Control Center! When I try, I get the following error message: "Catalyst Control Center: Monitoring program has encountered a problem and needs to close." At that point, the only option I have is to click on "Close".
More info on the printer: When this XP system was built, HP didn't have (and probably still doesn't) XP drivers for the Deskjet 682C. I had to buy a cable to convert (is that the correct term?) from LPT to USB in order to connect the printer to the computer. Then the XP drivers were installed for the printer, which has worked just fine until the .NET update.
Not having HP drivers, I don't have access to the printer's Toolbox, so I used the Troubleshooter in XP's Help and Support. I did everything it said up to the point where it wants me to uninstall and reinstall the USB port.
That's when I decided it was time to consult all you knowledgeable people. Any help you can offer will be greatly appreciated.
Jema