<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Force windows to load the kernel in memory (very effective tweak for windows XP)</title>
	<atom:link href="http://techtips.chanduonline.com/2006/08/18/force-windows-to-load-the-kernel-in-memory-very-effective-tweak-for-windows-xp/feed/" rel="self" type="application/rss+xml" />
	<link>http://techtips.chanduonline.com/2006/08/18/force-windows-to-load-the-kernel-in-memory-very-effective-tweak-for-windows-xp/</link>
	<description>Tips and Tricks to effectively use the latest Tools Technologies and Trends</description>
	<lastBuildDate>Sat, 27 Feb 2010 17:00:30 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Larry Miller</title>
		<link>http://techtips.chanduonline.com/2006/08/18/force-windows-to-load-the-kernel-in-memory-very-effective-tweak-for-windows-xp/comment-page-1/#comment-166413</link>
		<dc:creator>Larry Miller</dc:creator>
		<pubDate>Sat, 01 Nov 2008 17:09:54 +0000</pubDate>
		<guid isPermaLink="false">http://techtips.chanduonline.com/2006/08/18/force-windows-to-load-the-kernel-in-memory-very-effective-tweak-for-windows-xp/#comment-166413</guid>
		<description>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</description>
		<content:encoded><![CDATA[<p>WARNING<br />
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.</p>
<p>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.</p>
<p>References:<br />
<a href="http://support.microsoft.com/kb/895932" rel="nofollow">http://support.microsoft.com/kb/895932</a></p>
<p>YOU HAVE BEEN WARNED.</p>
<p>IOPageLockLimit:<br />
Support for this setting was dropped as of Windows 2000 SP1. It has never been supported on any version of XP or Vista.</p>
<p>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 &#8211; or worse. Changing registry settings without a solid understanding of what they do is dangerous and is strongly discouraged.</p>
<p>Larry Miller<br />
Microsoft MCSA</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://techtips.chanduonline.com/2006/08/18/force-windows-to-load-the-kernel-in-memory-very-effective-tweak-for-windows-xp/comment-page-1/#comment-52</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Tue, 12 Sep 2006 11:34:43 +0000</pubDate>
		<guid isPermaLink="false">http://techtips.chanduonline.com/2006/08/18/force-windows-to-load-the-kernel-in-memory-very-effective-tweak-for-windows-xp/#comment-52</guid>
		<description>The following are Myths in Windows XP:

LargeSystemCache
IOPageLockLimit

http://mywebpages.comcast.net/SupportCD/XPMyths.html</description>
		<content:encoded><![CDATA[<p>The following are Myths in Windows XP:</p>
<p>LargeSystemCache<br />
IOPageLockLimit</p>
<p><a href="http://mywebpages.comcast.net/SupportCD/XPMyths.html" rel="nofollow">http://mywebpages.comcast.net/SupportCD/XPMyths.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
