Windows Preinstallation Environment [Thunder download]

游客，如果您要查看本帖隐藏内容请回复

辛苦的劳动...只为了你一个回帖:yct06

What is Windows PE?

Windows Preinstallation Environment (Windows PE) 2.0 is a minimalWin32 operating system with limited services, built on theWindows Vista kernel. It is used to prepare a computer for Windowsinstallation, to copy disk images from a network file server, and toinitiate Windows Setup.
Windows PE is not designed to be theprimary operating system on a computer, but is instead used as astandalone preinstallation environment and as an integral component ofother setup and recovery technologies, such as Setup for Windows Vista,Windows Deployment Services (Windows DS), the Systems Management Server(SMS) Operating System (OS) Deployment Feature Pack, and the WindowsRecovery Environment (Windows RE).
This topic includes:

• Benefits of Windows PE
• Common Windows PE Scenarios
• Windows PE Limitations
• Windows PE Dependencies
• Supported Drivers
• Technologies Related to Windows PE

Benefits of Windows PEWindows PEwas created to help original equipment manufacturers (OEMs) andcorporations boot a computer with no functioning operating system. Inthe past, OEMs and corporations often used an MS-DOS-based boot floppydisk to start a computer, and then either to:

• Connect to a network share where a Windows installation source or disk image was located.
• Troubleshoot and recover a copy of Windows that did not start.

However,an MS-DOS-based boot floppy disk has a number of limitations that makeit awkward to use for preinstalling Windows or recovering existinginstallations or data:

• No support for the NTFS file system.
• No native networking support.
• No support for 32-bit (or 64-bit) Windows device drivers, making it necessary to locate 16-bit drivers.
• Rudimentary support for custom applications and scripts.

Thelimitations of MS-DOS-based boot disks led Microsoft to developWindows PE, which is Microsoft’s primary tool for booting computerswith no functional operating system. Once you boot a computer intoWindows PE, you can prepare a computer for Windows installation andthen initiate Windows Setup from a network or a local source.Otherwise, you can service an existing copy of Windows or recover data.
BecauseWindows PE is based on the kernel for Windows Vista, it overcomes thelimitations of MS-DOS-based boot disks by providing the followingcapabilities:

• Native support for NTFS 5.x file systems, including dynamic volume creation and management.
• Native support for TCP/IP networking and file sharing (client only).
• Native support for 32-bit (or 64-bit) Windows device drivers.
• Native support for a subset of the Win32 Application ProgrammingInterface (API); optional support for Windows ManagementInstrumentation (WMI) and Windows Script Host (Windows SH).
• Can be started from different kinds of media, including CDs, DVDs, USBflash devices (UFD), and Windows Deployment Services (Windows DS).

Note

This section discusses the standalone version of Windows PE. Customizedversions of Windows PE that are used in other products and Windowstechnologies (such as Windows DS) may provide different functionality.For more information about using Windows PE in these environments,consult the relevant product documentation.

Common Windows PE ScenariosWindows PEis a modified version of the Windows operating system that is designedto support installing Windows and troubleshooting and recovering aninstallation that can no longer boot.

• Installing Windows Vista.Windows PE runs every time you install Windows Vista. The graphicaltools that collect configuration information during the setup phase arerunning within Windows PE. In addition, information technology (IT)departments can customize and extend Windows PE to meet their uniquedeployment needs. Windows PE also provides support for servicingWindows images.
  

  Important

  Windows PE supports the deployment of previous versions of Windows.Refer to your licensing agreement for restrictions or contact yourMicrosoft representative.

• Troubleshooting.Windows PE is useful for both automatic and manual troubleshooting. Forexample, if Windows Vista fails to start because of a corrupted systemfile, Windows PE can automatically start and launch the WindowsRecovery Environment (Windows RE). You can also manually startWindows PE to use built-in or customized troubleshooting and diagnostictools.
• Recovery. OEMs and independentsoftware vendors (ISVs) can use Windows PE to build customized,automated solutions for recovering and rebuilding computers runningWindows Vista. For example, users can start their computers fromWindows PE recovery CDs or recovery partitions to automaticallyreformat their hard disks and to reinstall Windows Vista with theoriginal drivers, settings, and applications.

Windows PE LimitationsWindows PE is a subset of Windows Vista, and has the following limitations:

