From owner-freebsd-current Mon Jan 11 08:17:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA24618 for freebsd-current-outgoing; Mon, 11 Jan 1999 08:17:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vanessa.eliuk.org (pme199.sunshine.net [209.17.178.199]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA24613 for ; Mon, 11 Jan 1999 08:17:17 -0800 (PST) (envelope-from kevin_eliuk@sunshine.net) Received: from localhost (cagey@localhost) by vanessa.eliuk.org (8.9.1/8.8.8) with SMTP id IAA03896; Mon, 11 Jan 1999 08:15:14 -0800 (PST) (envelope-from cagey@vanessa.eliuk.org) Date: Mon, 11 Jan 1999 08:14:44 -0800 (PST) From: "Kevin G. Eliuk" Reply-To: "Kevin G. Eliuk" To: Sue Blake cc: Kris Kennaway , Kenneth Wayne Culver , current@FreeBSD.ORG Subject: Re: MSDOS filesystems being corrupted? In-Reply-To: <19990112003754.45869@welearn.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 12 Jan 1999, Sue Blake wrote: > On Mon, Jan 11, 1999 at 11:00:19PM +1030, Kris Kennaway wrote: > > > > I forgot to reply to this when I investigated further; I copied another large > > file onto my msdos partition, and after rebooting into win95 Norton Utilities > > complained about having found a damaged partition. Cancelling the dialog box > > and running M$ ScanDisk revealed no errors - therefore something is being done > > by the MSDOS filesystem code which ScanDisk is happy with, but NU is not. > > > > Should I open a PR on this? To whom ;-) > [Warning: newbie guesswork follows] > > considered tracking it down with a disk editor but then the problems > with FreeBSD writing to FAT disappeared when I stopped running Nortons > and NT :-) I really think this is the best solution :) > I'm not sure where to place the blame for the old or the new behaviour, > but it sounds possible that some long-standing Nortons/Windows quibble > could be having an unknown effect which would hold some of the answers. > FreeBSD could have been trolling rather than making the final blow. I have had my doubts about NU since the first time that I used the software, that's only a personal opinion though. From my point of view it would seem that NU has a flaw. Regards, Kevin G. Eliuk Discover Rock Solid, Discover FreeBSD | http://www.FreeBSD.Org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message