|
Also, you might look in Device Manager to see if your IDE controllers look OK. (no exclamation marks) - Make sure that you aren't running in "DOS compatibility mode" on any of the controllers.
Regarding Virtual Memory settings, it's OK also to "Let Windows manage my virtual memory settings" - Win2k usually does an OK job as long as your disks aren't filling up. (might want to check your free disk space, too - though with a 40gb drive you should have all kinds of room).
Might want to check the air blowing from the power supply's exhaust fan to see if it's unusually warm. If this is a notebook, it will slow down in response to heat to prevent the chip from overheating. If this is a desktop, enter Bios Setup and check the temps in "PC Health" or "Hardware Monitor"...or whatever your bios calls it. Most PIIIs don't have a problem with heat, but if your fans are clogged with dust they might not be spinning well.
Have you looked in on your Event Logs to check for anything unusual?
Do your programs mostly run locally, or pulled from a network server?
And I suppose you could run the System File Checker just in case the system files are out of whack (from Command Prompt: sfc/scannow . . . and have your Win2000 installation disk handy - or point to the install directory [usually i386] on your hard drive) . . . & you could boot from your Win2k disk and try a "repair" installation if you've tried everything else with no luck.
Has the pc been slow the whole time, or just recently - possibly after a hardware/software change?
________
My break is over, I got to go back to some cranky mainframes. . . but I'll look in later on. Really cranky mainframes, today it's the Alphas...
. . . Gary
|