Sheesh! He would do what you expect him to do in the Recovery Console
but he would do it in a GUI environment rather than at a command line
and he would have way more options available to him than the handful of
commands available in the Recovery Console!
John
If the OP doesn't know how to replace two system files what do you
think the chances are of coming up with an original XP installation CD
that matches his installation, downloading, building and creating a
Bart PE (or equivalent) CD on a functioning system, testing it,
successfully booting the afflicted system using it, navigating some
probably never seen before GUI and successfully locating and copying
two files - and how long will that take.
Will someone volunteer to walk the OP through using a Bart PE CD to
replace those two files?
Or what do you think the chances are of removing the afflicted HDD,
configuring it as a slave drive, moving it to another computer and
replacing the files and putting it all back together again? How long
will that take? What if it is a laptop and the drive is not easily
moved?
I also don't understand how to implement a System Restore on a system
that will not boot either, but that would be a good trick too and do
you really think SR will magically replace those two mismatched files
with XP versions?
Once booting into RC, replacing the two files is generally just
entering 2 commands. If you can type, you can do it with a fraction
of the effort and time.
So far, most people are able to follow simple directions to make a
bootable RC CD and that eliminates the need for any original XP media,
puzzling over some new GUI, or moving any hardware around. Yes - by
all means compose instructions on how to create and build a Bart PE
and replace those two files. No link was provided to Bart PE either,
so I will need all those instructions too. Pretend I know nothing
about any (equivalent) environment and get me started.
But the chances are also pretty good that there is something else
going on besides simply replacing two mismatched files, that is the
easy part. There is no notice of what provoked this action in the
first place. After replacing the two files the system still may not
boot and then the original problem can be investigated.