This doesn't exactly fall into the category of "earth shattering", but I do find it quite odd and unexpected, and the question is whether there is something going on here I didn't expect and don't understand or is this a strange bug of some kind? And the issue can be illustrated quite simply and completely by the following: Code: Mon Jan 9, 2012 1:38:10p ISO8601 plugin v1.1.1 loaded. SafeChars plugin v1.5.7 loaded. TCC 12.11.76 Windows 7 [Version 6.1.7601] Copyright 2011 Rex Conn & JP Software Inc. All Rights Reserved Registered to Daniel Mathews [Z:\]W: [W:\]dir /K /M /H 12/26/2011 11:38 852 AAAAAAAA AAAA AAAA.txt 1/08/2012 20:43 113,505 BBBBBBBBBBBBB.txt 1/08/2012 22:40 11,121 CCCCCCCCCCCCCCCCCCC+1.txt 1/08/2012 22:36 3,738 DDDDDDDDDDDDDDDDDDDD+1.txt 1/08/2012 22:45 66,707 EEEEEEEEEEEEEEEEEEEEEEEE+1.txt 1/08/2012 23:38 201,271 FFFFFFFFFFFFFFFFF.txt 1/08/2012 14:17 552,304 GGGGGGGGGGGGGGGGGGGG.txt 1/08/2012 15:00 1,344 HHHHHHHHHHHHHHHHHHHH.btm 1/08/2012 22:59 595 ProduceFinalSongNames.btm 1/09/2012 13:36 466 Sample.btm [W:\]dir *1.* /K /M /H 12/26/2011 11:38 852 AAAAAAAA AAAA AAAA.txt 1/08/2012 20:43 113,505 BBBBBBBBBBBBB.txt 1/08/2012 22:40 11,121 CCCCCCCCCCCCCCCCCCC+1.txt 1/08/2012 22:36 3,738 DDDDDDDDDDDDDDDDDDDD+1.txt 1/08/2012 22:45 66,707 EEEEEEEEEEEEEEEEEEEEEEEE+1.txt 1/08/2012 23:38 201,271 FFFFFFFFFFFFFFFFF.txt 1/08/2012 14:17 552,304 GGGGGGGGGGGGGGGGGGGG.txt 1/08/2012 15:00 1,344 HHHHHHHHHHHHHHHHHHHH.btm [W:\] I don't think I have to spend a lot of time pointing out that the files that are displayed (all of them, actually) do not match the "pattern". 'Nough said.
Go to OPTION and turn off "Search for SFNs". Otherwise, DIR will match both the LFN and the SFN (which usually has a trailing '1' in the filename). As usual, this is for compatibility with CMD.
Thank you, Rex!!! Since I don't (and haven't for many years) use SFN's at all, that is a completely expected result of their existence (in hindsight, of course! ).
