![]() ![]() You will see Errors that are specific to Safe Mode and don't give us the information we need- such as "DCOM didn't start. Try to find Error from the last normal Mode. When you do that, include information from this: You are looking for Errors that correspond to the time of the BSOD. Please copy your post above and start a new thread as requested. ![]() You should now be out of the SAFE MODE trap. Wait seven or eight minutes for Safe Mode to boot and to become stable.Īfter working in Safe Mode, restart in Normal Mode by doing the following:Ģ On the Windows taskbar, click Start -> Runģ In the open box, type the following text: msconfigĥ In the System Configuration Utility, on the BOOT.INI tab, uncheckħ Close all programs, then restart the computer ![]() To use the System Configuration Utility in staring Windows XP in Safe Mode.Ģ At the Windows taskbar, click Start > Runĥ In the System Configuration Utility, on the BOOT.INI tab, check /SAFEBOOTħ When you are asked to restart the computer, click Restart and go to Step 4 However this is a useful patch when all else fails and you are running out of time.Īlternately, here is a way, though a bit cumbersome, that will bring you out of the Symantec SAFE MODE Trap: you may have to use all the steps, or just the second half. This will take some time, and it will remove Service Pack 3 and some other updates. Boot normally, and wait until the next screens AFTER Repair Console for the screen which gives you the choice to depress "R" which will give you the opportunity to boot to Windows in a repair mode without removing or damaging any other files which are not Windows files. I would avoid going into Repair Console, but if you have the install CD, this would be a good time to go to repair. Can you describe more about ".some iexplore bugs."? Any chance those bugs are still in play? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |