<?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: XP:  Registry Hack to Disable or Modify Prefetch</title>
	<atom:link href="http://www.tech-recipes.com/rx/1285/xp-registry-hack-to-disable-or-modify-prefetch/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.tech-recipes.com/rx/1285/xp-registry-hack-to-disable-or-modify-prefetch/</link>
	<description>Computer and technology tutorials and guides</description>
	<lastBuildDate>Sat, 21 Nov 2009 20:38:45 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: mariocoluzzi</title>
		<link>http://www.tech-recipes.com/rx/1285/xp-registry-hack-to-disable-or-modify-prefetch/comment-page-1/#comment-15916</link>
		<dc:creator>mariocoluzzi</dc:creator>
		<pubDate>Tue, 27 Oct 2009 21:19:06 +0000</pubDate>
		<guid isPermaLink="false">guid-fix-me!#comment-15916</guid>
		<description>I do not like prefetch system. I believe to be another Microsoft BS. When I delete my prefetch directory my PC starts faster and without any problem. &lt;br&gt;&lt;br&gt;Once a virus kept reappearing, it was loaded in a prefetch file. &lt;br&gt;&lt;br&gt;Based on this experience, I have modified my shutdown and reboot system --&gt; they empty the prefetch directory.&lt;br&gt;&lt;br&gt;I am having less problem since.</description>
		<content:encoded><![CDATA[<p>I do not like prefetch system. I believe to be another Microsoft BS. When I delete my prefetch directory my PC starts faster and without any problem. </p>
<p>Once a virus kept reappearing, it was loaded in a prefetch file. </p>
<p>Based on this experience, I have modified my shutdown and reboot system &#8211;&gt; they empty the prefetch directory.</p>
<p>I am having less problem since.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Miami Carpet Cleaning</title>
		<link>http://www.tech-recipes.com/rx/1285/xp-registry-hack-to-disable-or-modify-prefetch/comment-page-1/#comment-12618</link>
		<dc:creator>Miami Carpet Cleaning</dc:creator>
		<pubDate>Thu, 18 Jun 2009 01:51:59 +0000</pubDate>
		<guid isPermaLink="false">guid-fix-me!#comment-12618</guid>
		<description>Nice blog.. I encountered that problem and I don&#039;t know what to do.. luckily I read this blog... Thank you for this.. Hope that It can help me..</description>
		<content:encoded><![CDATA[<p>Nice blog.. I encountered that problem and I don&#39;t know what to do.. luckily I read this blog&#8230; Thank you for this.. Hope that It can help me..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ClearlbyBiased</title>
		<link>http://www.tech-recipes.com/rx/1285/xp-registry-hack-to-disable-or-modify-prefetch/comment-page-1/#comment-11379</link>
		<dc:creator>ClearlbyBiased</dc:creator>
		<pubDate>Wed, 13 May 2009 22:28:16 +0000</pubDate>
		<guid isPermaLink="false">guid-fix-me!#comment-11379</guid>
		<description>I have prefect running with the scheduler.   Every few days, or so, I delete the contents.  Always makes things load faster.  Almost instantly when I delete the fetch.  Then wait and wait after a few days of a full fetch.&lt;br&gt;Why?  Others have the same thing.  I was hoping to find that I could list only the 15 or so programs I use most often.  Like setting the &quot;page&quot; to 15 instead of 4000 (dec) but that probably isn&#039;t the right approach.  I need to find someone who understands the interplay of the parameters.  I also know it degrades when I use the registry to turn it off.</description>
		<content:encoded><![CDATA[<p>I have prefect running with the scheduler.   Every few days, or so, I delete the contents.  Always makes things load faster.  Almost instantly when I delete the fetch.  Then wait and wait after a few days of a full fetch.<br />Why?  Others have the same thing.  I was hoping to find that I could list only the 15 or so programs I use most often.  Like setting the &#8220;page&#8221; to 15 instead of 4000 (dec) but that probably isn&#39;t the right approach.  I need to find someone who understands the interplay of the parameters.  I also know it degrades when I use the registry to turn it off.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mitu</title>
		<link>http://www.tech-recipes.com/rx/1285/xp-registry-hack-to-disable-or-modify-prefetch/comment-page-1/#comment-3783</link>
		<dc:creator>Mitu</dc:creator>
		<pubDate>Thu, 02 Oct 2008 10:21:12 +0000</pubDate>
		<guid isPermaLink="false">guid-fix-me!#comment-3783</guid>
		<description>Mucho thanks Larry.... I really appreciate it...</description>
		<content:encoded><![CDATA[<p>Mucho thanks Larry&#8230;. I really appreciate it&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: </title>
		<link>http://www.tech-recipes.com/rx/1285/xp-registry-hack-to-disable-or-modify-prefetch/comment-page-1/#comment-3700</link>
		<dc:creator></dc:creator>
		<pubDate>Mon, 01 Sep 2008 10:49:14 +0000</pubDate>
		<guid isPermaLink="false">guid-fix-me!#comment-3700</guid>
		<description>WRONG WRONG WRONG!

This article contains a descriprion of how prefetching works that is simple and easily understood. If only it were correct.

Prefetch does NOT preload applications at bootup and no memory is wasted. This view of prefetching is very common but completely wrong.

When an application starts Windows does not immediately load the entire application. Program code and data are loaded into memory only as needed and then cached for future use. This action is handled by the processor and operating system and is invisible to the application. This procedure is followed by virtually all systems that are based on virtual memory.

This system saves considerable memory and load time, particularly with large and complex applications. But the process isn&#039;t optimum. Fragments of multiple files will be referenced in an order that is far from optimum for loading efficiently. The prefetch system was designed to solve this problem.

When an application starts, Windows checks the prefetch folder for an associated entry. If none is found a conventional load is performed. But while this occurs Windows monitors which files are accessed and the parts that are loaded. After the application has started this data is saved in an associated prefetch file. But take note, only an index to the files is saved, not the data itself.

When the application is run at a later time, Windows will find an associated prefetch file. The system uses the contents of this file as a guide to &quot;prefetch&quot; the program code and data and places it into the system cache. A normal program load is then initiated, but proceeds much faster than usual because the data is already in memory. This is what prefetching really means.

After the prefetch folder reaches 128 application entries no more will be added. Later, during idle time, the system will examine the folder and delete all but the 32 most recently used entries. The process will then continue as before. The folder is thus self cleaning and no user action is required - or desireable.

Prefetching this way has none of the problems that are commonly described, such as in this article. Application prefetch files are referenced only after application launch has been initiated so boot time is not prolonged. No data is loaded into memory that would not be loaded a few seconds later anyway. No memory is wasted so sytems with limited memory will not be impaired. Systems with as little as 64MB will benefit but 128 MB is requred to take full advantage of prefetching.

The prefetch system relies on the Task Scheduler service for proper operarion so it must be enabled and set to Automatic. Some uninformed sources have said that this service is unnecessary and may be safely disabled. Doing so will cripple the prefetch system and performace degraded. Over time this degradation can become severe.

The description of prefetch above is very much simplified and much more is actually involved. The prefetch system has been extensively tested by both Microsoft and others. My own tests confirm it. Examining the last access date of prefetch files will clearly show thay are accesed only when the program is run, not at boot time.

Manual cleaning of prefetch files will deprive Windows of a valuable resource and serves no useful purpose. The relevant registry entries are set to optimum by default and there is nothing to be gained by changing them.

The article by Tech-Recipes is incorrect and offers advice that will impair performance. Informed readers are well aware of this. Such serious errors must corrected.

The article at URL: http://www.tech-recipes.com/windows_tips671.html
is also based on the incorrect understanding of prefetch.

References:
http://home.comcast.net/~SupportCD/XPMyths.html
Also check the references on this page. One is by Ryan Myers, a Microsoft engineer on the client performance team.

I am well aware of the fact that many respected websites are promoting the same false idea as on this site. I have seen many of them. They are wrong.

Larry Miller
Microsoft MCSA
CompTIA Network+, A+
Amateur programmer.</description>
		<content:encoded><![CDATA[<p>WRONG WRONG WRONG!</p>
<p>This article contains a descriprion of how prefetching works that is simple and easily understood. If only it were correct.</p>
<p>Prefetch does NOT preload applications at bootup and no memory is wasted. This view of prefetching is very common but completely wrong.</p>
<p>When an application starts Windows does not immediately load the entire application. Program code and data are loaded into memory only as needed and then cached for future use. This action is handled by the processor and operating system and is invisible to the application. This procedure is followed by virtually all systems that are based on virtual memory.</p>
<p>This system saves considerable memory and load time, particularly with large and complex applications. But the process isn&#8217;t optimum. Fragments of multiple files will be referenced in an order that is far from optimum for loading efficiently. The prefetch system was designed to solve this problem.</p>
<p>When an application starts, Windows checks the prefetch folder for an associated entry. If none is found a conventional load is performed. But while this occurs Windows monitors which files are accessed and the parts that are loaded. After the application has started this data is saved in an associated prefetch file. But take note, only an index to the files is saved, not the data itself.</p>
<p>When the application is run at a later time, Windows will find an associated prefetch file. The system uses the contents of this file as a guide to &#8220;prefetch&#8221; the program code and data and places it into the system cache. A normal program load is then initiated, but proceeds much faster than usual because the data is already in memory. This is what prefetching really means.</p>
<p>After the prefetch folder reaches 128 application entries no more will be added. Later, during idle time, the system will examine the folder and delete all but the 32 most recently used entries. The process will then continue as before. The folder is thus self cleaning and no user action is required &#8211; or desireable.</p>
<p>Prefetching this way has none of the problems that are commonly described, such as in this article. Application prefetch files are referenced only after application launch has been initiated so boot time is not prolonged. No data is loaded into memory that would not be loaded a few seconds later anyway. No memory is wasted so sytems with limited memory will not be impaired. Systems with as little as 64MB will benefit but 128 MB is requred to take full advantage of prefetching.</p>
<p>The prefetch system relies on the Task Scheduler service for proper operarion so it must be enabled and set to Automatic. Some uninformed sources have said that this service is unnecessary and may be safely disabled. Doing so will cripple the prefetch system and performace degraded. Over time this degradation can become severe.</p>
<p>The description of prefetch above is very much simplified and much more is actually involved. The prefetch system has been extensively tested by both Microsoft and others. My own tests confirm it. Examining the last access date of prefetch files will clearly show thay are accesed only when the program is run, not at boot time.</p>
<p>Manual cleaning of prefetch files will deprive Windows of a valuable resource and serves no useful purpose. The relevant registry entries are set to optimum by default and there is nothing to be gained by changing them.</p>
<p>The article by Tech-Recipes is incorrect and offers advice that will impair performance. Informed readers are well aware of this. Such serious errors must corrected.</p>
<p>The article at URL: <a href="http://www.tech-recipes.com/windows_tips671.html" rel="nofollow">http://www.tech-recipes.com/windows_tips671.html</a><br />
is also based on the incorrect understanding of prefetch.</p>
<p>References:<br />
<a href="http://home.comcast.net/~SupportCD/XPMyths.html" rel="nofollow">http://home.comcast.net/~SupportCD/XPMyths.html</a><br />
Also check the references on this page. One is by Ryan Myers, a Microsoft engineer on the client performance team.</p>
<p>I am well aware of the fact that many respected websites are promoting the same false idea as on this site. I have seen many of them. They are wrong.</p>
<p>Larry Miller<br />
Microsoft MCSA<br />
CompTIA Network+, A+<br />
Amateur programmer.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
