strange colored columns after BCD2

P

panis

Member
Hi,

pls excuse me if there is a thread already discribe my problem, but i can't find anything so far and i'm running out of time!

I installed Windows 7 on a second hd with Windows XP hd disconnected.
After Installation i reconnected Windows xp hd.

i was able to boot both by switching bootorder in bios.

Then i installed EasyBCD2.0 in Windows XP, added an entry for Windows7.
Now if i reboot there appear strange colored columns on screen.
If i change bootorder in bios i am still able to boot into Windows7 but the Windows XP ntloader seems to be broken.
I can still access Windows XP hd from Win7.
Booting Windows XP CD and do fixboot / fixmbr doesn't help.

pls, need help here - my girlfriend is going to kill me if she find out i crashed her XP-Installation :wink:
 

Attachments

  • IMG_8216.JPG
    IMG_8216.JPG
    394.3 KB · Views: 4
Last edited:
You can't boot a newer OS from XP. The NTLDR bootmanager/loader is not forward compatible.
Put W7 first in the BIOS permanently.
Boot W7, add an XP entry to the BCD with EasyBCD 2.0. Let it auto-configure the XP boot.
 
tnx for your fast answhere.

I booted into Windows 7 and istalled latest beta of BCD2.
Then i added an entry for Windows XP and let BCD install NTLoader by itself.

If i select Windows XP at reboot i get the following message:

Windows could not start because of a computer disk hardware configuration problem.
Could not read from the selects boot disk. Check boot path and disk hardware. (see screenshot)

btw. Windows XP Installation is on SATA drive while Windows 7 on ATA100
 

Attachments

  • P0014_090110.jpg
    P0014_090110.jpg
    429.4 KB · Views: 2
k, this is what my BCD2 config looks like:

Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=C:
path \bootmgr
description Windows Boot Manager
locale en-us
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {abd6a7fd-fd3a-11de-94ff-00044b808003}
resumeobject {abd6a7f7-fd3a-11de-94ff-00044b808003}
displayorder {abd6a7fc-fd3a-11de-94ff-00044b808003}
{abd6a7fd-fd3a-11de-94ff-00044b808003}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 30
Real-mode Boot Sector
---------------------
identifier {abd6a7fc-fd3a-11de-94ff-00044b808003}
device partition=C:
path \NTLDR
description Microsoft Windows XP
Windows Boot Loader
-------------------
identifier {abd6a7fd-fd3a-11de-94ff-00044b808003}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Ultimate (wiederhergestellt)
locale de-DE
recoverysequence {abd6a7fa-fd3a-11de-94ff-00044b808003}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {109b45e7-fd5b-11de-ae1c-806e6f6e6963}

my diskmanagement is attached as png

thank you for helping me with this.

drive g: on that screenshot is just my 1gig usb-stick; i forget to remove that. so just ignore it.
 

Attachments

  • dm.PNG
    dm.PNG
    122.1 KB · Views: 10
Last edited:
Everything else appears OK. That message indicates boot.ini wrongly configured.
Easy2 should have done that for you
Use EasyBCD /Tools/ Edit legacy entries to locate boot.ini and post the contents here
 
Last edited:
That's seriously deficient of the required detail.
Was there some kind of problem when you let EasyBCD auto-configure ?
try tools/auto-configure, then tools/edit to see it's done it properly.
It should look like this

[boot loader]
timeout=20
default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Windows XP on D:\" /fastdetect

copy/paste the above into C:\boot.ini if the auto-configure fails, and report what the problem was.
also check that C:\ NTLDR and C:\ntdetect.com are present.
 
Last edited:
Back
Top