Date: Tue, 16 Jun 1998 07:54:39 -0400 (EDT) From: "Joe \"Marcus\" Clarke" <marcus@miami.edu> To: Robert Withrow <witr@rwwa.com> Cc: "Joe \"Marcus\" Clarke" <marcus@miami.edu>, freebsd-questions@FreeBSD.ORG Subject: Re: Is fips truly updated to handle fat32 Message-ID: <Pine.OSF.3.96.980616075320.27424A-100000@jaguar.ir.miami.edu> In-Reply-To: <199806152340.TAA11095@spooky.rwwa.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Problems 2 and 3 I think I can answer. The ?? that BootEasy shows seems to be pretty common for FAT32 partitions. FAT32 isn't handled until you get to -current. However, the new mtools, mtools 3.9.1, will read and write FAT32 disks. Joe Clarke On Mon, 15 Jun 1998, Robert Withrow wrote: > > marcus@miami.edu said: > :- Yes, there is a fips 1.5c that recognizes FAT32. It's in the tools > :- directory on ftp.freebsd.org. The exact path is: > :- ftp://ftp.freebsd.org/pub/FreeBSD/tools/fips15c.tar.gz > > Thank you. This version seems to work fine with three caveats: > > 1) After fips is done doing its thing, command.com tries to restart > and gets an "out of memory" error, and the (dos) system halts. This > is using a floppy made from a W95 system. This doesn't seem to harm > anything. > > 2) Booteasy (from 2.2.6 R) shows "???" for the resulting DOS partition. > This can probably be fixed by using a newer booteasy. It boots both > partitions just fine though. > > 3) 2.2.6 R can't mount the fat32 partition. This can probably be fixed > by using -stable or applying some patches. > > I'll check around for solutions to 2 and 3. I'll try to inform the > fips developer about 1. > > --------------------------------------------------------------------- > Robert Withrow, R.W. Withrow Associates, Swampscott MA, witr@rwwa.COM > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.OSF.3.96.980616075320.27424A-100000>