Date: Wed, 1 Mar 2000 16:13:20 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
cc: djgpp-workers AT delorie DOT com
Subject: Re: short file names when using LFN
In-Reply-To: <Pine.LNX.4.10.10003011319090.10912-100000@acp3bf>
Message-ID: <Pine.SUN.3.91.1000301160931.14618A@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 1 Mar 2000, Hans-Bernhard Broeker wrote:

> The only halfway safe method of doing what you want is to do it from raw
> DOS, where no LFN driver is present in the OS. Then use the very
> old-fashioned FCB functions, or maybe even direct disc writes, to modify
> the directory entries by hand to modify the SFN, but make sure you don't
> damage the LFN, while doing that.

Alas, this won't work, either: Windows stores hidden info about the 
file names (checksums etc.) as part of the LFN entry, and when it sees a 
file whose name doesn't fit the checksum, it nukes the long file name.  
So you are left with a short file name only.

Like usual with MS, it's as if they saw in advance every possible way of 
working around their misfeature and carefully sealed off every single one 
of them...