Andrew Boothman writes: > [...] > It's possible I guess that we both suffered from the same problem. I'd > be inclined to think that it must be operator error over something wrong > with sysinstall since I've not seen people complaining of these problems > before, yet there must be loads of people dual-booting. Having said > that, I still can't understand what I did differently or how to prevent > the same thing from happening in the future. > > I guess I'll just use GRUB or something instead. > > Looks like my Windows drive is heading for a reformat.... :-/
I'm pretty sure that it's not operator error on my part, since it happened several times. I suspect that there aren't that many people playing with 5.0 that don't install the standard boot stuff, and so that path isn't exercised too much. It happened repeatedly for me, and one of the things that's on my list of things to do is to recreate it and file a PR, but it hasn't risen to the top of the queue yet. It's a bit problematic because I don't really want to loose the contents of that drive (it takes *forever* to get windows and office updated after the intial installs: reboot, reboot, reboot...) and it's not hard to imagine that whatever's bitten me the past few times might get me irrecoverably the next time... GRUB is cool. Backup's of your partition/slice/disklabel info are extra cool. g. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
