from the recommend-regular-use-of-registry-cleaners dept.
jerud wonders: "I assume that most people on Slashdot are forced to, at some point, touch Windows. Further, I assume that many of them are forced to administer Windows boxes. I am in the unfortunate situation of using Windows for about 90% of my tasks, due to the nature of my job. As a firm believer in 'if it isn't broke don't fix it', I've delayed moving to XP for just about as long as possible, holding onto my Windows 2000 installation, while my brother spent a lot of time complaining about the XP issues he dealt with, at work. Finally, I made the transition and, low and behold, it didn't seem to bad. In fact, there were a few things that I really liked. Now, a few years later I have quite a few XP machines and they all share the same problem: over time they have slowed so noticeably that they have made even the most solid configurations run like they were made in 1999. Is there any regular treatment out there that can minimize this kind of system degradation?"
"Solid practices are in use on most of these machines, or at least the ones that are completely under my control. Even with that, I know these machines are much slower now then when I bought them. I really don't want to spend two weekends every year starting over from scratch, simply because thats the only way to reclaim performance."
Real Programs don't use shared text. Otherwise, how can they use functions
for scratch space after they are finished calling them?