Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.comp.os.windows-10 > #181582
| From | Paul <nospam@needed.invalid> |
|---|---|
| Newsgroups | alt.comp.os.windows-10 |
| Subject | Re: Searching for files |
| Date | 2025-01-19 15:12 -0500 |
| Organization | A noiseless patient Spider |
| Message-ID | <vmjmbk$2fr8h$1@dont-email.me> (permalink) |
| References | <btqnoj56t1kndgg64ou8eafr1qc79im11f@4ax.com> <vmipq2.4mg.1@ID-201911.user.individual.net> <msaqoj9li2tei2qqb1h8qqslvoidbujci5@4ax.com> <vmjig8$2ebt9$1@dont-email.me> |
On Sun, 1/19/2025 2:06 PM, knuttle wrote:
>
>>> Steve Hayes <hayesstw@telkomsa.net> wrote:
>>>> Is there a way to search for files in Win 10 without being taken on
>>>> long detours by Bing or CoPilot?
>>>>
>>>> I collected a lot of text from the web intio a dile for research, and
>>>> then savedd it.
>>>>
>>>> When I wanted to copy it, it wasn't where I expected it to be.
>>>>
>>>> In Win XP or 7 I can just enter all or part of the file name into a
>>>> search box, and it is found. But in Win 10, but comes Big with useless
>>>> information.
> In Windows 10 you can do basically the same thing that was done in XP,..............
>
> Open the file manager, look on the right end of the location window.
> ie mine currently says ThisPC> Window(C)................
> There is a box that when all of, or part of a name is enter it will search the follder for thattext in then file names.
>
> My search need are minimal and the native search is adequate for my needs.
The Windows Search (as exemplified by the upper-right corner of an Explorer window),
is context sensitive.
If you click "This PC", and then conduct a search, it searches the entire PC.
In my example picture of setting up the search index, if you enable
the index to be built for the entire PC (21 partitions in the example),
then the portion that has been mechanically indexed in advance, returns
a search result soonest.
If you click "This PC" indicating a scope of the "entire PC", and
none of it is indexed, then Explorer trundles through the file system,
and a green progress bar appears in the address area of Explorer,
indicating how far it has searched.
Thus, by not generating an index in advance, it slows the search.
Now, in your case, you may have clicked "Downloads" or "Documents"
as your search context, and the file system descent to check
those, will be faster than a whole PC search. Explorer only has
a short trundle to do, to evaluate your Downloads folder.
Originally, the Search Indexer part of the search subsystem, it
had a tick box indicating "filenames and Contents" or "Only Filenames".
The "Only Filenames" option *never worked*. The thing always
processes the internal contents of files, and especially for
file types with a "provider". Maybe .txt files have a provider,
so they can be searched globally. If it spots .eml files, it
can index the text in those. It can do a text extraction of
the PDFs (or, a commercial tool like Acrobat Reader may be helping,
but we do know that MSEdge has PDF capabilities. Each file type
needs a Provider or otherwise, the content will not be
included in the Index for later. Now that Windows has archive-lib,
it can "see into" more file types, such as .7z archives. It's
not limited to .cab and .zip any more.
If you don't do anything at all to the Search Indexer settings,
chances are its scope never exceeds the C: drive. And at first.
it will index only a tiny part of C: related to your account perhaps.
Later, when files change on disk, whether created, updated, or erased,
only the known context is tracked for what to do. If it is only
indexing Downloads for example, then if a file in Documents is
erased, the indexer doesn't particularly care to do anything,
as the filter mask puts that area off limits.
You can edit the Search Indexer values, and have the indexer consider
more of your disk drive(s). In the example picture I provided, is
my setup that preserves my older files. Maybe 7TB worth of files
in 21 partitions. I entered all 21 partitions (their names are
masked off in the picture and only the first letter of each
volume name is visible in the picture).
[Picture]
https://i.postimg.cc/g0xFD166/windows-indexing-options.gif
When I first set this up, it hardly worked properly at all. I
set it up as a test mainly. Today, after resetting it and having
it regenerating the database a half a dozen times, it performs
reasonably well. It can take 3 to 60 seconds for a search
of the entire machine to complete. Having it set up, means
it does not matter what context I select, whether it is just
the Downloads folder, or it is all 21 partitions of "This PC".
I can have any scope I want, with minimal interference.
By nominating a working directory (TEMP) and excluding it from
the index, as files are added to that TEMP folder, the Search Indexer
ignores those. Thus, the index is always up to date with regard
to my contribution to the behavior of the machine. If it does
Windows Update, some files in those kinds of trees, may get
added or subtracted from the database.
Hardly anybody uses this, and I use it on my Archive Machine to
save time.
I suspect File Locator Pro (the commercial side of Agent Ransack),
may have an Inverted Index as well, but I haven't tested that,
and I don't know if anyone here runs File Locator Pro so we can ask.
Paul
Back to alt.comp.os.windows-10 | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Searching for files Steve Hayes <hayesstw@telkomsa.net> - 2025-01-18 20:06 +0200
Re: Searching for files D <noreply@mixmin.net> - 2025-01-18 18:47 +0000
Re: Searching for files Steve Hayes <hayesstw@telkomsa.net> - 2025-01-20 08:32 +0200
Re: Searching for files Paul <nospam@needed.invalid> - 2025-01-20 04:45 -0500
Re: Searching for files D <noreply@mixmin.net> - 2025-01-20 13:19 +0000
Re: Searching for files Newyana2 <newyana@invalid.nospam> - 2025-01-20 08:45 -0500
Re: Searching for files "Allan Higdon" <allanh@vivaldi.net> - 2025-01-20 09:29 -0600
Re: Searching for files Newyana2 <newyana@invalid.nospam> - 2025-01-20 13:33 -0500
Re: Searching for files "Allan Higdon" <allanh@vivaldi.net> - 2025-01-20 14:01 -0600
Re: Searching for files Paul <nospam@needed.invalid> - 2025-01-20 15:45 -0500
Re: Searching for files Newyana2 <newyana@invalid.nospam> - 2025-01-18 13:56 -0500
Re: Searching for files Michael Logies <logies@t-online.de> - 2025-01-18 19:58 +0100
Re: Searching for files Nil <rednoise9@rednoise9.invalid> - 2025-01-18 14:01 -0500
Re: Searching for files VanguardLH <V@nguard.LH> - 2025-01-19 00:50 -0600
Re: Searching for files Steve Hayes <hayesstw@telkomsa.net> - 2025-01-20 08:34 +0200
Re: Searching for files VanguardLH <V@nguard.LH> - 2025-01-20 06:16 -0600
Re: Searching for files Nil <rednoise9@rednoise9.invalid> - 2025-01-22 19:57 -0500
Re: Searching for files Paul <nospam@needed.invalid> - 2025-01-22 23:49 -0500
Re: Searching for files Steve Hayes <hayesstw@telkomsa.net> - 2025-02-21 03:18 +0200
Re: Searching for files Nil <rednoise9@rednoise9.invalid> - 2025-02-24 13:50 -0500
Re: Searching for files Graham J <nobody@nowhere.co.uk> - 2025-02-24 22:01 +0000
Re: Searching for files Paul <nospam@needed.invalid> - 2025-02-24 18:34 -0500
Re: Searching for files Steve Hayes <hayesstw@telkomsa.net> - 2025-02-25 05:39 +0200
Re: Searching for files GlowingBlueMist <zapbot@truely.invalid> - 2025-02-25 17:16 -0600
Re: Searching for files Steve Hayes <hayesstw@telkomsa.net> - 2025-02-26 10:30 +0200
Re: Searching for files ...w¡ñ§±¤ñ <winstonmvp@gmail.com> - 2025-02-25 11:49 -0700
Re: Searching for files Paul <nospam@needed.invalid> - 2025-02-25 22:39 -0500
Re: Searching for files Steve Hayes <hayesstw@telkomsa.net> - 2025-02-26 06:02 +0200
Re: Searching for files Paul <nospam@needed.invalid> - 2025-02-26 00:32 -0500
Re: Searching for files knuttle <keith_nuttle@yahoo.com> - 2025-01-18 14:30 -0500
Re: Searching for files Hank Rogers <Hank@nospam.invalid> - 2025-01-18 13:49 -0600
Re: Searching for files "R.Wieser" <address@is.invalid> - 2025-01-18 21:39 +0100
Re: Searching for files Herbert Kleebauer <klee@unibwm.de> - 2025-01-18 21:44 +0100
Re: Searching for files Marion <marion@facts.com> - 2025-01-20 03:38 +0000
Re: Searching for files Paul <nospam@needed.invalid> - 2025-01-18 18:00 -0500
Re: Searching for files Anton Shepelev <anton.txt@gmail.moc> - 2025-01-19 02:10 +0300
Re: Searching for files Paul in Houston TX <Paul@Houston.Texas> - 2025-01-18 18:17 -0600
Off-topic: X-No-Archive header (was: Searching for files) VanguardLH <V@nguard.LH> - 2025-01-19 01:00 -0600
Re: Off-topic: X-No-Archive header Marion <marion@facts.com> - 2025-01-20 03:22 +0000
Re: Off-topic: X-No-Archive header "Kerr-Mudd, John" <admin@127.0.0.1> - 2025-01-20 09:13 +0000
Re: Off-topic: X-No-Archive header (was: Searching for files) Steve Hayes <hayesstw@telkomsa.net> - 2025-01-20 09:00 +0200
Re: Off-topic: X-No-Archive header VanguardLH <V@nguard.LH> - 2025-01-20 06:31 -0600
Re: Searching for files wasbit <wasbit@nowhere.com> - 2025-01-19 09:36 +0000
Re: Searching for files Newyana2 <newyana@invalid.nospam> - 2025-01-19 08:29 -0500
Re: Searching for files Michael Logies <logies@t-online.de> - 2025-01-19 17:48 +0100
Re: Searching for files Frank Slootweg <this@ddress.is.invalid> - 2025-01-19 11:05 +0000
Re: Searching for files Paul <nospam@needed.invalid> - 2025-01-19 08:43 -0500
Re: Searching for files Ken Blake <Ken@invalid.news.com> - 2025-01-19 09:43 -0700
Re: Searching for files knuttle <keith_nuttle@yahoo.com> - 2025-01-19 14:06 -0500
Re: Searching for files Paul <nospam@needed.invalid> - 2025-01-19 15:12 -0500
Re: Searching for files Steve Hayes <hayesstw@telkomsa.net> - 2025-01-20 08:57 +0200
Re: Searching for files Paul <nospam@needed.invalid> - 2025-01-20 05:37 -0500
Re: Searching for files Steve Hayes <hayesstw@telkomsa.net> - 2025-01-20 17:50 +0200
Re: Searching for files Paul <nospam@needed.invalid> - 2025-01-20 14:09 -0500
csiph-web