From owner-freebsd-questions Wed Sep 8 22:34:18 1999 Delivered-To: freebsd-questions@freebsd.org Received: from br3-de0.dnsmgr.net (br3-de0.dnsmgr.net [198.145.92.3]) by hub.freebsd.org (Postfix) with ESMTP id 8933B14C1F for ; Wed, 8 Sep 1999 22:34:12 -0700 (PDT) (envelope-from hamellr@hamell.hpc1.com) Received: from heorot.hamell.hpc1.com (host74-125.iwbc.net [216.228.74.125]) by br3-de0.dnsmgr.net (8.9.3/8.9.3) with SMTP id WAA59403; Wed, 8 Sep 1999 22:33:36 -0700 (PDT) (envelope-from hamellr@hamell.hpc1.com) Date: Tue, 7 Sep 1999 14:58:10 -0700 (PDT) From: Rick Hamell To: Kurt Joseph Windisch Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Messed up boot MBR? Boot loaders failing In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > After doing this, and having everything work fine, I let my windows > virus scanner (Norton) "repair" my modified MBR for the drive and the boot > record for C: (this was the big mistake). Now windows will only boot > from BootMgr (not it's own MBR) and Freebsd will only boot from a boot > disk. Here's what I've done before, it's hit and miss but you may get lucky. Check your slice configuration and write down the settings. Blow everything out then write the slices again. FreeBSD seems to handle this pretty well. Windows may gack on it, if so, reinstall it. After that reinstall the boot manager. :) You'll want to back up data and such of course. Rick --- Religion exists because mankind is to arrogant to believe he is nothing more then a random accident. http://www.grendal.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message