Archives » July 10th, 2005

July 10, 2005

Windows Search Doesn’t Look Inside PHP Files

Recently I was trying to search through a group of files for a particular word. And in most cases, Windows Search works fine for this. There’s a box to type in the text you’re looking for, and Windows scans the text of each file to find your word. But this time it wasn’t working. And the catch is that I was scanning a bunch of PHP files for a particular piece of code. And even though I knew that code existed in these files, the Search Assistant was saying “There were no results to display”.

So Windows is pissing me off again. What else is new? This time it was refusing to search inside PHP files, even when I told it to. After some searching around, I found the solution. It’s outlined in this Knowledge Base article, under Method 2.

  1. Click Start, and then click Search (or point to Search, and then click For Files or Folders).
  2. Click Change preferences, and then click With Indexing Service (for faster local searches).
  3. Click Change Indexing Service Settings (Advanced). Note that you do not have to turn on the Index service.
  4. On the toolbar, click Show/Hide Console Tree.
  5. In the left pane, right-click Indexing Service on Local Machine, and then click Properties.
  6. On the Generation tab, click to select the Index files with unknown extensions check box, and then click OK.
  7. Close the Indexing Service console.

And it works, and now I can search through PHP files for a particular piece of code. I don’t know why this is turned off in Windows XP…maybe to make searches faster? Personally I’d rather add five seconds to the search time and find the results I’m looking for, but I’m just kooky that way.


Yesterday afternoon a brush fire broke out in the hills south of Gardnerville, sending up a plume of smoke that could be seen from the entire Carson Valley and even parts of Carson City.

Called the “Mud Lake Fire”, it was centered a few miles northeast of Woodfords, on the other side of the California state line. Thanks to a quick response from firefighters all over the area, there is no plume of smoke this morning, meaning it’s been put out, or nearly so.

The cause hasn’t been determined yet, but this just serves as another reminder that we’ve got another hot, dry summer on our hands, and that fire and the outdoors generally don’t mix well this time of year. So if you’re going to go around shooting fireballs, keep it indoors!