<?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: Why does Windows put 64-bit binaries in System32?</title>
	<atom:link href="http://brandonlive.com/2008/12/22/why-does-windows-put-64-bit-binaries-in-system32/feed/" rel="self" type="application/rss+xml" />
	<link>http://brandonlive.com/2008/12/22/why-does-windows-put-64-bit-binaries-in-system32/</link>
	<description>Seattle Geek with lots to say.</description>
	<lastBuildDate>Mon, 30 Jan 2012 11:30:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Kevin</title>
		<link>http://brandonlive.com/2008/12/22/why-does-windows-put-64-bit-binaries-in-system32/comment-page-1/#comment-129045</link>
		<dc:creator>Kevin</dc:creator>
		<pubDate>Sun, 11 Jan 2009 01:12:26 +0000</pubDate>
		<guid isPermaLink="false">http://brandonlive.com/?p=503#comment-129045</guid>
		<description>Alexandre, although I doubt you&#039;ll see this, the answer for Windows XP is Copernic.  I&#039;ve never used Live Search 4 on XP, but it couldn&#039;t possibly be better than Copernic, because that search is super fast.

I&#039;m still undecided on whether it&#039;s better than Vistas search, because I run Vista and 7 at home and XP at work.

Kevin</description>
		<content:encoded><![CDATA[<p>Alexandre, although I doubt you&#8217;ll see this, the answer for Windows XP is Copernic.  I&#8217;ve never used Live Search 4 on XP, but it couldn&#8217;t possibly be better than Copernic, because that search is super fast.</p>
<p>I&#8217;m still undecided on whether it&#8217;s better than Vistas search, because I run Vista and 7 at home and XP at work.</p>
<p>Kevin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon</title>
		<link>http://brandonlive.com/2008/12/22/why-does-windows-put-64-bit-binaries-in-system32/comment-page-1/#comment-128988</link>
		<dc:creator>Brandon</dc:creator>
		<pubDate>Thu, 25 Dec 2008 20:47:52 +0000</pubDate>
		<guid isPermaLink="false">http://brandonlive.com/?p=503#comment-128988</guid>
		<description>At this time we have no plans to offer new features for Windows XP.  We&#039;re very focused right now on making sure that Windows 7 offers the best search and browse experience that we can put together.</description>
		<content:encoded><![CDATA[<p>At this time we have no plans to offer new features for Windows XP.  We&#8217;re very focused right now on making sure that Windows 7 offers the best search and browse experience that we can put together.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alexandre Grigoriev</title>
		<link>http://brandonlive.com/2008/12/22/why-does-windows-put-64-bit-binaries-in-system32/comment-page-1/#comment-128984</link>
		<dc:creator>Alexandre Grigoriev</dc:creator>
		<pubDate>Wed, 24 Dec 2008 15:43:08 +0000</pubDate>
		<guid isPermaLink="false">http://brandonlive.com/?p=503#comment-128984</guid>
		<description>Brandon,

Thanks for heeding my wishes. Are those enhancements in XP version yet?</description>
		<content:encoded><![CDATA[<p>Brandon,</p>
<p>Thanks for heeding my wishes. Are those enhancements in XP version yet?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon</title>
		<link>http://brandonlive.com/2008/12/22/why-does-windows-put-64-bit-binaries-in-system32/comment-page-1/#comment-128983</link>
		<dc:creator>Brandon</dc:creator>
		<pubDate>Wed, 24 Dec 2008 08:40:47 +0000</pubDate>
		<guid isPermaLink="false">http://brandonlive.com/?p=503#comment-128983</guid>
		<description>Alex - 

You&#039;ve pretty much described how Windows Search already works.  It already &quot;backs off&quot; on user activity, and takes great care in the use of I/O, memory, and processor prioritization.  On Vista or later, the shell will perform a Grep search in unindexed locations.  In Windows 7, we&#039;ve done a lot of work to improve the scenario of searching locations that are only partially indexed, with items being added to the view as they&#039;re crawled, and the location you&#039;re viewing being prioritized in the indexing queue.

We already have two posts about the Windows Search indexer up on the Engineering Team blog, covering a lot of what you&#039;ve asked.

http://blogs.msdn.com/e7/archive/2008/10/13/windows-desktop-search.aspx
and
http://blogs.msdn.com/e7/archive/2008/10/23/follow-up-windows-desktop-search.aspx</description>
		<content:encoded><![CDATA[<p>Alex &#8211; </p>
<p>You&#8217;ve pretty much described how Windows Search already works.  It already &#8220;backs off&#8221; on user activity, and takes great care in the use of I/O, memory, and processor prioritization.  On Vista or later, the shell will perform a Grep search in unindexed locations.  In Windows 7, we&#8217;ve done a lot of work to improve the scenario of searching locations that are only partially indexed, with items being added to the view as they&#8217;re crawled, and the location you&#8217;re viewing being prioritized in the indexing queue.</p>
<p>We already have two posts about the Windows Search indexer up on the Engineering Team blog, covering a lot of what you&#8217;ve asked.</p>
<p><a href="http://blogs.msdn.com/e7/archive/2008/10/13/windows-desktop-search.aspx" rel="nofollow">http://blogs.msdn.com/e7/archive/2008/10/13/windows-desktop-search.aspx</a><br />
and<br />
<a href="http://blogs.msdn.com/e7/archive/2008/10/23/follow-up-windows-desktop-search.aspx" rel="nofollow">http://blogs.msdn.com/e7/archive/2008/10/23/follow-up-windows-desktop-search.aspx</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alexandre Grigoriev</title>
		<link>http://brandonlive.com/2008/12/22/why-does-windows-put-64-bit-binaries-in-system32/comment-page-1/#comment-128981</link>
		<dc:creator>Alexandre Grigoriev</dc:creator>
		<pubDate>Wed, 24 Dec 2008 04:48:24 +0000</pubDate>
		<guid isPermaLink="false">http://brandonlive.com/?p=503#comment-128981</guid>
		<description>Mio,

Do an experiment. Install, for example new DDK or SDK, just a bunch of files. With Windows Search 4, try to find some word _in_ _that_ _directory_ that you know should be there, some function name. If you do it too soon, you&#039;ll be greeted with ever friendly &quot;Folder not indexed yet&quot;. Is is truly impossible to do what&#039;s requested: just run through the files and find the requested files/words, etc? It takes finite time, you know, not as fast as for an indexed directory, but still faster than getting a cup of coffee. Why Windows search should be completely orthogonal to the built-in traditional search? I want one function: Find, not &quot;Find with index&quot; and &quot;Find without index&quot;. It should just do a best effort.

And don&#039;t get me started on those non-indexable files. If I want search in non-indexable files, *please* just do traditional search, not ignore them altogether.</description>
		<content:encoded><![CDATA[<p>Mio,</p>
<p>Do an experiment. Install, for example new DDK or SDK, just a bunch of files. With Windows Search 4, try to find some word _in_ _that_ _directory_ that you know should be there, some function name. If you do it too soon, you&#8217;ll be greeted with ever friendly &#8220;Folder not indexed yet&#8221;. Is is truly impossible to do what&#8217;s requested: just run through the files and find the requested files/words, etc? It takes finite time, you know, not as fast as for an indexed directory, but still faster than getting a cup of coffee. Why Windows search should be completely orthogonal to the built-in traditional search? I want one function: Find, not &#8220;Find with index&#8221; and &#8220;Find without index&#8221;. It should just do a best effort.</p>
<p>And don&#8217;t get me started on those non-indexable files. If I want search in non-indexable files, *please* just do traditional search, not ignore them altogether.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mio</title>
		<link>http://brandonlive.com/2008/12/22/why-does-windows-put-64-bit-binaries-in-system32/comment-page-1/#comment-128980</link>
		<dc:creator>Mio</dc:creator>
		<pubDate>Wed, 24 Dec 2008 04:07:29 +0000</pubDate>
		<guid isPermaLink="false">http://brandonlive.com/?p=503#comment-128980</guid>
		<description></description>
		<content:encoded><![CDATA[<p>&#8220;I want to find a file, it’s here, not somewhere on internet.&#8221;</p>
<p>But the content on the internet is indexed, and thus easier and faster to find.</p>
<p>Do you have any idea how long it takes to find a file on your hard drive by brute force? It&#8217;s a limitation of hardware. Your hard drive can only be read so fast. Indexing it is the only way to be able to find what you want fast.</p>
<p>You uninstalled it? So you went back to the slow-no-matter-what grep method of searching through files? Doesn&#8217;t that defeat your entire purpose?</p>
<p>Also, Windows Search does run with reduced priority.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alexandre Grigoriev</title>
		<link>http://brandonlive.com/2008/12/22/why-does-windows-put-64-bit-binaries-in-system32/comment-page-1/#comment-128979</link>
		<dc:creator>Alexandre Grigoriev</dc:creator>
		<pubDate>Wed, 24 Dec 2008 00:29:34 +0000</pubDate>
		<guid isPermaLink="false">http://brandonlive.com/?p=503#comment-128979</guid>
		<description>Oh, that was my comment; nice to hear from you. So how about making Windows search that runs on reduced priority (doesn&#039;t slow the rest of the system responsiveness), doesn&#039;t take &gt;50% of 2.4GHz processor, and opens files in non-buffered mode, to avoid that ugly file cache bloat that makes the whole system stand still while madly inpaging. I mean, runs on an XP-capable machine, reasonably. And which doesn&#039;t make that lame &quot;the folder is not indexed yet&quot; excuse. If a folder is not indexed, just read the damn files. Who cares? I want to find a file, it&#039;s here, not somewhere on internet. What would BillG say for that &quot;not indexed&quot; message? He would rant even longer than me. I just uninstalled it very promptly.</description>
		<content:encoded><![CDATA[<p>Oh, that was my comment; nice to hear from you. So how about making Windows search that runs on reduced priority (doesn&#8217;t slow the rest of the system responsiveness), doesn&#8217;t take &gt;50% of 2.4GHz processor, and opens files in non-buffered mode, to avoid that ugly file cache bloat that makes the whole system stand still while madly inpaging. I mean, runs on an XP-capable machine, reasonably. And which doesn&#8217;t make that lame &#8220;the folder is not indexed yet&#8221; excuse. If a folder is not indexed, just read the damn files. Who cares? I want to find a file, it&#8217;s here, not somewhere on internet. What would BillG say for that &#8220;not indexed&#8221; message? He would rant even longer than me. I just uninstalled it very promptly.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

