My system environment:
Three operating systems: C: the disk is WINXP, D: the disk is win2003, and there is a redhad fedora core3. The guiding management software is gun grub.
I added a hard disk to the machine last Saturday. At that time, it was no problem to start the machine, but it could not be started the next day. The system reported an alarm and went on for a long time. At that time, it was determined that it was a memory failure, I started to think that the hard drive was installed yesterday when I encountered a memory stick, resulting in poor contact. I re-inserted the memory stick. The problem still persists, then, I inserted all the memory into the two slots of the CPU. The system did not trigger an alarm and the test passed. However, when I entered the operating system, all the three systems crashed after selecting the system menu and pressing enter, I thought the system crashed because WINXP and win2003 could not be started due to a change in the hardware environment of the system. There was no way. We only had to reinstall the system and fix it. We couldn't do it. We went to DoS and installed it on the hard disk.ProgramThis is okay, but after the system copies the file, the system will not see the installed operating system in the operating system menu during the restart, and the installation will be the same again; then try to install it on the XP system disc, an error occurred while copying the file: An Unexpected error (0) occurred at line 1768 in F: \ nt2 \ base \ Boot \ Setup \ arcdisp. c.
There is no way, but why is there no response from the hard disk installation? The reason should be that the write permission to the Master Boot zone was not obtained during system installation. I suspect that it was caused by grub and then dos, run fdisk/MBR. After restart, you cannot see the grub boot menu, but you can also see two windows system menus and install them from the hard disk, after the file is copied, you cannot view the installation system menu after restarting;
Go to DoS and run fdisk/MBR again. This time the system is out of the moles. You can see the Operating System Menu after you execute this command and restart it. For some reason, the fdisk/MBR command is executed, but the master boot area is not overwritten.
There is no way at last. I can only find the cause from the hardware. The most likely problem is the memory stick. Then I unplugged a memory stick and restarted the system. The system can actually go in. the culprit is the memory stick.
However, I don't understand why the two plug-ins are either warning or fail to enter the system. When the dual-channel plug-in is used, the two plug-in will not go to the CPU, but will not be able to enter the system or reinstall the system.