Date: Thu, 8 Apr 1999 18:56:57 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Martin Str|mberg <ams AT ludd DOT luth DOT se>
cc: DJGPP-WORKERS <djgpp-workers AT delorie DOT com>
Subject: Re: LFN=y and MS-RAMDRIVE
In-Reply-To: <199904081648.SAA12220@father.ludd.luth.se>
Message-ID: <Pine.SUN.3.91.990408185010.27027O@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Thu, 8 Apr 1999, Martin Str|mberg wrote:

> According to Eli Zaretskii:
> > What does ``_use_lfn ("g:/")'' return?
[snip]
> says
> 
> "0.
> "

Yep, it seems the MS RAM drive doesn't support long file names.  I'd bet 
they simply didn't want to work on the driver to make it LFN-aware.  What 
a joke!

You should be able to change the sources of `sort' to make it call 
_use_lfn on the temp file prefix, instead of using _USE_LFN.  

But personally, I won't recommend using that RAM drive at all, since many
other programs will probably fail in ``interesting'' ways.  DJGPP does not
live well with systems where some drives support LFN while others don't,
since too many library functions call _USE_LFN, and the logic inside
_use_lfn that caches the last drive it was called with isn't perfect...