Date: Thu, 20 Nov 1997 12:12:16 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Andrew Crabtree <andrewc AT rosemail DOT rose DOT hp DOT com>
cc: djgpp-workers AT delorie DOT com
Subject: Re: LFN on NT
In-Reply-To: <01bcf54a$f4ad89d0$45111d0f@ros51675cra.rose.hp.com>
Message-ID: <Pine.SUN.3.91.971120121158.11842H-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Wed, 19 Nov 1997, Andrew Crabtree wrote:

> It is particularly troublesome
> for me now that I have found out that Clearcase (my version control system)
> does not generate short file names at all so that LFN files are
> basically invisible to DJGPP apps.

Does this mean that you have given up on the problem with Clearcase
volume with 8+3 names?  (Read: can I nuke all the mail we exchanged on
the subject and which I'm keeping for future discussions with you?)
Or are you still trying to see the short names at least?

> In the startup code we can detect if we are running under NT or not.  Then,
> if LFN is set in the environment we will
> load in the nt-lfn DLL (this will need to be written).  We will then have to
> have conditional code in most of the lfn and other file routines that either
> call into the DOS LFN api or into the nt-lfn dll depending on whether we are
> under NT or not.

Can't that DLL export the same LFN API that Windows 9X supports?  That
would make libc immediately compatible, with no need to add any code
bloat.  Is there any problem on NT for a DLL to hook Int 21h?

> The big problem with this approach is that it will require a dll to be
> distributed with apps that intend to use LFNs under NT.

Doesn't look like to much of a problem to me.  We already have
emu387.dxe, which is the same problem.