The "content" command works fine when it does. But it seems to not recognize certain extensions.
Example,
If I use the command
"*.txt" AND content:"need"
, it will work perfectly and it will show me only the TXT files that contain the word "need".
But if I use this command,
"*.ffpreset" AND content:"need"
, it will not display anything.
"ffpreset" internally is just a text file with other extension. If I rename the "ffpreset" extension to "txt", it will behave correctly, but it will be cumbersome to have to rename all the files every time I encounter a similar situation but with thousands of files.
The "content" command does not search specific files.
-
- Posts: 3
- Joined: Fri May 26, 2023 6:30 am
Re: The "content" command does not search specific files.
There is most likely an iFilter behaving badly.
Please try the following search:
*.ffpreset utf8content:"need"
Please try SearchFilterView to manage iFilters.
Remove .ffpreset from any iFilters.
Please try the following search:
*.ffpreset utf8content:"need"
Please try SearchFilterView to manage iFilters.
Remove .ffpreset from any iFilters.
-
- Posts: 3
- Joined: Fri May 26, 2023 6:30 am
Re: The "content" command does not search specific files.
No luck.
I use Text Crawler as an alternative search tool, works but Everything is much faster doing the same job.Please try SearchFilterView to manage iFilters.
Remove .ffpreset from any iFilters.
Re: The "content" command does not search specific files.
Please try the following search:
*.ffpreset unicodecontent:"need"
utf8content: / unicodecontent: will override the system iFilter and use the specified text encoding.
Do you know the text encoding of the ffpreset files?
Everything 1.5 will have a textplaincontent: search.
*.ffpreset unicodecontent:"need"
utf8content: / unicodecontent: will override the system iFilter and use the specified text encoding.
Do you know the text encoding of the ffpreset files?
Everything 1.5 will have a textplaincontent: search.
-
- Posts: 3
- Joined: Fri May 26, 2023 6:30 am
Re: The "content" command does not search specific files.
This worked perfectly! I didn't know, it's not on the command list. Thank you so much!
I don't know. I only know that it can be opened with notepad and edited as a plane text: open, edit and save. FFDShow (decoder) imports it without problems.Do you know the text encoding of the ffpreset files?
It would be great. This is one of the most useful PC programs I've used in years. Congratulations!Everything 1.5 will have a textplaincontent: search.
Re: The "content" command does not search specific files.
Do you know the text encoding of the ffpreset files?
*.ffpreset unicodecontent:"need"
Looks like it must be UnicodeThis worked perfectly! I didn't know, it's not on the command list. Thank you so much!