From owner-freebsd-questions@FreeBSD.ORG Mon Sep 27 13:11:28 2004 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 0286D16A4CE; Mon, 27 Sep 2004 13:11:28 +0000 (GMT) Received: from tensor.xs4all.nl (tensor.xs4all.nl [194.109.160.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9049043D5C; Mon, 27 Sep 2004 13:11:27 +0000 (GMT) (envelope-from dimitry@andric.com) Received: from kilgore.dim (kilgore.dim [192.168.0.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.xs4all.nl (Postfix) with ESMTP id F00E122852; Mon, 27 Sep 2004 15:11:18 +0200 (CEST) Date: Mon, 27 Sep 2004 15:01:36 +0200 From: Dimitry Andric X-Mailer: The Bat! (v3.0.0.18) Professional X-Priority: 3 (Normal) Message-ID: <1565082305.20040927150136@andric.com> To: Andrew Boothman In-Reply-To: <1046192310.3e5ba0b6aa039@sms.ed.ac.uk> References: <9F67035A-48C9-11D7-8C19-0030656DD690@foolishgames.com> <1046192310.3e5ba0b6aa039@sms.ed.ac.uk> MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="----------9DC81322E657FF0" cc: questions@FreeBSD.ORG cc: dwbear75@gmail.com cc: current@FreeBSD.ORG Subject: Re: "NTLDR missing" after 5-RELEASE install 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, 27 Sep 2004 13:11:28 -0000 ------------9DC81322E657FF0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable On 2003-02-25 at 18:58:30 Andrew Boothman wrote: > I can't understand how the 5.x boot manager has managed to break my windo= ws > boot, i've never had any trouble under 3.x or 4.x, both of which played w= ith > windows perfectly nicely. Sorry for catching up on this thread so late, but couldn't this be some nasty problem with hard drive geometries? I.e. FreeBSD's interpretation of the partition table could be totally different from Windows', causing the rather flaky Microsoft bootloaders to fail. I personally have had complaints from PartitionMagic and various other Windows-based tools about partitions being "invalid" or having "different CHS and LBA boundaries" etc, after installing some versions of FreeBSD, and creating partitions from its installer. Could you please give us some info about your drive geometry, and/or or a somewhat low-level dump of your partition table data? ------------9DC81322E657FF0 Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: GnuPG v1.2.4 (MingW32) iD8DBQFBWA8wsF6jCi4glqMRApWuAJ0SIaCr6Qd1E8vPpOOXDn7468coVgCfQIgO 1CZIy+9u0uBQkastMvQnQAQ= =iaCN -----END PGP MESSAGE----- ------------9DC81322E657FF0--