command prompt DIR with wildcard returns unexpected results

Posted by Don Dickinson on Server Fault See other posts from Server Fault or by Don Dickinson
Published on 2011-02-03T14:54:44Z Indexed on 2011/02/03 15:27 UTC
Read the original article Hit count: 296

Filed under:

command-line

I am running 2003 server (latest service pack). When i type this on the command line:

dir 2010*

or

 dir 2010*.*

i receive this as the result:

    02/01/2011  02:34 PM             2,460 2011-02-01-14-34-23-807.mdn  
    02/02/2011  08:59 AM             3,757 2011-02-02-08-59-32-604.req  
    02/01/2011  09:16 AM               235 2011-02-01-09-16-35-104.dat  
    02/02/2011  05:06 PM               460 2011-02-02-17-06-05-166.log  
    02/01/2011  03:31 PM            66,570 2011-02-01-15-31-27-838.dat  
    02/01/2011  03:16 PM               145 2011-02-01-15-16-51-135.log  
    02/01/2011  08:52 PM         1,608,916 2011-02-01-20-52-57-416.req
                   7 File(s)      1,682,543 bytes  
                   0 Dir(s)  42,891,452,416 bytes free

can anyone tell me why? i was expecting to see a list of only files that begin with "2010". there are no such files in the directory, so i wasn't expecting to see anything. i must either misunderstand how DIR handles wildcards or i'm doing something stupid.

Related posts about command-line

WMI permissions: Select CommandLine, ProcessId FROM Win32_Process returns no data for CommandLine

as seen on Server Fault - Search for 'Server Fault'
Hi all, I am gathering performance data via WMI and would like to avoid having to use an account in the Administrators group for this purpose. The target machine is running Windows Server 2003 with the latest SP/updates. I've done what I believe to be the appropriate configuration to allow our user… >>> More
WMI permissions: Select CommandLine, ProcessId FROM Win32_Process returns no data for CommandLine

as seen on Server Fault - Search for 'Server Fault'
I am gathering performance data via WMI and would like to avoid having to use an account in the Administrators group for this purpose. The target machine is running Windows Server 2003 with the latest SP/updates. I've done what I believe to be the appropriate configuration to allow our user access… >>> More
Java 1.5 Command Line Password Masking

as seen on Stack Overflow - Search for 'Stack Overflow'
All, Our server is running Java 1.5 and I am having difficulty trying to mask user input from the command line. I am executing a jar file (java -jar my.jar) and am working through command line prompts via printlns. I cannot use Java Console. Thanks >>> More
Modifying AD Schema permissions from the command line

as seen on Geeks with Blogs - Search for 'Geeks with Blogs'
Recently while making some changes for a client, I accidently dug myself into a pretty deep hole. I was trying to explicitly deny a certain user from reading a few group policies including the Default Domain Policy. When I went in to make the change I accidently denied Authenticated Users rather… >>> More
Ask the Readers: Do You Use the Command Line?

as seen on How to geek - Search for 'How to geek'
Most people have heard of it but not everyone is familiar or comfortable with how to use this bastion of geekdom. This week we would like to know if you use the command line or not. The command line…the bastion of ultimate geekery in many peoples’ eyes. You often hear people referring to doing… >>> More

Developer IT

command prompt DIR with wildcard returns unexpected results - Developer IT

command prompt DIR with wildcard returns unexpected results

command-line

Related posts about command-line

WMI permissions: Select CommandLine, ProcessId FROM Win32_Process returns no data for CommandLine

WMI permissions: Select CommandLine, ProcessId FROM Win32_Process returns no data for CommandLine

Java 1.5 Command Line Password Masking

Modifying AD Schema permissions from the command line

Ask the Readers: Do You Use the Command Line?

Categories cloud