Slashdot Mirror
Maintaining Windows XP System Performance?
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."
Start -> Run 'services.msc' Cut off most of these. Many are useless, and yet are enabled by default.
defragment your hard drive. Of course, you can't defrag the registry. So use sysinternal's PageDefrag utility which can. Over time, the registry accumulates a lot of stuff, and defragging it can help quite a bit.
Do you even lift?
These aren't the 'roids you're looking for.
http://www.mlin.net/StartupMonitor.shtml - it's a freeware app that tells you each time something tries to register itself to run at startup. Those damn on-startup apps are what slow the machine down the most, especially for non-technical home users. You'll be amazed at how many things believe they must run every time you start your computer.
Nikon slidescanner attached via FireWire; couple of years old and every now and again gets put on a new machine, scan time improve but the after all the updating both windows and Antivirus etc do suddenly slows.
Ask around, do dependancy checks run spy+ no great insight
Then a friend says "What anti-virus you use?"
"AVG, you know the free one"
"ARGHH dumpit, replace it with something else"
Turns out AVG puts some drivers into the pipeline so it can scan ethernet,USB and FireWire, so everytime the scanner sent a glob of the slide this software was checking to see if it was a virus!
And yes this continued AFTER I removed the 1364 network stuff, I even go as far as trying another card
My scanning speeds have droped from 5 mins a slide to 1.35mins, do you know how much more of a life I can have!
So have a look at device manager, choose view->devices by connection & tick hidden devices box, right near the top you'll see among much else you Antivirus drivers, some dumb some not so dumb
Correct. I don't know anyone who could really say what was happening. I've heard in tech shops the recommended lifespan is 18 months of a Windows installation. I'd say that was about right, with minimal crashes during that time.
I'd recommend reinsatlling Windows, installing all your apps and patches. Then get a copy of Norton Ghost and take an image of your machine. Save that to a jillion CD's or a couple of DVD's and shelve them. When your box gets trashed again, slap the image back on and apply any updates from there. Saves some time.
-m
http://www.invisik.com
1)Like Lone Starr said in Spaceballs, "Take only what you need to survive". Basically only install what you need for the primary task the computer does. The more stuff you install, the slower it gets.
2)Disk Cleanup, Chkdsk, and Defragment the hard drive at least once a month. a lot of speed can be gained just by doing this regularly.
3)Protect windows like the plague. Patch to the latest revisions of Service packs, critical, and recommended updates. also use third party protection to protect against malware. Spywareblaster, Microsoft Antispyware and Grisoft AVG free edition are my personal favorites.
4)Keep system restore on and always make a restore point before you install anything. That way, if it screws up the machine after you installed it, you can uninstall it and roll the computer back to ensure that the system is totally clean of it.
5) If you got Norton ghost lying around, use it to make an image of your machine after you set it all up, that way you can roll back to that image just in case something really hoses windows.
So far, I've kept this mantra going with my machine. It's been a good 1 to 2 years since I reinstalled windows either from scratch or by ghost and I've haven't noticed any slowdown to date that I couldn't attribute to the machine getting more obsolete by the day.
In Soviet Russia, Trojan exploits YOU!
Height: 38U, Weight: 0 Newtons, Eyes: #0000FF, OS: Gray Matter 1.0 (Alpha)
Most of the other tips are good, but nobody's mentioned CCleaner yet. That is one awesome app for cleaning out old cruft.
It's only an insult if it's not true.
I actually got sick of family and friends asking me to tune up their XP installs, so I wrote a detailed article on the entire process and posted it on our family website here: http://www.farleyfamily.net/articles/tuneup/
It's a comprehensive step-by-step of what any aunt or uncle should be able to follow in order to free system resources and make for a better (faster!) desktop experience.
Run msconfig. Despite what your better judgement might say, you can safely disable everything in the startup tab. Then glance through the list and recheck anything that you can both identity and wish to have running in the background.
Other small speedups:
Switch to the classic win2k theme.
If your wallpaper is a gif or jpeg, replace it with a bmp and disable active desktop. For anything other than bmps, it uses Internet Explorer to render your desktop.
Get more ram.
If less than about 20% disk free, delete stuff you don't need and then defrag.
Disable window animations and other eye candy.
Check for malware.
Install and run ShellExView. Some programs install shell extensions which can (but not usually) cause slowdowns and pauses in Windows Explorer. It should color code items depending on if they come with windows, if they are known, if they are known to be bad, or if they are unknown. I encountered a system where a Eudora shellexecute hook was causing the system to freeze for 2 minutes whenever you tried to start a program.
Disable the indexing service.
Disable/uninstall your virus scanner, if you're the type who never installs viruses.
16bit color is sometimes faster. You'll have to test for yourself.
Sometimes I get lucky with this one: In control panel->hardware->device manager, open the properties for the "Primary IDE Channel" and see whether it's in DMA or PIO mode. If it's in PIO mode, right click the "Primary IDE Channel" and click remove/uninstall, and reboot. I've encountered several systems where this was the cause of major slowdown. Windows occasionally encounters timeouts reading from the hard drive, and sometimes mistakingly assumes that stepping down to a slower transfer mode will solve the problem. I see it happen most on systems that go to sleep a lot. Microsoft's website says it's fixed, and shouldn't happen much at all in the future, but you'll still need to do the fix I described on systems that already have the problem.
Some people suggest removing System Restore. I've had occasions where it helped out a lot, like when a Microsoft Windows Update badly broke my system, so I can't recommend disabling it unless you don't mind the occasional reinstall.
I'm typing this on Linux, so some of the above instructions might be slightly off, but are generally correct.
If you want a minimal Windows install, use nLiteOS -- it creates an install CD for Windows from your existing copy, only including what you choose.
Also, remember to have a sane partitioning scheme, in case you need to reinstall. You might want to use FAT for your data partition; that way, you can read it via a Knoppix CD in a real emergency.
The following registry tweaks should be used with caution:E T\CONTROL\Session Manager\Memory Management\IoPageLockLimit. If it is no there you can create it. This is DWORD value. For systems with at least 256MB of RAM, 8000 hex (32768 decimal) or 10000 hex (64536 decimal). You can use 20000 hex (131072 decimal) on systems with 512MB+ of RAM. Warning: this setting may not be compatible with some drivers; especially video drivers. Enabling this option could cause critical processes and services to fail. You might not be able to log in.
E T\CONTROL\Session Manager\Memory Management\LargeSystemCache. If the key is not there, you can create it. This is a DWORD value. 0 for disabled. 1 for enabled.
E T\CONTROL\Session Manager\Memory Management\DisablePagingExecutive. This is a DWORD value. 0 for disabled. 1 for enabled.
IoPageLockLimit: increases the amount of pages that can be locked into memory. Changing this setting can improve performance although there is some controversy over this setting's effectiveness. Make sure that you have at least 256MB of RAM. HKEY_LOCAL_MACHINE\SYSTEM\CONTROL\CURRENTCONTROLS
LargeSystemCache: This setting is primarily used for servers but can help improve performance. Again, it's effectiveness may be controversial. It is located at HKEY_LOCAL_MACHINE\SYSTEM\CONTROL\CURRENTCONTROLS
DisablePageExecutive: Again this is a controversial setting. You may or may not notice a difference in performance and it is driver sensitive so be forewarned about using it. It too has the potential to cause crashes after being enabled. This setting prevents kernel memory from being paged. It is located at HKEY_LOCAL_MACHINE\SYSTEM\CONTROL\CURRENTCONTROLS
Note: Any problems encountered from changing these settings will be noticed on next boot. They are a "either it's fine or it isn't" settings.
To reduce boot time, you can disable autodetection of devices on IDE controllers that have no devices connected to them. This can be done from the device manager. Also, adjust Windows for best performance and turn off the themes service.
Lastly, there's XPlite which can help cut down on some of the fat. Also, be sure to check out TweakXP.com for more XP performance tweaks. And there's nLite. Unlike XPlite, nLite allows you to remove Windows components before installation. It also has service pack integration.
If you've got multiple partitions, try installing a maintenance OS on an extra partition. If you've still got a license for Windows 2000, just install it on the other partition, it should go smoothly and give you a nice boot menu when you're done.
The main advantage of doing this is that you'll have full access to your XP installation without having any system files blocked. What I did was take a fresh install of XP (with all of my base drivers and applications installed) and make a copy of the Windows, Program Files, and Documents and Settings directories. Now, if I feel that my XP installation is getting bloated to the point where I can't fix it anymore, I can "reinstall" XP by booting into my maintenance partition and replacing those directories. As long as you are booted into another partition when you do it, Windows is completely oblivious to the fact that you've just replaced your primary OS.
Having a maintenance partition is also advantageous when defragmenting your primary partition, since no system files will be locked. It's also handy if you suspect you've been infected with a rootkit, since that seems to be a trendy topic at the moment.
A lot of the system slowdown on Windows boxes can be traced to explorer. Explorer is a single threaded application, and when used on a network, over time it tends to collect many network relative paths to resources like icons. Later the network shares dissapear or are moved. The result is, every time explorer tries to generate lists of icons to display for files it pauses - using 0% CPU - waiting for non existant network hosts to respond.
A couple of tips, in case someone might not be familiar with these...
Running as a plain old User privileges may be good for some situations, but I run my XP box with Power User privileges for a bit more power. This option is not presented by the Control Panel applet, but is available through Computer Management, opened by right-clicking My Computer and selecting Manage. Once there, go to System Tools -> Local Users and Groups -> Groups. Double-click Power Users on the right-side window and add your user account to the group.
For more info on the differences between the privilege levels, see here.
If you use applications that require admin privileges, either use the Run as... command from the right-click menus of the shortcuts (or the runas command inside the cmd shell), or modify the shortcuts permanently so clicking them always produces the dialog for entering alternate credentials: right-click an icon, choose Properties, click Advanced inside the Shortcut tab and check the box labeled Run with different credentials.
CD-ROM and DVD-ROM drives can revert to using PIO mode, despite being set to use "DMA if Available." Here's how to make Windows XP redetect the DMA capabilities of the drives.
o l\ Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\000x
This behaviour occurs with the following conditions:
Windows XP is the operating system
A CD-ROM, DVD-ROM, or sometimes even a HDD, which is known to support DMA mode now works only in PIO mode.
The drive controller is set to use "DMA if available" but reports to be only in PIO mode.
Following is the mechanism that has worked for me, please try it at your own risk, it involves hacking the registry:
Open RegEdit
Find the following KEY:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contr
The last four digits will be 0000, 0001, 0002, 0003, and so on.
Under each key, delete all occurences of the following values:
MasterIdDataChecksum
SlaveIdDataChecksum
Reboot the computer. Windows will now redetect DMA settings.
This happens if a device on the bus has been getting periodic errors either because of a hardware problem or because of scratched or copy-protected CDs. XP steps down the DMA to try and stop the errors because it assumes it is a hardware problem.
Those who open their minds too far often let their brains fall out.