| Back to logs list
145462 2009 年 07 月 08 日 21:26 Reading (loading. ..) Comments (1) Category: Computer Applications
a , windows xp installation disk boot process
the most widely used in the original xp installation disk, it is necessary in this brief description of the startup process.
disc boot information boot.bin (CD-ROM is written to guide the track) boot CD started, call the CD-ROM: i386 setupldr.bin and ntdetect.com text configuration files according to winnt.sif file and installed to detect system is installed to the hard disk.
Second, WIN_PE_LOADER CD boot process
(a) WIN_PE_LOADER file list
PE after all, is a subsidiary of MS products, including the following documents (one for each XP startup disk that several files):
1. PEBOOT.BIN; 2. SETUPLDR.BIN (PELDR); 3. NTDETECT.COM ;; 4. WINNT.SIF (WINNT.XPE) must be placed in the root directory;
Also included WINPE
the ISO file WINPE.ISO,
chi pink dazzle limited edition, this file is compressed CAB can still be PELDR call.
specific boot process: PEBOOT.BIN in the production of CD-ROM CD-ROM guide is written when the track starts the disc called CD: I386 SETUPLDR.BIN find the root directory of the WINNT.SIF,
Chi dazzle flat iron, according to the text in WINNT.SIF configuration information and to find WINPE.ISO load a RAM disk WINPE.ISO X:. In the process, requiring WINNT.SIF (WINNT.XPE) must be placed in the root directory. SETUPLDR.BIN (PELDR) and NTDETECT.COM must be in the same directory, if two files on the wxpe to this directory, you must also modify the content of setupldr.bin peboot.bin and through which ASCII editor i386 into wxpe; Similarly, if the need to modify the winnt.sif (winnt.xpe) file names have to go through this approach to modify the content of setupldr.bin.
(b) WINNT.SIF (WINNT.XPE) of the text example:
[SetupData]
BootDevice =
BootPath =
OsLoadOptions =
said winPE.iso line 3 which is activated after the RAMDISK.SYS and other documents included in the WINPE.ISO the position;
line 4 that WINPE.ISO file on the CD / hard drive called the location, can be similar to the hard disk partition boot.ini ntldr in the representation of cross-partition call
example: OsLoadOptions =
(c) Other instructions
document also mentioned a number of PE XPEMENU.INI (PEinstall.log) files. It must be stored in the root directory called pe file pe external program is used to describe the location of the old moto pe example external program must be placed on a disk's root directory, if the external program and winpe.iso pe not in the same partition,
CHI Turbo Ceramic Flat Iron, you must by xpemenu.ini (peinstall.log) for guidance. However, in the CD, there must not worry about this file, because all the files to be placed in a dish - CD-ROM.
Third, through the c: drive (hd0, 0) NTLDR (NT/2K/XP/2K03) method call winpe.iso
(a) the need to use third-party boot loader here grub4dos several files:
Grldr (Chinese version) menu.lst (boot menu configuration file) c:
fonts (Chinese characters) c: winpe
GRUB is a very good software, it can be loaded multiple systems, and can guide the startup files in multiple formats. Basically to meet the current production system boot / CD boot area needs.
(b) peldr file
Setupldr.bin (peldr) c: winpe
winnt.sif (winnt.xpe) c:
(c) winpe.iso and its subsidiaries file
Winpe.iso ; c: winpe
Peinstall.log (xpemenu.ini) c:
(d) The NTLDR
NTLDR is NT/2K/XP/2K03 system is installed directly on the system disk to install MS boot loader, the installation process in the system tray BOOT area is called the information stored in the NTLDR boot to CD-ROM guide rail as the content stored in CDBOOT.BIN the same. When the hard disk drive after the first call is the BOOT zone information, and then boot the computer code through this guide to find C: NTLDR and then further stimulate the NT Series systems.
NTLDR specifically include the following documents need to be stored in the root directory of boot
NTLDR NTDETECT.COM BOOT.INI ; BOOTFONT.BIN
which NTLDR BOOT.INI boot device is the text configuration file, the system used by NTLDR boot NT/2K/XP/2K03.
NTLDR BOOT area can also call the information file or other device attached boot to boot into another system.
(e) the contents of the configuration file:
1. Winnt.sif (winnt.xpe) reads as follows:
[SetupData]
BootDevice =
BootPath =
OsLoadOptions =
2. Menu.lst as follows:
color black / cyan yellow / cyan
timeout 10
default call WINXPE iso
fontfile (hd0, 0) / winpe / fonts
title search the hard disk NTLDR boot MS_WINDOWS NT/2K/XP/2K03
find - set-root / ntldr
chainloader / ntldr
savedefault - wait = 2
title called WINXPE iso
root (hd0, 0)
chainloader (hd0, 0) / winpe / setupldr.bin
savedefault - wait = 2
title restart
savedefault - wait = 2
reboot
Turn off the computer
title
Halt
savedefault - wait = 2
3.xpemenu.ini (peinstall.log) file name in the configuration about the decision by the winpe.iso
as follows:
WinPE image file = WinPE.IS_
WinPE plug location = c:
WinPE installation date = 2007-11-14 Wednesday 9:01:32.17
4. Boot.ini file,
CHI Pink Dazzle Flat Iron, add the following line:
c: grldr =
through the c: drive (hd0, 0) MSDOS_IO.SYS method call winpe.iso
(a) the need to use third-party boot loader here grub4dos several files:
Grldr.exe (Chinese version), menu.lst (boot menu configuration file), fonts (Chinese characters) these three files in c: grub
(b) peldr file
Setupldr.bin (peldr) c : winpe
winnt.sif (winnt.xpe) ; c:
(c) winpe.iso and its subsidiaries file
Winpe.iso ; c: winpe
Peinstall.log (xpemenu.ini) c:
(d) The NTLDR
winpe, after all, perhaps because the product after nt level, so its boot on the hard disk root directory exists when the need for the following two files ntldr
NTLDR TDETECT.COM
(V ) on the io.sys msdos
Msdos produced by Microsoft dos improved system integration, the core of the boot file is c: io.sys, there is a command parsing file C: COMMAND.COM and a central configuration file C: MSDOS.SYS . The startup configuration file includes c: config.sys and C: autoexec.bat. WIN9X once popular series of the moment is actually using this system as the underlying operating system. MSDOS MSDOS system is also installed by the time the hard disk boot sector (BOOT area) to write some code, and then boot the computer at boot time to find C: IO.SYS to start MSDOS's.
us achieve by configuring the Config.sys file via msdos start grub4dos
(f) the contents of the configuration file:
1. Winnt.sif (winnt.xpe) reads as follows:
[SetupData]
BootDevice =
BootPath =
OsLoadOptions =
2. Menu.lst as follows:
color black / cyan yellow / cyan
timeout 10
default 0
fontfile (hd0, 0) / grub / fonts
title normal access to MSDOS
quit
savedefault - wait = 2
title called WINXPE iso
root (hd0, 0)
chainloader (hd0, 0) / winpe / setupldr.bin
savedefault - wait = 2
title restart
savedefault - wait = 2
reboot
Turn off the computer
title
Halt
savedefault - wait = 2
3.xpemenu.ini (peinstall.log) file name in the configuration about the decision by the winpe.iso
as follows:
WinPE image file = WinPE.IS_
WinPE plug location = c:
WinPE installation date = 2007-11-14 Wednesday 9:01:32.17
5. Config.sys file, make sure the following line at the top:
DEVICE = C: GRUB GRUB.EXE - CONFIG-FILE = c: grub MENU.LST
five runs in the U disk WINPE.ISO
In fact, at this point, through the U drive start WINPE should be very simple, as long as U disk formatted HDD format and then import the NTLDR boot loader or MSDOS core system, and then III or IV according to the previous content operation can be realized.
of course,
chi pink dazzle hair straightener, some hardware support,
cheap chi flat iron, such as: BIOS to support the HDD in the boot, U disk into a boot disk to support the production and so on.
---------------( End)