Date:	Wed, 1 Mar 2000 12:17:21 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Mariano Alvarez =?iso-8859-1?Q?Fern=E1ndez?= <malfer AT teleline DOT es>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: short file names when using LFN
In-Reply-To:	<38BC0F27.25F413BF@teleline.es>
Message-ID:	<Pine.SUN.3.91.1000301121652.12637M-100000@is>
MIME-Version:	1.0
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 =?iso-8859-1?Q?Fern=E1ndez?= wrote:

>     Searching the Ralph Brown I found the interrupt to get the short
> file name when using LFN. Here is the routine. Really I d'ont know very
> much about the DJGPP internals, so I made the routine modifying the
> "_gen_short_filename" one.

_lfn_gen_short_filename is not meant to do this, it has a different
(and very important) functionality.  Do NOT replace
_lfn_gen_short_filename with this function, or you will see strange
subtle bugs all over the place!

What you seem to want requires a separate function.  You can do the
same today with the following snippet:

     putenv ("LFN=n");
     _truename (long_name, short_name);
     putenv ("LFN=y");

> Now, I only need the put routine :-) I'm playing with a crazy idea:
> do the copy, compare the short filenames
> if they don't match rename the copied file adding .00n
> do another copy and try again
> when the short filenames match, delete the bad copies.

I don't understand what are you trying to accomplish.  Please
explain.

- Raw text -