Optimize XP - A Windows XP Optimization Guide v1.8


Recommended Posts

BootVis is not built into XP. Windows XP has a automatic boot time optimization routine that runs at an unknown time/date. BootVis allows you to optimize your boot up time when you want, it also lets you see graphically what is slowing down your bootup.

I didn't read all the posts, and I can't even remember where I found out about it, so if this one has been mentioned, forgive me, lol.

"The Tweaking Experience Registry Guide" seems pretty good.

http://windowsxp.homedns.org/

Seems to be set up nicely anyways.

That guide there is the perfect example of what I am trying to avoid, editing the registry is just a bad way to go about making changes to your system. You can do it much safer with applications, not to mention some of the tweaks mentioned are useless. 90% of the performance tweaks mentioned can be much easier and safely done using Cacheman. Alot of the "tweaks" are irrelevant or very application or instance specific that most users have no need for them. IMO it is messy, you have mentions of applications that do the same exact thing CCleaner and MRU Blaster. Then applications that are older versions of newer ones, XAIDA32 (Not even spelled right, should be AID32) and Everest. There are alot of things wrong there.

  • 2 weeks later...
Please note that Bootvis.exe is not a tool that will improve boot/resume performance for end users. Contrary to some published reports, Bootvis.exe cannot reduce or alter a system's boot or resume performance. The boot optimization routines invoked by Bootvis.exe are built into Windows XP. These routines run automatically at pre-determined times as part of the normal operation of the operating system.

http://www.microsoft.com/whdc/system/syspe...BootVisdwn.mspx

That guide there is the perfect example of what I am trying to avoid, editing the registry is just a bad way to go about making changes to your system. You can do it much safer with applications, not to mention some of the tweaks mentioned are useless. 90% of the performance tweaks mentioned can be much easier and safely done using Cacheman. Alot of the "tweaks" are irrelevant or very application or instance specific that most users have no need for them. IMO it is messy, you have mentions of applications that do the same exact thing CCleaner and MRU Blaster. Then applications that are older versions of newer ones, XAIDA32 (Not even spelled right, should be AID32) and Everest. There are alot of things wrong there.

585215021[/snapback]

cacheman is junk, xp manages it's memory better without any program like it, the best program to dl is not mentioned in your list, x-setup pro for editing the registry, ccleaner is good, never tried mru blaster... link?

This is quite clear in the guide:

"BootVis is a boot performance trace visualization and optimization tool. This tool invokes the built in Windows XP boot time optimization process when you run it, instead of waiting for it to be scheduled at some unknown time by Windows. You will notice immediate improvement in boot performance for this reason."

cacheman is junk, xp manages it's memory better without any program like it, the best program to dl is not mentioned in your list, x-setup pro for editing the registry, ccleaner is good, never tried mru blaster... link?
Again, Cacheman is specifically NOT used in the guide to manage memory, instead it is used as an easy way to optimize cache and memory related registry settings. It is specifically recommended NOT to load it at startup:

"Then under "Options" uncheck "Load Cacheman on Windows Startup", Exit and Save Cacheman."

Again, X-Setup lets you change alot of settings but not alot are related to performance. The ones that are, are already covered in the guide.

Edited by Mastertech
  • 2 weeks later...

personally... i think most of those guides (if not all) are close to useless/pointless.

as in most cases never offer any real performance increases... if anything i think it messes stuff up in certain cases.

to put it simply... DONT mess with settings like these ;) u will thank me in the long run.

Yeah, I don't use to toy around with things like this unless it's a specific setting I need to change for some very specific thing. I wouldn't recommend anyone starting to browse a list of stuff and "tweaking" settings. I've even seen stuff that automatically does it for you -- even worse. (it just takes one bug in such an app to mess up your system)

When Microsoft is setting default settings for Windows XP, you also need to understand it's not always for speed, but for stability too. Windows XP is also closed source, and you need to respect the fact that modifying "hidden" cool settings may have unintended and undocumented effect you can't gain proper support for. "Registry guides" are the worst and usually neglect these aspects. Or wait... No, I think the .sys file tweak to "improve" P2P app performance was.

NTFS registry changes like these in this guide makes me scared:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem]

"NtfsDisable8dot3NameCreation"=dword:00000001

I mean, that will instantly break anything that rely on 8.3 filenames in Windows.

You don't have any? You sure how the internals in all your apps work, and that none use any legacy file management code? Then go ahead and change it, but you won't improve the performance noticeably at all so there's no win in doing it. This change is to "make NTFS run better" according to the author though. Define "better".

Here we have another suggested change to destroy the cached data when you reboot:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]

"ClearPageFileAtShutdown"="1"

