From owner-freebsd-current@FreeBSD.ORG Mon Jun 30 15:29:53 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81BFB37B401; Mon, 30 Jun 2003 15:29:53 -0700 (PDT) Received: from transpacific.net (lincoln.transbay.net [209.133.53.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id E237743FDF; Mon, 30 Jun 2003 15:29:52 -0700 (PDT) (envelope-from sreese@codysbooks.com) Received: from [192.168.0.24] (stalwart.codysbooks.com [209.133.54.175]) by transpacific.net (8.11.6p2/8.11.4) with ESMTP id h5UMTmp48419; Mon, 30 Jun 2003 15:29:48 -0700 (PDT) From: Scott Reese To: Doug White In-Reply-To: <20030630151326.I31036@carver.gumbysoft.com> References: <1056997197.39385.25.camel@borges> <200306302310.34846.andrew@cream.org> <20030630151326.I31036@carver.gumbysoft.com> Content-Type: text/plain Organization: Cody's Books, Inc. Message-Id: <1057012222.694.16.camel@borges> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.0 Date: 30 Jun 2003 22:30:22 +0000 Content-Transfer-Encoding: 7bit cc: current@FreeBSD.org cc: freebsd-questions@FreeBSD.org Subject: Re: 5.1-RELEASE & Windows XP dual-boot issues X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2003 22:29:53 -0000 On Mon, 2003-06-30 at 22:14, Doug White wrote: > On Mon, 30 Jun 2003, Andrew Boothman wrote: > > > This seems to be a recurring problem after 5-RELEASE. I had exactly the same > > problem, and I know of others that are the same. For some reason -current > > doesn't seem to be inter-operating well with the WinXP/Win2k loader anymore. > > I'm not sure if it's only happening to some installations - but I was > > certainly in the same boat. > > > > I ended up having to re-install Win2k and I used Grub as my new bootloader. > > Can't say I'm having any boot0 issues here with -current and win2k pro > sp3. Note windows is partition #2 and about 40GB in. I think it's something particular about the way the 5.1-RELEASE install works. As I mentioned in the original post, I had 5.0-RELEASE installed in this configuration and my dual-boot setup worked just fine. Subsequent source upgrades to 5.1-PRE also worked fine. After a fresh install of 5.1, kaboom. I have a hunch that it has something to do with 5.1 defaulting to UFS2 and it's subsequent handling of filesystems originally created with UFS1. Seems to me I saw something about this on the -current list a while ago but I don't remember the particulars. -Scott