Say goodbye to Common Errors in Windows and Linux dual-system startup (1)

Most of the time, Windows and Linux operating systems can coexist on the same machine, which we usually call a dual system. After all, Windows and Linux operating systems are not brothers, and some problems may inevitably occur during installation and deployment. Even experts in this field sometimes encounter similar problems that are hard to solve.

1. After Linux is installed, the Windows operating system cannot start normally.

Under normal circumstances, if there is already a Linux System in the system, when installing the Windows operating system, the installer will automatically set the parameters required to start (that is, the startup List) add to the boot list. The system administrator no longer needs to perform maintenance. However, after the Windows operating system is installed, the startup list is damaged and the Windows operating system cannot be started normally. In addition, sometimes the system administrator may change the startup list, for example, setting the Windows operating system as the default startup operating system. However, after modification, the Windows operating system cannot be started normally. In this case, the system administrator needs to manually modify the startup list file to fix the startup error.

If you find that the Windows system cannot be started normally and the Linux system can be started normally, most of the reasons are caused by the startup list. To solve this problem, the system administrator needs to modify the/boot/grub/ment. lst STARTUP configuration file. As shown in:

The system administrator needs to add the Windows Startup LIST parameters in this file. However, the system administrator must run the grub-install/dev/had command to enable the configuration file. That is to say, only after running this command will the startup Item of the Windows operating system be added to the startup list.

However, sometimes the system administrator may not like the setting interface of the Linux operating system, but is familiar with the graphical startup list management interface of the Windows system. To this end, the system administrator wants to temporarily access Microsoft operating systems, such as XP, and then make changes. It is also feasible to achieve this requirement. The system administrator needs to press the C key when the system displays the multi-Start menu interface, and then the system will prompt the system administrator to enter relevant startup parameters. In this case, the system administrator can enter the startup parameters of the Windows operating system and enter the Windows operating system, such as XP. Note that the input parameters are only valid for the system to be started. If the startup configuration file is not manually changed after startup, this problem still occurs during the second startup. Therefore, you need to manually change these configurations after you temporarily enter the XP or Linux operating systems.

In fact, the GRUB file used by the system administrator is a system boot guide manager. It is the first program that runs after the computer is started (either Linux or Windows. It is used to load and transmit data to the kernel of the operating system. Once the kernel is mounted, the System Boot manager completes the task and automatically exits. At this time, the system will guide other content. For example, the system initialization and startup processes are completely controlled by the kernel. GRUB is the next well-known startup manager for multiple operating systems in Linux. It can be used to solve the startup problems of most Linux systems, including compatibility issues with Windows operating systems.

2. After Windows is reinstalled, the system cannot normally enter the Linux system.

If the system administrator installed the Windows and Linux operating systems on the host in advance, the Windows operating system may cause problems, such as viruses. The system administrator reinstalls the Windows operating system. At this time, it is likely that the Linux operating system cannot be normally accessed. This is mainly because when Microsoft reinstalls the operating system, it is possible to clear multiple boot loaders In the MBR. At this time, the system will not be able to continue using GRUB as the boot program, and the system administrator will not be able to smoothly enter the Linux system. In this case, the system administrator has a headache.