Searching in Win7 is not better than Vista


Recommended Posts

Searching in Win7 seems to work even worse than in Vista

Suppose I search for a file named ABC, but only remmember BC

Win7 cannot find it !!

Even if I search ABC , Win7 will return a list with lots of irrelevant results !

So I will have to pick out the gem from the garbage.

From my experience, 7's search has been a lot better.

Say I have 2 files. One named "thisisatest.txt", the other "This is a test.txt" with both having the text "Will this work?"

1. Search for "this" and both files will show.

2. Search for "test" and only "This is a test.txt" will show.

3. Search for "work" and both files will show.

Works as expected, and provides accurate results. Now, do you know why "thisisatest.txt" was not included in the results of test #2? It won't look for words embedded within a word, but it will look for results starting with the search term. Which is why test #1 was able to find both files and not #2. Sure, it could look within a word, but most people look for the beginning of the file name. So, search works in the same way.

Troll is fail troll.

You have to set up indexing before 7 can do anything with it's searching.

Um, no setup is required.

Troll is fail troll.

You have to set up indexing before 7 can do anything with it's searching.

Nope, not at all. Search does not require indexing, that's just a feature that makes searching faster. Instead of calling him a troll, how about answering his actual question?

The actual answer is that if you want to search for partial words, you have to use a star. Type in *BC and it will find 123ABCDE.

Nope, not at all. Search does not require indexing, that's just a feature that makes searching faster. Instead of calling him a troll, how about answering his actual question?

The actual answer is that if you want to search for partial words, you have to use a star. Type in *BC and it will find 123ABCDE.

+1 to using wildcards. Totally forgot about that.

Nope, not at all. Search does not require indexing, that's just a feature that makes searching faster. Instead of calling him a troll, how about answering his actual question?

The actual answer is that if you want to search for partial words, you have to use a star. Type in *BC and it will find 123ABCDE.

There's just something suspicious about one post wonders coming in here with a wild rant about some new software. The rant doesn't contain a question in any form and seems like just another microsoft bash. Now if he really came in here expecting an answer to his "question" than I apologize. But something tells me we will never hear of this latabar again. If we do, he needs to learn some manners ;)

There's just something suspicious about one post wonders coming in here with a wild rant about some new software. The rant doesn't contain a question in any form and seems like just another microsoft bash. Now if he really came in here expecting an answer to his "question" than I apologize. But something tells me we will never hear of this latabar again. If we do, he needs to learn some manners ;)

Well I read it as someone whose first language is probably not English being upset about the search not working as one might expect and wondering how to make it go. It's not an unreasonable complaint, as I think most people would expect it to do partial word matches by default. Now he knows how to do it and everyone is presumably happy.

since this thread is about searching, how do I search through hidden files and folders? in windows xp you can just select that option but in windows 7 its nowhere to be seen.

From explorer click Organize >> Folder and Search Options

post-8011-1258456038_thumb.jpg

Nope, not at all. Search does not require indexing, that's just a feature that makes searching faster. Instead of calling him a troll, how about answering his actual question?

The actual answer is that if you want to search for partial words, you have to use a star. Type in *BC and it will find 123ABCDE.

+1 but the the search should work without the wildcard and it has worked for me.... I will test it when i get back home....

+1 but the the search should work without the wildcard and it has worked for me.... I will test it when i get back home....

If you don't use wildcards then it will only match the beginning of words. In other words, 123 will match the file Xyz 123.jpg or Xyz_123.jpg, but not Xyz123.jpg. It's somewhat confusing.

OK sir, that worked.

But what if I want to search only file names ? or only content ?

By the way: is there a button so I quickly can find my topics immediately on entering this site ? or perhaps get a message on my mail ?

From my experience, 7's search has been a lot better.

Say I have 2 files. One named "thisisatest.txt", the other "This is a test.txt" with both having the text "Will this work?"

1. Search for "this" and both files will show.

2. Search for "test" and only "This is a test.txt" will show.

3. Search for "work" and both files will show.

Works as expected, and provides accurate results. Now, do you know why "thisisatest.txt" was not included in the results of test #2? It won't look for words embedded within a word, but it will look for results starting with the search term. Which is why test #1 was able to find both files and not #2. Sure, it could look within a word, but most people look for the beginning of the file name. So, search works in the same way.

Um, no setup is required.

OK sir, that worked.

But what if I want to search only file names ? or only content ?

By the way: is there a button so I quickly can find my topics immediately on entering this site ? or perhaps get a message on my mail ?

You should already get e-mails of replies to your topic or posts.

Anyway, here's a list of search syntax's you might find handy: http://www.microsoft.com/windows/products/...s/advquery.mspx

Search in Win 7 is much better than Vista.

Does anyone know though if you can search network drives on Win 7 without installing that UNCsomething patch in Vista (to be able to automatically search in mapped network drives)?

+1 but the the search should work without the wildcard and it has worked for me.... I will test it when i get back home....

Search does prefix matching by default. This is far and away the most common design for fairly obvious reasons. Google and everyone else does the same thing. You don't want a search for "rum" to return a hit against the word "forum." The signal-to-noise ratio becomes just appalling. Plus we return results as you type, so you're usually searching against the first few letters of the word or phrase you're typing.

If there is a word breaking character like a space, hyphen, period, etc - then of course you can match against the beginning of the next word.

Search in Win 7 is much better than Vista.

Does anyone know though if you can search network drives on Win 7 without installing that UNCsomething patch in Vista (to be able to automatically search in mapped network drives)?

