Ok, fair enough. But if the way the system starts after installing works slightly differently then a problem with NTLDR could leave me stuck like I am. (I've tried CHDSK, FIXBOOT and FIXMBR).
So regardless of whether the installer touches NTLDR (whatever that is) it's the installation of Ubuntu that led to this problem being seen. Windows along was starting (apparently) fine. So, I still think that some kind of integrity check would be a good idea. -- Windows can't boot "NTLDR is Missing" https://launchpad.net/bugs/54283 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
