• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Missing NTLDR - dual boot system

WT

WT

Diamond Member
I'm running a dual boot box with three HDs, two set up running Windows 2000 and a third that is booting to Windows Home Server beta.

Before installing WHS, I manually unplugged the molex connectors from the pair of HDs that were running W2K, and my idea was to manually plug/unplug drives based on what OS I wanted to boot to. I've been very happy using WHS, but decided to boot back to W2K to do the usual A/V dat updates and whatnot and I hit the dreaded NTLDR missing error.

I haven't tried a fixboot, fixmbr on things yet, worried that this would hose my WHS setup (even though that drive will physically be unplugged from even spinning up). So will it fix my boot issue and not hose WHS, or am I faced with some other workaround or repair install ??

I don't mind losing my WHS setup, as a new build is already available, but for the first time in 15+ years I have a backup of all of my data on all PCs, and that just tickles me pink ! Thanks for any help on this one ... hopefully its an easy procedure to repair my oversight.
 
Originally posted by: WT
I haven't tried a fixboot, fixmbr on things yet, worried that this would hose my WHS setup (even though that drive will physically be unplugged from even spinning up). So will it fix my boot issue and not hose WHS, or am I faced with some other workaround or repair install ??
Click to expand...

Altering the MBR will only affect the drive that is able to receive power, which presumably won't receive any power when the other operating system is going to be booted. You might as well have two separate computers, as far as boot records are concerned.
 
If the boot files are present, and no errors in the file structure, it's usually the bios booting on the wrong drive
 
that message is generated when the partitions (not mbr) boot code is running and is unable to find ntldr.

Barring some disk corruption or an actual missing ntldr this would be caused by either bios booting to the wrong disk, or bios booting to the right disk but the wrong partition on that disk is set to active.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top