Quote:
|
Originally Posted by Rock Steady
Well, we'll just have to have a gentlemen's disagreement here. Typically, the Windows Registry gets so screwed up it's hard to repair and optimize. Then you have all the malicious stuff on top of that. I don't bother finding problems.
|
Recently found the defective part, and replaced that IC in a Gateway power supply. Why? Clearly not to save money. Clearly not faster. But I learned. I learned why power supplies fail - and even that Gateway power supplies are missing essential functions. A problem also found in so many clone computers. Those who are considering a new machine - Gateway power supply was found missing essential functions.
Been using Windows NT on systems even before Windows 98 was marketed. Never once saw problems traceable to registry - except viruses. And yes, I have even cleaned a virus by deleting and modifying files - to learn the hows and whys. A rare case where the registry was part of a problem because the registry kept reloading the virus. More often, the registry is too often blamed for problems elsewhere.
If a system contains no value, then a 'nuke and pave' may work. But defined is a problem more often directly traceable to hardware - which means the 'nuke and pave' would only make things more difficult.
Meanwhile, what does a clone computer builder not get? Comprehensive diagnostics. A first thing executed when hardware integrity is suspect. Therefore clone builders rarely recommend diagnostics since such was never available. It explains why shotgunning is so often recommended - a technique that even auto mechanics no longer call acceptable.
Always start by not trying to fix the problem. Fixing comes later. First collect facts. NT based OSes (unlike the unreliable Win9x systems) make that easy. If problem was a failing hard drive, then that too would be obvious in system (event) logs. (his symptoms are consistent with a failing hard drive but facts are not yet provided.) Then step two - the repair - is done right the first time.