From owner-freebsd-hackers Thu Sep 11 23:32:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA09024 for hackers-outgoing; Thu, 11 Sep 1997 23:32:35 -0700 (PDT) Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.219]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA09019 for ; Thu, 11 Sep 1997 23:32:33 -0700 (PDT) Received: from postbox.india.hp.com (postbox.india.hp.com [15.10.45.1]) by palrel3.hp.com (8.8.5/8.8.5tis) with ESMTP id XAA13197; Thu, 11 Sep 1997 23:32:22 -0700 (PDT) Message-Id: <199709120632.XAA13197@palrel3.hp.com> Received: from localhost by postbox.india.hp.com with ESMTP (1.39.111.2/16.2) id AA161665724; Fri, 12 Sep 1997 11:58:44 +0530 To: grog@lemis.com Cc: freebsd-hackers@freebsd.org Subject: Floppy trouble contd. Date: Fri, 12 Sep 1997 11:58:43 +0530 From: A Joseph Koshy Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk gl> most expensive per byte. But I'm getting the feeling that there is gl> more to it than that, that possibly there's a bug in the floppy driver gl> and that we're blaming it on the inherent unreliability of the medium. gl> 1. Floppy formatted under on the same machine. gl> 2. FreeBSD runs into hardware problems with the floppy (typically gl> things like checksum errors). gl> 3. can read the entire floppy with no trouble. I've seen (1), (2), and (3). After a (2), doing a format using the freebsd tools sometimes helps, but see below. I've also seen that formatting 3-4 times under FreeBSD (fdwrite or fdformat) causes the floppy to become unuseable, even under DOS. I've seen these on just too many floppies, new, used, of various brands, to dismiss it as due to the unreliability of the medium. Koshy My Personal Opinions Only.