Comments on: Force windows to load the kernel in memory http://www.ditii.com/2006/04/14/force-windows-to-load-the-kernel-in-memory/ Technology, Blogging, Computer, Hardware, Software, Networking, Web, Media, LifeStyle, Gadgets Tue, 06 Jan 2009 01:52:44 +0000 http://wordpress.org/?v=2.7 hourly 1 By: Larry Miller http://www.ditii.com/2006/04/14/force-windows-to-load-the-kernel-in-memory/comment-page-1/#comment-61126 Larry Miller Thu, 21 Aug 2008 05:48:54 +0000 http://www.ditii.com/blog/2006/04/14/force-windows-to-load-the-kernel-in-memory/#comment-61126 Several errors here. DisablePagingExecutive: By default Windows will always attempt to keep the kernel in RAM. Only under times of heavy memory load will it be paged out. This setting prevents this from occuring. If adequate memory is available this will not occur often. At best there is little to be gained, at worst it will impair performance. LargeSystemCache: This is a potentially dangerous setting. Microsoft clearly documents that this setting is for systems used as servers, and then only in specific cases. It is not appropriate for general use. It tells the system that caching has priority over memory for applications. Good for servers, bad in other cases. This setting is dangerous with some common hardware configurations. It can cause a variety of problems, including data corruption. Some users have had to reinstall Windows to restore operation. Investigate thoroughly before attempting this setting. You have been warned! IOPageLockLimit: This setting is not supported on any version of XP. In fact, support ceased as of Windows 2000 Service Pack 1. Larry Miller Microsoft MCSA Several errors here.

DisablePagingExecutive:
By default Windows will always attempt to keep the kernel in RAM. Only under times of heavy memory load will it be paged out. This setting prevents this from occuring. If adequate memory is available this will not occur often. At best there is little to be gained, at worst it will impair performance.

LargeSystemCache:
This is a potentially dangerous setting. Microsoft clearly documents that this setting is for systems used as servers, and then only in specific cases. It is not appropriate for general use. It tells the system that caching has priority over memory for applications. Good for servers, bad in other cases.

This setting is dangerous with some common hardware configurations. It can cause a variety of problems, including data corruption. Some users have had to reinstall Windows to restore operation. Investigate thoroughly before attempting this setting. You have been warned!

IOPageLockLimit:
This setting is not supported on any version of XP. In fact, support ceased as of Windows 2000 Service Pack 1.

Larry Miller
Microsoft MCSA

]]>