leejosepho
New Member
Oh yes, and I think I nearly drove myself nuts while learning about all those "confusing possibilities"!Very impressive setup. It does make for some confusing possibilities.
No, but I have never noticed anything different whether running EasyBCD in XP or Win7.Can I assume you always run EasyBCD from Windows 7?
"H", the first partition on the drive where Win7 is located. I used to have Win7's loader on my first drive, but now I can get to Win2K (or out to XP) from my first drive without having to go through Win7's loader ... and I can boot Win7 either via Grub4Dos on the USB stick or by using "Select Boot Options" at machine startup and going directly to my third drive.So XP in on the 3rd drive, 3rd partition. Windows 7 is on the 3rd drive, 2nd partition.. The Windows 7 boot files are on Drive ?...
That is my point. EasyBCD either modifies or removes-and-replaces the original ntldr when adding XP to the Win7 loader.The NTLDR file on my old laptop shows the same file size are your attachment. I certainly cannot say the one included with EasyBCD is not different in some way ...
No, replacing the easyBCD version with an original ntldr from the XP installation disk will get rid of "Invalid boot.ini file" when going back to using only the original XP loader ...... if that were the case, replacing just the version of ntldr that works correctly with the one from EasyBCD should duplicate the problem...?
... and with that understood, I will not bother going back and re-creating a "problem" (as I would see things) here in my system to show you the different Properties of "ntldr" -- "Modified: (current date and time)" -- after EasyBCD has been used to add XP to the Win7 loader.
Last edited: