OT: Speeding up a slow computer

[Xrati]

Do the Control-Alt-Delete and see how many processes you are currently running. This will give you a good idea of how much of your resources are being devoured by 'background' programs. Virus programs as Norton or McAfee will totally suck up your resource space.
If you have more then 40 processes running (ideally you want between 32 to 40) you will need a program (like Spybot S&D or there are others) to turn off some of those processes, reclaiming memory for you to run the programs you want.

[Fyron]

Xrati said:
(ideally you want between 32 to 40)

Where did this range come from?

[Xrati]

Xrati said:
(ideally you want between 32 to 40)

then Fyron said: Where did this range come from?

Fyron, that is an average I've found from personel experiences working for many companies over the years. The more processes, the slower the computer.

When you install Win XP, right after the final reboot but before you install any programs, if you do a ctrl-alt-del you will have about 16 processes running. After that it just goes up as you add on programs. Quick launch programs get put into memory and become active processes that slow down your performance. You can create shortcuts to these rather then have them in memory waiting to be used. Also defragging once a month will help disk efficiency. A good registry cleaner used monthly will also keep small bits of lost or deleted files from building up in your registry. Also, for those who keep the power on all the time, a reboot will flush memory and release some of the registry entries for cleaning up. Good maintenance will keep your computer in good running condition.

[dmm]

Give it a good vacuuming. All that dust slows down the gears.

[Renegade 13]

That's what I feared Seems odd that a computer (or, more specifically, an operating system) would kinda 'decay' over time. I mean, it's just bits stored on a magnetic storage device, it shouldn't be *able* to decay!

[Solymr]

Trust me, it happens. As you use the OS more it accumulates more and more "rubbish".

I'm building a new computer and while I'm waiting for the RAM to come in, I've preinstalled XP onto a new hard drive with this computer. Now, the copy of XP on one of the drives on here that I boot from has been installed for a year and a half now and pretty much runs poorly. The fresh XP install on the new hard drive runs like a dream, and ran Oblivion really sweet on this computer, which normally would be a bit jumpy.

[capnq]

Renegade 13 said:Seems odd that a computer (or, more specifically, an operating system) would kinda 'decay' over time. I mean, it's just bits stored on a magnetic storage device, it shouldn't be *able* to decay!

Believe it or not, passing cosmic rays can flip individual bits on magnetic media.

Another problem on really old media is the "glue" holding the magnetic particles to the surface of the media deteriorating. The stuff you have to occaisionally clean off tape heads is particles that have scraped off the tape.

Most of the debris my registry cleaner finds is references to files that have been deleted.

[dogscoff]

That's what I feared Seems odd that a computer (or, more specifically, an operating system) would kinda 'decay' over time. I mean, it's just bits stored on a magnetic storage device, it shouldn't be *able* to decay!

Well, even if we disregard fragmentation, the crap cluttering up the registry, all the pointless bloat that wants to install itself and autostart, the malware and everything else, and not wanting to sound like a conspiracy theorist, bear in mind that if your OS worked flawlessly forever, you'd never want to buy the next one...

[Fyron]

Defragmentation is 99% useless. Disk read rates are so high these days that any effect of fragmentation in modern file systems is nullified. There are occasional uses for degramentation, such as a bizarre case of 90% fragmented drives, but for the most part, its a relic of a bygone age. Its especially useless to have a policy of defragmenting before installing new games or large programs...

Xrati:
Look at the total CPU Time for such processes; anything that has 0:00:05 CPU Time after 2 weeks of running (most such services) is not going to be bogging anything down, especially when its total memory usage is in the 100s of KBs. If you see unnecessary services that have significant amounts of CPU Time and/or Mem Usage, removing them can help (a little bit). I just think your time is better served cleaning the registry and such, than stopping services that use almost 0 resources in the big picture.

[Suicide Junkie]

Quality vs Quantity.

Look for the big hogs, and go from there