Dustin Cook <spamfilterineffect.see.sig@nowhere.com>, the
unlawfully-begotten gate-keeper, trivialised:

> Pennywise@DerryMaine.Gov wrote in
> news:1v1gi258g79rq9be6n8o2kk7db1hru0r5r@4ax.com:
>
>> Dustin Cook <spamfilterineffect.see.sig@nowhere.com> wrote:
>>
>>> Pennywise@DerryMaine.Gov wrote in
> news:gq88i2125vgm7l24pn1slksu7j8eobivc8
>>> @4ax.com:
>>>
>>>> "ninjutsu28@gmail.com" <ninjutsu28@gmail.com> wrote:
>>>>
>>>>> hi der was a sudden blackout at my place 4 lyk a minute..i was
>>>>> using da laptop at dat time, it was connected to a power point
>>>>> coz my battery was flat..anyways, when i boot it agen, it wont
>>>>> boot and dis message appears ""windows could not start because da
>>>>> following file is missing or corrupt:
>>>>> windows\system32\config\system. you can attempt to repair this
>>>>> file by starting windows setup using da original setup cd
>>>>> rom..any ideas? thnx
>>>>
>>>> That's a bad error, you can run a repair - reinstall or as a last
>>>> resort replace the registry hives.
>>>
>>> Bad error, not really. One corrupted file.
>>>
>>> See here:
>>>
>>> http://forums.pcper.com/showthread.php?t=384102
>>>
>>> Scroll down to this section:
>>>
>>> It's best to have a bartPE disc, you shouldn't have too much trouble
>>> locating one.
>>>
>>>
> # Now you need to find a fairly recent restore point: Inside the
> 'System Volume Information' folder, there will be one or more folders
> with a name similar to '_restore{A41FD8B9-27F4-4FC5-AE69-
> D3A03EA91657}'. These are Restore Points. Inside each of these are
> lots of folders titles 'RP?' ? these are repositories containing
> backups of system files that have been preserved periodically. Check
> the 'Date Created' properties on the 'RP?' folders. Don?t go for the
> newest one in case it also contains the problem. Go for the second
> oldest one ? write down the date and then open it. # Now you want to
> copy the registry files from there to your C:\Windows \bak: In the
> 'RP?' folder, you should see a sub-folder called 'snapshot'. You need
> to select and copy (do not cut!) the following files so you can paste
> them into C:\Windows\bak: _REGISTRY_MACHINE_SAM
> _REGISTRY_MACHINE_SECURITY _REGISTRY_MACHINE_SOFTWARE
> _REGISTRY_MACHINE_SYSTEM _REGISTRY_MACHINE_.DEFAULT # Now you need to
> rename the files that you?ve just copied to C: \Windows \bak. Make
> sure you?re in C:\Windows\bak!! Click on each one individually and
> then press F2 to rename them. Rename '_REGISTRY_MACHINE_SAM' to SAM
> Rename '_REGISTRY_MACHINE_SECURITY' to SECURITY Rename
> '_REGISTRY_MACHINE_SOFTWARE' to SOFTWARE Rename
> '_REGISTRY_MACHINE_SYSTEM' to SYSTEM Rename
> '_REGISTRY_MACHINE_.DEFAULT' to DEFAULT (no dot!)
>>
>> Better approach, I don't use restore points so wasn't aware of this
>> tactic (never look'd at the info stored).
>
> It's only viable if you use restore points.
>
>> I copied this to a text file for use later, of course I'll make it
>> look like I came up with it myself
>> Na, I'll tack your name to the bottom of it.
>
>
> No need man, It's a well known trick as far as I know in repair
> circles...

BWAHAHAHAHHAAHAHAHAH! 'as far as [you] know' - what a ****ing huge get-out
clause that is.

Anyone with half a brain can see it's a technical procedure, and anyone with
a brain can see the OP doesn't have the ****ing nous to carry it out,
therefore anyone with a brain would have advised the OP to do a repair
installation instead. As you can see, you are excluded from the set of those
with a brain.


--
alt.usenet.kooks - Pierre Salinger Memorial Hook, Line & Sinker:
September 2005 and April 2006

"K-Man's particular genius, however, lies not merely in his humour,
but his ability to make posters who had previously seemed reasonably
well-balanced turn into foaming, frothing, death threat-uttering
maniacs" - Snarky, Demon Lord of Confusion

Thou sow of lead. Thou despicable, spleeny dunghill.