The author claims it prevents fragmenting, however in the same sentence he says he isn't sure. But go ahead and do it, it's "probably good". You won't keep the cache across sessions, but who cares? :huh: I also fail to see how forcing Windows to recreate a, say, 1024 MB file will in any way reduce fragmentation. More like the opposite. It's when data is reallocated, there's the risk of physical fragmentation, if you didn't know.

Edited by Jugalator
personally... i think most of those guides (if not all) are close to useless/pointless. as in most cases never offer any real performance increases... if anything i think it messes stuff up in certain cases. to put it simply... DONT mess with settings like these ;) u will thank me in the long run.

Pointless for those who do not care how fast their system runs. The real performance increases can be observed by those who take the time to run through their guide, results speak for themselves.

It is important you read the guide before making assumptions:

NTFS registry changes like these in this guide makes me scared:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem]

"NtfsDisable8dot3NameCreation"=dword:00000001

I mean, that will instantly break anything that rely on 8.3 filenames in Windows.

You don't have any? You sure how the internals in all your apps work, and that none use any legacy file management code? Then go ahead and change it, but you won't improve the performance noticeably at all so there's no win in doing it. This change is to "make NTFS run better" according to the author though. Define "better".

#1 no where in the guide are registry changes mentioned directly ESPECIALLY not this one. This one is included as an OPTION in Cacheman. If you follow the instructions it DOES NOT say to check this box by default. By default it is unchecked. If you follow the instructions this will not be enabled. The box also lists a CLEAR warning for those who want to turn it off: "Do not use with Norton Utilities, AntiVirus or System Works"

Here we have another suggested change to destroy the cached data when you reboot:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]

"ClearPageFileAtShutdown"="1"

The author claims it prevents fragmenting, however in the same sentence he says he isn't sure. But go ahead and do it, it's "probably good". You won't keep the cache across sessions, but who cares?

Huh? Are you even reading the same guide!? This is mentioned under XP-AntiSpy

"_ Clear pagefile at shutdown - This causes Windows XP to take longer to shutdown but is a good idea for security." What site are reading this nonsense in your post from? Please if your not going to take the time to read the guide do not post Misinformation.

  • 3 weeks later...

Optimize XP v1.9.0

v1.9.0

Spyware - Sun Java Virtual Machine Item Added

Spyware - All Java Instructions Updated

Spyware - All Java Links Updated

Utilities - Cacheman v5.50 Instructions Updated

Tweaks - Diskeeper Instructions Added

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I think the car analogy is more this: Left hand drive, basic commands on the left side of the infotainment screen. Right hand drive, basic commands on the right side of the infotainment screen. Granted, you're not swapping between the two often so it's doesn't really work. But it's to do with the proximity of you (your mouse, or the driver) to the controls.
    • I mean, the old one was broken and so stupidly complex for many users, so I don't see that as a feasible option. A context menu needs to be simple to use, and for me the Windows 11 style actually worked really well for me, and many others. I used to have to scroll the damn context menu just to get to "file properties" in Windows 10. That was not a good experience, and I'm sure you'd agree. What they're trying to do is make it the best of both worlds, as clearly you'd prefer the Win10 style. I'm curious how they're going to do this.
    • The "Show more options" has its place, as does the simpler context menu, but it should perhaps be a separate fly-out rather than relaunching the entire, old context menu. The old context menu was getting absurd in Windows 10. Often I'd have to make the context menu scroll just to get to "File properties" on my old laptop. Even without much installed, the amount of items was just too much. It's a context menu, not a "do all" menu. Making it configurable is fraught with challenges too, so I'm interested to see how Microsoft tackles this one.
    • I don't hate the new menus, I am not a fan of the lack of features and how they went live when they clearly are not complete. The menu itself presents much better than the previous - but what's lacking (IMO) is: 1) Any kind of automated manipulation such as: "this goes on the new menu because you use this feature more often on this filetype" "this is rarely used and will fall back to the old menu" 2) Any kind of user manipulation such as: "a UI to add/remove/order items to the new menu"
  • Recent Achievements

    • Week One Done
      I2D earned a badge
      Week One Done
    • Week One Done
      Dr Jared Dental Studio earned a badge
      Week One Done
    • Week One Done
      RG INVESTMENT GROUP earned a badge
      Week One Done
    • Very Popular
      The Norwegian Drone Pilot earned a badge
      Very Popular
    • Very Popular
      s0nic69 earned a badge
      Very Popular
  • Popular Contributors

    1. 1
      +primortal
      484
    2. 2
      PsYcHoKiLLa
      260
    3. 3
      Skyfrog
      84
    4. 4
      FloatingFatMan
      64
    5. 5
      Michael Scrip
      63
  • Tell a friend

    Love Neowin? Tell a friend!