2009/7/9, jean-francois <jfsimon1...@gmail.com>: > Something has been changed which prevent sd1 and sd2 to start however no > data loss. > > I don't understand, I have launched install on sd0 ?
I suspect you had the bootloader on sd0 originally. I suggest you install a new one and configure it appropriately. Afaik the windows boot program is installed at the start of the partition. Grub is installed somewhere on the disk as well. In both cases the MBR of the boot drive effectively leads the bootloader from elsewhere into memory and jumps. Both systems are fine, but neither has a pointer from the booted mbr. > Le jeudi 09 juillet 2009 C 11:29 +0200, Jean-FranC'ois SIMON a C)crit : >> Sorry, I mean, I installed on SD0 using "all disk space". >> I am not sure the MBR has been modified, I have to look further what >> was modified, however the other disks do not boot anymore. >> Windows (sd1) starts and crashes during the load. >> Ubuntu (sd2) says "no os" ? >> >> I hope that other disks were not erased, since I only wanted to >> installed on sd0. >> >> FYI sd1 and sd2 had their own boot manager and OS, they were so to say >> "stand alone" disks, choice of starting was made during the bios >> start, selecting at this moment which disk will be booted up. >> >> Thanks >> BR >> JF >> >> 2009/7/9 Richard Toohey <richardtoo...@paradise.net.nz> >> On 9/07/2009, at 7:41 PM, Eric Furman wrote: >> >> This is the best advice you will get. >> Don't try duel booting until you know what you are >> doing. >> And I'm not trying to be a smartass. >> >> >> duel[sic] booting - someone will end up getting shot! 8-)
