From: Endlisnis <s257m AT unb DOT ca>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: RHIDE Problems (C++ Headers)
Date: Wed, 26 Aug 1998 20:07:21 -0300
Organization: NBTel Internet
Lines: 22
Message-ID: <35E49528.66025C30@unb.ca>
References: <E0zAiz4-0003r3-00 AT sable DOT ox DOT ac DOT uk> <iCdMCj1ZQ5j2-pn2-MVnOqveQHhFc AT portC20 DOT Generation DOT NET>
NNTP-Posting-Host: fctnts07c01.nbnet.nb.ca
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

sl AT psycode DOT com DOT REMOVE_THIS wrote:

> > Yes, that's already been done for v2.02.  This will fix nearly all of
> > these problems; some will still exist though.  I think the original
> > reason for defaulting to `n' was that it wasn't known how stable the
> > LFN support would be.
>         But setting LFN to 'y' makes no real sense.. Not _EVERYONE_ has
> access to LFNs.. I run under OS/2 which only supports FAT-16..

    1st of all, FAT-32 and LFN are 2 independent things.  You can have a
FAT-16 drive with LFN and you can have a FAT-32 drive without LFN.
    2nd:  If LFN is set to 'y', and your machine cannot support LFN's, then
it will be as if it was set to 'n'.  No problems could arrise.
--
     (\/) Endlisnis (\/)
          s257m AT unb DOT ca
          Endlisnis AT GeoCities DOT com
          Endlis AT nbnet DOT nb DOT ca