First I cannot find files when I use the full path name and the path name contains a & (ampersand) character. When I replace the affected directory by a *, I can generally find files.
Second, I have 4 files on my hard disk with the name ScanIdentRaw.txt in different folders located below above described folders. The file name length is long, but below 220 chars.
The files are found when I use ScanIdent*Raw.txt but they are not found when I use ScanIdentRaw.txt.
I do not have Regex enabled, so I assume normal DOS wildcard behaviour.
I will try to attach screenshots.
Problem with *
Re: Problem with *
Here are three attachments. One shows that there are 4 files on my hard disk. The search term is the longest serach term I figured out which will still show the files.
The other two screenshots show: when I add one more character in the affected directory, no files are found any more.
The other two screenshots show: when I add one more character in the affected directory, no files are found any more.
- Attachments
-
- An additional Space also finds nothing
- Additional Space find nothing.png (16.46 KiB) Viewed 8467 times
-
- An additional D finds nothing
- Additional D find nothing.png (16.31 KiB) Viewed 8467 times
-
- Screenshot of search result finding 4 files
- Find 4 files.png (28.53 KiB) Viewed 8467 times
Re: Problem with *
This attachment shows: when I remove the Star in the file name, no files are found any more, although there is no additional character in the file name.
- Attachments
-
- Removing the star finds nothing
- Remove Star find nothing.png (16.25 KiB) Viewed 8467 times
Re: Problem with *
As a start, a '?' (question mark) is an invalid filename character in Windows.
(It may not even be an actual (question mark) but rather just a representation of something else.)
(It may not even be an actual (question mark) but rather just a representation of something else.)
"Use any character in the current code page for a name, including Unicode characters and characters in the extended character set (128–255), except for the following:
* The following reserved characters:
o < (less than)
o > (greater than)
o : (colon)
o " (double quote)
o / (forward slash)
o \ (backslash)
o | (vertical bar or pipe)
o ? (question mark)
o * (asterisk)" ...
http://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx
Re: Problem with *
(And while we're here, is Everything restricted to the ~260 character path/filename length limits or is it able to run wild - ~32K ?)
Re: Problem with *
Include your search in double quotes to include the spaces.
With out the spaces the search would be:
E:\Projects\MM\fdtCONTAINER\trunk\Research\Scanning\Profibus\TestResults\Schneider\master AND *1.0.23.0\DTM___Se_MasterPrmDtm.DTMCore\ScanIdentRaw.txt
With spaces:
With out the spaces the search would be:
E:\Projects\MM\fdtCONTAINER\trunk\Research\Scanning\Profibus\TestResults\Schneider\master AND *1.0.23.0\DTM___Se_MasterPrmDtm.DTMCore\ScanIdentRaw.txt
With spaces:
Code: Select all
"E:\Projects\MM\fdtCONTAINER\trunk\Research\Scanning\Profibus\TestResults\Schneider\master *1.0.23.0\DTM___Se_MasterPrmDtm.DTMCore\ScanIdentRaw.txt"
"Everything" has the same limit as Windows, that is 32000 characters.(And while we're here, is Everything restricted to the ~260 character path/filename length limits or is it able to run wild - ~32K ?)
Re: Problem with *
Ok, it's not a bug. First, I agree for the quotes.
The solution of the required second * is that the files reside in different directories. [...] does not match the file name, it matches a part of the directory (which also starts with ScanIdent) and a part of the file name. The correct search term would have been [...], where [...] is the replacement for the long beginning of the search term, * matches any subdirectory and ScanIdentRaw.txt matches the file name.
Anyway, I found the files with Everything. Thank you for the great tool.
@therube: Maybe ? is a invalid character for Windows, but it isn't for NTFS. I didn't really understand how that comment is related to my question.
The solution of the required second * is that the files reside in different directories. [...]
Code: Select all
ScanIdent*Raw.txt
Code: Select all
\*\ScanIdentRaw.txt
Anyway, I found the files with Everything. Thank you for the great tool.
@therube: Maybe ? is a invalid character for Windows, but it isn't for NTFS. I didn't really understand how that comment is related to my question.
Re: Problem with *
You're right, what was I thinking ?I didn't really understand how that comment is related to my question.
When I read your post, & you said, "contains a & (ampersand) character", my mind automatically converted that to a '?' (question mark), & that is why I posted what I did. And that does not apply at all .
The & is a valid character, the ? is not. (Though it is possible to get an ? character or something that "displays" as an ?, most often when archive files are extracted from a foreign OS.)