From: sl AT psycode DOT com DOT REMOVE_THIS Newsgroups: comp.os.msdos.djgpp Subject: Re: RHIDE Problems (C++ Headers) Date: 28 Aug 1998 04:06:48 GMT Organization: http://www.supernews.com, The World's Usenet: Discussions Start Here Lines: 19 Message-ID: References: <35E49528 DOT 66025C30 AT unb DOT ca> NNTP-Posting-Host: 205.205.70.104 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8bit To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk On Wed, 26 Aug 1998 23:07:21, Endlisnis wrote: > 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. 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. Gili