Date: Wed, 9 May 2001 13:29:18 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: JT Williams <jeffw AT darwin DOT sfbr DOT org>
cc: djgpp-workers AT delorie DOT com
Subject: Re: DJGPP 2.04 release date
In-Reply-To: <20010508142430.N23521@kendall.sfbr.org>
Message-ID: <Pine.SUN.3.91.1010509132856.19857O-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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
Precedence: bulk


On Tue, 8 May 2001, JT Williams wrote:

> It generates a 48-bit CRC for the LFN and uses that
> for the SFN---so instead of MICROS~1 you get a SFN that has characters
> from the upper 128 of the current character set.

I hope this is done only for the second long file name whose
truncation to 8+3 limits clashes with an existing file.  The first
occurence of a truncated file name should be left intact.

In other words, if none of the long names clash after truncation to
8+3, their short names should not be munged in any way, they should be
simple truncations to 8+3.

If this is not so, I expect a lot of problems with this TSR.