I have a user share mounted as a Network drive within Win7 (Home Premium, 32-bit), i.e. Z:

 

If I enter the command:

 

Z:\> dir /S /OG /ON topdir1

 

I get the top-level dir (topdir1) files/dirs listed in alphabetical order (grouped by directories first), but the ordering of the subsequent subdirs seems to be all over the place (although files within each subdir are also alphabetically sorted & grouped). Perhaps this is due to the physical dispersement of the actual files/dirs across the real (physical) disks??

 

Yet the unRAID server console 'ls -laR /mnt/user/shareXX/topdir1' command yields fully sorted (nested) results properly.

Not only that, but the GnuWin32 'ls' win32 executable also works similarly - from the Win7 DOS command prompt.

 

Does anybody know why my native 'dir' command behaves this way, and if it is possible to construct a 'dir' command to fully alphabetize my listing (i.e. using only native DOS 'dir')?

Hi,

 

You van try to use the command tree  see more using

tree --help

 

For example tree -d -L 3, it goes 3 level directories deep

 

tree -d -L 3 > /boot/shares.txt , save output to a file

interesting

 

the DOS variant of the tree command lists the dirs in the same (seemingly haphazard) order that the DOS dir command ends up recursing them...

 

something tells me I will be better off doing everything in shell-script from the tower itself :-)