From: Endlisnis <s257m AT unb DOT ca>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: RHIDE Problems (C++ Headers)
Date: Fri, 28 Aug 1998 11:31:30 -0300
Organization: NBTel Internet
Lines: 17
Message-ID: <35E6BF42.981079D1@unb.ca>
References: <E0zAiz4-0003r3-00 AT sable DOT ox DOT ac DOT uk> <iCdMCj1ZQ5j2-pn2-MVnOqveQHhFc AT portC20 DOT Generation DOT NET> <35E49528 DOT 66025C30 AT unb DOT ca> <iCdMCj1ZQ5j2-pn2-RGFgyiRB1wUU AT portY05 DOT lanzen DOT net>
NNTP-Posting-Host: fctnts06c09.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:
> >     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.
>         I disagree... FAT-16 can only support 8.3 filenames.. VFAT, which is
> an extension of FAT-16 can support long filenames, but the two are not
> equivilent.
	Well, if that is true, then changing from FAT-16 to VFAT does not require
formating, becuase I have a hard-drive that was formated as FAT-16, and when I
use Win95, it just writes long-filenames there.  I think it is just using a
different directory structure.
-- 
     (\/) Endlisnis (\/)
          s257m AT unb DOT ca
          Endlisnis AT GeoCities DOT com
          Endlis AT nbnet DOT nb DOT ca