"Kevin" <(E-Mail Removed)> wrote in message
news:00AA9155-74C1-49DE-8222-(E-Mail Removed)...
> Im working with a OEM XP install how worried should I be about the warning
> at
> the top of that article?
You should take it seriously. However, by OEM, you could mean two things
(at least). One is that you obtained an OEM copy of XP with a piece of
hardware and installed it yourself. This should be OK.
However, the other possibility is that you are using a system that came with
XP pre-installed and custom configured, for example an HP or Dell (I have
used this procedure sucessfully on a number of Dell systems).
In that case, you need to ask the OEM to determine if it's safe to use this
procedure. No-one else will really know.
HTH
-pk
> "Patrick Keenan" wrote:
>
>> "Kevin" <(E-Mail Removed)> wrote in message
>> news:401C6656-AC99-4DEC-BD8F-(E-Mail Removed)...
>> > Getting this when I try to boot my comp.
>> >
>> > Windows can not start...following file is corrupt or missing..
>> > \windows\system32\config\system
>> >
>> > You can attempt to repair...CD... press r for repair.
>> >
>> >
>> > I have the CD and get to the C:Windows\ > promt after choseing repair.
>> > What's the next set to get it to repair the file?
>>
>> You use the recovery console for the next number of steps described in
>> the
>> KB entry Microsoft has on this topic.
>>
>> You're describing a fairly ordinary circumstance, registry damage.
>>
>> It helps a lot if you've got a floppy drive, and if you are able to cut
>> and
>> paste the text in the KB entry into a text file using another working
>> machine, you can use the "batch" command as described to save a lot of
>> typing.
>>
>> http://support.microsoft.com/kb/307545/en-us
>>
>> HTH
>> -pk
>>
>>
>>