New
#11
You read gregrockers and my comments. Choose yourself what you want. Post back result of win7 install. Can it see raidset etc
You read gregrockers and my comments. Choose yourself what you want. Post back result of win7 install. Can it see raidset etc
in elevated command prompt
C:>bcdedit /create {ntldr} /d “Windows XP”
This will create a boot loader entry using NTLDR for your Windows XP installation.
C:>bcdedit /set {ntldr} device partition=D:
C:>bcdedit /set {ntldr} path ntldr
C:>bcdedit /displayorder {ntldr} /addfirst
C:>bcdedit /default {ntldr}
change partition=D: to your driveletter. start recovery environment to check which one.
Maybe you have to change your boot.ini on winxp partition as well (?) if so change rdisk(0) to rdisk(1) don't know if that's necessary
Easier to install EasyBCD 2.0 to Win7 to add XP. EasyBCD 2.0.2 - NeoSmart Technologies
Users tend to appreciate the automated tools here, especially since they're free.
Well I got W7 installed on the separate HDD. When the RAID was plugged back in, W7 saw (and sees) it just fine.
I used BCDEdit Win version not the command line one) to add WinXP to the Boot choices.
However, when I brought the system up with the RAID back on, I had my Logical drive assignments: C and H on the separate HDD, D, E and F on the RAID. This won't do as what was changed to E: was D; and has a ton of data and more shortcuts and links than I care to think about. So I relabeled D: as X:, E: as D: and F: as E: thus maintaining at least my data consistency.
So BCDEdit added WinXP as being on X: and the path as NST/ntldr. While ntldr sits in the root of X:, there is no NST folder...
I tried reboot and the boot choices showed - I 1st went back to W7 just fine. However, attempts to get WinXP going have run into an error saying something is missing or corrupted suggesting I use the WinXP disk to repair the install. It also listed the path as NST/ntldr.
I then tried putting BCD and W7 boot loader on to the WinXP partition (the boot loader going to the MBR.) This still has no solved the issue.
I am going to try creating a NST folder with a copy of ntldr but thought it wast time to reach out to you folks.
BTW: to make the day more fun, my second desktop decided to go south in the midst of this. Murphy is alive and well!!!
Install EasyBCD 2.0 to Win7 to add XP, accept boot files, autocompletes, Save, Reboot. Hopefully the legacy tool didn't ruin it for the proven method.
None of this would have been necessary had your taken my original advice to leave RAID unplugged while installed Win7, then after install booting one via BIOS boot order or choose the other using BIOS Boot menu.
Last edited by gregrocker; 17 Nov 2011 at 22:02.
gregrocker: sorry I actually missed the recommendation for EasyBCD. My bad.
However, I went into the now X: drive while under W7 and added a /NST folder and put a copy of ntldr into it.
Rebooted, selected WinXP and up she came. So far all seems to be fine...
On review, I did use EasyBCD - I think BCDEdit was just an incorrect term for it. I apologize for being imprecise.
It does raise the question why it added the /NST level into the path?
Since this was my first outing with dual booting, I was not aware that the running OS would treat the primary partition as C: and reassigning its dormant cousin to another letter...
Thanks for your help.
Jim