From owner-freebsd-stable Mon Feb 8 08:40:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA26656 for freebsd-stable-outgoing; Mon, 8 Feb 1999 08:40:17 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from guru.phone.net (guru.phone.net [209.157.82.120]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA26651 for ; Mon, 8 Feb 1999 08:40:16 -0800 (PST) (envelope-from mwm@phone.net) Received: (qmail 15065 invoked by uid 100); 8 Feb 1999 16:40:13 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 8 Feb 1999 16:40:13 -0000 Date: Mon, 8 Feb 1999 08:40:13 -0800 (PST) From: Mike Meyer To: freebsd-stable@FreeBSD.ORG Subject: Re: Fully Dedicated HD may clobber some BIOS' In-Reply-To: <199902072330.AA03060@waltz.rahul.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 7 Feb 1999, Rahul Dhesi wrote: > I see that there are some slight risks to being "dangerously dedicated"< > if you are using a big-name system. If I've correctly figured out what happened, then it's more than just "big-name" systems. My SuperMicro box lost the boot blocks on reboot a couple of times (seems to be related to booting with a floppy in the drive). I suspect it was the anti-virus feature of the BIOS writing a "good" MBR onto the drive. I've since disabled that feature, but not tried booting with a floppy in the drive again. Since the system came from a FreeBSD systems integration house, I'm sort of surprised they left that feature on. Then again, they may not have expected me to install 3.0-RELEASE as a DD system.