From owner-freebsd-questions@FreeBSD.ORG Sat Sep 6 21:00:17 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 2363916A4BF for ; Sat, 6 Sep 2003 21:00:17 -0700 (PDT) Received: from lariat.org (lariat.org [63.229.157.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5811443FFD for ; Sat, 6 Sep 2003 21:00:16 -0700 (PDT) (envelope-from brett@lariat.org) Received: from mustang.lariat.org (IDENT:ppp1000.lariat.org@lariat.org [63.229.157.2]) by lariat.org (8.9.3/8.9.3) with ESMTP id WAA20088 for ; Sat, 6 Sep 2003 22:00:08 -0600 (MDT) X-message-flag: Warning! Use of Microsoft Outlook renders your system susceptible to Internet worms. Message-Id: <4.3.2.7.2.20030906215542.028ddc60@localhost> X-Sender: brett@localhost X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sat, 06 Sep 2003 22:00:04 -0600 To: questions@freebsd.org From: Brett Glass Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: 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: Sun, 07 Sep 2003 04:00:17 -0000 I'm attempting to install FreeBSD 4.8 on a system which will boot it and also Windows 2000 Server. I've done this with two multiboot utilities: the simple boot manager that comes with FreeBSD and V Communications' System Commander. In both cases, I have found that when I install FreeBSD it corrupts neighboring NTFS and FAT partitions. After the install, the OSes in these partitions fail to boot or the partitions become entirely unreadable. Whether I tell FreeBSD not to install an MBR or whether I tell it to install its boot manager, the result is the same: Neighboring partitions are being corrupted to the point where one can not get to data on them. I realize that dual booting is not common, but I need to do it on this laptop. Has anyone else on the lists encountered this problem? --Brett Glass