"You may have sorted by another column. Sort by "search ranking", and file name matches will be prioritized (if there are any) over any content matches. I'm not suggesting anyone memorize anything. I've never ever had to type a syntaxed query. I click buttons
just like in XP. Windows 7 works like a search engine. You type a keyword, you get results. You don't tell Google to only search contents sometimes, do you? "
Not really directed at Shawn Keene, but he has brought up some of the issues that are most pertinent:
File Search should NOT function like a search engine. I have never in my life needed a file search to behave in that way.
With a search engine, I start knowing what kind of information that I am looking for but not where or what form that I might find it: a fuzzy search. If I get too much, or the wrong things, I refine my keywords and retry until I get what I want, which is
a previously unknown information source.
With a file system search, I want an exact and complete list based on the criteria I put forth. I know the kind of information and I know where and the form I will find it in. It should not be a fuzzy search.
Windows 7 search uses keywords with your defined location and then makes some choices on what you will or will not get back based on non-obvious controls. It is a semi-fuzzy search. And worse, how to make it less fuzzy is not clear, obvious or well-documented:
- You have to make global changes to include hidden files.
- You have to make global changes to toggle searching of subfolders.
- You have to know about indexing, update it, and apparently define the extensions you want to search if it is outside what Microsoft defined. If it isn't in a library and have an accepted extension, too bad. But don't index your whole machine.
- You have to know or "guess" at the names of filters to get what you could do in XP. Some would think that the non-technical should have *no* problem guessing those even when the technical do. I still haven't guessed what would filter: "A word or phrase
in the file", "search system folders", "search hidden files and folders", "search subfolders", or "case sensitive". I could look it up on the msdn list that someone posted, which says that this non-obvious, poorly documented.
- You have to search your search. Sure it prioritizes based on what you asked for first. But when you column sort your results it loses those priorities, and all the **** you didn't ask for gets mixed in. Sure if you get 3 million results and it is #3 that
is great, but if it is #30,000, not so much. And if you were looking for a group, or a number, or have any reason to column sort, it has no value.
These are not things your average user is going to know how to do, and will never figure out.
Assuming that people only work at their designated customized machine which they fully understand is not reality. A file search should work the same on every machine, no matter what folder you start in.
The two biggest issues I have (providing support) are searching hidden/system areas and getting a complete search. All the extra filters would be nice, but if I can't get the search to be complete, it is a non-starter. And having to go into each system to
set it up to search the way I need it to, kind of says that it is broken.
I still haven't seen how to (or even heard anyone claim that you can) hidden and system files and folders in a search (without by playing with global settings). I can supposedly see hidden and system files on my own machine, yet I have come across folders
I can see from a program's default save location, and from dos, but I can't get explorer to see it until I explicitly type it in the address bar. Do you think search will find it? Nope.
Folders on the server occasionally get accidentally moved. Where did they go? Search by folder name, not anymore (at least without going and tweaking something somewhere else in the system). Searching under windows 7, I can search on a file I just created
and not find it. I can search on a file I can see and not get it as a result. Why? I'm still trying to figure it out.
Despite what the Microsoft engineers think, their code in the search does not know why I am conducting the search, so shouldn't be making changes and assumptions that I do not know about. Am I looking for a file, or seeing how many files are have my criteria?
Am I just trying to get a quick idea of how much space is taken up in certain directories by certain types of files? Too bad for me with Windows 7 search. If I say *.doc, I want *.doc, not *.doc*. If I wanted *.docx, I would enter *.doc*. There may be a switch
or setting that would turn this off, but why should that be needed? Designing it for someone who has no knowledge (always assuming wildcards) is painful for those who have even a modicum of knowledge. If you are concerned about people not understanding wildcards,
put in a link on "how to search" that covers the basics, like wildcards.
Just the number of experienced people who raise the issue should say something. And despite what someone on here keeps saying, the answer that "well it really is more powerful, and there are 300 options which I figured out by trial and error, see how smart
I am, I did it, and everyone should be exactly like me" is the same sort of horrible logic used to make these changes in the first place. How hard would it have been to have something like the search in XP, either as a button in the search, or just have the
XP search as the default with a box where you could put in you 300 filters to your heart's content? And maybe a link to a listing of those 300 filters and what they do. It is like Microsoft has a split personality. Half is dumbed down to those with no knowledge
of computers, the other half is made to be semi or fully scripted, with no help, no documentation and only forums to try to ferret out how to use them. The tools are less and less useful for the 98% in the middle.
Microsoft is relying more and more on the user community to provide documentation, they barely even try anymore. Most of the time, F1 help searches bounce to the internet to provide answers from here there and everywhere. Yes you can control it, but if you
don't, that's where it goes. And if search was the only issue like this with MS products, it probably wouldn't be a big deal, but it is one of many. Ribbons; can't have 4 or more network shortcuts on the desktop; defaulting apps to not have the menu bar; deprecated
functions in office, the windows orb instead doesn't say start (yes, this is a real problem when people don't see "start"), etc., etc., etc. I am in an office where we are migrating from XP to W7. I have been hit with more of these kind of obvious productivity
killers than I have seen advantages of W7. The only productivity boost the people I support have seen comes from the hardware being better on new machines. They their computers to do their jobs, which is what should be expected. W7 is not designed for them.