Possible Windows XP Speed Boost


Recommended Posts

This tweak is for those with mobile Athlon XP processors; it may work with other brand processors, but I was only able to test this with my mobile XP.

Windows often incorrectly detects the amount of L2 cache on the processor, which may slightly hamper performance. To do this tweak, you are going to need CPU-Z which can be downloaded for free from here.

Open up cpuz.exe and look for the cache section on the CPU tab (default selected), and note the number beside "Level 2".

post-43261-1105052828.jpg

Open up regedit by clicking start, run, and typing "regedit" into the text box.

Navigate to HKEY_LOCAL_MACHINE\STSTEM\ControlSet001\Control\Session Manager\Memory Management

post-43261-1105053075_thumb.jpg

Double click on "SecondLevelDataCache"

post-43261-1105053157.jpg

Type one of the following values into the text box according to the value presented by CPU-Z in DECIMAL form

256 KBytes = 0

512 KBytes = 200

1024 KBytes = 400

post-43261-1105053348.jpg

Click OK, exit regedit and restart your computer.

Link to comment
https://www.neowin.net/forum/topic/267746-possible-windows-xp-speed-boost/
Share on other sites

Basically, this trick doesn't work. There is alot of misinformation floating around out there, and you can find it on various (usually dubious) "tweaking" sites. This is an old value in the registry that was for the old days when people had off chip L2 caches that could actually be replaced by the user. Nowadays, for chips with ondie cache (that's pretty much everything from the PIII on up) this value is ignored, so entering anything in it won't do anything for your performance. Windows automatically uses the full ondie L2 cache with newer chips.

Basically, this trick doesn't work. There is alot of misinformation floating around out there, and you can find it on various (usually dubious) "tweaking" sites. This is an old value in the registry that was for the old days when people had off chip L2 caches that could actually be replaced by the user. Nowadays, for chips with ondie cache (that's pretty much everything from the PIII on up) this value is ignored, so entering anything in it won't do anything for your performance. Windows automatically uses the full ondie L2 cache with newer chips.

585245965[/snapback]

(Y) thanks! :D

Very old tweak. And yes it does work with older CPU's as the fella previously stated. The Athlon worked somewhat ok with it. Duron's liked it and even some socket 478 Intels would twitch abit with it from time to time..... But for mobiles, I don't think yu'll get much out of this at all....... What you could do is use the ole tweak ( AlwaysUnloadDLL ) and set it for ( 1 )...... in the reg. That one works pretty good !

Hmm too bad... I was hoping so :p

by the way ev0| any chance that you're dutch?

585245989[/snapback]

I'm afraid that I'm not dutch.

Also, since this value is ignored, there is no harm in changing its value. It's not going to do anything to speed up your computer, but it won't do anything bad either.

You are correct, stupid me :no: ...

SecondLevelDataCache records the size of the processor cache, also known as the secondary or L2 cache. If the value of this entry is 0, the system attempts to retrieve the L2 cache size from the Hardware Abstraction Layer (HAL) for the platform. If it fails, it uses a default L2 cache size of 256 KB. If the value of this entry is not 0, it uses this value as the L2 cache size. This entry is designed as a secondary source of cache size information for computers on which the HAL cannot detect the L2 cache.

This is not related to the hardware; it is only useful for computers with direct-mapped L2 caches. Pentium II and later processors do not have direct- mapped L2 caches. SecondLevelDataCache can increase performance by approximately 2 percent in certain cases for older computers with ample memory (more than 64 MB) by scattering physical pages better in the address space so there are not so many L2 cache collisions. Setting SecondLevelDataCache to 256 KB rather than 2 MB (when the computer has a 2 MB L2 cache) would probably have about a 0.4 percent performance penalty.

http://support.microsoft.com/default.aspx?...kb;en-us;183063

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

    • No registered users viewing this page.
  • Posts

    • These features described above are good, but far from what developers like me was eager to get. And that main feature that developers will love it`s the ability to connect to LOCAL AI models running on Ollama. So if you have a beefy spec machine you can now use your own model 100% local inside Visual Studio 2026 18.7.0
    • Microsoft Teams is getting a controversial location tracking feature that users may hate by Usama Jawad Image generated with Microsoft Copilot Earlier this year, Microsoft planned to roll out a controversial location tracking feature in Teams, but following customer feedback, it decided to delay its release. The bad news is that the company has decided to launch it later this year, but it's based on roughly the same design that was shared earlier, which means that many users still have good reason to worry. Basically, Microsoft Places and Teams have received workplace check-ins via Wi-Fi. The idea is that if an employee arrives at the office and connects to their enterprise network, their profile status indicator will show them as being present in the office. For example, if you arrive at work, open Teams on your PC, and connect to the "Studio B" company Wi-Fi network, your Teams profile will indicate that you are present in "Studio B", as shown below: Microsoft says that this feature is basically a replacement for physical workplace check-in peripherals, it reduces the need to manually update your status, and it also enables co-workers to know that you're at work so that they can coordinate in-person meetings with you. IT admins can enable this workplace check-in capability at a tenant level, and users have the ability to control whether they want to enable it or not. Of course, all of that sounds great on paper, but naturally, many Teams customers may still have concerns, as they did before. This is because it enables your reporting manager and other members of the organization to track if you are at the office, when you arrive at the office, and where you are right now. This could be problematic for people who work in what they consider to be flexible work environments or hybrid setups, and this kind of location tracking could be considered an invasion of privacy. Microsoft has tried to alleviate some of these concerns by letting users know that they can manually set their location easily, which essentially overrides workplace check-in if they feel uncomfortable with it. However, that doesn't really solve the problem because your organization could enforce a workplace policy that mandates that this feature remains enabled. The Redmond tech giant has also assured users that this capability does not store historical data and is only a real-time indicator of location. Finally, it only generates a signal when you connect to a corporate network, which means that if you are working from home and connect your PC to your personal Wi-Fi, it won't broadcast your location to your employer; you will simply be shown as "Remote". Microsoft has encouraged IT admins to prepare for this change and begin informing users so they know what to expect once it begins rolling out later this year.
    • Wow, Microsoft IS cooking lately... This only shows that they COULD improve, they just chose not to for whatever reasons. That obsession with AI was destroying them from the inside out.
  • Recent Achievements

    • Very Popular
      AndrewSteel earned a badge
      Very Popular
    • Veteran
      Taliseian went up a rank
      Veteran
    • One Month Later
      Clizby earned a badge
      One Month Later
    • One Month Later
      Timaximus earned a badge
      One Month Later
    • Week One Done
      Timaximus earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      511
    2. 2
      +Edouard
      162
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      80
  • Tell a friend

    Love Neowin? Tell a friend!