On 8/10/2004 10:26:18 PM, Gary Darsey wrote:
>The command line dir command
>shows the same behavior, which
>I was not aware of (that is,
>searching on the 8.3 filename
>and not the full filename).
I do not believe that this is the case.
The basic problem is the string "*1*."
This is not supported by Windows, although the Microsoft documentation fails to specify exactly what is supported.
You could try their knowledgebase.
Support unfortunately also varies between Windows versions. (You do not specify what you are using.)
The Help in XP, very unhelpfully, contains information about wildcard in DOS "The asterisk (*) wildcard character cannot be placed before a static string in a wildcard search path."
A more reliable way of performing your task in a command window would be:-
dir /b | find "1"
Alternately use the Vedit Dir, then search for lines containing "1"