Archived from groups: comp.sys.ibm.pc.hardware.storage (
More info?)
"J. Clarke" <jclarke@nospam.invalid> wrote in message news:cuvn7o01uha@news1.newsguy.com
> Euan Kerr wrote:
> > "J. Clarke" jclarke@nospam.invalid> wrote in news:cuu9hm0b3p@news1.newsguy.com:
> > > Euan Kerr wrote:
> > > > "J. Clarke" jclarke@nospam.invalid> wrote in news:cutils02en0@news1.newsguy.com:
> > > > > marslee@hotmail.com wrote:
> > > > >
> > > > > >
> > > > > > I moved my hard disk from my old computer to
> > > > > > the new motherboard since the old motherboard was broken
> > > > > > but i get the following error message.
> > > > > >
> > > > > > NTLDR Is Missing
> > > > > >
> > > > > > I use win2000, Anyone know how to fix it?
> > > > >
> > > > > Most likely cause of that message is that you have an
> > > > > optimized disk driver for your old board installed and that
> > > > > driver's not compatible with your new one.
> > > > >
> > > > ...and the easiest of all approach is to do a repair
> > > > installation after booting from the Windows 2000 CD.
> > > >
> > > > As suggested earlier BTW, before a troll polluted the thread.
Who are you calling a troll, troll?
Are you just so chicken that you don't dare name him in case he may
be just right and you can just say: No, I disn't mean him, I meant the
other guy.
> > >
> > > That's _if_ the repair installation (a) behaves and (b) fixes
> > > the problem. I've had it (a) trash the original installation and
> > > (b) go in apparently cleanly but not properly overwrite the disk
> > > drivers so you're back to where you started from.
> > >
> >
> > You are right in that a repair installation doesn't always fix all
> > faults on a corrupted disk. But when moving a working boot disk to
> > another system, I've used the technique successfully on several
> > occasions.
> >
> > The key point is that kernel of NT4, W2K, XP etc is customised to
> > the hardware at installation time eg a system built for a P4
> > processor won't run on an AMD Athlon.
> > So *just* replacing NTLDR is addressing a symptom,
It is not a symptom if it is essential to booting and most important of
all, *missing*.
> > unless the original and new mobos use the same CPU and chipset.
> > From the OP, the latter is apparently *not* the case.
OP didn't say anything about that. He actually barely said anything.
Not even whether he checked that the error message was correct.
>
> I'm not trying to be argumentative here, just pointing out that there is
> risk involved. If the repair installation doesn't get you going then you
> are back where you started from and little loss, but if it loses data
> that's another story entirely.
>
> And I don't believe that I have ever suggested replacing NTLDR as a
> solution--that doesn't help if you don't have the right drivers loaded.
I think you should let Eric out of your killfile.