I didn't look this thread carefully so excuse me if information I give to all you is useless.
My investigation show that FreeBSD reads full partition table, and after modification
puts it back. It fix all entries from its own point of view. Windows dies from change
of end of partition entry. As I understand with large disk it shouldn't mean anything
at all. But windows checks it. You may save this entry and after installation of FreeBSD
put it back.
rik
Dimitry Andric wrote:
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 windows
boot, i've never had any trouble under 3.x or 4.x, both of which played with
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?
_______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
