HP Server tc2120 HP Server tc2120 Network Operating System - Installation Guid - Page 24
Tip #4. Windows 2000 Recovery Options, Recovery option #1: Last known good configuration
View all HP Server tc2120 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 24 highlights
Tip #4. Windows 2000 Recovery Options In the event that the current installation of Windows 2000 fails to boot (this might happen after installing a new driver, component, software, etc), Windows 2000 provides the following recovery options to help you gain access to your Windows 2000 installation to replace damaged files and services for troubleshooting purpose. HP therefore recommends that you install the Recovery Console (see option 3 below) to enhance the system configuration. Recovery option #1: Last known good configuration • Activated by pressing F8 during the system process of Windows 2000 and selecting "Last Known Good Configuration" from the menu. • This boot mode is used in the case that the system fails to boot after installing a new software or driver. The system will use the previous registry setting to initialize and boot the system. Recovery option #2: Safe Mode Boot Activated by pressing F8 during the OS boot. It provides a minimal configuration with required drivers and services. The safe mode boot provides three options: 1. Standard safe mode boot. Provides no network services or drivers. 2. Networking disabled. Excludes network services and drivers. 3. Directory services restore mode. Brings system up with directory services disabled with the intent of recovering active directory. Safe mode boot is guided by the registry key hklm\CurrentControlSet\Control\SafeBoot with the use of the Minimal and Network subkeys. The IOManager and Service Control Manager look at the registry to load the driver and services. Such approach avoids loading a problematic driver or service. 4. Command prompt. Provides an alternate command shell CMD.EXE instead of the explorer. This is dictated by the registry key: hklm\system\CurrentControlSet\Control\SafeBoot\AlternateShell There is a Safe-Mode boot loophole. Since NTLDR loads "Boot Load" drivers, these drivers bypass the IO Manager's Safe Mode check. 24