Microsoft Windows opk (OEM pre-installation kit) official and winpe ISO Production
In the Microsoft opk toolkit, this disc is labeled as xxxopk_cn.
Of course, there are non-OEM Microsoft Windows pe cd labels xxxwpe_cn
At present, it is easy to get the opk tool because the Microsoft website has downloaded it.
:
Winpe 2004 (corresponding to Windows XP SP2) English version
Http://oem.microsoft.com/downloads/worldwide/OPK_XPSP2/xpsp2_2180_usa_x86fre_opk.zip
Winpe 2004 (corresponding to Windows XP SP2) Simplified Chinese version
Http://oem.microsoft.com/downloads/worldwide/OPK_XPSP2/xpsp2_2180_chs_x86fre_opk.zip
Winpe 2004 (Windows XP SP2) Traditional Chinese Version
Http://oem.microsoft.com/downloads/worldwide/OPK_XPSP2/xpsp2_2180_cht_x86fre_opk.zip
Winpe 2005 (corresponding to Windows Server 2003 SP1) English version
Http://oem.microsoft.com/downloads/worldwide/WinServer2003SP1_OPK/ensp1opk.zip
Winpe 2005 (corresponding to Windows Server 2003 SP1) Simplified Chinese version
Http://oem.microsoft.com/downloads/worldwide/WinServer2003SP1_OPK/chssp1opk.zip
Winpe 2005 (corresponding to Windows Server 2003 SP1) Traditional Chinese Version
Http://oem.microsoft.com/downloads/worldwide/WinServer2003SP1_OPK/chtsp1opk.zip
What is Windows PE?
Microsoft Windows pre-installation environment (Windows PE) is the minimal Win32 subsystem with limited services. It is based on the Windows XP Professional kernel running in protected mode. It includes running Windows Installation Program Install the operating system from a shared network, automate the basic process, and perform the most basic functions required for hardware verification.
By integrating windows pe into factory preinstallation, you can convert existing MS-DOS-based tools into a subset of 32-bit windows APIs, this allows you to maintain these applications in a standard development environment (such as Microsoft Visual Studio. These hardware diagnostics and other pre-installed utilities can then use the same signed Windows XP driver on your computer, and you no longer need to request an independent hardware vendor (ihv) provides a 16-bit driver.
Windows PE provides the following features:
As a hardware-independent Windows environment based on the X86 architecture, it does not occupy much of the bootable media and memory.
* A subset of Win32 Application Programming APIs and a command line interface (cmd.exe) that can run batch files ), windows Script Host (wsh), HTML Application (HTA), and ActiveX Data Object (ADO) used to create custom OEM tools or scripts are also supported ).
* Supports network access and standard windows network drivers, which can be used to copy images and test suites from the network through TCP/IP. You can easily add or delete network drivers in a Windows PE custom version.
* Supports a large number of storage drivers that use Windows 2000 or Windows XP drivers. When the new * device is available, you can easily Delete unnecessary drivers or merge other drivers into the custom version of Windows PE.
* Provides built-in support for creating, deleting, formatting, and managing NTFS file system partitions.
* The hardware diagnostic program can load and test specific hardware drivers.
* Supports the PXE protocol. If the computer supports PXE boot, the computer can be automatically started from the Windows PE image on the Remote Installation server (RIS. Windows PE images are not automatically installed on your computer's hard disk.
How to create a custom windows PE Image
1. What is an image? My personal understanding is that an operating system that has not been applied after generation.
I did it according to the Microsoft tutorial, and even changed the file name of the example. Why not use personalized names? Because a good style (fixed name) has a positive effect on productivity.
2. First, copy the winpe folder in the opk toolkit to c: \ (of course, it may not be C or work style) and rename winpe to build_x86
Then, put the product CD in the optical drive, and use the virtual optical drive (we recommend that you use the virtual optical drive with a low sound, prolong the service life of the optical drive, and save time)
Next, we need to use the command. Open "run" And Enter cmd.
Enter the command CD \ to return to the C root directory.
Enter CD build_x86 to enter the directory of the generation tool.
Next, enter the command mkimg. CMD [product CD location] [location of the generated windows PE image].
For example, I use Microsoft's virtual optical drive. My product CD is in Z: I want to generate a Windows PE image in C: \ winpe.
I should enter mkimg Z: \ c: \ winpe
OK.
Of course, you can also enter mkimg. CMD [product CD location] [location of the generated windows PE image] [ISO file name]
Generate an ISO file directly. However, considering teaching and intermediate customization, I will explain it step by step.
3. generate an ISO file
Using oscdimg to generate an ISO file is similar to cdimage. (It is very similar. I now give up cdimage when I do ISO, and my family is not good. Unknown)
Enter the command in the build_x86 directory.
Oscdimg-BC: \ build_x86 \ etfsboot.com-N c: \ winpe c: \ winpex86.iso
4. Write down the oscdimg command parameters below
It facilitates customization of special requirements.
Option operation
-Blocation specifies the location of the El torito Boot Sector file. Do not use any space.
Example:-BC: \ directory \ etfsboot.com
-D do not convert the file name of lowercase letters to uppercase letters.
-G uses the Universal Coordinated time instead of the local time for all files.
-H contains hidden files and directories.
-J1 encodes Joliet Unicode file names and generates DOS-compatible 8.3 file names in the ISO-9660 namespace. These file names can be read by Joliet or a traditional ISO-9660 system, but oscdimg may change some file names in the ISO-9660 namespace to comply with DOS 8.3 and/or ISO-9660 naming restrictions.
When the-J1 or-J2 option is used, the-D,-N, and-nt options are not applied and cannot be used.
-J2 does not use standard ISO-9660 names to encode Joliet Unicode file names (the joliet operating system is required to read files from the CD-ROM ).
When the-J1 or-J2 option is used, the-D,-N, and-nt options are not applied and cannot be used.
-Llabelname indicates the volume label. Do not use spaces between l and labelname.
Example:-lmylabel
-N long file names are allowed.
-NT allows long file names compatible with Windows NT 3.51.
-O optimizes storage by encoding duplicate files.
-Oi optimizes storage by encoding duplicate files. When comparing files, ignore the diamond compression timestamp.
-OS optimizes storage by encoding duplicate files. Duplicate files are displayed when an image is created.
-OIS optimizes storage by encoding duplicate files. When comparing files, ignore the diamond compression timestamp. Duplicate files are displayed when an image is created.
-TMM/DD/YYYY, HH: mm: SS specifies the timestamp for all files and directories. Do not use any space. The date format and 24-hour format are used. Any separator can be used between projects.
Example:-T12/31/2000, 15: 01: 00
-X calculates and encodes the autocrc value in the image.
Sourceroot is required. Specifies the location of the Windows PE file to be created in the. ISO image.
Image_file specifies the name of The. ISO image file to be created from the Windows PE file. There is also the latest winpe 2.0, but it has not been verified Http://download.microsoft.com/download/7/2/a/72ab61c6-4d8a-44b7-9353-38bf616df2c9/winpe.cab |
