Xref: news2.mv.net comp.os.msdos.djgpp:1744
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: LFN questions
Date: Thu, 07 Mar 1996 23:01:11 CST
Organization: Rice University, Houston, Texas
Lines: 16
Message-ID: <313fbf17.sandmann@clio.rice.edu>
References: <199603071341 DOT IAA09324 AT mv DOT mv DOT com>
Reply-To: sandmann AT clio DOT rice DOT edu
NNTP-Posting-Host: clio.rice.edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

> DJ informed me that LFN is supported only if you use the LFN=Y option when 
> you compile.

Well, it's supposed to work that way, but it seems I overlooked a detail in
the implementation which causes LFN to always be enabled on W95.  So, if
you have a program which depends on file name truncation to 8.3, you need to
set "SET LFN=n"

> In addition, DJ did not mention the suggestion to modify the registry for 
> LFN as is suggested in the FAQ.

This isn't a requirement.  If you never boot outside of W95, it's useless
(and can be harmful in some cases if you use a buggy applets which hardcodes
the ~1 into the tail of a name).  It just makes something like longnamefile.dat
appear under DOS as longname.dat instead of "longna~1.dat", which can be
very irritating.