Just a few more explanations and thoughts on these three issues:

> > 1. In FMode, Unsorted files are now displaying in Creation Date,
> > Ascending, Path (on) sequence, rather than as they were correctly
> > displayed in v202 in Name, Ascending, Path (on) sequence for NTFS, and
> > FAT-table entry, Path (on) sequence for FAT32 (the default unsorted
> > sequence for both).

To me this is the most important Unsorted issue. I maintain a small FAT32 partition for directories into which I use a BAT script to copy files so they always appear in a particular order. This has worked perfectly since XTree until ZTree v2.4.203. ZTree is now sorting those files into Creation Date sequence, rather than the order they were written and appear in the FAT directory. Consequently I now have to revert to v2.4.202 to display and ZIP them into the order I prefer.

As it correctly did in v2.4.202 and earlier, Unsorted should display files in the same order as the simple DIR command does for both FAT and NTFS volumes, without any sorting.

> > 2. In FMode Unsorted BSG windows, changing any of the following
> > settings: Path, Order, Charset, F8, F9, or eXit, in any direction,
> > displays the files in Path (off) sequence. Upon exit to the DW and back
> > to the FW, the files are re-displayed in Path (on) sequence.

This bug is easy to reproduce, so needs no further explanation.

> > 3. In DMode, Unsorted directories are being displayed sorted into
> > Creation Date, Ascending, Path (off) sequence. In NTFS the default is
> > Name, Ascending, Path (on), and in FAT32 it's FAT-table entry, Path (on)
> > sequence (the same as for files).

> These are seemingly simple problems to fix, but there is a fundamental
> issue with supporting DMode consistently, because there is no current
> tracking of the order directories are read from disk (while there is for
> files).
> ...
> So while 'unsorted' should literally mean don't sort, I have no
> option but to do so with directories, and by creation-date seemed the
> most logical, as it would in theory be the order in which they were
> written to (a FAT) drive, which seems more 'unsorted' than to sort by
> name.

OK, without a method of tracking the true directory sequence, I think DMode Unsorted should list the directories in Tree sequence if possible, with subdirectories immediately following their parents. This is not the same as either Path (on) or (off), and is a sequence I'd find useful. I think this might be the more expected sequence when unsorted.

> I guess I can check the partition type and do creation-date for FAT and
> Name for NTFS...

No need to do that. I suggest displaying them in Tree sequence for both NTFS and FAT.

- John