[Recent Entries][Archive][Friends][User Info]
December 28th, 2008
| December 28th, 2008 | |
|---|---|
| 06:19 am [Link] |
computer "problem"&solution log: unexpected reasons for Win not to boot After an installation of a GNU/Linux onto a computer where there was already Windows (this operation included resizing and moving the Windows partition, and removing the factory Windows recovery partition), Windows did not boot. And the reason/solution was something I could not expect to be a solution. So, I am writing it down for it to be findable. So, I had installed a LILO into MBR. And when booting Windows, Windows wrote it could not correctly read the "BCD" (or "BDC"... a file specified by a path "C:\..." and meaning something related to the boot configuration). I did automatic recovery from a recovery DVD. I did *everything* related I found in Google by manual commands from this recovery DVD (I did only the things I considered relevant, of course). It did not help! I thought I had a sound assumption that the Windows bootloader works "independently", and after LILO passed control to it, all the problems can be only inside this Windows bootloader (probably caused by moving the filesystem). The solution was... ...executing a certain recovery tool from the recovery DVD with "/fixmbr" option! Crazy magic! After this, Windows booted, did some restoration. Then I was able to reinstall LILO into MBR. So, logically the Windows bootloader could not be dependent on the state of MBR and the fact that LILO was there. Because after the self-restoration, it works even with that state that caused it not work, so it could not be the cause! It looks lile it can only be a guard against dual-boot configurations and rival OSes, something that has been included in Windows. But its behaviour is too unstable to believe that this guess is true. Either way, I have no other idea of an explanation. Tags: computer problem |
| Previous Day | 2008/12/28 [Archive] |
Next Day |