Date: Sat, 26 Apr 1997 19:58:29 -0500 From: Tony Overfield <tony@dell.com> To: terry@lambert.org, ksmm@cybercom.net Cc: joa@kuebart.stuttgart.netsurf.de, hackers@freebsd.org Subject: Re: VFAT 32 support in msdosfs Message-ID: <3.0.1.32.19970426195829.007af2b0@bugs.us.dell.com> In-Reply-To: <199704261941.MAA07443@phaeton.artisoft.com> References: <1.5.4.32.19970426035451.006fa82c@cybercom.net>
next in thread | previous in thread | raw e-mail | index | archive | help
At 12:41 PM 4/26/97 -0700, Terry Lambert wrote:
>[OEMSR2] machines are capable of reading long-name-in-volume-label FAT
>drives ("VFAT"). But the partitions they use by default, and the
>partition table format, and the MBR and the io.sys/io.dos/msdos.dos
>where the INT 21 interface is instantiated *all* expect VFAT32. I'm
>not sure that an OEMSR2 INT 21 is capable of identifying and booting
>from a "VFAT" drive at all.
This is nonsense.
FAT32 is a superset of FAT16/FAT12. The OEMSR2 version of io.sys
supports all three. There is not a special version of io.sys
which only supports FAT32 partitions.
io.sys does not "do" VFAT at all. VFAT "happens" when the
protected mode VFAT driver is loaded. This is why real-mode
Windows 95 (DOS mode) cannot see or use long filenames.
Of course, io.dos/msdos.dos are irrelevant, since they aren't even
used when booting Windows 95, they're used when booting your
*previous* DOS, which might be MS-DOS 5.0.
Why you think that INT 21 is related to any of this remains a
mystery to me.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.1.32.19970426195829.007af2b0>