However, when I try to boot Windows from the LILO, I receive 'NTLDR is missing' error.
I'm a GRUB user, but this type of "missing" message usually is correct. Just a guess, but consider verifying your LILO config that LILO is looking at the correct drive/device in order to find ntldr
. I don't recall the /dev
device for SATA drives, but if, for example, your Windows install was located on a second IDE, the correct location for finding ntldr
would be /dev/hdb1
or something similar, not hda
I don't think this is a problem from Windows itself because it runs properly when I boot it by using BIOS settings; however when I try to boot Windows from LILO, the error message appears.
I agree. Windows boots fine by itself. There is nothing wrong with Windows. I believe you have provided your own clues: take a look at your LILO configuration.
But here is another caveat. After you boot with LILO, and even after you revise the LILO config to find ntldr
on the correct hard drive device, you then will need to edit the Windows boot.ini
file so that ntldr
is looking at the correct hard drive device too. That is, the BIOS will see the Windows hard drive as a different device, and the Windows ntldr
will see this too. I touch upon this concept in my mini how-to: Multibooting Tips