A win2k to start the wrong case!

Today, when I was preparing to format my NTFS partition, I accidentally had 98 C: the grid dropped, and I went into a sleepless night!
At first 2000 in also can't go in, but with Win2000 reinstall when found that the monitor will appear blue screen error, not to change the disk, it is estimated that the registry information is wrong! So to find Win2000 boot disk to be able to start normally, but to the High-profile installed Win2K is prompted to find the optical drive (note my CD drive is a SCSI port). There's no way to find it. WinME boot disk boot to have CDROM dos, again fdisk, good heartache (98 of some documents and information are all hungry play out). This thought that because the CD can be launched from the Win2000, but did not think the blue screen error. There is no way to dismantle the hard drive is in trouble, so find a WinME plate WinME, now WinME installed, because it can be installed 2000 bar, but the CD in a blue screen reappear, is really defeated. Why is this happening?
I can't think of a solution!
A user introduces the following article:
In theory, as long as the software will have bug,win2000 is no exception, for Win2000 can not start the failure of the general may be divided into two situations: one is Win2000 can guide, but can not log in normally, the screen has error message, and the second is Win2000 can not guide, When you choose to start Win2000, you enter the Win9x or DOS state, or you display an error message. Knowing how to start the Win2000 process is very helpful for us to solve the problem that cannot be started. Win2000 specific start-up process is roughly divided into the following four steps: The first step: the Power of self test. Step two: Load the master boot record into memory, the master boot record looks for the partition boot table, and loads the boot sector on the active partition into memory. Step three: Initialize the NTLDR from the boot sector. Step Fourth: If you have a SCSI device, NTLDR will NT-BOOOTDD. SYS loads into memory and runs NTLDR read boot. INI file, and then display the boot menu. If you select Win2000, NTLDR runs NTDETECT. COM detects computer hardware devices and saves the results to the registry and finally loads the NTOSKRN1. EXE, HAL. DLL and other file and device drivers, the boot process is complete. If you choose Win9x or DOS, run Bootsect. Dos to start the Win9x or DOS operating system. For the first case, the cause of the failure is mainly caused by the registry error, we can restart the machine, press F8, the Win2000 System boot menu, select "Last Known Good Configuration", the system will automatically choose to use the last normal boot registry to start. If you have started more than once and cannot boot properly, you can choose Safe Mode from the system boot menu and the registry will be automatically repaired, and you can choose the Normal startup mode after Safe mode starts successfully. For the second case, the cause of the failure is mainly caused by a corrupted system file. We can use the "Install boot Disk" to start the machine, when the "Welcome to the Installer" interface appears on the screen, press the "R" button to select "Repair with the emergency repair process." After pressing the "R" key, there are two options for "manual repair" and "auto Repair". The system defaults to "Check startup Environment", "Verify Win2000 System Files", "Check boot Sector", whether you choose either "Manual repair" or "automatic repair", you need to provide Win200 "Emergency Repair Disk", if there is no " Emergency Repair Disk, you can press the "L" key to automatically find the hard disk's Win2000 system files. After the repair process is complete, reboot the machine to reboot and allow the user to log in to the Win2000 as it was originally configured. If we have a dual system installed, generally there will not be two systems crashing at the same time, unless the C disk boot sector is corrupted. We can go into Win9x or DOS directly execute win2000 installation file Setup. EXE, directly select the Repair function to the Win2000 system integrity repair. In addition, the author found in the practical application, Win2000 can not start the fault is mostly caused by user misoperation, accidentally deleted the hard drive boot partition ntldr, boot. INI, Ntde-tect. COM, Bootsect. Dos and other files, resulting in the system can not automatically boot. Although it can be solved by the above method, but too cumbersome. As you can see from the Win2000 boot process described above, once Win2000 is installed, it generates NTLDR and boot in the root directory of the boot partition on the hard disk installation. INI, Ntdetect. COM, Bootsect. Dos and other files, they are responsible for the system to complete the boot. If these files are corrupted, Win2000 will not be able to start. Therefore, we can complete the Win2000 installation successfully, following the production of four "Installation Guide disk", an "Emergency Repair Disk", but also need to make up an "emergency boot Disk", when the system does not start, you can use it to start and repair. The production method is as follows: first, format a sheet of 3 under Win2000. 5-inch floppy disk, and then copy all files from the Win2000 system that may exist under the root directory of the hard disk primary boot partition to the floppy disk. Note: These files have properties such as implicit, read-only, system, and so on. Once the boot file in the Win2000 is corrupted, causing the system to fail to boot automatically, you can use the "Emergency Boot Disk" to boot, and after the successful boot, copy all the files on the floppy disk to the root of the hard drive's primary boot partition, so you can achieve the purpose of the quick fix system. This repair method is quick and convenient, and has high practicability.?