From owner-freebsd-questions@FreeBSD.ORG Mon Sep 8 16:09:42 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9D3116A4BF for ; Mon, 8 Sep 2003 16:09:42 -0700 (PDT) Received: from mail3.bluewin.ch (mail3.bluewin.ch [195.186.1.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id D4F8B43FFB for ; Mon, 8 Sep 2003 16:09:41 -0700 (PDT) (envelope-from raphael@computer-rental.ch) Received: from computer-rental.ch (195.186.183.151) by mail3.bluewin.ch (Bluewin AG 7.0.020) id 3F5705890007D89A; Mon, 8 Sep 2003 23:09:04 +0000 Date: Tue, 9 Sep 2003 01:06:52 +0200 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Mime-Version: 1.0 (Apple Message framework v552) To: "Jud" From: =?ISO-8859-1?Q?Rapha=EBl_Marmier?= In-Reply-To: <20030908200145.7384E76324@smtp.us2.messagingengine.com> Message-Id: <227025D8-E251-11D7-B384-000393D67E4A@computer-rental.ch> Content-Transfer-Encoding: quoted-printable X-Mailer: Apple Mail (2.552) cc: Dan Harrison cc: Brett Glass cc: freebsd-questions Subject: Re: FreeBSD install corrupts neighboring partitions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Sep 2003 23:09:42 -0000 Le Lundi, 8 sep 2003, =E0 22:01 Europe/Zurich, Jud a =E9crit : --snip-- > Once you've installed FreeBSD, if you > can't boot back into Windows, use the Windows tools to restore the > familiar Win MBR: for 9x, boot from the emergency floppy and run fdisk > /mbr; for more recent versions, boot from CD into console repair mode=20= > and > run fixboot and fixmbr. In my case, I think I could mount the windows partition only from=20 linux. I couldn't read it with a dos disk (same w98 se). So I thought=20 that it was some kind of incompatibility between the way FreeBSD/Linux=20= and Windows recognized the drive's geometry. Installing freeBSD would=20 change something in subtil way in the partition table that would=20 confuse windows' boot loader. I did fdisk /mbr, sys c:, etc... to no=20 avail. Finally, installing windows in second solved the issue. I never really=20= understood what happened though. I have to mention the windows partition was not the first primary=20 partition (well, ok, slice in BSDspeak). Rapha=EBl=