cd md rd:DIRS;
NTFS always keeps files in alphabetical order.Filename completion options being discussed in this thread have nothing to do with DIR sort order.
That being said, I too notice that *dir /o:u still seems to sort everything alphabetically on my system. Not sure if that's a functional change in the operating system APIs (I'm running on Windows 7) or what.
Filename / directory completion is always in the order the file system returns them (alphabetic on an NTFS drives; other file systems will vary). There is no sorting option.I read the topic above, and my problem is that no matter what I do, I can't get my folders to appear in the unsorted order I want. I am looking at a network share to which I have mapped a drive, u:. When I enter dir u: /o:u, it always ends up with "VESTA Map" before VESTA. (I want VESTA completed first.) I've tried creating a new folder that lists after VESTA and then moving all of the contents of "VESTA Map" into that new folder, then deleting "VESTA Map" and finally renaming the new folder to "VESTA Map", and all of a sudden, dir u: /o:u lists "VESTA Map" first again.
Am I doing something wrong? Or is there some way to force its completion to go in alphabetical order (since a regular dir lists VESTA first)?
Ah. Personally I'm glad for this, and it probably means I no longer have to put DIRCMD=/O to get default sorting in cmd.exe any more! I had been doing that since MS-DOS 6...thru Windows 9x..etc.NTFS always keeps files in alphabetical order.