18
2006
Force windows to load the kernel in memory (very effective tweak for windows XP)
The best tweak for windows -
1) Open the regedit tool (Start -> Run -> regedit.exe)
2) Use the navigation in the left and go to HKEY LOCAL MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
3) Double click the DisablePagingExecutive attribute, and put 1 in the decimal value field. This will make the drivers and the XP kernel run in memory.
4) Double click the LargeSystemCache attribute, and put 1 in the decimal value field
This will improve performance of the kernel
5) Double click the IOPageLockLimit attribute. On some later versions of windows XP that doesn't exists, so if this is the case you're done. Otherwise you have to put to the hex value : 4000 for pcs with 128 mb ram, 10000 for 256 mb ram and if you have more put 40000. This value specifies how many bytes can be used for I/O operations in your system.
Originally from http://www.gibberishtalk.com/
Force windows to load the kernel in memory (very effective tweak for windows XP)
Originally from 361degrees by
The following are Myths in Windows XP:
LargeSystemCache
IOPageLockLimit
http://mywebpages.comcast.net/SupportCD/XPMyths.html
WARNING
LargeSystemCache is potentially dangerous. Microsoft makes it quite clear that this setting is only for systems that are primarily used as file servers. It is not appropriate for general use. Basically it tells Windows that file caching has priority over memory for applications. This will impair performance on workstations. The setting has nothing to do with Kernel performance.
Microsoft has also issued warnings related to inappropriate use of this setting. When used with some common hardware configurations there can be serious problems. Problems range from severe performance issues, system instability, and data corruption. Some users have been froced to reinstall Windows to restore operation. Many hardware devices and drivers were not designed to operate in such an environment. This setting is deadly with a number of popular video cards and other devices.
References:
http://support.microsoft.com/kb/895932
YOU HAVE BEEN WARNED.
IOPageLockLimit:
Support for this setting was dropped as of Windows 2000 SP1. It has never been supported on any version of XP or Vista.
Contrary to popular assertions to the contrary, XP and Vista manage memory very well on their own. The default values for registry entries were carefully chosen for best performance and stanility. There are no settings that will dramatically improve performance. More often than not they will impair performance – or worse. Changing registry settings without a solid understanding of what they do is dangerous and is strongly discouraged.
Larry Miller
Microsoft MCSA