delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/2000/03/01/08:29:26

X-Authentication-Warning: acp3bf.physik.rwth-aachen.de: broeker owned process doing -bs
Date: Wed, 1 Mar 2000 13:25:14 +0100 (MET)
From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
X-Sender: broeker AT acp3bf
To: djgpp-workers AT delorie DOT com
Subject: Re: short file names when using LFN
In-Reply-To: <38BC0F27.25F413BF@teleline.es>
Message-ID: <Pine.LNX.4.10.10003011319090.10912-100000@acp3bf>
MIME-Version: 1.0
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by delorie.com id HAA12889
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

On Tue, 29 Feb 2000, Mariano Alvarez Fernández wrote:

[... getting the SFN of a file, given the LFN ...]
> Now, I only need the put routine :-) I'm playing with a crazy idea:

You want the routine that lets you set the SFN, by hand, for an exiting
file. There is no such thing, and no safe way to write one without
circumventing Windows.

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. That's the only way I see, short of
replacing Windows' own LFN driver, or the hard disk driver, you'll get
that done. It's also the way tools like DOSLFNBK work, AFAIK.

Windows doesn't give you control over directory contents (FCB functions
are forbidden, with a reason), so you can't do this from inside it.

Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019