If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#16
|
|||
|
|||
how the blinking heck do I have Search just look a _FILEWW_ names?
VanguardLH on Thu, 3 May 2018 20:11:44 -0500 typed in
alt.windows7.general the following: pyotr filipivich wrote: Stan Brown typed the following: pyotr filipivich wrote: How, or is it even possible, to get Windows to just search for "job" in filenames. dir /s /b C:\*job* That's DOS, i.e. the command line. (I have many copies of _cmdprmt.bat scattered all round the place. For just hat reason.) Windows is not DOS. 'dir' is an internal DOS-mode command (i.e., internal to the command shell program). You run those in a command shell whether it was back in MS/IBM-DOS days or nowadays inside of Windows (which also has a command shell via cmd.exe). You NEVER ran a machine-coded 'dir' program. It is an internal command defined within the command shell. And that is too far into the weeds for my current use. (Last time I coded for the machine level was a Minex Class. Not fun.) -- pyotr filipivich Next month's Panel: Graft - Boon or blessing? |
Ads |
#17
|
|||
|
|||
how the blinking heck do I have Search just look a _FILEWW_ names?
Ron C on Thu, 3 May 2018 19:59:47 -0400 typed in
alt.windows7.general the following: On 5/3/2018 6:59 PM, Char Jackson wrote: On Thu, 3 May 2018 18:36:00 -0400, Stan Brown wrote: On Thu, 3 May 2018 09:50:41 +0100, J. P. Gilliver (John) wrote: In message , Stan Brown writes: On Wed, 02 May 2018 09:04:14 -0700, pyotr filipivich wrote: How, or is it even possible, to get Windows to just search for "job" in filenames. dir /s /b C:\*job* I think he wanted to search for _just_ job, not *job*. [in which case \job.* might work in your suggestion.] Maybe you're right, but he said "in" filenames. You and I agree on the main point, though: this is really easy on the command line. He seems to want to exclude directory (folder) names, so I think an additional parameter might be required: dir /s /b /a-d search_target Damn, don't they ever test these search procedures on the "vast wasteland" of non-computer-geeks? Apparently, the answer is "no". The scary part - the organizational structures these people seem most comfortable, what does that say about their minds? -- pyotr filipivich Next month's Panel: Graft - Boon or blessing? |
#18
|
|||
|
|||
how the blinking heck do I have Search just look a _FILEWW_ names?
On Fri, 04 May 2018 07:30:39 -0700, pyotr filipivich
wrote: VanguardLH on Thu, 3 May 2018 20:11:44 -0500 typed in alt.windows7.general the following: pyotr filipivich wrote: Stan Brown typed the following: pyotr filipivich wrote: How, or is it even possible, to get Windows to just search for "job" in filenames. dir /s /b C:\*job* That's DOS, i.e. the command line. (I have many copies of _cmdprmt.bat scattered all round the place. For just hat reason.) Windows is not DOS. 'dir' is an internal DOS-mode command (i.e., internal to the command shell program). You run those in a command shell whether it was back in MS/IBM-DOS days or nowadays inside of Windows (which also has a command shell via cmd.exe). You NEVER ran a machine-coded 'dir' program. It is an internal command defined within the command shell. And that is too far into the weeds for my current use. (Last time I coded for the machine level was a Minex Class. Not fun.) Coded for the machine level?? Are you still referring to running the dir command at a command prompt? Is that what you're calling coding for the machine level? LOL -- Char Jackson |
#19
|
|||
|
|||
how the blinking heck do I have Search just look a _FILEWW_ names?
On Fri, 04 May 2018 07:30:39 -0700, pyotr filipivich
wrote: Ron C on Thu, 3 May 2018 19:59:47 -0400 typed in alt.windows7.general the following: On 5/3/2018 6:59 PM, Char Jackson wrote: On Thu, 3 May 2018 18:36:00 -0400, Stan Brown wrote: On Thu, 3 May 2018 09:50:41 +0100, J. P. Gilliver (John) wrote: In message , Stan Brown writes: On Wed, 02 May 2018 09:04:14 -0700, pyotr filipivich wrote: How, or is it even possible, to get Windows to just search for "job" in filenames. dir /s /b C:\*job* I think he wanted to search for _just_ job, not *job*. [in which case \job.* might work in your suggestion.] Maybe you're right, but he said "in" filenames. You and I agree on the main point, though: this is really easy on the command line. He seems to want to exclude directory (folder) names, so I think an additional parameter might be required: dir /s /b /a-d search_target Damn, don't they ever test these search procedures on the "vast wasteland" of non-computer-geeks? Apparently, the answer is "no". No, the answer is "yes", at least in my case. I tested it extensively before I posted. The scary part - the organizational structures these people seem most comfortable, what does that say about their minds? Aren't you the guy who had a document that you couldn't find, even though you knew it was named "jobsomething.3le"? That should have been one of the all-time easiest searches. -- Char Jackson |
#20
|
|||
|
|||
how the blinking heck do I have Search just look a _FILEWW_ names?
Char Jackson on Fri, 04 May 2018 10:57:53 -0500
typed in alt.windows7.general the following: On Fri, 04 May 2018 07:30:39 -0700, pyotr filipivich wrote: Ron C on Thu, 3 May 2018 19:59:47 -0400 typed in alt.windows7.general the following: On 5/3/2018 6:59 PM, Char Jackson wrote: On Thu, 3 May 2018 18:36:00 -0400, Stan Brown wrote: On Thu, 3 May 2018 09:50:41 +0100, J. P. Gilliver (John) wrote: In message , Stan Brown writes: On Wed, 02 May 2018 09:04:14 -0700, pyotr filipivich wrote: How, or is it even possible, to get Windows to just search for "job" in filenames. dir /s /b C:\*job* I think he wanted to search for _just_ job, not *job*. [in which case \job.* might work in your suggestion.] Maybe you're right, but he said "in" filenames. You and I agree on the main point, though: this is really easy on the command line. He seems to want to exclude directory (folder) names, so I think an additional parameter might be required: dir /s /b /a-d search_target Damn, don't they ever test these search procedures on the "vast wasteland" of non-computer-geeks? Apparently, the answer is "no". No, the answer is "yes", at least in my case. I tested it extensively before I posted. Yes, you tested it. But did Microsoft? Does Microsoft? The scary part - the organizational structures these people seem most comfortable, what does that say about their minds? Aren't you the guy who had a document that you couldn't find, even though you knew it was named "jobsomething.3le"? That should have been one of the all-time easiest searches. When I got 1049 "hits" on "job" with such relevant files as "Icebreaker Questions.rft" SD-Log01.wpd, "SERVICE BOOK of the Holy Orthodox Catholic Apostolic Church - Hapgood - 1906", _cmdprompt.bat, and 3rd Angle Projection.pdf, plus the ever relevant "6-d.jpg" - let me just say that the last time I had to wade through that many "hits" trying to find the relevant ones, I was doing evidence discovery for a law firm. -- pyotr filipivich Next month's Panel: Graft - Boon or blessing? |
#21
|
|||
|
|||
how the blinking heck do I have Search just look a _FILEWW_ names?
Char Jackson on Fri, 04 May 2018 10:49:37 -0500
typed in alt.windows7.general the following: On Fri, 04 May 2018 07:30:39 -0700, pyotr filipivich wrote: VanguardLH on Thu, 3 May 2018 20:11:44 -0500 typed in alt.windows7.general the following: pyotr filipivich wrote: Stan Brown typed the following: pyotr filipivich wrote: How, or is it even possible, to get Windows to just search for "job" in filenames. dir /s /b C:\*job* That's DOS, i.e. the command line. (I have many copies of _cmdprmt.bat scattered all round the place. For just hat reason.) Windows is not DOS. 'dir' is an internal DOS-mode command (i.e., internal to the command shell program). You run those in a command shell whether it was back in MS/IBM-DOS days or nowadays inside of Windows (which also has a command shell via cmd.exe). You NEVER ran a machine-coded 'dir' program. It is an internal command defined within the command shell. And that is too far into the weeds for my current use. (Last time I coded for the machine level was a Minex Class. Not fun.) Coded for the machine level?? Are you still referring to running the dir command at a command prompt? Is that what you're calling coding for the machine level? LOL No, but do try to keep up. -- pyotr filipivich Next month's Panel: Graft - Boon or blessing? |
#22
|
|||
|
|||
how the blinking heck do I have Search just look a _FILEWW_ names?
On Thu, 03 May 2018 17:59:08 -0500, Char Jackson wrote:
On Thu, 3 May 2018 18:36:00 -0400, Stan Brown wrote: On Thu, 3 May 2018 09:50:41 +0100, J. P. Gilliver (John) wrote: In message , Stan Brown writes: On Wed, 02 May 2018 09:04:14 -0700, pyotr filipivich wrote: How, or is it even possible, to get Windows to just search for "job" in filenames. dir /s /b C:\*job* I think he wanted to search for _just_ job, not *job*. [in which case \job.* might work in your suggestion.] Maybe you're right, but he said "in" filenames. You and I agree on the main point, though: this is really easy on the command line. He seems to want to exclude directory (folder) names, so I think an additional parameter might be required: dir /s /b /a-d search_target Good catch -- thanks! -- Stan Brown, Oak Road Systems, Tompkins County, New York, USA http://BrownMath.com/ http://OakRoadSystems.com/ Shikata ga nai... |
#23
|
|||
|
|||
how the blinking heck do I have Search just look a _FILEWW_ names?
On Thu, 03 May 2018 16:44:18 -0700, pyotr filipivich wrote:
That's DOS, i.e. the command line. You're more than a decade out of date. The command line hasn't been DOS for a long, long time. -- Stan Brown, Oak Road Systems, Tompkins County, New York, USA http://BrownMath.com/ http://OakRoadSystems.com/ Shikata ga nai... |
#24
|
|||
|
|||
how the blinking heck do I have Search just look a _FILEWW_ names?
Stan Brown wrote:
On Thu, 03 May 2018 16:44:18 -0700, pyotr filipivich wrote: That's DOS, i.e. the command line. You're more than a decade out of date. The command line hasn't been DOS for a long, long time. The running process might say "NTVDM". https://en.wikipedia.org/wiki/Virtual_DOS_machine One difference between the Command Prompt and a "real DOS boot-up", is real DOS gives you access to hardware, whereas Command Prompt is insulated. You can't flash the BIOS the normal way from Command Prompt, whereas putting the flasher EXE and flash ROM file on a boot floppy, works. That's part of the difference between the two environments. Command Prompt emulates the traditional commands just fine, and allows you to do a few things. Some softwares, the usage notes will tell you of the difference, and how the software won't work right without "real DOS". Paul |
#25
|
|||
|
|||
how the blinking heck do I have Search just look a _FILEWW_ names?
On Fri, 04 May 2018 16:05:00 -0700, pyotr filipivich
wrote: Char Jackson on Fri, 04 May 2018 10:57:53 -0500 typed in alt.windows7.general the following: On Fri, 04 May 2018 07:30:39 -0700, pyotr filipivich wrote: Ron C on Thu, 3 May 2018 19:59:47 -0400 typed in alt.windows7.general the following: On 5/3/2018 6:59 PM, Char Jackson wrote: On Thu, 3 May 2018 18:36:00 -0400, Stan Brown wrote: On Thu, 3 May 2018 09:50:41 +0100, J. P. Gilliver (John) wrote: In message , Stan Brown writes: On Wed, 02 May 2018 09:04:14 -0700, pyotr filipivich wrote: How, or is it even possible, to get Windows to just search for "job" in filenames. dir /s /b C:\*job* I think he wanted to search for _just_ job, not *job*. [in which case \job.* might work in your suggestion.] Maybe you're right, but he said "in" filenames. You and I agree on the main point, though: this is really easy on the command line. He seems to want to exclude directory (folder) names, so I think an additional parameter might be required: dir /s /b /a-d search_target Damn, don't they ever test these search procedures on the "vast wasteland" of non-computer-geeks? Apparently, the answer is "no". No, the answer is "yes", at least in my case. I tested it extensively before I posted. Yes, you tested it. But did Microsoft? Does Microsoft? The scary part - the organizational structures these people seem most comfortable, what does that say about their minds? Aren't you the guy who had a document that you couldn't find, even though you knew it was named "jobsomething.3le"? That should have been one of the all-time easiest searches. When I got 1049 "hits" on "job" with such relevant files as "Icebreaker Questions.rft" SD-Log01.wpd, "SERVICE BOOK of the Holy Orthodox Catholic Apostolic Church - Hapgood - 1906", _cmdprompt.bat, and 3rd Angle Projection.pdf, plus the ever relevant "6-d.jpg" - let me just say that the last time I had to wade through that many "hits" trying to find the relevant ones, I was doing evidence discovery for a law firm. I don't see "job" in any of those results. My suggestions, FWIW: 1. Pay attention to where you put things so that you don't have to search for them later. 2. Pay attention to how you name things so that your searches can be more effective. 3. You knew what the file extension was, so include that in your search. 4. Learn to use your search tools so that you can avoid another case of not being able to find something on short notice. 5. Windows search is the worst of your available options, so learn to use tools such as Everything and Agent Ransack. Anyway, all's well that ends well, right? You found your document and you lived another day. Another narrow escape. -- Char Jackson |
#26
|
|||
|
|||
how the blinking heck do I have Search just look a _FILEWW_names?
On 5/5/2018 10:34 AM, Char Jackson wrote:
snip My suggestions, FWIW: 1. Pay attention to where you put things so that you don't have to search for them later. 2. Pay attention to how you name things so that your searches can be more effective. 3. You knew what the file extension was, so include that in your search. 4. Learn to use your search tools so that you can avoid another case of not being able to find something on short notice. 5. Windows search is the worst of your available options, so learn to use tools such as Everything and Agent Ransack. Anyway, all's well that ends well, right? You found your document and you lived another day. Another narrow escape. I love Search Everything by voidtools, it's very fast, free, and full-featured. From the FAQ: Type the partial file or folder name into the search edit, the results will appear instantly. AND is the default boolean operator. For example, to search for abc and 123, search for: abc 123 To search for either of two search terms, add a | between the terms. For example, to search for .jpg or .bmp, search for: .jpg | .bmp To exclude something from the search include a ! at the front of the term. For example, to search for everything except abc, search for: !abc To show the basic search syntax in Everything: In "Everything", from the Help menu, click Search syntax. Using a * in your search will match any number of any type of character. For example, here is how to search for files and folders that start with e and end with g: e*g Using a ? in your search will match one character. For example, here is how to search for files that have a 2 letter file extension: *.?? To include spaces in your search enclose your search in double quotes. For example, here is how to search for foospacebar: "foo bar" To search for a file type, type the file extension into the search edit, eg: to search for the mp3 file type, type *.mp3 into the search edit. To search for more than one type of file type use a | to separate file types, eg: *.bmp|*.jpg will search for files with the extension bmp or jpg. To search for files and folders in a specific location include a \ in your search string. For example, here is how to search for all your mp3s in a downloads folder: downloads\ .mp3 You could alternately enable Match Path in the Search menu and include the location in your search string. For example, here is how to search for all your avis in a downloads folder with Match Path enabled: downloads .avi (also has advanced searching) https://www.voidtools.com/faq/ |
#27
|
|||
|
|||
how the blinking heck do I have Search just look a _FILEWW_ names?
In message , Mike S
writes: [] I love Search Everything by voidtools, it's very fast, free, and full- Me too. featured. From the FAQ: Type the partial file or folder name into the search edit, the results will appear instantly. AND is the default boolean operator. For example, to search for abc and 123, search for: abc 123 To search for either of two search terms, add a | between the terms. For example, to search for .jpg or .bmp, search for: .jpg | .bmp (I didn't know about that one.) To exclude something from the search include a ! at the front of the term. For example, to search for everything except abc, search for: !abc (Or that one. Though what happens if you want to search for a filename that starts with !, which can occur, and in fact I often use it to make those files appear at the top?) To show the basic search syntax in Everything: In "Everything", from the Help menu, click Search syntax. Using a * in your search will match any number of any type of Including zero character. For example, here is how to search for files and folders that start with e and end with g: e*g (So including eg itself, Actually, I think e*g will include f&f that contain an e followed by a g _anywhere_ in the name, not just start with e and end with g - e. g. "legs". But I'm not _sure_ about that.) Using a ? in your search will match one character. For example, here is how to search for files that have a 2 letter file extension: *.?? To include spaces in your search enclose your search in double quotes. For example, here is how to search for foospacebar: "foo bar" To search for a file type, type the file extension into the search edit, eg: to search for the mp3 file type, type *.mp3 into the search edit. I think the * is not needed - .mp3 will work. (Their example above explaining the | [OR] operator implies it will!) To search for more than one type of file type use a | to separate file types, eg: *.bmp|*.jpg will search for files with the extension bmp or jpg. Again (and as above!). To search for files and folders in a specific location include a \ in your search string. For example, here is how to search for all your mp3s in a downloads folder: downloads\ .mp3 You could alternately enable Match Path in the Search menu and include the location in your search string. So including "\" is the same as "match path". Interesting. For example, here is how to search for all your avis in a downloads folder with Match Path enabled: downloads .avi (also has advanced searching) https://www.voidtools.com/faq/ Thanks for that. -- J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf Experience is that marvelous thing that enables you to recognize a mistake when you make it again. -Franklin P. Jones |
#28
|
|||
|
|||
how the blinking heck do I have Search just look a _FILEWW_ names?
Char Jackson on Sat, 05 May 2018 12:34:24 -0500
typed in alt.windows7.general the following: When I got 1049 "hits" on "job" with such relevant files as "Icebreaker Questions.rft" SD-Log01.wpd, "SERVICE BOOK of the Holy Orthodox Catholic Apostolic Church - Hapgood - 1906", _cmdprompt.bat, and 3rd Angle Projection.pdf, plus the ever relevant "6-d.jpg" - let me just say that the last time I had to wade through that many "hits" trying to find the relevant ones, I was doing evidence discovery for a law firm. I don't see "job" in any of those results. My suggestions, FWIW: 1. Pay attention to where you put things so that you don't have to search for them later. I did. I've got everything organized by 'category. 2. Pay attention to how you name things so that your searches can be more effective. I knew it was called "Job_Hist" 3. You knew what the file extension was, so include that in your search. Good point. I'll try that. 4. Learn to use your search tools so that you can avoid another case of not being able to find something on short notice. That is a good idea. Unfortunately, "Windows Help" is the anti-program. 5. Windows search is the worst of your available options, so learn to use tools such as Everything and Agent Ransack. Unfortunately, that means I have to go install Yet Another Program. Fnord, I've already installed many programs so I don't have to use MS products. Anyway, all's well that ends well, right? You found your document and you lived another day. Another narrow escape. Narrow, yes, that's one way of putting it. -- pyotr filipivich Next month's Panel: Graft - Boon or blessing? |
#29
|
|||
|
|||
how the blinking heck do I have Search just look a _FILEWW_ names?
Stan Brown on Sat, 5 May 2018 10:09:10
-0400 typed in alt.windows7.general the following: On Thu, 03 May 2018 16:44:18 -0700, pyotr filipivich wrote: That's DOS, i.e. the command line. You're more than a decade out of date. Not surprising, I stopped being computer geek way back in the last century. Like photography, when I stopped having access to a darkroom, I stopped developing my own film and printing my pictures. Might as well switch to color - which I did. The command line hasn't been DOS for a long, long time. Whatever that is called when I run "CMD" - it looks & acts like Ye Olde Command Lynn. -- pyotr filipivich Next month's Panel: Graft - Boon or blessing? |
#30
|
|||
|
|||
how the blinking heck do I have Search just look a _FILEWW_ names?
Paul on Sat, 05 May 2018 12:55:36 -0400 typed
in alt.windows7.general the following: Stan Brown wrote: On Thu, 03 May 2018 16:44:18 -0700, pyotr filipivich wrote: That's DOS, i.e. the command line. You're more than a decade out of date. The command line hasn't been DOS for a long, long time. The running process might say "NTVDM". https://en.wikipedia.org/wiki/Virtual_DOS_machine One difference between the Command Prompt and a "real DOS boot-up", is real DOS gives you access to hardware, whereas Command Prompt is insulated. You can't flash the BIOS the normal way from Command Prompt, whereas putting the flasher EXE and flash ROM file on a boot floppy, works. That's part of the difference between the two environments. There was a time when I could boot from monitor. "Because I could." {Saved my house mate a load of issues when I answered the call for tech support and told them how to do that. Yeah, back before cellphoens, blah, blah. "Back in my day, we only had six bits - not even a full byte!") Command Prompt emulates the traditional commands just fine, and allows you to do a few things. Some softwares, the usage notes will tell you of the difference, and how the software won't work right without "real DOS". Paul -- pyotr filipivich Next month's Panel: Graft - Boon or blessing? |
Thread Tools | |
Display Modes | Rate This Thread |
|
|