However, he does read them all. If you've ever tried to fix a damaged Windows NT machine, you know how difficult it can be to do so. Part of the reason for this is that you can't work with Windows NT from a command-prompt level unless Windows NT is running.
Therefore, if you have a problem that prevents Windows NT from booting, you're pretty much stuck. Assuming that you have enough free hard disk space, you can always install a second copy of Windows NT and use this copy to fix the original copy. However, using this process can really put your skills to the test if you need to do anything more than just basic file manipulation.
Fortunately, Microsoft understands just how hard life can be. In this Daily Feature, I'll discuss the Recovery Console in detail and explain how to use it to fix various problems. What is the Recovery Console? The Recovery Console is a utility that's built into Windows This utility allows you to boot a PC containing a damaged copy of Windows to a command line.
From the command line, you may accomplish such tasks as enabling and disabling services and manipulating files, even if they're stored on an NTFS partition. When you see the Windows splash screen, close it. We should warn you that the Recovery Console requires 74 MB of hard disk space. If your copy of Windows is already damaged and you can't install the Recovery Console in this way, don't worry.
If Windows can't resolve a resource conflict, verify that the computer is configured to allow Windows to enumerate the devices in the computer. To change the computer's BIOS settings, see the computer documentation or contact your computer manufacturer. If the computer starts correctly, the device that you disabled may be the cause of the startup problem. For more information about how to configure devices in Device Manager, see How to use Device Manager to configure devices in Windows Server System Configuration Utility Msconfig.
You can use this tool to change the system configuration and troubleshoot the problem by using a process-of-elimination method. You must be logged on as Administrator or as a member of the administrative groups to use System Configuration Utility. If your computer is connected to a network, network policy settings may prevent you from using the utility. As a security best practice, consider using the Run as command to perform these procedures.
We recommend that you don't use System Configuration Utility to modify the Boot. To test the software loading process, make sure that the Load Startup Items check box is selected, and then select OK.
Clear all the check boxes under Selective Startup. INI check box. Repeat this process and select each check box one at a time. Restart your computer every time. Repeat the process until the problem occurs. When the problem occurs, select the tab that corresponds to the selected file.
For example, if the problem occurs after you select the Win. The Startup tab lists items that load at startup from the Startup group, Win. To isolate problems by using the Startup tab, follow these steps. To start troubleshooting, select the first check box, select OK, and then restart the computer when you're prompted.
Repeat steps 5 through 8 for each service until the problem occurs. When the problem occurs, you'll know that the last service that you turned on is causing the problem. Note this service, and then go to step Select Enable All, the check box next to the faulty service, clear the check boxes of any other services that you noted in step 3, select OK, and then restart your computer. As a workaround, you can leave the faulty service turned off not selected. Contact the manufacturer of the faulty service for more assistance.
You may be able to determine more quickly which service is causing the problem by testing the services in groups. Divide the services into two groups by selecting the check boxes of the first group, and then clearing the check boxes of the second group.
Restart your computer, and then test for the problem. If the problem occurs, the faulty service is in the first group. If the problem doesn't occur, the faulty service is in the second group.
Repeat this process on the faulty group until you have isolated the faulty service. Note any items that aren't selected. You might have to expand some items such as [drivers] to determine whether any subitems aren't selected.
When the problem occurs, you'll know that the last item that you turned on is causing the problem. Note this item, and then go to step Select Enable All, clear the check box next to the faulty item, clear the check boxes of any other items that you noted in step 3, select OK, and then restart your computer.
As a workaround, you can leave the faulty item turned off not selected. If it's possible, contact the manufacturer of the faulty item for more assistance. You may be able to determine more quickly which System. Divide the items into two groups by selecting the check boxes of the first group, and then clearing the check boxes of the second group.
Repeat this process on the faulty group until you have isolated the faulty System. You might have to expand some items such as [OLFax Ports to determine whether any subitems aren't selected. Select Enable All, clear the check box of the faulty item, clear the check boxes of any other items that you noted in step 3, select OK, and then restart your computer. You may be able to determine more quickly which Win. Repeat this process on the faulty group until you have isolated the faulty Win.
Only system administrators and advanced users should try to change the Boot. Steps for troubleshooting Boot. The Recovery Console is a command-line tool that you can use to repair Windows if the computer doesn't start correctly. Use the Recovery Console if the Last Known Good Configuration startup option was not successful, and you can't start the computer in safe mode.
We recommend that you use the Recovery Console method only if you're an advanced user who can use basic commands to identify and locate problem drivers and files.
When you're prompted during text-mode setup, press R to start the Recovery Console. You can use the Recovery Console to perform the following actions:.
To confirm that your hard disk or file system isn't damaged, start your computer from the Windows Server CD, start the Recovery Console, and then use the Chkdsk command prompt utility. It may resolve your problem. We recommend that only advanced users or administrators use the Recovery Console. You have to know the password for the Administrator account to use the Recovery Console.
For more information about how to test and repair a damaged hard disk by using Chkdsk, see the "How to use the Recovery Console" and "How to use the Recovery Console Command Prompt" sections in the following article: How to install and use the Recovery Console in Windows XP. If Chkdsk reports that it can't access your hard disk, you may have a hardware failure. Examine all cable connections and any jumper settings on your drive. Contact a computer repair professional or the manufacturer of your computer for more assistance.
If Chkdsk reports that it can't fix all hard disk problems, your file system or MBR may be damaged or no longer accessible. Hmmm… i got the log file but it doesnt just seem to have a clear end where the problem is. Service Pack 2 4 24 SYS Loaded driver compbatt. SYS Loaded driver pciide. SYS Loaded driver fltMgr. SYS Did not load driver kbdhid. SYS Did not load driver eeCtrl. Doesn't help me. I can't enable boot logging without successfully booting, and I can't boot.
And I can't access the recovery console because the manufacturer set it up with a password and won't disclose the password to me. I can still access the disk, by booting into Linux.
Is there any way to enable boot logging by file-twiddling, without having to go into the recovery console? So where does Safe Mode get the info that it loads? I mean all the files it loads into memory, like mup. Is it in a file somewhere on the HD? If I could boot I wouldn't need the boot log.
So, i have a problem while booting windows vista home professional. None of safe modes work, and acctually none of any modes work! Just browsing this old thread. If anyone is in the same hole, and can access their disk via a linux live or other OS:. Find the file boot. It will repair the currrent corrupt system files that allow you to bootup. Yes, both windows xp with service pack 1 and 2, it works. If you dont have, you kaked, try borrowing an xp pocket xp from someone, it will only allow you to access your admin user control for you to backup your work.
Gud luck and ohhh, Stop drinking too much Savannah, drink beer, you wont forget what we were taught in class. So did anyone figure out where the place is, that Safe Mode goes to, to determine what files to load? So my computer says that BootLogging is enabled. But when I go to Event Viewer, it tells me to "save events as…" I try to, and it tells me that. I can't even log on now…. At first my battery was not good I change the battery every since all I get is F1 F2 F12 Boot and then I just did what you said about enable boot logging and it just goes right back to Windows XP, then the Dell Optiplex GX, shows the blue screen and keeps repeating the same thing.
I can't even get into the computer to go to the control panel or restore to an earlier time Please help me.
0コメント