Path:
eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!n
ews.albasani.net!.POSTED!not-for-mail
From: JJ 
Newsgroups: microsoft.public.windowsxp.help_and_support
Subject: Re: Explorer filename sorting problem - NoStrCmpLogical already
present
Date: Sun, 27 Mar 2016 20:50:40 +0700
Organization: ?
Lines: 58
Message-ID: 
References: 


Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Trace: news.albasani.net
0r18dtDPDUl9CXmz3XBRmLgUDfSs57XawGGY5pjhW0tSm5vCzZYkN7kRMPpFWJV09iw3+Q12QS2PCGH
QR7AkCw==
NNTP-Posting-Date: Sun, 27 Mar 2016 13:50:30 +0000 (UTC)
Injection-Info: news.albasani.net;
logging-data="AOwPmWFtv//scxBmLz4/wEX4XX0gomrSlXP3QMehaSFyYKQg1grPdtS40/UBJnkJR
sqjHzRK25ecflh6IzMx+hsEFReuOSOE0kkSJkLxG6/PTgM0uM7kcjv9rPT5J+sv";
mail-complaints-to="abuse{at}albasani.net"
User-Agent: 40tude_Dialog/2.0.15.1
X-Face: 
\*\`0(1j~VfYC>ebz[&O.]=,Nm\oRM{of,liRO#7Eqi4|!]!(Gs=Akgh{J)605>C9Air?pa
d{sSZ09u+A7f<^paR"/NH_# 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  schreef in berichtnieuws
> 1f6vwnr37eok9.1jaqewr69jsjg$.dlg{at}40tude.net...
>> 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

See the cached page from Google using below Google search query:

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

Or use web archive.
--- Platinum Xpress/Win/WINServer v3.1