<?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: The Ongoing Windows Desktop Search Controversy</title>
	<atom:link href="http://www.zoliblog.com/2007/09/12/the-ongoing-windows-desktop-search-controversy/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.zoliblog.com/2007/09/12/the-ongoing-windows-desktop-search-controversy/</link>
	<description>Connecting the dots ...</description>
	<lastBuildDate>Sat, 21 Nov 2009 06:03:39 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Karl</title>
		<link>http://www.zoliblog.com/2007/09/12/the-ongoing-windows-desktop-search-controversy/#comment-18043</link>
		<dc:creator>Karl</dc:creator>
		<pubDate>Sat, 04 Jul 2009 00:30:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.zoliblog.com/2007/09/12/the-ongoing-windows-desktop-search-controversy/#comment-18043</guid>
		<description>Yep, I was just curious today as to why Desktop Search was not working on my PC.  I have the old indexing service disabled, and I HAD the index flag unslected on many of my folders.  As mentioned above, Desktop Search will honor those settings, so you need to allow indexing for it to work.  However, you DO NOT need to enable the old Indexing Service.  Just confirming what Brandon said above, thanks.</description>
		<content:encoded><![CDATA[<p>Yep, I was just curious today as to why Desktop Search was not working on my PC.  I have the old indexing service disabled, and I HAD the index flag unslected on many of my folders.  As mentioned above, Desktop Search will honor those settings, so you need to allow indexing for it to work.  However, you DO NOT need to enable the old Indexing Service.  Just confirming what Brandon said above, thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kirk M</title>
		<link>http://www.zoliblog.com/2007/09/12/the-ongoing-windows-desktop-search-controversy/#comment-6560</link>
		<dc:creator>Kirk M</dc:creator>
		<pubDate>Sun, 14 Oct 2007 14:45:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.zoliblog.com/2007/09/12/the-ongoing-windows-desktop-search-controversy/#comment-6560</guid>
		<description>Brandon,

That would explain the problem then. I&#039;ll give it another go then. Perhaps I missed it but these parameters didn&#039;t seemed to be listed in the requirements or FAQ&#039;s on the MS website for Desktop Search.

Thanks for the info. Much appreciated.</description>
		<content:encoded><![CDATA[<p>Brandon,</p>
<p>That would explain the problem then. I&#8217;ll give it another go then. Perhaps I missed it but these parameters didn&#8217;t seemed to be listed in the requirements or FAQ&#8217;s on the MS website for Desktop Search.</p>
<p>Thanks for the info. Much appreciated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon Paddock</title>
		<link>http://www.zoliblog.com/2007/09/12/the-ongoing-windows-desktop-search-controversy/#comment-6544</link>
		<dc:creator>Brandon Paddock</dc:creator>
		<pubDate>Thu, 11 Oct 2007 22:57:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.zoliblog.com/2007/09/12/the-ongoing-windows-desktop-search-controversy/#comment-6544</guid>
		<description>Indexing Service should definitely be disabled.  Running both is not a supported configuration and known to cause problems.

They do both honor the &quot;Not content indexed&quot; flag on drives / folders / files, which is probably why you were unable to choose that drive for indexing.</description>
		<content:encoded><![CDATA[<p>Indexing Service should definitely be disabled.  Running both is not a supported configuration and known to cause problems.</p>
<p>They do both honor the &#8220;Not content indexed&#8221; flag on drives / folders / files, which is probably why you were unable to choose that drive for indexing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kirk M</title>
		<link>http://www.zoliblog.com/2007/09/12/the-ongoing-windows-desktop-search-controversy/#comment-6537</link>
		<dc:creator>Kirk M</dc:creator>
		<pubDate>Thu, 11 Oct 2007 21:15:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.zoliblog.com/2007/09/12/the-ongoing-windows-desktop-search-controversy/#comment-6537</guid>
		<description>Thanks for the info. Although I know the workings of my OS fairly well perhaps I did something wrong then. I had disabled the indexing service long ago for just that reason and my C: drive was set not to be indexed. It seems I had to enable both before WDS would index anything at all or let me choose what folders I wished to add to the index but maybe just enabling the C: drive to be indexed allowed WDS to work then rather than enabling XP&#039;s indexing service?

Oh, and I have a fully updated XP PRO with .net 1,2 and 3 installed and not a whole lot of extra software. Ilike to keep things fairly pure.

Sorry if this comment is a bit off topic but in the above case, when using WDS should the normal XP indexing service be enabled or disabled?</description>
		<content:encoded><![CDATA[<p>Thanks for the info. Although I know the workings of my OS fairly well perhaps I did something wrong then. I had disabled the indexing service long ago for just that reason and my C: drive was set not to be indexed. It seems I had to enable both before WDS would index anything at all or let me choose what folders I wished to add to the index but maybe just enabling the C: drive to be indexed allowed WDS to work then rather than enabling XP&#8217;s indexing service?</p>
<p>Oh, and I have a fully updated XP PRO with .net 1,2 and 3 installed and not a whole lot of extra software. Ilike to keep things fairly pure.</p>
<p>Sorry if this comment is a bit off topic but in the above case, when using WDS should the normal XP indexing service be enabled or disabled?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon Paddock</title>
		<link>http://www.zoliblog.com/2007/09/12/the-ongoing-windows-desktop-search-controversy/#comment-6536</link>
		<dc:creator>Brandon Paddock</dc:creator>
		<pubDate>Thu, 11 Oct 2007 19:52:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.zoliblog.com/2007/09/12/the-ongoing-windows-desktop-search-controversy/#comment-6536</guid>
		<description>Kirk - WDS has a very tiny resource footprint, and definitely won&#039;t make your hard drive I/O any greater while you&#039;re using the computer.  WDS, by default, only indexes when your system is idle (no mouse + keyboard usage, low CPU usage, and low disk I/O).  WDS was designed to run well on much older systems than what you described (tons of enterprises running it on 1ghz 512MB machines, for example).  Tests have shown the impact on system performance is roughly the same as Copernic, and less than GDS.

If you are experiencing any noticeable impact on performance, it is likely you&#039;re encountering a compatibility issue.  Otherwise, it&#039;s probably something other than WDS causing the problem.

Further, the XP built-in Indexing Service *did* cause disk trashing, largely because it didn&#039;t back-off on user activity, though also because it&#039;s a much older version of the indexing technology and not optimized for desktop use.

WDS does NOT depend on the built-in Indexing Service.</description>
		<content:encoded><![CDATA[<p>Kirk &#8211; WDS has a very tiny resource footprint, and definitely won&#8217;t make your hard drive I/O any greater while you&#8217;re using the computer.  WDS, by default, only indexes when your system is idle (no mouse + keyboard usage, low CPU usage, and low disk I/O).  WDS was designed to run well on much older systems than what you described (tons of enterprises running it on 1ghz 512MB machines, for example).  Tests have shown the impact on system performance is roughly the same as Copernic, and less than GDS.</p>
<p>If you are experiencing any noticeable impact on performance, it is likely you&#8217;re encountering a compatibility issue.  Otherwise, it&#8217;s probably something other than WDS causing the problem.</p>
<p>Further, the XP built-in Indexing Service *did* cause disk trashing, largely because it didn&#8217;t back-off on user activity, though also because it&#8217;s a much older version of the indexing technology and not optimized for desktop use.</p>
<p>WDS does NOT depend on the built-in Indexing Service.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kirk M</title>
		<link>http://www.zoliblog.com/2007/09/12/the-ongoing-windows-desktop-search-controversy/#comment-6535</link>
		<dc:creator>Kirk M</dc:creator>
		<pubDate>Thu, 11 Oct 2007 17:08:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.zoliblog.com/2007/09/12/the-ongoing-windows-desktop-search-controversy/#comment-6535</guid>
		<description>Okay, so Photo Gallery is dependent on Desktop Search and it&#039;s not blatantly advertised that this is so. Not good but typical. MS taking advantage of the &quot;average user&quot; that really doesn&#039;t check things out thoroughly before downloading. Another real problem here is that Desktop Search is a resource hog when it shouldn&#039;t be. It also is constantly banging on your hard drive so much it never seems to stop being accessed (default settings). This never happens with XP&#039;s normal indexing service activated (which Desktop Search is dependant on so why the difference? Copernic doesn&#039;t do this.).

Perhaps folks with dual core PC&#039;s with 2 GB of memory don&#039;t experince this problem (running XP) however the majority of PC owners are still (currently) running single core processor&#039;s with 1GB of RAM or less and having Desktop Search installed when it&#039;s not obvious to the user is definately a problem. As usual, MS needs to be more up front with their requirements for new software.

A long time MS OS/software user.</description>
		<content:encoded><![CDATA[<p>Okay, so Photo Gallery is dependent on Desktop Search and it&#8217;s not blatantly advertised that this is so. Not good but typical. MS taking advantage of the &#8220;average user&#8221; that really doesn&#8217;t check things out thoroughly before downloading. Another real problem here is that Desktop Search is a resource hog when it shouldn&#8217;t be. It also is constantly banging on your hard drive so much it never seems to stop being accessed (default settings). This never happens with XP&#8217;s normal indexing service activated (which Desktop Search is dependant on so why the difference? Copernic doesn&#8217;t do this.).</p>
<p>Perhaps folks with dual core PC&#8217;s with 2 GB of memory don&#8217;t experince this problem (running XP) however the majority of PC owners are still (currently) running single core processor&#8217;s with 1GB of RAM or less and having Desktop Search installed when it&#8217;s not obvious to the user is definately a problem. As usual, MS needs to be more up front with their requirements for new software.</p>
<p>A long time MS OS/software user.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon Paddock</title>
		<link>http://www.zoliblog.com/2007/09/12/the-ongoing-windows-desktop-search-controversy/#comment-5794</link>
		<dc:creator>Brandon Paddock</dc:creator>
		<pubDate>Thu, 13 Sep 2007 00:59:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.zoliblog.com/2007/09/12/the-ongoing-windows-desktop-search-controversy/#comment-5794</guid>
		<description>Regarding the Live Photo Gallery issue you mentioned - that&#039;s still a BETA offering right?  Perhaps you should clarify that in your post, as the user experience there is not final.

Further, Photo Gallery has a technical dependency on the Windows Search property system - which is only redistributed to XP via WDS.  It&#039;s definitely not trying to &quot;sneak&quot; anything anywhere, it just needs that in order to function on a pre-Vista system.  Countless applications do this with DirectX, XMLLite, SQLLite, MSDE, hotfixes, .NET Framework, C++ runtimes, etc.  Though I agree that the user experience here needs work, I wouldn&#039;t call it a &quot;violation&quot; of your computer for an application to install a system update that it depends on.

Also - if you install Photo Gallery by itself, is the experience better?  Perhaps this is just an issue with the combined Live Installer tool?</description>
		<content:encoded><![CDATA[<p>Regarding the Live Photo Gallery issue you mentioned &#8211; that&#8217;s still a BETA offering right?  Perhaps you should clarify that in your post, as the user experience there is not final.</p>
<p>Further, Photo Gallery has a technical dependency on the Windows Search property system &#8211; which is only redistributed to XP via WDS.  It&#8217;s definitely not trying to &#8220;sneak&#8221; anything anywhere, it just needs that in order to function on a pre-Vista system.  Countless applications do this with DirectX, XMLLite, SQLLite, MSDE, hotfixes, .NET Framework, C++ runtimes, etc.  Though I agree that the user experience here needs work, I wouldn&#8217;t call it a &#8220;violation&#8221; of your computer for an application to install a system update that it depends on.</p>
<p>Also &#8211; if you install Photo Gallery by itself, is the experience better?  Perhaps this is just an issue with the combined Live Installer tool?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