• To reduce its size, Windows PE includes only a subset of the availableWin32 application programming interfaces (APIs). I/O (disk and network)and core Win32 APIs are included.
• To prevent its use as a pirated operating system, Windows PEautomatically stops running the shell and reboots after 72 hours ofcontinuous use. This time period is not configurable.
• Windows PE cannot act as a file server or terminal server. (Remote Desktop is unsupported.)
• Distributed File System (DFS) name resolution is supported for standalone roots only. Domain roots are not supported.
• The tested methods of gaining network connectivity to file servers areTCP/IP and NetBIOS over TCP/IP. Other methods, such as the IPX/SPXnetwork protocol, are not supported.
• All changes that you make to the Windows PE registry while runningWindows PE are lost the next time you restart the computer. To makepermanent registry changes, you must edit the registry offline beforestarting Windows PE.
• Drive letters are assigned in consecutive order as you createpartitions in Windows PE. However, the drive letters are reset to thedefault order when you restart Windows PE.
• Windows PE does not support the Microsoft .NET Framework or the Common Language Runtime (CLR).
• Windows PE does not include the “Windows on Windows 32” (WOW32),“Windows on Windows 64” (WOW64), Virtual DOS Machine (VDM), OS/2 orPOSIX subsystems.
• To install a 64-bit version of Windows you must use a 64-bit version ofWindows PE. Likewise, to install a 32-bit version of Windows, you mustuse a 32-bit version of Windows PE.
• Windows PE can be used to configure and to partition a computer's disksbefore starting Windows Setup. If any hard disks are converted todynamic disks with Diskpart.exe before you start Windows Setup, thenthose hard disks are recognized as "foreign" when the operating systemis installed, and any volumes on those hard disks will not beaccessible.
• Windows PE does not support applications packaged with Windows Installer (.msi).
• WIM File System Filter (WIM FS Filter) driver is not supported in Windows PE.

Windows PE DependenciesWindows PE depends on a number of Windows technologies to function properly.

• If you use Windows PE on a network, DHCP and DNS servers are useful, but not required.
• If you boot Windows PE from the network, you must use a Windows DS server.
• If you install Windows, you must run Windows Setup (Setup.exe in Windows Vista or Winnt32.exe for Windows Server 2003).
• If you automate Windows Vista installation, you must use an Unattend.xml answer file.

Supported DriversWindows PE 2.0 supports the following drivers:
1394.inf
acpi.inf
adp94xx.inf
adpahci.inf
adpu160m.inf
adpu320.inf
agp.inf
apps.inf
arc.inf
arcsas.inf
battery.inf
brmfcmf.inf
brmfcsto.inf
brmfcumd.inf
brmfport.inf
bthpan.inf
bthspp.inf
cdrom.inf
cpu.inf
dc21x4vm.inf
defltbase.inf
defltwk.inf
disk.inf
djsvs.inf
dshowext.inf
dwup.inf
elxstor.inf
errata.inf
fdc.inf
flpydisk.inf
fontsetup.inf
hal.inf
hdaudbus.inf
hidbth.inf
hiddigi.inf
hidserv.inf
hpcisss.inf
i2omp.inf
iastorv.inf
iirsp.inf
iirsp2.inf
input.inf
ipmidrv.inf
iscsi.inf
iteatapi.inf
iteraid.inf
keyboard.inf
lsi_fc.inf
lsi_sas.inf
lsi_scsi.inf
machine.inf
mchgr.inf
megasas.inf
megasas2.inf
mf.inf
mraid35x.inf
mraid35x2.inf
mshdc.inf
msmouse.inf
msports.inf
net44x32.inf
net8185.inf
netathr.inf
netb57vx.inf
netbc6.inf
netclass.inf
nete1e32.inf
nete1g32.inf
netefe32.inf
netip6.inf
netirda.inf
netloop.inf
netmscli.inf
netmyk01.inf
netnb.inf
netnvm32.inf
netrasa.inf
netrass.inf
netrast.inf
netrtl32.inf
netrtx32.inf
netsis.inf
nettcpip.inf
nettun.inf
netuli6x.inf
netvgx86.inf
netvt86.inf
nfrd960.inf
ntrigdigi.inf
nvraid.inf
pcmcia.inf
puwk.inf
ql2300.inf
ql40xx.inf
ql40xx2.inf
ramdisk.inf
sbp2.inf
sceregvl.inf
scsidev.inf
secrecs.inf
sisraid2.inf
sisraid4.inf
symc8xx.inf
sym_hi.inf
sym_u3.inf
tape.inf
tdibth.inf
tpm.inf
ts_generic.inf
ts_wpdmtp.inf
uliahci.inf
ulsata.inf
ulsata2.inf
umbus.inf
unknown.inf
usb.inf
usbport.inf
usbprint.inf
usbstor.inf
volsnap.inf
volume.inf
vsmraid.inf
wd.inf

