PE was originally in the XP era, but many administrators prefer to use third-party management and Installation Tools. however, the new windows PE (Version 2.0) is completely new. not only does it come with tools like imagex and system image Manager (SIM), but it is also directly inserted into the windows automatic installation Toolkit (waIk), becoming part of waIk and Vista.
How to obtain windows PE
To use Windows PE 2.0, you must have one of the following tools: Windows OEM pre-Installation Tool (wopk), waIk or Windows PE tool kit. unfortunately, this is a tool for commercial users, so it is not included in the Vista beta installation CD yet. however, due to a large number of enthusiastic enthusiasts, Windows automatic installation kit (waIk) has been widely used on P2P networks (illegal. in this article, I used waIk obtained from Microsoft through legal channels.
Find winpe on your computer
Once waIk is installed, winpe will be available in C:/program files/Windows AIK/tools. including the architecture folder (x86, IA64, and amd64), as well as the petools and servicing folders.
Build your own startup winpe 2.0 Environment
The next step is to create a real winpe tool based on your own needs. our practice is to use copype in the petools folder. CMD command. switch to this folder in the command line environment or start "Windows PE tool command shortcut" in "start-> Program-> Microsoft Windows AIK ".
Copype. the cmd syntax is "copype. cmd ", in this example, I use" copype. CMD x86 C:/temp/x86_pe ". the target Folder does not have to exist. It can be created automatically with this command. the file will be unlocked and copied to the correct directory structure-the entire process takes one or two minutes.
The result shows that the x86_pe folder contains a winpe. wim file; a mount folder, you can use imagex to load Wim; an ISO folder that contains all the files required to create a winpe ISO image, and a BIN file used for ISO startup.
The command line tool for ISO creation is the oscdimg in winpe tools. There are few optional parameters and the most important ones are:
- -B (select the location of the boot file)
- -N (long file names allowed)
- -O (ignore duplicate files to optimize storage-a cool feature in Wim format ).
So my final syntax is "oscdimg-BC:/temp/x86_pe/etfsboot.com-n-o C:/temp/x86_pe/iso c:/temp/x86_pe.iso ". the entire creation process is smooth and fast. I used Nero to create a boot disc and burned it into CD under Vista.
Start and use Windows PE 2.0
Windows PE 2.0 looks like the login interface of Vista, but replaces the login window with a command line window. you can do a lot of work here. The biggest benefit of winpe is that it runs under the lite version of Vista, so it supports reading NTFS partitions and is compatible with 32-bit and 64-bit hardware drivers, access the network and run 32-bit and 64-bit applications.
The Partition Number occupied by winpe is X:, and all other partitions can also be accessed. you can also MAP network drives, create physical or logical drives and partitions, format them, and reinstall Vista, all in the winpe environment.
Custom windows PE 2.0
Because Windows PE 2.0 supports all Wim standards, you can bind your own tools and applications and create your own winpe operating environment. you can customize deployment options, create installation directories, and use local media, network resources, and Windows deployment services... in short, it is everything. windows PE 2.0 offers surprising System Administrator mobility. the system administrator can complete many tasks that cannot be implemented in winpe. if you want to use winpe to deploy Vista, let's take a look at it. in short, the Windows Image Format (WIM) and XML standards used by PE make Vista installation and deployment the most advanced and complete among all Windows operating systems so far. (aoouch compilation)
Note: Due to restrictions of the cnbeta news publishing system, all the right slashes in the text are replaced with the left slashes.
News source:Apcstart.com