You can search them using the normal "grep" (i.e. slow) search if they aren't indexed. If they are indexed on the server side, Windows 7 (and Vista) will use the remote machine's index automatically.

Why can I not find a file or subfolder under say e.g. AppData even if I've turned on hidden and system files and checked "Include subfolders in search results..."??, "Include system dirs and compressed files" I had to check "Dont use the index when searching in file folders for system files" for it to find non-indexed files properly. Indexed search is great. Real time search is a total disaster and definitely slower to the search in XP and sometimes ends up without finding files (I think especially if they are several folder levels deep). And even after dozens of complaints that we need a more comprehensive UI for building advanced searches, Windows 7 comes along and removes the advanced Vista UI and moves bits and portions of it to a search box dropdown. We need a separate classic fast real time search as well like this and sadly Windows Search doesn't live up to the real-time part since it tries to do indexed and non-indexed simultaneously which makes it slow.

So wait, you want them to show up when searching but not when browsing?

Generally "hidden files" are files you don't want to see, like random configuration or log files, temporary files, etc. What are you trying to use them for that the current show/hide option doesn't enable?

Searching in Win7 seems to work even worse than in Vista

Suppose I search for a file named ABC, but only remmember BC

Win7 cannot find it !!

Even if I search ABC , Win7 will return a list with lots of irrelevant results !

So I will have to pick out the gem from the garbage.

troll force is weak with in this one

Why can I not find a file or subfolder under say e.g. AppData even if I've turned on hidden and system files and checked "Include subfolders in search results..."??, "Include system dirs and compressed files" I had to check "Dont use the index when searching in file folders for system files" for it to find non-indexed files properly. Indexed search is great. Real time search is a total disaster and definitely slower to the search in XP and sometimes ends up without finding files (I think especially if they are several folder levels deep). And even after dozens of complaints that we need a more comprehensive UI for building advanced searches, Windows 7 comes along and removes the advanced Vista UI and moves bits and portions of it to a search box dropdown. We need a separate classic fast real time search as well like this and sadly Windows Search doesn't live up to the real-time part since it tries to do indexed and non-indexed simultaneously which makes it slow.

This and also remove the nagger "this drive is not indexed plz index it" thing. It is annoying.

Classic Search is best feature that M$ removed >:(

This and also remove the nagger "this drive is not indexed plz index it" thing. It is annoying.

So, you'd rather a user wonder why searches are fast in one folder, and slow in others? Sounds like a good idea to me! :rolleyes: Please, next time you have a thought, let it go.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft's fast coding model MAI-Code-1-Flash comes to Copilot Business and Enterprise by Karthik Mudaliar Microsoft’s recently announced MAI-Code-1-Flash model is now generally available to GitHub Copilot Business and Copilot Enterprise customers. With this support, organizations can have more centralized policy controls and billing while finally being able to use Microsoft’s lightweight, first-party coding model. According to GitHub’s announcement, Business and Enterprise plan administrators must enable the MAI-Code-1-Flash policy in Copilot settings before developers can access the model. Microsoft says that MAI-Code-1-Flash is for fast, iterative coding work rather than the most demanding architectural or debugging tasks. GitHub’s official model comparison page says that the model is great for "general-purpose coding and writing," while it excels at fast, accurate code completions and explanations Microsoft introduced MAI-Code-1-Flash on June 2 as part of a broader collection of internally developed MAI models. GitHub subsequently expanded support to Copilot CLI, the Copilot cloud agent, GitHub.com chat, GitHub Mobile, Visual Studio, JetBrains IDEs, Eclipse, and Xcode, but said support for managed Business and Enterprise customers was still on the way. In Microsoft’s own benchmark testing, MAI-Code-1-Flash scored 51.2% on SWE-Bench Pro, compared with 35.2% for Anthropic’s Claude Haiku 4.5. Microsoft also claimed that the model used up to 60% fewer tokens on SWE-Bench Verified. Do note that these are vendor-run results rather than independent measurements. The model is billed at provider list pricing under GitHub’s usage-based system. GitHub currently lists MAI-Code-1-Flash at $0.75 per million input tokens, $0.075 per million cached input tokens, and $4.50 per million output tokens. For organizations, the main incentive to use MAI-Code-1-Flash is likely to be efficiency rather than maximum capability. A smaller model that responds quickly and limits unnecessary output is quite useful for repetitive agent tasks at scale, especially after GitHub Copilot’s move toward usage-based billing. The "Flash" model is recommended for fast work and not necessarily for huge repositories with loads of context. It's better if teams compare their output with other larger models, especially if they're working on security-sensitive changes and complex, multi-file work.
    • yes AND no the "original" or plain/normal Optiplex 7010 won't be getting any more new firmware updates BUT the Optiplex SFF/SFF Plus {small form factor}, Micro/Micro Plus & Tower/Tower Plus 7010 editions DO get new updates such as this new one   and here are similar guides from the Dell web site for Dell systems: https://www.dell.com/support/kbdoc/en-us/000390990/secure-boot-transition-faq https://www.dell.com/support/kbdoc/en-us/000347876/microsoft-2011-secure-boot-certificate-expiration
    • AT&T has been spying on US citizens with the NSA for decades.. they just know how to keep it more under wraps.. the evil level is still there.
  • Recent Achievements

    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
    • Week One Done
      tuben earned a badge
      Week One Done
    • First Post
      OffsetAbs earned a badge
      First Post
    • Reacting Well
      OffsetAbs earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      443
    2. 2
      +Edouard
      200
    3. 3
      PsYcHoKiLLa
      155
    4. 4
      FloatingFatMan
      71
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!