Technologies Related to Windows PEWindows PEis closely related to a number of other Windows installationtechnologies, as well as several recovery technologies. Some of thesetechnologies, such as Windows DS and Setup for Windows Vista, includecustomized versions of Windows PE.
Windows SetupTobe faster and more efficient, Windows Setup uses Windows image (.wim)files to install Windows on a hard drive. Setup uses a customizedversion of Windows PE to start the computer and to copy Windows to thehard drive from .wim files.

Unattended SetupUnattendedSetup is a method of automating clean installations and upgrades withminimal administrator or technician interaction. It relies on an answerfile that you create and can be performed from the Windows product DVDor from a shared distribution folder.
Unattended Setup is particularly useful if you need to:

• Perform automated installations on computers that have heterogeneous hardware configurations.
• Perform automated installations on specific types of servers, such asdomain controllers, remote access servers, and servers that runCertificate Services or the Cluster service.
• Configure a wide range of operating system settings during an automated installation without using batch files and scripts.

Inaddition to these deployment solutions, unattended Setup is a usefulmethod of creating master installations for image-based and RISinstallations.
A common method to initiate an unattended Setup isto boot the computer by using Windows PE, and then launch Setup with ananswer file from a distribution folder on the network.

[ 本帖最后由 ~DeatHMooN~ 于 29-1-2009 06:09 编辑 ]

WIKIPEDIA

Windows Preinstallation Environment (WinPE) is a lightweight version of Windows XP, Windows Server 2003 or Windows Vista that is used for the deployment of workstations and servers. It is intended as a 32-bit or 64-bit replacement for MS-DOS during the installation phase of Windows, and can be booted via PXE, CD-ROM, USB flash drive or hard disk. Traditionally used by large corporations and OEMs(to preinstall Windows client operating systems to PCs duringmanufacturing), it is now widely available free of charge via the Windows Automated Installation Kit (WAIK).

OverviewWinPE was originally intended to be used only as a pre-installationplatform for deploying Microsoft Windows operating systems,specifically to replace DOS in this respect. In later versions WinPE has developed into a platform for the following uses:

• Deployment of workstations and servers in large corporations aswell as pre-installation by system builders of workstations and serversto be sold to end users.
• Recovery platform to run 32-bit or 64-bit recovery tools such as Sysinternals ERD Commander or the Windows Recovery Environment (Windows RE).
• Platform for running 3rd party 32-bit or 64-bit disk cloning utilities.

The package can be used for developer testing or as a recovery CD/DVD for system administrators. Many people[who?] on the Internet have created customized WinPE boot CDs and included other third-party applications for different uses.
Version 2.0 introduced a number of improvements and extended theavailability of WinPE to all customers, not just corporate enterprisecustomers by downloading and installing Microsoft's Windows AutomatedInstallation Kit (WAIK).
The current version is 2.1, based on the Windows Vista SP1 and Windows Server 2008 kernel.
It was originally designed and built by a small team of engineers inMicrosoft's Windows Deployment team, including Vijay Jayaseelan, RyanBurkhardt, and Richard Bond.[1]



WinPE VersionsThe following versions are known to exist:


Windows PE 1.0Built from the first version of Windows XP Professional.


Windows PE 1.1Built from Windows XP Professional with Service Pack 1 (SP1).


Windows PE 1.2Built from Windows Server 2003 family.


Windows PE 2004 (1.5)Built from Windows XP Professional with Service Pack 2 (SP2).


Windows PE 2005 (1.6)Built from Windows Server 2003 with Service Pack 1 (SP1).


