Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.comp.os.windows-10 > #181532 > unrolled thread
| Started by | Steve Hayes <hayesstw@telkomsa.net> |
|---|---|
| First post | 2025-01-18 20:06 +0200 |
| Last post | 2025-01-20 14:09 -0500 |
| Articles | 20 on this page of 54 — 22 participants |
Back to article view | Back to alt.comp.os.windows-10
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
Page 1 of 3 [1] 2 3 Next page →
| From | Steve Hayes <hayesstw@telkomsa.net> |
|---|---|
| Date | 2025-01-18 20:06 +0200 |
| Subject | Searching for files |
| Message-ID | <btqnoj56t1kndgg64ou8eafr1qc79im11f@4ax.com> |
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 saved 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. It suggested CoPilot could help, and after a long question and answer session suggested I go to the folder where the file was and search for it there, which was exactly where I had started -- it wasn't there, it was somewhere else. Eventually I called it up in the program I'd saved it from and saved it to a flash drive from there, but surely there must be a simpler way to find a file. -- Steve Hayes from Tshwane, South Africa Web: http://www.khanya.org.za/stevesig.htm Blog: http://khanya.wordpress.com E-mail - see web page, or parse: shayes at dunelm full stop org full stop uk
[toc] | [next] | [standalone]
| From | D <noreply@mixmin.net> |
|---|---|
| Date | 2025-01-18 18:47 +0000 |
| Message-ID | <20250118.184728.11f3ea16@mixmin.net> |
| In reply to | #181532 |
On Sat, 18 Jan 2025 20:06:00 +0200, 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 saved 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. >It suggested CoPilot could help, and after a long question and answer >session suggested I go to the folder where the file was and search for >it there, which was exactly where I had started -- it wasn't there, it >was somewhere else. >Eventually I called it up in the program I'd saved it from and saved >it to a flash drive from there, but surely there must be a simpler way >to find a file. been using agent ransack since xp days . . . https://www.mythicsoft.com/agentransack/
[toc] | [prev] | [next] | [standalone]
| From | Steve Hayes <hayesstw@telkomsa.net> |
|---|---|
| Date | 2025-01-20 08:32 +0200 |
| Message-ID | <uarroj1gvc5eep1h0en78li5m80e52f197@4ax.com> |
| In reply to | #181533 |
On Sat, 18 Jan 2025 18:47:28 +0000, D <noreply@mixmin.net> wrote: >On Sat, 18 Jan 2025 20:06:00 +0200, 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 saved 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. >>It suggested CoPilot could help, and after a long question and answer >>session suggested I go to the folder where the file was and search for >>it there, which was exactly where I had started -- it wasn't there, it >>was somewhere else. >>Eventually I called it up in the program I'd saved it from and saved >>it to a flash drive from there, but surely there must be a simpler way >>to find a file. > >been using agent ransack since xp days . . . > >https://www.mythicsoft.com/agentransack/ Yes, I might have to instal that. But when the operating system disables basic operations that it used to include, and wastes one's time with stpid bells and whistles, one starts looking for pirate versions of the old ones that did work. -- Steve Hayes from Tshwane, South Africa Web: http://www.khanya.org.za/stevesig.htm Blog: http://khanya.wordpress.com E-mail - see web page, or parse: shayes at dunelm full stop org full stop uk
[toc] | [prev] | [next] | [standalone]
| From | Paul <nospam@needed.invalid> |
|---|---|
| Date | 2025-01-20 04:45 -0500 |
| Message-ID | <vml5vi$31f7d$1@dont-email.me> |
| In reply to | #181590 |
On Mon, 1/20/2025 1:32 AM, Steve Hayes wrote:
> On Sat, 18 Jan 2025 18:47:28 +0000, D <noreply@mixmin.net> wrote:
>
>> On Sat, 18 Jan 2025 20:06:00 +0200, 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 saved 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.
>>> It suggested CoPilot could help, and after a long question and answer
>>> session suggested I go to the folder where the file was and search for
>>> it there, which was exactly where I had started -- it wasn't there, it
>>> was somewhere else.
>>> Eventually I called it up in the program I'd saved it from and saved
>>> it to a flash drive from there, but surely there must be a simpler way
>>> to find a file.
>>
>> been using agent ransack since xp days . . .
>>
>> https://www.mythicsoft.com/agentransack/
>
> Yes, I might have to instal that.
>
> But when the operating system disables basic operations that it used
> to include, and wastes one's time with stpid bells and whistles, one
> starts looking for pirate versions of the old ones that did work.
There are a multitude of search boxes in W10/W11. It's a minefield in fact :-)
For example:
In the Start Menu Box at top "Search for Apps"
In Settings box top left "Find a setting"
In Installed Apps Box at top "Search Apps"
File Explorer Box top right "(file search)" <=== Ding! Ding! Ding!
...
Navigate to the part of the file system you wish to search.
For example, click "Downloads" folder on the left, and then enter
filename:MyNotes
If that does not work, try
filename:*MyNotes*
and a few more items might show up.
[Picture]
https://i.postimg.cc/hvGfhzTF/File-Explorer-Search-W10.gif
Paul
[toc] | [prev] | [next] | [standalone]
| From | D <noreply@mixmin.net> |
|---|---|
| Date | 2025-01-20 13:19 +0000 |
| Message-ID | <20250120.131944.4ea6eaa0@mixmin.net> |
| In reply to | #181590 |
On Mon, 20 Jan 2025 08:32:39 +0200, Steve Hayes <hayesstw@telkomsa.net> wrote: >On Sat, 18 Jan 2025 18:47:28 +0000, D <noreply@mixmin.net> wrote: >>On Sat, 18 Jan 2025 20:06:00 +0200, 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 saved 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. >>>It suggested CoPilot could help, and after a long question and answer >>>session suggested I go to the folder where the file was and search for >>>it there, which was exactly where I had started -- it wasn't there, it >>>was somewhere else. >>>Eventually I called it up in the program I'd saved it from and saved >>>it to a flash drive from there, but surely there must be a simpler way >>>to find a file. >> >>been using agent ransack since xp days . . . >> >>https://www.mythicsoft.com/agentransack/ > >Yes, I might have to instal that. > >But when the operating system disables basic operations that it used >to include, and wastes one's time with stpid bells and whistles, one >starts looking for pirate versions of the old ones that did work. fortunately for the little guy, there are many freeware programs to choose from, some of which are very popular ... agent ransack is one of them
[toc] | [prev] | [next] | [standalone]
| From | Newyana2 <newyana@invalid.nospam> |
|---|---|
| Date | 2025-01-20 08:45 -0500 |
| Message-ID | <vmljvf$35s9u$1@dont-email.me> |
| In reply to | #181590 |
On 1/20/2025 1:32 AM, Steve Hayes wrote:
>> been using agent ransack since xp days . . .
>>
>> https://www.mythicsoft.com/agentransack/
>
> Yes, I might have to instal that.
>
> But when the operating system disables basic operations that it used
> to include, and wastes one's time with stpid bells and whistles, one
> starts looking for pirate versions of the old ones that did work.
>
I don't remember a time when Windows search was worth
trying. Today they're trying to turn it into a shopping helper,
but I started using Agent Ransack with XP, too. I did it because
Windows search was undependable and couldn't look inside
CAB files. CAB files, a Microsoft standard format, contain a
file list in plain text. It wasn't unusual to install some kind of
hardware and have Windows tell me it needs xyz.dll, which I
would then search the install CABs to find. But as I recall, even
the file search was shit (and came with that annoying puppy
cartoon).
I never tried Windows search again. It's one of the first things
I disable/remove, along with indexing. I don't need a feeble,
useless tool wasting SSD writes. And Win10 search wastes a
ridiculous amount of resources, even when it's not doing anything.
I also came across a clever little ditty to stop that. After removing
the Search bar, turning off the service, etc, there's still a search
process taking some 200MB RAM for no reason. If you kill it,
Background Tasks service starts it up again! If you disable BT then
things don't go well at all. I ended up with Windows "strobing". I
had to get into the Registry in between dark cycles to re-enable
BT and reboot.
(I got adventurous when I first tried installing
Win10, figuring that I could afford to mess it up in the interest of
science because I made disk images and was still in early tweaking
mode. It was still a long way from being a usable system. So there
was little to lose if I screwed up. I kind of wish now that I'd got more
adventurous. The amount of crap in Win10/11 is amazing. The amount
of obfuscation is amazing. Just look at the folder path to the
SearchApp. SystemApps is about 200MB. Does any of it deserve to
live? That's hard to know. I expect I can do without the
"PeopleExeprienceHost" and dozens of other things, but I had to
stop digging sometime.)
The following, run as a BAT file, kills search, then immediately
renames the folder. So when BT tries to restart it, it's gone. :)
taskkill /f /im SearchApp.exe
timeout /T 1
move %windir%\SystemApps\Microsoft.Windows.Search_cw5n1h2txyewy
%windir%\SystemApps\Microsoft.Windows.Search_cw5n1h2txyewy.old
(The last bit starting with move is all one line.)
[toc] | [prev] | [next] | [standalone]
| From | "Allan Higdon" <allanh@vivaldi.net> |
|---|---|
| Date | 2025-01-20 09:29 -0600 |
| Message-ID | <op.20oinivz1svx94@office-pc.attlocal.net> |
| In reply to | #181603 |
On Mon, 20 Jan 2025 07:45:01 -0600, Newyana2 <newyana@invalid.nospam> wrote: > I don't remember a time when Windows search was worth > trying. Today they're trying to turn it into a shopping helper, > but I started using Agent Ransack with XP, too. I did it because > Windows search was undependable and couldn't look inside > CAB files. CAB files, a Microsoft standard format, contain a > file list in plain text. It wasn't unusual to install some kind of > hardware and have Windows tell me it needs xyz.dll, which I > would then search the install CABs to find. But as I recall, even > the file search was shit (and came with that annoying puppy > cartoon). > > I never tried Windows search again. It's one of the first things > I disable/remove, along with indexing. I don't need a feeble, > useless tool wasting SSD writes. And Win10 search wastes a > ridiculous amount of resources, even when it's not doing anything. > > I also came across a clever little ditty to stop that. After removing > the Search bar, turning off the service, etc, there's still a search > process taking some 200MB RAM for no reason. If you kill it, > Background Tasks service starts it up again! If you disable BT then > things don't go well at all. I ended up with Windows "strobing". I > had to get into the Registry in between dark cycles to re-enable > BT and reboot. > > (I got adventurous when I first tried installing > Win10, figuring that I could afford to mess it up in the interest of > science because I made disk images and was still in early tweaking > mode. It was still a long way from being a usable system. So there > was little to lose if I screwed up. I kind of wish now that I'd got more > adventurous. The amount of crap in Win10/11 is amazing. The amount > of obfuscation is amazing. Just look at the folder path to the > SearchApp. SystemApps is about 200MB. Does any of it deserve to > live? That's hard to know. I expect I can do without the > "PeopleExeprienceHost" and dozens of other things, but I had to > stop digging sometime.) > > The following, run as a BAT file, kills search, then immediately > renames the folder. So when BT tries to restart it, it's gone. :) > > taskkill /f /im SearchApp.exe > timeout /T 1 > move %windir%\SystemApps\Microsoft.Windows.Search_cw5n1h2txyewy > %windir%\SystemApps\Microsoft.Windows.Search_cw5n1h2txyewy.old > > (The last bit starting with move is all one line.) > I appreciate the BAT file to kill the Search App. My problem has been that the Windows Search Service didn't always remain disabled. In the past, I had the same problem with the Device Management WAP Push message Routing Service. Back then, Paul posted the command to delete that service, so I decided to do the same with the Windows Search Service.
[toc] | [prev] | [next] | [standalone]
| From | Newyana2 <newyana@invalid.nospam> |
|---|---|
| Date | 2025-01-20 13:33 -0500 |
| Message-ID | <vmm4sq$3bf64$1@dont-email.me> |
| In reply to | #181609 |
On 1/20/2025 10:29 AM, Allan Higdon wrote: > > My problem has been that the Windows Search Service didn't always remain > disabled. > In the past, I had the same problem with the Device Management WAP Push > message Routing Service. > Back then, Paul posted the command to delete that service, so I decided > to do the same with the Windows Search Service. I think that I must have always had search disabled. I don't remember it getting re-enabled, but I did notice that Background Tasks Infrastructure would restart it. I'm teempted to just delete the folder it's in, but I don't understand the details well enough to start weeding systemapps. I haven't heard of deleting services, though I suppose maybe one could just delete the Registry key? I have noticed an odd thing over time. It seems that not all services in the Registry show in the complete list in the Services window. And things sometimes disappear.
[toc] | [prev] | [next] | [standalone]
| From | "Allan Higdon" <allanh@vivaldi.net> |
|---|---|
| Date | 2025-01-20 14:01 -0600 |
| Message-ID | <op.20ou75d01svx94@office-pc.attlocal.net> |
| In reply to | #181612 |
On Mon, 20 Jan 2025 12:33:44 -0600, Newyana2 <newyana@invalid.nospam> wrote: > On 1/20/2025 10:29 AM, Allan Higdon wrote: > >> >> My problem has been that the Windows Search Service didn't always remain >> disabled. >> In the past, I had the same problem with the Device Management WAP Push >> message Routing Service. >> Back then, Paul posted the command to delete that service, so I decided >> to do the same with the Windows Search Service. > > I think that I must have always had search disabled. I don't > remember it getting re-enabled, but I did notice that Background > Tasks Infrastructure would restart it. I'm teempted to just delete > the folder it's in, but I don't understand the details well enough > to start weeding systemapps. > > I haven't heard of deleting services, though I suppose maybe > one could just delete the Registry key? I have noticed an odd > thing over time. It seems that not all services in the Registry > show in the complete list in the Services window. And things > sometimes disappear. > Deleting the Registry key may work just as well. The command I use is "sc delete WSearch". I've also noticed that there are more services in the Registry than in the Services window. I don't recall anything disappearing.
[toc] | [prev] | [next] | [standalone]
| From | Paul <nospam@needed.invalid> |
|---|---|
| Date | 2025-01-20 15:45 -0500 |
| Message-ID | <vmmclf$3e1sr$1@dont-email.me> |
| In reply to | #181609 |
On Mon, 1/20/2025 10:29 AM, Allan Higdon wrote: > On Mon, 20 Jan 2025 07:45:01 -0600, Newyana2 <newyana@invalid.nospam> wrote: > >> I don't remember a time when Windows search was worth >> trying. Today they're trying to turn it into a shopping helper, >> but I started using Agent Ransack with XP, too. I did it because >> Windows search was undependable and couldn't look inside >> CAB files. CAB files, a Microsoft standard format, contain a >> file list in plain text. It wasn't unusual to install some kind of >> hardware and have Windows tell me it needs xyz.dll, which I >> would then search the install CABs to find. But as I recall, even >> the file search was shit (and came with that annoying puppy >> cartoon). >> >> I never tried Windows search again. It's one of the first things >> I disable/remove, along with indexing. I don't need a feeble, >> useless tool wasting SSD writes. And Win10 search wastes a >> ridiculous amount of resources, even when it's not doing anything. >> >> I also came across a clever little ditty to stop that. After removing >> the Search bar, turning off the service, etc, there's still a search >> process taking some 200MB RAM for no reason. If you kill it, >> Background Tasks service starts it up again! If you disable BT then >> things don't go well at all. I ended up with Windows "strobing". I >> had to get into the Registry in between dark cycles to re-enable >> BT and reboot. >> >> (I got adventurous when I first tried installing >> Win10, figuring that I could afford to mess it up in the interest of >> science because I made disk images and was still in early tweaking >> mode. It was still a long way from being a usable system. So there >> was little to lose if I screwed up. I kind of wish now that I'd got more >> adventurous. The amount of crap in Win10/11 is amazing. The amount >> of obfuscation is amazing. Just look at the folder path to the >> SearchApp. SystemApps is about 200MB. Does any of it deserve to >> live? That's hard to know. I expect I can do without the >> "PeopleExeprienceHost" and dozens of other things, but I had to >> stop digging sometime.) >> >> The following, run as a BAT file, kills search, then immediately >> renames the folder. So when BT tries to restart it, it's gone. :) >> >> taskkill /f /im SearchApp.exe >> timeout /T 1 >> move %windir%\SystemApps\Microsoft.Windows.Search_cw5n1h2txyewy >> %windir%\SystemApps\Microsoft.Windows.Search_cw5n1h2txyewy.old >> >> (The last bit starting with move is all one line.) >> > > I appreciate the BAT file to kill the Search App. > > My problem has been that the Windows Search Service didn't always remain disabled. > In the past, I had the same problem with the Device Management WAP Push message Routing Service. > Back then, Paul posted the command to delete that service, so I decided to do the same with the Windows Search Service. If you do your file searches within File Explorer, I don't see a reason for shopping results to show up. Shopping results show up, when you consult all the search boxes located elsewhere in the OS. A search box on the Task bar, sounds like an excellent place for shopping searches :-) Paul
[toc] | [prev] | [next] | [standalone]
| From | Newyana2 <newyana@invalid.nospam> |
|---|---|
| Date | 2025-01-18 13:56 -0500 |
| Message-ID | <vmgtfj$12ejq$2@dont-email.me> |
| In reply to | #181532 |
On 1/18/2025 1:06 PM, Steve Hayes 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 saved 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.
>
> It suggested CoPilot could help, and after a long question and answer
> session suggested I go to the folder where the file was and search for
> it there, which was exactly where I had started -- it wasn't there, it
> was somewhere else.
>
> Eventually I called it up in the program I'd saved it from and saved
> it to a flash drive from there, but surely there must be a simpler way
> to find a file.
>
>
I like Agent Ransack. Removing Windows Search is one of the first
things I do on 10/11.
[toc] | [prev] | [next] | [standalone]
| From | Michael Logies <logies@t-online.de> |
|---|---|
| Date | 2025-01-18 19:58 +0100 |
| Message-ID | <tbunojd6lsp95th6r1m92iugen4sepm39d@4ax.com> |
| In reply to | #181532 |
I use Copernic, https://copernic.com/en/, and an old X1 (x1.com)
[toc] | [prev] | [next] | [standalone]
| From | Nil <rednoise9@rednoise9.invalid> |
|---|---|
| Date | 2025-01-18 14:01 -0500 |
| Message-ID | <XnsB26B8EB19A3F7nilch1@wheedledeedle.moc> |
| In reply to | #181532 |
On 18 Jan 2025, Steve Hayes <hayesstw@telkomsa.net> wrote in alt.comp.os.windows-10: > 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 saved 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. > > It suggested CoPilot could help, and after a long question and > answer session suggested I go to the folder where the file was and > search for it there, which was exactly where I had started -- it > wasn't there, it was somewhere else. > > Eventually I called it up in the program I'd saved it from and > saved it to a flash drive from there, but surely there must be a > simpler way to find a file. I use Voidtools Everything search for finding files by file name, which is 99% of my searches. It returns results almost instantaneously. It's maybe my most-used utility. https://www.voidtools.com/ For the few times I need to find a file by content, I use Agent Ransack. Works very well, but searches can take a long time, since it has to examine within each file. https://www.mythicsoft.com/agentransack/ I never use Window's built-in search or Copilot.
[toc] | [prev] | [next] | [standalone]
| From | VanguardLH <V@nguard.LH> |
|---|---|
| Date | 2025-01-19 00:50 -0600 |
| Message-ID | <osopxccqhr3.dlg@v.nguard.lh> |
| In reply to | #181537 |
Nil <rednoise9@rednoise9.invalid> wrote: > On 18 Jan 2025, Steve Hayes <hayesstw@telkomsa.net> wrote in > alt.comp.os.windows-10: > >> 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 saved 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. >> >> It suggested CoPilot could help, and after a long question and >> answer session suggested I go to the folder where the file was and >> search for it there, which was exactly where I had started -- it >> wasn't there, it was somewhere else. >> >> Eventually I called it up in the program I'd saved it from and >> saved it to a flash drive from there, but surely there must be a >> simpler way to find a file. > > I use Voidtools Everything search for finding files by file name, which > is 99% of my searches. It returns results almost instantaneously. It's > maybe my most-used utility. > > https://www.voidtools.com/ > > For the few times I need to find a file by content, I use Agent > Ransack. Works very well, but searches can take a long time, since it > has to examine within each file. > > https://www.mythicsoft.com/agentransack/ > > I never use Window's built-in search or Copilot. [Search] Everything can also search within files by using its Search -> Advanced Search menu. That way, you only need 1 tool instead of 2.
[toc] | [prev] | [next] | [standalone]
| From | Steve Hayes <hayesstw@telkomsa.net> |
|---|---|
| Date | 2025-01-20 08:34 +0200 |
| Message-ID | <nirrojds6epjmpma2sd4cbhq0850ir6sbq@4ax.com> |
| In reply to | #181567 |
On Sun, 19 Jan 2025 00:50:29 -0600, VanguardLH <V@nguard.LH> wrote: >Nil <rednoise9@rednoise9.invalid> wrote: > >> On 18 Jan 2025, Steve Hayes <hayesstw@telkomsa.net> wrote in >> alt.comp.os.windows-10: >> >>> 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 saved 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. >>> >>> It suggested CoPilot could help, and after a long question and >>> answer session suggested I go to the folder where the file was and >>> search for it there, which was exactly where I had started -- it >>> wasn't there, it was somewhere else. >>> >>> Eventually I called it up in the program I'd saved it from and >>> saved it to a flash drive from there, but surely there must be a >>> simpler way to find a file. >> >> I use Voidtools Everything search for finding files by file name, which >> is 99% of my searches. It returns results almost instantaneously. It's >> maybe my most-used utility. >> >> https://www.voidtools.com/ >> >> For the few times I need to find a file by content, I use Agent >> Ransack. Works very well, but searches can take a long time, since it >> has to examine within each file. >> >> https://www.mythicsoft.com/agentransack/ >> >> I never use Window's built-in search or Copilot. > >[Search] Everything can also search within files by using its Search -> >Advanced Search menu. That way, you only need 1 tool instead of 2. How, when it can't even search for file names and goes straight to Bing? -- Steve Hayes from Tshwane, South Africa Web: http://www.khanya.org.za/stevesig.htm Blog: http://khanya.wordpress.com E-mail - see web page, or parse: shayes at dunelm full stop org full stop uk
[toc] | [prev] | [next] | [standalone]
| From | VanguardLH <V@nguard.LH> |
|---|---|
| Date | 2025-01-20 06:16 -0600 |
| Message-ID | <oxufciswbfpc.dlg@v.nguard.lh> |
| In reply to | #181591 |
Steve Hayes <hayesstw@telkomsa.net> wrote: > VanguardLH <V@nguard.LH> wrote: > >> Nil <rednoise9@rednoise9.invalid> 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 use Voidtools Everything search for finding files by file name, >>> which is 99% of my searches. It returns results almost >>> instantaneously. It's maybe my most-used utility. >>> >>> For the few times I need to find a file by content, I use Agent >>> Ransack. >> >> [Search] Everything can also search within files by using its Search >> -> Advanced Search menu. > > How, when it can't even search for file names and goes straight to > Bing? voidtools [Search] Everything does NOT use any online search engine. It performs only local searches. Not sure why you went off on a tangent claiming Everything uses some online search engine. Maybe you meant to reply to someone else. Also, if you know regex (regular expression), you can enable regex to allow you to more accurately define the filter on what to search. DOS wildcarding is inaccurate. regex allows far superior filtering, but you need to know PCRE (Perl Core Regular Expressions). There are online tutorials to learn regex. I didn't sit down studying regex to know it all. I just started doing a little bit at a time, wanted to do something that I would hunt online to see how to do it, and acquired some expertise. However, seems that no matter how much of regex that I learn, there is still a TON more that I could learn, but the effort would be a diminishing return on little-used expressions.
[toc] | [prev] | [next] | [standalone]
| From | Nil <rednoise9@rednoise9.invalid> |
|---|---|
| Date | 2025-01-22 19:57 -0500 |
| Message-ID | <XnsB26FCAFE872Fnilch1@wheedledeedle.moc> |
| In reply to | #181591 |
On 20 Jan 2025, Steve Hayes <hayesstw@telkomsa.net> wrote in alt.comp.os.windows-10: > On Sun, 19 Jan 2025 00:50:29 -0600, VanguardLH <V@nguard.LH> > wrote: >> >>[Search] Everything can also search within files by using its >>Search -> Advanced Search menu. That way, you only need 1 tool >>instead of 2. > How, when it can't even search for file names and goes straight to > Bing? It doesn't do that. If Everything takes you to Bing on a search, you've got some major system problems.
[toc] | [prev] | [next] | [standalone]
| From | Paul <nospam@needed.invalid> |
|---|---|
| Date | 2025-01-22 23:49 -0500 |
| Message-ID | <vmshpc$1fvdq$1@dont-email.me> |
| In reply to | #181661 |
On Wed, 1/22/2025 7:57 PM, Nil wrote:
> On 20 Jan 2025, Steve Hayes <hayesstw@telkomsa.net> wrote in
> alt.comp.os.windows-10:
>
>> On Sun, 19 Jan 2025 00:50:29 -0600, VanguardLH <V@nguard.LH>
>> wrote:
>>>
>>> [Search] Everything can also search within files by using its
>>> Search -> Advanced Search menu. That way, you only need 1 tool
>>> instead of 2.
>
>> How, when it can't even search for file names and goes straight to
>> Bing?
>
> It doesn't do that. If Everything takes you to Bing on a search, you've
> got some major system problems.
>
Name: Everything64.exe
Size: 4,772,872 bytes (4661 KiB)
SHA256: EAC349E0A4625A95ADAFB4997B2E42E3AF4D78D982395B3E6B199DFC7D5C5096
Product version: 1.5.0.1339a
*******
Administrator Command Prompt
cd /d %userprofile% # Switch to user home
cd Downloads # Get our Everything executable in Downloads
# When Everything64.exe runs, the prompt comes back immediately,
# but the disk light is jammed on and running.
# Wait for the disk light to stop, or check Task Manager for activity.
.\Everything64.exe -create-filelist every_c.txt "C:"
notepad every_c.txt # Comma separated list of filenames
No Bing/MSEdge/CoPilot in there :-)
This is a one line sample of a file entry, with column titles for reference.
Filename Size Date Modified Date Created Attributes
-------- ---- ------------- ------------ ----------
"C:\Users\paul\Downloads\Everything64.exe",4772872,133222580240000000,133231673612469126,8224
D:\>filetime 133222580240000000
1D94D3B 1B442400
03/02/2023 14:13:44.000
D:\>filetime 133231673612469126
1D95580 52808386
03/13/2023 03:49:21.246
Paul
[toc] | [prev] | [next] | [standalone]
| From | Steve Hayes <hayesstw@telkomsa.net> |
|---|---|
| Date | 2025-02-21 03:18 +0200 |
| Message-ID | <trkfrjtkrg41tdman0ohd0997slj4t6gbf@4ax.com> |
| In reply to | #181661 |
On Wed, 22 Jan 2025 19:57:18 -0500, Nil <rednoise9@rednoise9.invalid> wrote: >On 20 Jan 2025, Steve Hayes <hayesstw@telkomsa.net> wrote in >alt.comp.os.windows-10: > >> On Sun, 19 Jan 2025 00:50:29 -0600, VanguardLH <V@nguard.LH> >> wrote: >>> >>>[Search] Everything can also search within files by using its >>>Search -> Advanced Search menu. That way, you only need 1 tool >>>instead of 2. > >> How, when it can't even search for file names and goes straight to >> Bing? > >It doesn't do that. If Everything takes you to Bing on a search, you've >got some major system problems. My need to search for files was that I saved something in an editor program (RoughDraft) and didn't know where it had put it, when I wanted to copy it to a USB flash drive to put on another computer. Eventually found where it had put the file: in c:\system32 It seems a very strange place to store data files. -- Steve Hayes from Tshwane, South Africa Web: http://www.khanya.org.za/stevesig.htm Blog: http://khanya.wordpress.com E-mail - see web page, or parse: shayes at dunelm full stop org full stop uk
[toc] | [prev] | [next] | [standalone]
| From | Nil <rednoise9@rednoise9.invalid> |
|---|---|
| Date | 2025-02-24 13:50 -0500 |
| Message-ID | <XnsB2908CDE17679nilch1@wheedledeedle.moc> |
| In reply to | #182443 |
On 20 Feb 2025, Steve Hayes <hayesstw@telkomsa.net> wrote in alt.comp.os.windows-10: > My need to search for files was that I saved something in an > editor program (RoughDraft) and didn't know where it had put it, > when I wanted to copy it to a USB flash drive to put on another > computer. > > Eventually found where it had put the file: in c:\system32 > > It seems a very strange place to store data files. That is very strange. That location is protected by the OS and normally will force you to explicitly give administrator permission to save/move/copy/delete files there. User programs shouldn't suggest saving files anywhere near there.
[toc] | [prev] | [next] | [standalone]
Page 1 of 3 [1] 2 3 Next page →
Back to top | Article view | alt.comp.os.windows-10
csiph-web