snakeman1978
New Member
I have a raid 1 system drive with 3 partitions. Partition 1 had XP64 on it, partition 2 is a logical partition and is just storage, and partition 3 has XP32 bit on it. I got my copy of Windows7 and went to install over the XP64 install and it worked great. Now I can't boot into XP32. These partitions are C: E: F: respectively as the windows 7 diskmanager reports.
I have Easy BCD v.1.7.2 installed on Windows 7 and it seems to be a very useful tool. I have created another pointer in bootmgr which does work but when I choose the XP32 option is restarts the computer. I have run recovery console to try and rebuild the all the boot files. I tried bootcfg /rebuild and that didn't work. I manually moved \NTLDR and ntdetect to the F: drive where the XP32 install resides. and that didn't work.
The Original boot.ini file that was created by recovery console looks like this...
When running recover console it scans the disc for windows installs and puts the partition value to "2" but I think its partition "3" (unsure) I tried to manually make that value 3 and that didn't work.
If anybody can tell me how the whole relationship of the boot files works, i.e. can I just put any \NTLDR file on the root directory and manipulate the boot.ini file and it will work, or do they somehow have to be created together?
Do the \NTLDR files need to be inside the windows directory?
If I manually edit the boot.ini file on the f: drive and the run EASYBCD PowerConsole and type bootcfg, the file isn't the boot.ini file that I though I just edited. Any help will be so much appreciated.
I have Easy BCD v.1.7.2 installed on Windows 7 and it seems to be a very useful tool. I have created another pointer in bootmgr which does work but when I choose the XP32 option is restarts the computer. I have run recovery console to try and rebuild the all the boot files. I tried bootcfg /rebuild and that didn't work. I manually moved \NTLDR and ntdetect to the F: drive where the XP32 install resides. and that didn't work.
The Original boot.ini file that was created by recovery console looks like this...
[boot loader]
timeout=20
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="XP32" /fastdetect
It's a challenge to manually manipulate the boot.ini file but I managed to do that and it looks like this...timeout=20
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="XP32" /fastdetect
[boot loader]
timeout=20
default=multi(0)disk(0)rdisk(0)partition(3)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="XP32" /fastdetect
It appears that the Windows 7 boot manager is it own entity and then points to the boot.ini of the XP32 bit partition. So my problem, I think, is in my Boot.ini file.timeout=20
default=multi(0)disk(0)rdisk(0)partition(3)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="XP32" /fastdetect
When running recover console it scans the disc for windows installs and puts the partition value to "2" but I think its partition "3" (unsure) I tried to manually make that value 3 and that didn't work.
If anybody can tell me how the whole relationship of the boot files works, i.e. can I just put any \NTLDR file on the root directory and manipulate the boot.ini file and it will work, or do they somehow have to be created together?
Do the \NTLDR files need to be inside the windows directory?
If I manually edit the boot.ini file on the f: drive and the run EASYBCD PowerConsole and type bootcfg, the file isn't the boot.ini file that I though I just edited. Any help will be so much appreciated.