Windows XP search question (nsr)

[The AD]

I figure someone on here will know the answer to this one...

I just noticed something weird in Windows XP today. Up until last week my laptop at work was running Win 2K. I just got a new one that's running XP. Anyway, I used to use the "search" in a Windows Explorer window to look for text strings within files. Now I can't get that to work.

For example, if I enter * in the "search for files or folders named:" field and foo in "Containing text:" it will say nothing matches even though I know several files in the folder I'm searching contain the string foo. However, if there are any fileNAMES containing foo, it will find those. On my old laptop it would actually looks within the files and match the string.

So what the heck's going on here?

[Tuckerman]

Try it like this "*foo*" or is that what you are doing? * being a wild card. I use that search function all day it should work.

[The AD]

Using a wildcard doesn't affect it. It still finds no matches. It's pretty damn strange because it works for a coworker who's also on XP.

There's the option about turning on indexing. Could this be the problem? I have it turned off. My understanding is that would only speed up the searching (and probably slow down my machine in the process), but not affect the search, but maybe I'm wrong??

[Tuckerman]

Does it give you the option to seach for a word or a phrase in the file?

[dbp]

Googled: "Windows XP search" and this was the first result...
I don't know if this is legit or if it will help. GIYF

Windows® XP - Search Problems

Windows® XP has a known issue for not finding a number of File Types when you do a Search for Files "containing text" or using the "A word or phrase in the file" option. This can be remedied for many file types, but not all. The cause is the lack of a PersistentHandler value in the Registry for this type of file.

You can correct this by clicking Start, Run and entering REGEDIT Navigate to HKEY_CLASSES_ROOT and locating the entry for the file type in question. For example, .txt, .adm, .asp. Expand the branch for that file type, and if the PersistentHandler subkey does not exist, create it. Do this by clicking on the file extension key and going to Edit, New, Key. Name the Key, PersistentHandler. Click on the PersistentHandler sub-key. In Regedit's right pane, double click on the Default value and enter the following (copy and paste may be your best bet):

{5e941d80-bf96-11cd-b579-08002b30bfeb}

If the PersistentHandler sub-key does exist, do not change the default value. This could have very undesired consequences.

Close Regedit and reboot the computer. This file type will now be searched for "A word or phrase in the file" type searches.

An alternative is to download a small VB Script utility here. Save the file you just downloaded to your hard disk. Locate the file you just saved and double click it. Enter the file extension you wish to modify. If the PersistentHandler sub-key exists, no changes will be made. If it does not exist for the file type in question, the Registry will be updated accordingly. Reboot when you're finished with the file types you wish to change.

Many users are switching to a program called Agent Ransack, http://www.agentransack.com, to work around Windows XP's Search limitations.
This page last updated 08/19/2003 13:27
All material © 2003 Doug Knox

[Buster Highmen]

I figure someone on here will know the answer to this one...

I just noticed something weird in Windows XP today. Up until last week my laptop at work was running Win 2K. I just got a new one that's running XP. Anyway, I used to use the "search" in a Windows Explorer window to look for text strings within files. Now I can't get that to work.

For example, if I enter * in the "search for files or folders named:" field and foo in "Containing text:" it will say nothing matches even though I know several files in the folder I'm searching contain the string foo. However, if there are any fileNAMES containing foo, it will find those. On my old laptop it would actually looks within the files and match the string.

So what the heck's going on here?

Start->All Programs-> Accessories->Command prompt.

Use findstr.exe.
Example: "findstr foo *.txt" will search all .txt files for the string foo.

For help, type "findstr /?"

[The AD]

Start->All Programs-> Accessories->Command prompt.

Command prompt? But that's sooo '80s.

I think I'll try the regedit fix and see if that does anything.

[Tuckerman]

Not to hijack, but while the XP sexperts are on this, I have a question.

Yesterday my address bar disappeared. If I go to toolbars on the drop menu, it's checked, but will not display. This is somewhat frustrating for posting thread links.

Get firefox if you don't already have it.

edit only took 2 years to get to post 100

[Nobody Famous]

Googled: "Windows XP search" and this was the first result...
I don't know if this is legit or if it will help. GIYF

Yes, that is legit. Win XP's search fuxntion by default will only search files of registered types, .dat, .doc, .xls, etc.

Here's how to change that behavior: http://support.microsoft.com/default...b;en-us;309173. Scroll down and check the options it says for "Method 2".

[Mcwop]

Turn on indexing.

[Nobody Famous]

I forgot to add, on the original Windows XP search problem, the Google Desktop Search bar does not have this problem, and I think it's faster.

[fez]

weird, i just open a shell and i can find whatever i want with a couple simple commands.
i think you need a proper operating system.

[phUnk]

Turn on indexing.

Indexing will most likely slow down your machine for very little benefit.

[The AD]

weird, i just open a shell and i can find whatever i want with a couple simple commands.
i think you need a proper operating system.

I agree. We used Unix until about a year ago!

[Buster Highmen]

I agree. We used Unix until about a year ago!

80's? Ahem.

[Vets]

I figure someone on here will know the answer to this one...

I just noticed something weird in Windows XP today. Up until last week my laptop at work was running Win 2K. I just got a new one that's running XP. Anyway, I used to use the "search" in a Windows Explorer window to look for text strings within files. Now I can't get that to work.

For example, if I enter * in the "search for files or folders named:" field and foo in "Containing text:" it will say nothing matches even though I know several files in the folder I'm searching contain the string foo. However, if there are any fileNAMES containing foo, it will find those. On my old laptop it would actually looks within the files and match the string.

So what the heck's going on here?

Which foo are you looking for?

or

?

[davidof]

I agree. We used Unix until about a year ago!

Just install the Redhat Cygwin toolkit on XP and turn your Puta into a Man's machine.

[The AD]

80's? Ahem.

Yeah, yeah...