home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   ECHOLIST      [ADM] EchoList Access Conference      11,388 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 11,047 of 11,388   
   address@not.available to All   
   Explorer filename sorting problem - NoSt   
   31 Jan 19 19:14:19   
   
   Path:   
   eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!g   
   oblin3!goblin1!goblin.stu.neva.ru!uio.no!news.tele.dk!news.tele.dk!small.news.t   
   ele.dk!newsgate.cistron.nl!newsgate.news.xs4all.nl!nzpost1.xs4all.net!not-for-m   
   ail   
   From: "R.Wieser"    
   Newsgroups: microsoft.public.windowsxp.help_and_support   
   Subject: Explorer filename sorting problem - NoStrCmpLogical already present   
   Date: Sat, 26 Mar 2016 19:58:23 +0100   
   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: 29   
   Message-ID: <56f6db6e$0$5900$e4fe514c@news.xs4all.nl>   
   NNTP-Posting-Host: 83.163.119.5   
   X-Trace: 1459018606 news.xs4all.nl 5900 83.163.119.5:4993   
   X-Complaints-To: abuse@xs4all.nl   
   Xref: mx02.eternal-september.org   
   microsoft.public.windowsxp.help_and_support:31821   
      
   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   
      
      
   --- Platinum Xpress/Win/WINServer v3.1   
    * Origin: Prison Board BBS Mesquite Tx  //telnet.RDFIG.NET www. (1:124/5013)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca