From owner-freebsd-alpha Thu Nov 16 11: 4:33 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id C4BD937B4C5 for ; Thu, 16 Nov 2000 11:04:28 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id LAA26215; Thu, 16 Nov 2000 11:04:26 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.0/8.11.0) id eAGJ4Mf48976; Thu, 16 Nov 2000 11:04:22 -0800 (PST) (envelope-from jdp) Date: Thu, 16 Nov 2000 11:04:22 -0800 (PST) Message-Id: <200011161904.eAGJ4Mf48976@vashon.polstra.com> To: alpha@freebsd.org From: John Polstra Cc: mjacob@feral.com Subject: Re: 4.2-RC1 failure on 164LX In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article , Matthew Jacob wrote: > > > > A question: if the floppy had read errors, would they be detected > > and reported? I.e., is it worthwhile to try a different diskette? > > No, SRM does complain about bad diskettes. At least the Multia one does all > the time. But does /boot/loader complain about read errors after it gets control? > What I had been thinking of is taking boot.flp and copying all 3MB > to the head of a SCSI or IDE disk and booting that on your 164LX. Hrm, I'd love to help but I don't think I can take it quite that far. :-( John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message