On Tuesday 02 March 2010 23:31:16 Peter Ruskin wrote: > Thanks for your help, Mick.
You're welcome. Sorry it took me some time to get to it:
> Here's the bcdedit /v before I started:
> C:\Windows\System32\bcdedit /v >C:\bcdedit-orig.txt
It may be better to use the /export function to back up the BCD file.
> Windows Boot Loader
> -------------------
[snip ...]
>
> Resume from Hibernate
> ---------------------
[snip ...]
> Windows Memory Tester
> ---------------------
[snip ...]
I can't see in there your MSWindows Boot Manager entry. This BCD will not be
able to boot MSWindows natively, or chainload Linux from it ... you'll need to
repair it with your Vista CD as I suggested in the previous message.
> And here it is after I followed your procedure:
> C:\Windows\System32\bcdedit /v >C:\bcdedit.txt
>
> Windows Boot Manager
> --------------------
> identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
> displayorder {150a4189-2608-11df-b94d-00248cc04424}
> timeout 10
I suspect that's not enough to load the boot manager. Compare it to my entry:
==================================
Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=\Device\HarddiskVolume2
path \bootmgr
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {fda5ebf3-119b-11df-969c-f924691e8117}
resumeobject {5744906c-0bf4-11df-8e08-0026b920b49c}
displayorder {fda5ebf3-119b-11df-969c-f924691e8117}
{fda5ebf6-119b-11df-969c-f924691e8117}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 3
==================================
> Real-mode Boot Sector
> ---------------------
> identifier {150a4189-2608-11df-b94d-00248cc04424}
> device boot
> path C:\linux.bin
> description Gentoo Linux
> locale en-US
That's good, but I suspect it won't work because your Boot Manager entry is
not correct.
> After reboot it reverts to the original - just as well, because the
> Windows Boot Manager looks suspect to me.
Yes, it looks dodgy to me too. If it reverts to the original then that means
that you are not actually editing the BCD file that is being used for booting.
I suspect that what's happening here is that Acronis OSS has taken over the
MBR and the boot files (I think it saves them in a BOOTWIZ folder or something
similar). So the BCD file you are editing is not the one Acronis is using.
My method implies that you have restored your Vista to its original state as
far as MBR and MSWindows boot files are concerned. So, for it to work you
will need to uninstal Acronis OSS I'm afraid and repair the start up files as
I described in my previous email.
Alternatively, you may want to try using bcdedit to edit the correct BCD file,
*but* I am not sure that Acronis will allow you to do that (it probably
altered the access rights to it, that's why a reboot shows up the original
file).
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
