Subj : Re: Explorer filename sorting problem - NoStrCmpLogical already presen
To   : All
From : [email protected]
Date : Thu Jan 31 2019 07:14 pm

Path:
eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!f
eeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed9.news.xs4all.nl!nzpost1.xs4
all.net!not-for-mail
From: "R.Wieser" <[email protected]>
Newsgroups: microsoft.public.windowsxp.help_and_support
References: <[email protected]>
<[email protected]>
Subject: Re: Explorer filename sorting problem - NoStrCmpLogical already
present
Date: Sun, 27 Mar 2016 10:35:50 +0200
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Lines: 59
Message-ID: <[email protected]>
NNTP-Posting-Host: 83.163.119.5
X-Trace: 1459067754 news.xs4all.nl 5824 83.163.119.5:1491
X-Complaints-To: [email protected]
Xref: mx02.eternal-september.org
microsoft.public.windowsxp.help_and_support:31823

JJ,

> NoStrCmpLogical is a policy setting for (Windows) Explorer only.

Than is doubly remarkable that *both* show the same list ....

> CMD is never affected and will always use binary compare for sorting.

Please, don't do that.  You can see for yourself that it doesn't appear to
do so.  :-(

> <https://support.microsoft.com/en-us/kb/319827>

That page seems to have become outdated, as I was met with the (in)famous
"Try searching for what you need. This page doesn't exist." error message.

Regards,
Rudy Wieser


-- Origional message:
JJ <[email protected]> schreef in berichtnieuws
[email protected]...
> On Sat, 26 Mar 2016 19:58:23 +0100, R.Wieser wrote:
> > Hello All,
> >
> > My file explorer seems to have trouble sorting filenames in an intuitive
> > way.  Just look at the below (listing generated using "dir /one 60.*",
but
> > the same order appears in Explorer)
> >
> > 60.00.00.32.dds
> > 60.00.00.32.msh
> > 60.00.00.32.nif
> > 60.00.32.32.dds
> > 60.00.-32.32.dds
> > 60.00.32.32.msh
> > 60.00.-32.32.msh
> > 60.00.32.32.nif
> > 60.00.-32.32.nif
> >
> > I would expect the "60.00.-30.*" entries to come first, followed by the
> > "60.00.00.*" and "60.00.32.*" groups.
> >
> > Some time ago (years probably :-) ) I've added the NoStrCmpLogical
setting,
> > and thought that it was fixed.  But apperantly no such luck.
> >
> > Does anyone know what is going on here -- or better yet, how to fix it ?
> >
> > Regards,
> > Rudy Wieser
>
> NoStrCmpLogical is a policy setting for (Windows) Explorer only.
> CMD is never affected and will always use binary compare for sorting.
>
> <https://support.microsoft.com/en-us/kb/319827>

--- Platinum Xpress/Win/WINServer v3.1
* Origin: Prison Board BBS Mesquite Tx  //telnet.RDFIG.NET www. (1:124/5013)

You are viewing proxied material from cvs.synchro.net. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.