| 1 |
On Tuesday 02 March 2010 23:31:16 Peter Ruskin wrote: |
| 2 |
|
| 3 |
> Thanks for your help, Mick. |
| 4 |
|
| 5 |
You're welcome. Sorry it took me some time to get to it: |
| 6 |
|
| 7 |
> Here's the bcdedit /v before I started: |
| 8 |
> C:\Windows\System32\bcdedit /v >C:\bcdedit-orig.txt |
| 9 |
|
| 10 |
It may be better to use the /export function to back up the BCD file. |
| 11 |
|
| 12 |
> Windows Boot Loader |
| 13 |
> ------------------- |
| 14 |
[snip ...] |
| 15 |
|
| 16 |
> |
| 17 |
> Resume from Hibernate |
| 18 |
> --------------------- |
| 19 |
[snip ...] |
| 20 |
|
| 21 |
> Windows Memory Tester |
| 22 |
> --------------------- |
| 23 |
[snip ...] |
| 24 |
|
| 25 |
I can't see in there your MSWindows Boot Manager entry. This BCD will not be |
| 26 |
able to boot MSWindows natively, or chainload Linux from it ... you'll need to |
| 27 |
repair it with your Vista CD as I suggested in the previous message. |
| 28 |
|
| 29 |
> And here it is after I followed your procedure: |
| 30 |
> C:\Windows\System32\bcdedit /v >C:\bcdedit.txt |
| 31 |
> |
| 32 |
> Windows Boot Manager |
| 33 |
> -------------------- |
| 34 |
> identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795} |
| 35 |
> displayorder {150a4189-2608-11df-b94d-00248cc04424} |
| 36 |
> timeout 10 |
| 37 |
|
| 38 |
I suspect that's not enough to load the boot manager. Compare it to my entry: |
| 39 |
================================== |
| 40 |
Windows Boot Manager |
| 41 |
-------------------- |
| 42 |
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795} |
| 43 |
device partition=\Device\HarddiskVolume2 |
| 44 |
path \bootmgr |
| 45 |
description Windows Boot Manager |
| 46 |
locale en-US |
| 47 |
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e} |
| 48 |
default {fda5ebf3-119b-11df-969c-f924691e8117} |
| 49 |
resumeobject {5744906c-0bf4-11df-8e08-0026b920b49c} |
| 50 |
displayorder {fda5ebf3-119b-11df-969c-f924691e8117} |
| 51 |
{fda5ebf6-119b-11df-969c-f924691e8117} |
| 52 |
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d} |
| 53 |
timeout 3 |
| 54 |
================================== |
| 55 |
|
| 56 |
> Real-mode Boot Sector |
| 57 |
> --------------------- |
| 58 |
> identifier {150a4189-2608-11df-b94d-00248cc04424} |
| 59 |
> device boot |
| 60 |
> path C:\linux.bin |
| 61 |
> description Gentoo Linux |
| 62 |
> locale en-US |
| 63 |
|
| 64 |
That's good, but I suspect it won't work because your Boot Manager entry is |
| 65 |
not correct. |
| 66 |
|
| 67 |
> After reboot it reverts to the original - just as well, because the |
| 68 |
> Windows Boot Manager looks suspect to me. |
| 69 |
|
| 70 |
Yes, it looks dodgy to me too. If it reverts to the original then that means |
| 71 |
that you are not actually editing the BCD file that is being used for booting. |
| 72 |
I suspect that what's happening here is that Acronis OSS has taken over the |
| 73 |
MBR and the boot files (I think it saves them in a BOOTWIZ folder or something |
| 74 |
similar). So the BCD file you are editing is not the one Acronis is using. |
| 75 |
My method implies that you have restored your Vista to its original state as |
| 76 |
far as MBR and MSWindows boot files are concerned. So, for it to work you |
| 77 |
will need to uninstal Acronis OSS I'm afraid and repair the start up files as |
| 78 |
I described in my previous email. |
| 79 |
|
| 80 |
Alternatively, you may want to try using bcdedit to edit the correct BCD file, |
| 81 |
*but* I am not sure that Acronis will allow you to do that (it probably |
| 82 |
altered the access rights to it, that's why a reboot shows up the original |
| 83 |
file). |
| 84 |
-- |
| 85 |
Regards, |
| 86 |
Mick |
Archives