Posts RSSWhen I get a virus, trojan or other nasty, I like to remove it, clean up all traces of it, and kill off the previous System Restore point(s). I have Nod32, Xoftspy, Malwarebytes, Spybot S&D, Spysweeper and other tools to help me out in this regard. I don't do "re-format and rebuild" - not ever. You learn nothing, and you lose too much. It takes time to lovingly customise your user experience. Reloading XP might be quick, but all the little flourishes you add over months, even years, is definitely not.
The downside of all this, is that eventually, things start to slow down over time. It gets tougher and tougher to clean up the remnants of this and that. One by one, the applications, files, pictures, movies and mp3s accumulate until you're short of resources; CPU, memory and disk space.
So, you do your best spring clean and you look at what you can optimise.
This is a minefield... Many so called optimisations can do more harm than good, so it's best to stick to the few that are known to work well. Keep it safe, at least at the start.
Boot up - we all want that to be quick.
System readiness from logon - that's really important.
Application loading times - Firefox, anyone?
I'm not going to go through all the things you can do to improve performance, because this article makes a pretty good fist of that, but the most important thing to me to start with is boot time.
BootVis can really help here. There's a really good article on it from OReilly, but the best resource is straight from the horses mouth, and was written recently. The document, imaginatively called "Windows Platform Design Notes - Fast System Startup for PCs Running Windows XP" really explains the ins and outs of BootVis, if you really want to know. Otherwise, the OReilly guide is more than good enough.
If you don't feel like using a tool like BootVis, you can always turn on boot logging and read through the boot traces. You'll be digging around for ages, but you'll learn a lot this way (I picked up a thing or two, anyway). You can really see where the bottlenecks are occurring, and can address them one by one. You can read all about this painstaking approach and try it out if you want. Another alternative is tracelog.exe, part of the Win XP SP2 Toolkit, which is described in detail in an article on citrix.com.
One way to get a startup trace whenever you want, is to add the /BOOTLOG and /SOS boot switches to a new OS entry in your boot.ini. This is pretty organic. Just don't mess it up - I promise you'll regret it if you do ;-)
Happy boot optimising.
![Reblog this post [with Zemanta]](https://lh3.googleusercontent.com/blogger_img_proxy/AEn0k_vBydYYdn2TVqdXoIEL-oQxHiueVohiP4dB15qijkQyrAxuCBADvOs4A91p90MwEFN1_zD4L9WYDfo9hTqh7Srhof1JuJLNRhLpVIZbShDg4IQhuXIwM8fwnPDNndNXsNjZ_bFZN3A1g2wF6P_tXLVc=s0-d)
Subscribe to techForum by Email