In the drop-down box select the " New Installation (Advanced) " installation type. Then there is a license agreement, you may have to enter the license code.
Next you are prompted to reformat the NTFS-style drive, select ' No ' to reuse the installation files for Recovery Console, minimize the variables and be able to reformat the system drive we want to fix later. .
You will then be asked if you want to update these installation files. Select ' No ' to proceed with the installation to review the update files in your local hard drive as you continue. These files cannot be located in other systems.
Finally the program will start copying the installation files to the root directory of your hard drive and finish the installation process successfully.
Get what we need
In this section, you should have a directory called $ WIN_NT $. ~ BT in the root directory of drive C, along with some common files used during other installation when rebooting the system. We will get these files and some files from the installation media. Then delete all the remaining unnecessary parts
Locate the $ WIN_NT $. ~ BT directory , and delete the bootsect.dat , migrate.inf , winnt.sif files in which the bootsect.dat file contains your hard drive parameter information. The presence of this file may be the underlying cause of unexpected problems with other systems. The other two files may be the cause of confusion for the installation process.
Locate the root directory in drive C and rename the $ WIN_NT $. ~ BT folder as i386 .
Create another folder in the root of drive C, called rcfiles . Move the i386 directory into rcfiles to get the c: rcfilesi386 path and move txtsetup.sif from the root directory of drive C to the new c: rcfilesi386 directory .
Reposition the installation media: In the root directory of the installation tree there will be two or more files starting with the characters: WIN51 . File names are important. For example, Windows XP Professional SP2 has WIN51 , WIN51P , WIN51P.SP1 , and WIN51.SP2 files . Windows Server 2003 Enterprise Edition SP1 has WIN51 , WIN51I , and WIN51I.SP1 files. You need to copy all WIN51 * files to the root of rcfiles created in the previous step.
Now transfer the entire rcfiles folder to the software control CD system.
At this point you have worked with the installation system. To start, first delete the file named $ ldr $ in C: directory . If there is a $ WIN_NT $. ~ LS directory in the root directory of drive C you can also delete.
You also need to edit the Windows boot.ini file to make Windows boot up again. First use the attrib command to wipe hidden and read-only system properties in the boot.ini file. Then copy the boot.bak file to boot.ini ( boot.bak is automatically created by the installation program). Then use the attib command to hide system, hidden and read-only files in the new boot.ini file.
C:> attrib boot.ini "s" h "r
C:> copy boot.bak boot.ini 1 file (s) copied
C:> attrib boot.ini + s + h + r
Those are the commands described. You should return to the regular installation system.
Build a CD
Use CD control software, create a new boot disk and add the rcfiles directory contents to the root of the CD file system. Do not add the rcfiles directory itself but its content.
As before, you must use the boot sector CD of Windows 2000 or Windows XP for the boot sector
If you create a standalone Recovery Console CD, you will need CD control software to file on the boot sector. Control software should be set to ' no emulation ' and there should be 2 sectors to boot. The screen below shows this in Nero Burning ROM.
Now create a CD or ISO file and then return the resulting product back to the test machine.
We can boot from CD. It will automatically start the post process. Press the 'R' key when prompted, you will enter the Recovery Console program. (You can also press the 'F10' key in the first screen to go directly to the human-machine interface).
The above process returns results in a basic installation CD about 7MB. This CD will only run the Recovery Console and will only run the most basic ones. You cannot install Windows with this CD. And you may also encounter some problems when using Recovery Console on another computer, which has a different type of hardware.
For example, if you've ever had to hold down the F6 key during a normal installation to load a storage drive, you need to do the same for the Recovery Console process. However, you can split the drives into your Recovery Console so they can be loaded using setupldr.bin when the CD starts to work.
This process is described in http://www.jsifaq.com/SF/Tips/Tip.aspx?id=6575 and http://gosh.msfnhosting.com/txtsetup.htm. A new copy of txtsetup.inf is placed in the root directory of drive C during the installation process. You have to put it in the i386 folder in the previous section. You can find it there when you need it.
Another problem may arise with systems that use virtual hard layers or different processors. For example, if your test system uses a single HAL processor, you will have problems with multi-processor HAL systems. etc. You can solve this problem by repeating the installation process on multi-style systems and merging the final installation process.
Another problem is that you can only create a Recovery Console on a CD. You cannot have different types for Windows XP Professional and Windows Server 2003, or the same version of Windows but different data packets. This is because all Reclaim Console will find the setup file in the i386 folder of the CD. But each file in a slightly different version. Therefore they cannot use the same Recovery Console CD.
Some people solve this problem by setting for each console featured in each version a separate folder. And then use an editor to change the sector boot of the CD and setupldr.bin search for their files.
Another thing to consider is that the Recovery Console is limited by default. However, you can remove some advanced components by editing some registers in your device.
Remember that Recovery Console tries to access the operating system installation files when it loads. That means including reading and writing. So this method works even when you boot Recovery Console from a CD.