From: sl AT psycode DOT com DOT REMOVE_THIS
Newsgroups: comp.os.msdos.djgpp
Subject: Re: RHIDE Problems (C++ Headers)
Date: 29 Aug 1998 04:24:37 GMT
Organization: http://www.supernews.com, The World's Usenet: Discussions Start Here
Lines: 10
Message-ID: <iCdMCj1ZQ5j2-pn2-prc621MBRkU1@portX51.lanzen.net>
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> <35E6BF42 DOT 981079D1 AT unb DOT ca>
NNTP-Posting-Host: 205.205.70.70
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 Fri, 28 Aug 1998 14:31:30, Endlisnis <s257m AT unb DOT ca> wrote:

> 	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

	Correct.. VFAT extends FAT-16. It is fully compatible with it, yet 
writes to previously unused areas of the file structure. Hence any 
normal DOS app sees VFAT as FAT-16.

Gili