O
Odie Ferrous
Eric said:
Eric,
There's help for people like you. Not sure where you can get it, but
it's out there somewhere.
Odie
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Eric,
There's help for people like you. Not sure where you can get it, but
it's out there somewhere.
Odie
E
Euan Kerr
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, unless the original and new mobos use the
same CPU and chipset. From the OP, the latter is apparently *not*
the case.
J
J. Clarke
Euan said: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, unless the original and new mobos use the
same CPU and chipset. From the OP, the latter is apparently *not*
the case.
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.
E
Euan Kerr
There is risk I agree and I back up the user data by mounting theI'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.
drive as a data drive on a working system if possible before
attempting it.
The NTLDR reference was about a solution proposed by anotherAnd 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.
poster. Sorry if I caused you confusion.
F
Folkert Rienstra
Euan Kerr said:I'm interested to learn how - please would you provide more details?
Never mind. Like a few others I spoke too soon. Unless the driver replaces
some file called by the partition bootsector code that then calls ntldr,
I was wrong.
Eric's suggestion about wrong CHS geometry sounds more plausible but
has 2 problems:
1) Why would system A not have a problem with the CHS geometry but B will.
Unless the MBR was altered intentionally (i.e., not an accident) that doesn't
make sense.
2) The bootsector code appears to use LBA, ie Int 13 ext, not regular Int13.
So most likely the directory got corrupted when the previous MoBo
died and ntldr not found as a result, which was Eric's other suggestion.
R
Rod Speed
Folkert Rienstra said:Never mind. Like a few others I spoke too soon. Unless the driver replaces
some file called by the partition bootsector code that then calls ntldr,
I was wrong.
Eric's suggestion about wrong CHS geometry sounds more plausible but
has 2 problems:
1) Why would system A not have a problem with the CHS geometry but B will.
Just because a different drive type entry is used in the two systems.
Unless the MBR was altered intentionally
(i.e., not an accident) that doesn't make sense.
Fraid it does.
The fix isnt hard tho, just use the AUTO drive type always.
2) The bootsector code appears to use LBA, ie Int 13 ext, not regular Int13.
So most likely the directory got corrupted when the previous MoBo
died and ntldr not found as a result, which was Eric's other suggestion.
That's just one of the possibilitys.
F
Folkert Rienstra
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.
It is not a symptom if it is essential to booting and most important of
all, *missing*.
OP didn't say anything about that. He actually barely said anything.
Not even whether he checked that the error message was correct.
I think you should let Eric out of your killfile.
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.
It is not a symptom if it is essential to booting and most important of
all, *missing*.
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.