Yes, that is my own experience. The only "exception" there, I believe, is if someone wants to use EasyBCD to restore an XP loader. To do that, and if I remember correctly (from reading on the EasyBCD forums), one would need the older version of EasyBCD to do that ... and I think that might be...
I think I only ever saw a modified ntldr in "root" in my own system, and with the easyldr1, etc, in an NST folder. However, I certainly do not claim to have experienced every possible scenario here! In my own experience, the EasyBCD-modified boot.ini was not even being used. No matter how I...
Yes, and that might work even in Win7 is not on the first drive where its boot loader is installed. In my own case, I have once done something similar (via BCDEdit) to manually -- better get everything right! -- add a BCD entry for XP.
An aside here in relation to EasyBCD in a certain situation: If anything ever happens to break Win7's loader and Win7 is not on the first drive, Win7's "Startup Repair" will *not* be able to repair the Win7 loader first placed on the first drive during Win7 installation. However, and if you can...
If you cannot, I will gladly use EasyBCD in either XP or Win7 to again add XP to Win7's loader and then share what I had found. Just let me know ... Joe
Oh yes, and I think I nearly drove myself nuts while learning about all those "confusing possibilities"! No, but I have never noticed anything different whether running EasyBCD in XP or Win7. "H", the first partition on the drive where Win7 is located. I used to have Win7's loader on my first...
Not sure whether you are asking me or the OP here, but easyBCD certainly can create a BCD even "from scratch", so to speak, and even from within XP, if necessary. In my own case, I was at a point where nothing at all would boot, so I began by using XP's "Repair Console" to get XP booting again...
About three years ago, and after having grown quite weary of dealing with modified boot loaders whenever anything anywhere had later gone wrong, my overall goal became that of being able to multi-boot Win98-Win2K-WinXP-Win7-Linux with each OS's original boot loader remaining completely untouched...
I know this is an old thread, and the OP's problem seems to me to have been more than just something related to EasyBCD, yet I do believe I have some answers for anyone who might have an EasyBCD-related "Invalid boot.ini" problem in the future ... ... and I learned all of this the hard way...