Damn DOS

[avram]

Can anyone explain this to me?

N:\fake\path\here>dir *bur*
 Volume in drive N is fakevolumename
 Volume Serial Number is 12345678

 Directory of [path deleted]

05/18/2004  02:08p              30,666 TX030_BUR.jpg
04/14/2004  12:44p              36,537 SO129_ECR.jpg
05/18/2004  02:08p              28,059 TX032_BUR.jpg
05/07/2004  02:02p              25,932 FT098_BUR.jpg
05/18/2004  02:08p              28,587 TX031_BUR.jpg
05/13/2004  12:20p              30,084 FT097_BUR.jpg
05/07/2004  02:02p              25,584 FT099_BUR.jpg
               7 File(s)        205,449 bytes
               0 Dir(s)  36,263,952,384 bytes free

Comments

[avram]

This problem isn’t actually causing me any difficulty at work, so I don’t know how much effort I want to take away from what I’m actually supposed to be doing. Still, that glitch could cause me trouble in the future, and it might (as you say) be a symptom of something worse, so if it’s still doing it tomorrow, I’ll bring it to our sysadmin’s attention.

[barking-iguana.livejournal.com]

Related to what's above, iirc, COMMAND.COM has an 8.3 name and cmd.exe has long names. Wht you've got isn't of the form that Windows automatically translates long names to, when making an 8.3 name for a longly named file. But to be sure, I'd open a cmd.exe session and see what's in that directory. If you don't see the same file name, then there's probably an additonal file that has your search string in it and has the name you've seen as it's short name.