Differences between startup and recovery units in Windows7

In the following illustration, the Setup screen for the Windows7 beta operating system and the 2003 operating system "startup and recovery" platform. On the left is the Windows7 test version of the operating system, and the right-hand one belongs to the 2003 operating system. As you can see from the graph, most of the features in the 2003 operating system are retained in the Windows7 operating system. But some adjustments are still being made. The following author will do some analysis of these differences to help you understand the WINDOWS7 operating system as soon as possible.

First, the operating system boot sequence.

In the startup and recovery management platform, the first step is to set the startup order of the operating system. If more than one operating system is installed within the user's computer, you can modify the boot sequence of the operating system in this startup and recovery platform. If you think of Windows7 as the default operating system, you can select Windows7 in this Drop-down list. In this platform, you can also set the time for the user to select in the operating System selection interface, which is the "time to display the list of operating systems" here. If you set this time to 0, the system defaults to the Windows7 OS when it is started, and does not give users the opportunity to choose.

As you can see from the diagram above, the biggest difference between Windows7 and XP is that there is an edited button in the XP operating system. But not in the Windows7 operating system. In the XP system, the selection settings for this system are saved in a boot.int configuration file. The system administrator can make changes through this graphical interface, or you can use this edit button to open the configuration file directly to modify it. However, in general, the author does not recommend that the system administrator (especially ordinary users) manually modify this profile, so as not to cause this configuration file corruption and can not start the operating system. Some features, however, need to be implemented by modifying this configuration file. When choosing an operating system in the startup interface, we want it to show no content that is not meant to be XP, but rather to display the operating system according to the user, such as "XP Test", and so on. In this way, users can see the name to understand the use of the operating system, which is conducive to their choice. At this point in the XP operating system you need to click the "Edit" button to open the configuration file, and modify the multi (0) disk (0) rdisk (0) partition (1) \windows= "Microsoft WINDOWS XP Professional "This content, change Microsoft Windows XP Professiona to XP test. The Edit button is canceled in the Windows7 operating system, possibly for the protection of this profile, and the user is not allowed to modify the profile manually.

Second, the system when the failure of processing.

What to do when the operating system fails for some reason during use or startup? This applies to the Windows7 and XP operating systems. And as you can see from the graph above, they are using a similar scheme. But the solutions they recommend are different.

In an XP or 2003 operating system, when a system failure or other problem results in a system failure, the system can take three solutions, either to write the event to the system log, to send an administrative alert, or to restart automatically. If the system is written to the system log, the system administrator can view the contents of the System log through Event Viewer to see what causes the system to fail. If you choose to restart automatically, the operating system automatically restarts to fix the associated errors when the systems fail to run. If set to send administrative alerts, it means that a warning message is sent to the system administrator when a Stop error occurs on the system. In these three solutions, writing the events to the System log and automatically restarting them has been successful in both XP and 2003 operating systems. But the ability to send management alerts doesn't seem to have much practical value, or it doesn't work at all. I originally thought in the Windows7 will be perfect for this solution, but did not think in the Windows7 operating system, unexpectedly put this function directly deleted. This surprised me. As you can see from previous Microsoft Official documents, the solution to this system failure is very useful. If the Microsoft operating system as a server, then when the server failed to die when the system administrator can be the first time to understand this information. The system administrator needs to know this information, regardless of whether the server is automatically started and fixes the error. This allows the system administrator to take early action to eliminate errors and prevent frequent operating system failures due to similar causes. The author of why in the Windows7 operating system to remove this feature is not very clear (is it because the technical constraints can not be achieved, simply give up?), but I still look forward to the introduction of the formal version of the program can be perfected.