Posted 29 April 2009 - 08:41 PM
I'd regard my computing skills as "average end-user": I have followd instructions and built and given myself an XP-SP2 (OEM) box with, a little more in theory than in practice, a program drive, a data drive (which I'm going to backup manually this evening), and a 1-TB backup drive. No problem getting that far. However, Outlook (Office 2007) has gotten squirrely. Sometimes it works for 20 minutes, sometimes for hours, and then . . . in the background, it starts consuming 50+ percent resources and becomes unapproachable.
While trying to solve that problem, I may have made some missteps, and I'm inclined to build the box--but the box is a pretty good functional box.
I downloaded the Tweaking Companion a few days ago and have been looking it over this evening.
I wish I could get a four-year degree in computer science inside of, say, four hours, but I'm not yet Borg.
Instead: developing language, routine, and procedure seems a better course.
Today, I uninstalled Norton Ghost, my backup utility, thinking it might have had a conflict with Outlook. Result: no. It was probably fine. Outlook still hangs.
My theme here: how would an administrator look at the problem?
The administrator tools have been loaded off the XP disk--I just wish I knew how to use what in what order and toward what knowledge base. Having hit Microsoft's pages on everything XP, it's evident that prior knowledge helps make sense of each discussion.
I just noticed--opened the Tweak Guide, got siphoned off to startup, around p. 97, opened msconfig--that msconfig was checked for a selective startup rather than "normal", so I've checked "normal" and will see if anything happens.
I'm a little worried about initiating a clean install off the OEM disk--I'm not sure how Microsoft's computer will take a second hello from a familiar old number. However, if I'm able to do that, at least I'll be working with a clean machine and a sensible build from commercial software. When there's odd behavior, I may also be better prepared to relate it to something I did close to the event rather than something that happened along the way and made itself a part of the personality of the machine.
How long does one give a problem before a clean install starts to look like the best solution available?