From:	sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id:	<10110121232.AA19039@clio.rice.edu>
Subject:	Re: W2K/XP fncase [was Re: New perl package]
To:	djgpp-workers AT delorie DOT com, eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
Date:	Fri, 12 Oct 2001 07:32:38 -0500 (CDT)
Cc:	tim DOT van DOT holder AT pandora DOT be (Tim Van Holder)
In-Reply-To:	<6137-Fri12Oct2001103925+0200-eliz@is.elta.co.il> from "Eli Zaretskii" at Oct 12, 2001 10:39:25 AM
X-Mailer:	ELM [version 2.5 PL2]
Mime-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> > Was this on a FAT32 or NTFS filesystem (the 'c:' suggests the latter)?
> > Since NTFS does not store a short name, that might make a difference.

Most tests have been on FAT32.

> > Fair enough - after all, the only reason we have FNCASE at all is to
> > avoid seeing DOS names as all-uppercase, right?  And XP users are
> > unlikely to have many FAT32 partitions where that problem could show up.
> 
> I think your assumption is wrong: this isn't related to FAT.  Try
> running `ls' on c:\winnt (or whatever it is called on XP) and its
> subdirectories, and I think you will see lots of UPPER case.

Actually you see some upper case, but most files are stored as all lower.
This is probably why we haven't noticed this until now.

Since I dual boot (and Ghost my disks) I prefer FAT32 to NTFS unless I
need the built in compression on certain directories.

Anyway, I'll look at the short name functions.

- Raw text -