OSDev.org

No, everything works as before.

Operating system installers should typically not alter the behaviour of the MBR code, and should only access the MBR to modify the partition table (if necessary). The purpose of the MBR is solely to load and execute the VBR for the active partition. In the case of Windows, the VBR loads some more sectors which in turn load NTLDR or BOOTMGR. Both NTLDR and BOOTMGR allow for booting another operating system via their menus, by loading a program to 7C00h or D000h.

In that case, I'm now wondering if Ranger's problem is occuring after his MBR code has run and after he has selected the Windows 7 partition to boot from. I had assumed before that that was not the case because he was talking about seeing the same message before the MBR code worked properly, at which time it shouldn't have been able to get to the point where it loads in the Windows Bootmanager code that displays that message.

Anyway, I don't know enough about this to help fix the problem, but I hope to hear how the it is eventually solved, so I wish Ranger the best of luck with it and hope a solution isn't far off.