Date: Sun, 30 Jan 2000 09:51:16 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: salvador <salvador AT inti DOT gov DOT ar>
cc: djgpp AT delorie DOT com
Subject: Re: Rhide, NT and LFN - some news
In-Reply-To: <389196AB.75F4F711@inti.gov.ar>
Message-ID: <Pine.SUN.3.91.1000130095057.17273K-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Fri, 28 Jan 2000, salvador wrote:

> Dan Levin wrote:
> 
> > I've been doing some continued work on this problem. I've found that
> > everything works great - IF YOU STICK TO LFN ALL THE TIME when you
> > create files. As soon as you name a file according to the classical DOS
> > 8.3 format in Rhide, you end up with a filename in UPPERCASE.
>
> 1) What's that "fix"? a TSR or something like that?
> 2) I think the problem is in the "fix". RHIDE doesn't make any funky thing with
> names, just uses djgpp's libc. As djgpp's libc works very well under W9x I think
> this "fix" behaves different than W9x LFN API and that's the source of the
> problems.


FWIW, I'm guessing that the emulation of function 71A8h of Int 21h
doesn't work correctly.  The DJGPP library relies on this function to
determine when to downcase the file name it gets from the OS.  (DOS
8+3 file names are stored in the directory in all-upper case.)

For more details, see the source of the function _lfn_gen_short_fname
in the library, and the docs of the _preserve_fncase function in
libc.info.