Windows PE 2.0Built from Windows Vista,this version differs from previous versions in that it does not requirea source CD as the files are built into the initial installation of thetoolkit. This means that the download is now 900MB instead of the 60MBor so of the earlier versions. It is possible to modify the bootableimage created to contain a variety of plug-ins such as WMI access, Windows Scripting Host(WSH), additional drivers and other 32-bit applications (or 64-bit forthe 64-bit version). Other new features include the ability to use are-writeable RAM disk (WinPE 1.x versions used a read-only RAM disk), and the hot-plugging of extra peripherals such as USB flash drives.


Windows PE 2.1Built from Windows Server 2008, the same codebase as Windows Vista SP1.

Windows PreInstallationEnvironment 深入研究


Windows PreInstallationEnvironment（WinPE）直接从字面上翻译就是“Windows预安装环境”，微软在2002年7月22日发布，它的原文解释是：“Windows预安装环境（WinPE）是带有限服务的最小Win32子系统，基于以保护模式运行的Windows XPProfessional内核。它包括运行Windows安装程序及脚本、连接网络共享、自动化基本过程以及执行硬件验证所需的最小功能。”换句话说，你可把WinPE看作是一个只拥有最少核心服务的Mini操作系统。微软推出这么一个操作系统当然是因为它拥有与众不同的系统功能，如果要用一句话来解释，我认为与Win9X/2000/XP相比，WinPE的主要不同点就是：它可以自定义制作自身的可启动副本，在保证你需要的核心服务的同时保持最小的操作系统体积，同时它又是标准的32位视窗API的系统平台。当然，现在这么说也许难以理解，没有关系，下面让我们来仔细研究它。
WinPE概览
　　即使有刚才的解释，你一定还是对这个全新概念的Mini操作系统一头雾水，没关系，在这里我将演示一下其运行的全过程，相信看过之后你或许就会有大致的了解。大多数人获得的WinPE光碟（包括我手上这张ISO镜像光碟）应该是一张“Windows XPOPK”CD，意思就是Windows XP OEM预安装工具包CD。实际上，Windows XP OPK CD是WinPE32位版本的一个可引导副本，也就是说，这张CD已经是个用WinPE定义制作的操作系统了，我们可直接用它来引导系统。先看看这张CD的目录结构吧（图1），总共有352MB，是不是有些大呢？其实由于这是个副本（至少包含了不少驱动程序），大小是由当时自定义制作决定的，若是WinPE的32位非自定义版本，其在磁盘上的镜像大约为120MB。
　1.引导WinPE
　　笔者考虑到网络环境等问题，主要的使用环境是VMware虚拟机和Virtual PC虚拟机，不过这两种虚拟机环境与实际PC环境几乎没有区别（就是说如果你不清楚虚拟机也没关系，就当是在真实PC上直接运行）。
　　将BIOS中设置成光驱引导，并开始启动系统，当屏幕画面上出现“Press any key bootfromcd”时（图2），按任意键从光驱上的WinPE引导启动（图3、4）。如果你的存储设备驱动不被支持，在启动时按下F6键可加载特殊设备的驱动。当启动到桌面时系统会做一些如调整分辨率的工作（图5），最后打开默认的CMD命令行解释工具，大家看看，是货真凼档耐夹尾僮骰肪撑叮ㄍ?）。
　　可以看到桌面上空空如也，不要指望可以拿鼠标点来点去，毕竟是个什么应用程序都没有安装的最小化图形操作系统。但它确实是标准的视窗环境，光碟上带有记事本，在命令行下输入“Notepad”并回车就可打开（图7）；另外尽管光碟上带有的可执行的命令行工具有限，但明显可以自己添加，看看这是什么（图8）？没错，是我们最熟悉的扫雷游戏（现在知道题头所指了吧，呵呵），拿鼠标先玩玩吧，这是笔者从大家熟悉的WinXP操作系统中加入的（方法很简单，用ISO工具直接拷入刚才的镜像文件就可以了）。
　　那么还是先回到CMD命令行工具中吧。默认的目录是\I386\system32\，输入命令行“dir *.exe /w”可查看有哪些可运行的程序（图9）。下面我们实际研究一下对个人用户有实际意义的WinPE特性的操作。
　　在光碟镜像中可同时看到32位和64位操作系统的工具（图10），对于个人用户来讲，你可用它直接引导没有安装任何系统的机器，并在其上实现32位系统的许多功能，这在后面会一一道来。
　2.WinPE对网络的支持
　　刚才dir时我们看到了ping命令，熟悉这个命令的读者应该都知道，只有安装了TCP/IP协议才能使用，那么不管三七二十一，先来ping自己试试吧，在CMD中键入“ping127.0.0.1”，回车搞定（图11），显然是可ping通的，这证明TCP/IP协议确实已在运行。再试一试光碟上另一个命令IPConfig，键入运行（图12），看到IP地址已经自动分配好了。既然网络确实已经连接，那让我们来实际操作使用吧（这里可能有不少从视窗系统开始接触计算机的朋友会对操作不知所措，其实并没有想象中那么困难，你可以在CMD中使用命令工具带“/？”参数来查询具体使用方法，如果你机器上本来就装有XP，那么在帮助中心查询就更方便了，多实验一下，掌握命令行以后你会发现方便很多）。
　　现在我的物理机和虚拟机构成了一个虚拟网络，使用光碟镜像中的net命令，在虚拟机中键入“netview”查看已连接的服务器（图13），这里显示的服务器“XQ-B6QAS26953EC”，名字表示虚拟机已通过网络连接了我的物理机器。我的物理机器上有一个名为TUKU的文件夹已经共享，所以再键入“net usee:\\XQ-B6QAS26953EC\TUKU”，意思是将物理机器上的共享目录TUKU镜像为虚拟机器上的E盘（图14），成功后可在虚拟机里自由地访问共享目录（图15），这时就可通过这个来做远程安装等工作。net命令还有不少参数，自己可以查阅并多加尝试，才可以发挥WinPE强大的网络环境功能，如果只是简单地访问服务器，上面的两个命令参数基本足够了。不过这里要记住用WinPE的机器可访问其他操作系统的机器，而逆操作是不能的，这是由于WinPE本身的限制，我们后面再讲这个问题。事实说明，WinPE启动后就可以使用网络环境。
　　
　3.利用WinPE创建、删除、格式化和管理NTFS文件系统分区
　　对于个人用户来说这个功能很是实用和方便。但不少朋友在dir完以后就叫苦，怎么只有format.com，没有fdisk啊，根本没办法分区嘛。其实这是个误解，WindowsXP中针对磁盘管理工作有专用的命令行工具DiskPart.exe，它是一种文本模式命令解释程序，能让你通过使用脚本或从命令提示符直接输入来管理对象（磁盘、分区或卷），WinPE使用的当然也是DiskPart。
　　在CMD模式下键入“diskpart”并回车进入DiskPart命令行解释（图16）。键入“list disk”，显示有两块硬盘（图17），分别为磁盘0和磁盘1。键入“selectdisk=0”执行，意思是选择指定磁盘，并将焦点转移到此磁盘，接下来的操作就都是针对它的（后面的操作都是一样，在磁盘、分区或卷上使用DiskPart命令前，必须首先将对象列表，然后选择要给予焦点的对象，只有对象拥有焦点时，键入的任何DiskPart命令才对该对象进行操作）。键入“detaildisk”可以查看磁盘0的细节信息（图18），现在磁盘0整个是一个活动分区C，格式为FAT32，容量为16G。下面我们以实际操作将磁盘0分为两个区，分别为NTFS格式的8G主分区C和FAT32格式8G逻辑分区D，而将磁盘1整个转为FAT32格式的分区E来演示WinPE对磁盘的管理操作：
　　（1）执行“select disk=0”，将焦点转到磁盘0。执行“select partition 1”，将焦点转到磁盘0的分区活动C上面。
　　（2）执行“delete partition”将原来的分区C删除（图19）。
　　（3）执行“create partition primary size=8000”回车，在磁盘0上建立一个新的8000MB的主分区（图20），焦点会自动转到新建立的分区上。
　　（4）接着执行“create partition extended”回车，将磁盘0上剩余的磁盘空间建立为扩展分区（图21）。
　　（5）完成上一步后再执行“create partition logic”回车，将刚建立的扩展分区创建为一个逻辑分区（图22）。
　　（6）至此，我们就已经把原来一个活动分区C的磁盘0创建为有一个主分区和一个逻辑分区了（图23），不过这两个分区还没有驱动器号，执行“select partition 1”将焦点转到主分区1，然后执行“assignletter=C”（图24），将驱动器号C：分配给主分区。执行“active”回车将主分区设为活动使其可以引导系统（图25）。
　　（7）接下来执行“select partition3”将焦点转到逻辑分区，执行“assign”回车，意思是系统将下一个可用的驱动器号分配给逻辑分区，由于驱动器号D、E均被占用（D为磁盘1分区占用，E为光驱占用），所以系统将F分配给了逻辑分区（图26）。不过没关系，我们先不管驱动器号的顺序，到这里我们对磁盘0的操作就结束了，剩下的目标是将磁盘1的活动分区D转换为分区E。
　　（8）执行“select disk 1”将焦点转到磁盘1，执行“select partition 1”将焦点转到活动分区D。
　　（9）由于磁盘1的D分区是活动的主分区，所以设其驱动器号为E，显然是要将它重新建立为一个非主分区的驱动器，那么它就不会占据驱动器号D而将它让给磁盘0的逻辑分区了。执行“delete partition”删除原来分区D，执行“createpartition extended”将磁盘1上所有的磁盘空间建立为扩展分区。
　　（10）完成上步后再执行“create partition logic”将刚建立的扩展分区创建为一个逻辑分区（图27）。
　　（11）最后执行“assign”自动分配驱动器号，系统仍然把D分配给了它（不过在机器重新启动后系统会自动调整将D分配给磁盘0的逻辑分区，磁盘1的逻辑分区会使用驱动器E，而光驱就顺延到F了，重启一次系统这些改变都会自动实现）。
　　（12）现在我们对机器上硬盘的重新分区工作就结束了，执行“exit”退出DiskPart命令行解释工具，然后执行“format c: /fs:ntfs”，将刚才建立的DISK0主分区格式化为NTFS文件格式的分区（图28），同理执行“format d: /fs:fat32”、“format f:/fs:fat32”将分区D、F格式化（图29），我们最终的操作就完成了。
　　（13）完成后执行“exit”重新启动机器，可以再次进入“DiskPart”来查看分区情况是否正确（图30）。
　　上面的操作基本包括了对磁盘的创建、删除、格式化和管理，如果你再仔细读读帮助说明，保证你在掌握它强大的功能以后不再想使用Fdisk去管理磁盘。实际上你如果在使用WindowsXP，这些知识都非常实用。此外“DiskPart”工具最方便的地方是支持脚本，在这里就不详细说明了。
WinPE的限制
　　上面我们已经将WinPE特性的基本操作都实践了一下，应该可以体会到WinPE对个人的方便之处，但是就像上文所说的那样，WinPE只是有限功能的Mini操作系统，要正确使用WinPE，当然也要了解它的一些限制。
　　1.为了防止将它用作盗版操作系统，在连续使用24小时后WinPE将自动退出并重启。
　　2.你可从WinPE计算机通过网络直接访问服务器和共享。但不能从网络上的另一个位置访问WinPE计算机上的任何文件或文件夹。WinPE通过TCP/IP及其上的NetBIOS获得到达文件服务器的网络连接，不支持其他方法（如IPX/SPX网络协议）。
　　3.因为涉及反盗版，所以只能从Windows XP Professional CD建立WinPE的自定义版本。而不能从Windows XP Home Edition或Windows 2002 Server操作系统家族的任何成员建立。
　　4.WinPE太大，不能放在软盘上。WinPE仅包括可用Win32API的子集（包括I/O（磁盘和网络）和核心Win32 API）。如果Win32下运行的服务基于Win32API子集，则它在WinPE是否可用需具体分析。这里不详细列出WinPE不支持的API了，反正rundll32.exe和shell.dll等是不被支持的，想要在WinPE下面玩Quake的朋友还是趁早放弃。
WinPE的作用
　　不少朋友看到这儿无论是否有收获，肯定都会想WinPE到底对自己有什么明确的作用，这里不妨总结一二。
　1.方便易用的启动工具盘
　　通过刚才的叙述，大家可以看出，WinPE启动相当快捷，而且对启动环境要求不高；最可贵的是，虽然名为启动盘，其功能却几乎相当于安装了一个WindowsXP的“命令行版本”——别忘了网络支持哦。因此，对于个人计算机用户，只要将其刻录在一张光碟上，便可放心地去解决初始化系统之类的问题；而对小型网络环境（如网吧等）用户来说，这一功能尤其实用。
　　
　2.有趣的硬盘使用功能
　　自定义的WinPE不仅可放到那些可移动存储设备如CD上，还可以放在硬盘上使用。因为许多朋友会认为将WinPE的自定义版本放在硬盘上没有什么意义，其实不然。把WinPE放在硬盘上应该是最为有趣的地方，且不说你的操作系统损坏无法进入的情况下启动硬盘上的WinPE可以方便地修复，关键是由于WinPE在硬盘上，所以在WinPE环境下安装应用程序就有了可能。呵呵，撇开题外话不讲，这里看一下如何把自定义的WinPE放到硬盘上吧（只能在硬盘上放置WinPE的32位版本）。
　　首先要安装恢复控制台：
　　（1）将Windows XP Professional CD放在CD-ROM驱动器中，这里指定其为cd_drive。
　　（2）在命令行CMD窗口中运行cd_drive\i386\winnt32.exe /cmdcons。
　　然后将WinPE自定义可引导副本放置在硬盘上，如下操作：
　　（1）在目标硬盘上，创建“C:\Minint”的目录（这里必须将目录命名为“Minint”）。
　　（2）将WinPE“根目录\i386”下的所有内容复制到C:\Minint。
　　（3）从WinPE根目录下将Winbom.ini复制到目标硬盘的根目录。
　　（4）在目标硬盘上，将“C:\Cmdcons\txtsetup.sif”的只读属性改为读/写。
　　（5）在目标硬盘上，将“C:\Minint\txtsetup.sif”复制到“C:\Cmdcons”进行覆盖。
　　（6）重新启动目标计算机。在“引导”菜单上，选择引导到“命令控制台”，计算机将使用WinPE引导。
　　
　3.Windows XP OPK CD的本职工作
　　上面说了其实我们拿到的是WinPE的一个可执行副本，即Windows XP OPK（WindowsXPOEM预安装工具包）CD。从名字都知道它原来的本职工作是为了方便OEM工作的。如果你在Windows操作系统环境下打开光碟，它就会自动运行Autorun为你的系统安装一个“Windows安装管理器”的工具包（图31）。利用它，你可以轻易制造出带有计算机厂商OEM标志的Windows安装镜像。虽然这是Windows XP OPKCD的主要本职工作，但显然对我们个人没什么意义，当然，如果你想把手上的Windows安装CD都打上自己独有的印记，并在朋友的机器上安装时炫一下，那么使用它是个好主意。当然自己的“印记”绝非OEM标志那么简单，实际上你还可任意设定WinPE携带的软件，并可设置这些软件在WinPE启动时运行；理想的情形下你甚至可以为自定义的WinPE版本加上类似于Windows Explorer的图形外壳程序——要不怎么叫专为厂商OEM设计呢？
================================================================================
2、Microsoft Windows Preinstallation Environment (WinPE)微软官方主页链接
================================================================================
WinPE is a tool based on Microsoft Windows? XP Professional that allowsIT staff to build custom solutions that speed up deployment throughautomation so they spend less time and effort keeping desktops updated.WinPE can run Windows setup, scripts, and imaging applications.Enterprise Agreement (EA) and Software Assurance Membership (SAM)customers received WinPE in their October 2002 updates, and it willcontinue to be offered as a benefit of Software Assurance.
================================================================================
3、What's the Windows Preinstallation Environment (WinPE)?
================================================================================
John Savill
InstantDoc #38308
John Savill's FAQ for Windows   

A. WinPE is a minimal OS, based on the Windows XPkernel, that will replace MS-DOS during the initial OS installationstages beginning with the next Windows desktop OS, which is known asLonghorn. Recent alpha builds of Longhorn use WinPE, which provides aGUI environment during the entire installation instead of the oldtext-based screen prompts that are common during the initial setup ofearlier Windows installations. WinPE will also let the user enter thelicense key during the initial stage of the installation, rather thanforcing the user to wait until later in the installation process.
Click here to view image
Because WinPE is based on XP, this new minimal OS can
　　●create and format disk partitions for FAT, FAT32, and NTFS
　　●access file shares on an intranet and connect to as many as four file shares
　　●support all mass-storage drivers for XP and Windows 2000




以上资料来自baidu

没功都有劳...找个沙发坐下先...顺便申精:yct53
搞了几个小时...才搞定那些乱码...非常感动中:yct61

有什么用途的？:yct33

上面一大堆解释...=_=

太多啦。。懒去看。。。:yct33

你跑去楼下问foo最快:yct38

借个位子顶一顶:yct06