Date: Sun, 27 Apr 1997 22:03:38 -0400 From: The Classiest Man Alive <ksmm@cybercom.net> To: Terry Lambert <terry@lambert.org> Cc: terry@lambert.org, joa@kuebart.stuttgart.netsurf.de, hackers@freebsd.org Subject: Re: VFAT 32 support in msdosfs Message-ID: <1.5.4.32.19970428020338.00707950@cybercom.net>
next in thread | raw e-mail | index | archive | help
At 12:07 PM 4/27/97 -0700, Terry Lambert wrote: >>>not sure that an OEMSR2 INT 21 is capable of identifying and booting >>>from a "VFAT" drive at all. >> >> Windows 95 OEM SR2 certainly can boot from a VFAT drive. That's my point. >> VFAT32 may be coming into widespread use, but I don't think it's time for us >> (or Microsoft) to start dropping support for VFAT. > >I don't know how you got an OEMSR2 boot block and INT 21 code onto a >VFAT drive, but I'd be interested in finding out. > I formatted the drive as a FAT drive then installed Windows 95. It booted. I'm not sure what else there is to tell you. >I suspect that if you are running OEMSR2 on VFAT that you have the >older bootblock code. > >MSDN-2 developers (like me) got betas with the ability to "upgrade" an >existing VFAT drive to VFAT32. Since there was no reverse process, I >wonder at how you can claim to be using the VFAT32 io.sys on a VFAT >drive. > Look, man, back up off me. I don't know from a bootblock or IO.SYS, but I just installed straight onto a FAT formatted drive. The resulting installation now reads/writes both VFAT and VFAT32 drives (as indicated by their properties). If you ever need to convert back and forth, Partition Magic 3.0 does the job admirably. K.S.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1.5.4.32.19970428020338.00707950>