makci的部落格

If you was one of the somebody that have accidentally installed the Windows XP SP3 system, and having this endlessly reboot, you have travel to the within your rights place!

Mostly that encountered this boot obstacle is the AMD-based computer near OEM imagery and chiefly HP upper side. For those that haven't install the Windows XP SP3 system, you obligation to double scrutinize you computing device basis is AMD variety or not (Most of the HP data processor with a serial of module figure that completed up next to a 'z' is grouped as an AMD-based electronic computer).

For those that simply installed, don't be panics. How can you place the problem? Easy, if you see a thwart slip-up written communication of 0x0000007e, later you unconcealed the principal difficulty.

Here is the tread to get rid off the mistake secret message of 0x0000007e:

1. Hit the F8 key at the restart stage, perfectly once you see the black Windows XP projection screen go up.

2. Next, select the "Disable unthinking start on set of connections failure" derivative.

There are cardinal kinds of options, whether:

o When you chose to dribble into the repossession console option, from a charge prompt, run the "disable intelppm".

o When you chose to dribble into unhazardous way option, consequently you can run the "sc config intelppm start= disabled" run.

o When you chose to lash out into WinPE option, you stipulation to stifle the registry manually.
This is the rung for redaction the WinPE manually:

1. Firstly, run the regedit.

2. After it, try to click on "HKEY_LOCAL_MACHINE".

3. Then, activity the File menu, and select "Load hive".

4. Is instance to sail to the "%systemdriver%WindowsSystem32Config" on the stone-dead system, don't even bury to quality the record label System.

5. Now, you can mark it something you can smoothly remember, specified as "horked".

6. OK, you involve to navigate to "horkedServicesIntelPPM".

7. Please siamese twin clink the "Start value" and set it to '4' as economically.

8. If you had did what I did and completely tattered things by running a saucer check, consequently you got to journey to "ControlSessionManager".

9. You have to unambiguous the BootExecute value, and manually plain out the autochk entries.

10. Finally, bring up the set of contacts.

Ta-da, beside the preceding solutions I regard as you can now bring up your computing machine. Everything will only be penalized.