Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


paxamime

Commands for working with Windows PE 3.0 and the new WAIK

Recommended Posts

For those that are looking at working with Windows PE 3.0 and have not had the time to research them you can check out the updated commands at OS Attack. I copied these commands from the post there.

http://www.osattack.com/windows/commands-f...-windows-pe-30/

Create winpe_x86 directory in C:\PE (this WILL delete it if the directory already exists):

rd /s/q C:\PE\winpe_x86

cd “c:\Program files\windows aik\tools\petools”

call copype.cmd x86 C:\PE\winpe_x86

Mount the WIM image:

cd “C:\Program Files\Windows AIK\Tools\x86\Servicing”

DISM.exe /Mount-Wim /WimFile:C:\PE\winpe_x86\ISO\sources\boot.wim /index:1 /MountDir:C:\PE\winpe_x86\mount

UnMount the WIM image commiting changes:

cd “C:\Program Files\Windows AIK\Tools\x86\Servicing”

DISM.exe /unmount-Wim /MountDir:C:\PE\winpe_x86\mount /Commit

Add packages into your WIM, this can be edited to only add in what you need to reduce the size of the WIM:

cd “C:\Program Files\Windows AIK\Tools\x86\Servicing\”

dism /image:C:\PE\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_OCs\winpe.cab”

dism /image:C:\PE\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_OCs\winpe-wmi.cab”

dism /image:C:\PE\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_OCs\winpe-hta.cab”

dism /image:C:\PE\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_OCs\winpe-legacysetup.cab”

dism /image:C:\PE\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_OCs\winpe-mdac.cab”

dism /image:C:\PE\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_OCs\winpe-scripting.cab”

dism /image:C:\PE\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_OCs\winpe-setup.cab”

dism /image:C:\PE\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_OCs\winpe-wds-tools.cab”

Check what packages are installed:

cd “C:\Program Files\Windows AIK\Tools\x86\Servicing\”

dism /image:c:\PE\winpe_x86\mount\ /Get-Packages

UnMount the WIM image discarding changes:

cd “C:\Program Files\Windows AIK\Tools\x86\Servicing”

DISM.exe /unmount-Wim /MountDir:C:\PE\winpe_x86\mount /discard

Create Windows PE ISO:

cd “C:\Program Files\Windows AIK\Tools\x86″

oscdimg -n -bc:\PE\winpe_x86\etfsboot.com c:\PE\winpe_x86\ISO c:\PE\winpe_x86\winpe_x86.iso

Share this post


Link to post
Share on other sites

1) You have to have WAIKv3 installed.

2) If you follow through the steps listed; 'call copype.cmd x86 C:\PE\winpe_x86' ; will create the file where it should be.

Share this post


Link to post
Share on other sites

Thanks for the reply.

I have "Windows Automated Installation Kit for Windows 7" installed and followed step 2 (I had C:\PE folder created in advance) . It didn't create boot.wim under C:\PE\winpe_x86\ISO\Sources.

As a result I'm unable to proceed further.

BTW, I'm using a WinXPPRO SP3 machine.

Edited by srivatsacsn

Share this post


Link to post
Share on other sites

Here's the output

C:\PE\winpe_x86\etfsboot.com

C:\PE\winpe_x86\ISO

C:\PE\winpe_x86\mount

C:\PE\winpe_x86\winpe.wim

C:\PE\winpe_x86\ISO\boot

C:\PE\winpe_x86\ISO\bootmgr

C:\PE\winpe_x86\ISO\EFI

C:\PE\winpe_x86\ISO\sources

C:\PE\winpe_x86\ISO\boot\bcd

C:\PE\winpe_x86\ISO\boot\boot.sdi

C:\PE\winpe_x86\ISO\boot\bootfix.bin

C:\PE\winpe_x86\ISO\boot\etfsboot.com

C:\PE\winpe_x86\ISO\boot\fonts

C:\PE\winpe_x86\ISO\boot\fonts\chs_boot.ttf

C:\PE\winpe_x86\ISO\boot\fonts\cht_boot.ttf

C:\PE\winpe_x86\ISO\boot\fonts\jpn_boot.ttf

C:\PE\winpe_x86\ISO\boot\fonts\kor_boot.ttf

C:\PE\winpe_x86\ISO\boot\fonts\wgl4_boot.ttf

C:\PE\winpe_x86\ISO\EFI\microsoft

C:\PE\winpe_x86\ISO\EFI\microsoft\boot

C:\PE\winpe_x86\ISO\EFI\microsoft\boot\bcd

C:\PE\winpe_x86\ISO\EFI\microsoft\boot\fonts

C:\PE\winpe_x86\ISO\EFI\microsoft\boot\fonts\chs_boot.ttf

C:\PE\winpe_x86\ISO\EFI\microsoft\boot\fonts\cht_boot.ttf

C:\PE\winpe_x86\ISO\EFI\microsoft\boot\fonts\jpn_boot.ttf

C:\PE\winpe_x86\ISO\EFI\microsoft\boot\fonts\kor_boot.ttf

C:\PE\winpe_x86\ISO\EFI\microsoft\boot\fonts\wgl4_boot.ttf

Share this post


Link to post
Share on other sites

In addition the output of "call copype.cmd x86 C:\PE\winpe_x86" is as follows:

C:\Program Files\Windows AIK\Tools\PETools>call copype.cmd x86 C:\PE\winpe_x86

===================================================

Creating Windows PE customization working directory

C:\PE\winpe_x86

===================================================

1 file(s) copied.

1 file(s) copied.

C:\Program Files\Windows AIK\Tools\PETools\x86\boot\bcd

C:\Program Files\Windows AIK\Tools\PETools\x86\boot\boot.sdi

C:\Program Files\Windows AIK\Tools\PETools\x86\boot\bootfix.bin

C:\Program Files\Windows AIK\Tools\PETools\x86\boot\etfsboot.com

C:\Program Files\Windows AIK\Tools\PETools\x86\boot\fonts\chs_boot.ttf

C:\Program Files\Windows AIK\Tools\PETools\x86\boot\fonts\cht_boot.ttf

C:\Program Files\Windows AIK\Tools\PETools\x86\boot\fonts\jpn_boot.ttf

C:\Program Files\Windows AIK\Tools\PETools\x86\boot\fonts\kor_boot.ttf

C:\Program Files\Windows AIK\Tools\PETools\x86\boot\fonts\wgl4_boot.ttf

9 File(s) copied

C:\Program Files\Windows AIK\Tools\PETools\x86\EFI\microsoft\boot\bcd

C:\Program Files\Windows AIK\Tools\PETools\x86\EFI\microsoft\boot\fonts\chs_boot

.ttf

C:\Program Files\Windows AIK\Tools\PETools\x86\EFI\microsoft\boot\fonts\cht_boot

.ttf

C:\Program Files\Windows AIK\Tools\PETools\x86\EFI\microsoft\boot\fonts\jpn_boot

.ttf

C:\Program Files\Windows AIK\Tools\PETools\x86\EFI\microsoft\boot\fonts\kor_boot

.ttf

C:\Program Files\Windows AIK\Tools\PETools\x86\EFI\microsoft\boot\fonts\wgl4_boo

t.ttf

6 File(s) copied

1 file(s) copied.

Success

Updating path to include peimg, cdimage, imagex

C:\Program Files\Windows AIK\Tools\PETools\

C:\Program Files\Windows AIK\Tools\PETools\..\x86

Share this post


Link to post
Share on other sites

An important note, in your copype command, you must specify a destination folder that does not already exist.

Share this post


Link to post
Share on other sites

Verified that the folder winpe_x86 doesn't exist when I call copype.cmd. But still I don't see boot.wim being created. So, should I create a boot.wim ?

Share this post


Link to post
Share on other sites

After you are finished with editing the winpe.wim in the base folder, you rename that to boot.wim and put it in the sources folder.

Share this post


Link to post
Share on other sites

Here are my commands and results.

C:\Program Files\Windows AIK\Tools\PETools>call copype.cmd x86 C:\PE\winpe_x86

===================================================

Creating Windows PE customization working directory

C:\PE\winpe_x86

===================================================

1 file(s) copied.

1 file(s) copied.

C:\Program Files\Windows AIK\Tools\PETools\x86\boot\bcd

C:\Program Files\Windows AIK\Tools\PETools\x86\boot\boot.sdi

C:\Program Files\Windows AIK\Tools\PETools\x86\boot\bootfix.bin

C:\Program Files\Windows AIK\Tools\PETools\x86\boot\etfsboot.com

C:\Program Files\Windows AIK\Tools\PETools\x86\boot\fonts\chs_boot.ttf

C:\Program Files\Windows AIK\Tools\PETools\x86\boot\fonts\cht_boot.ttf

C:\Program Files\Windows AIK\Tools\PETools\x86\boot\fonts\jpn_boot.ttf

C:\Program Files\Windows AIK\Tools\PETools\x86\boot\fonts\kor_boot.ttf

C:\Program Files\Windows AIK\Tools\PETools\x86\boot\fonts\wgl4_boot.ttf

9 File(s) copied

C:\Program Files\Windows AIK\Tools\PETools\x86\EFI\microsoft\boot\bcd

C:\Program Files\Windows AIK\Tools\PETools\x86\EFI\microsoft\boot\fonts\chs_boot.ttf

C:\Program Files\Windows AIK\Tools\PETools\x86\EFI\microsoft\boot\fonts\cht_boot.ttf

C:\Program Files\Windows AIK\Tools\PETools\x86\EFI\microsoft\boot\fonts\jpn_boot.ttf

C:\Program Files\Windows AIK\Tools\PETools\x86\EFI\microsoft\boot\fonts\kor_boot.ttf

C:\Program Files\Windows AIK\Tools\PETools\x86\EFI\microsoft\boot\fonts\wgl4_boot.ttf

6 File(s) copied

1 file(s) copied.

1 file(s) copied.

Success

Updating path to include peimg, cdimage, imagex

C:\Program Files\Windows AIK\Tools\PETools\

C:\Program Files\Windows AIK\Tools\PETools\..\x86

And here is the final Directory contants:

C:\PE\winpe_x86

C:\PE\winpe_x86\etfsboot.com

C:\PE\winpe_x86\ISO

C:\PE\winpe_x86\mount

C:\PE\winpe_x86\winpe.wim

C:\PE\winpe_x86\ISO\boot

C:\PE\winpe_x86\ISO\bootmgr

C:\PE\winpe_x86\ISO\EFI

C:\PE\winpe_x86\ISO\sources

C:\PE\winpe_x86\ISO\boot\bcd

C:\PE\winpe_x86\ISO\boot\boot.sdi

C:\PE\winpe_x86\ISO\boot\bootfix.bin

C:\PE\winpe_x86\ISO\boot\etfsboot.com

C:\PE\winpe_x86\ISO\boot\fonts

C:\PE\winpe_x86\ISO\boot\fonts\chs_boot.ttf

C:\PE\winpe_x86\ISO\boot\fonts\cht_boot.ttf

C:\PE\winpe_x86\ISO\boot\fonts\jpn_boot.ttf

C:\PE\winpe_x86\ISO\boot\fonts\kor_boot.ttf

C:\PE\winpe_x86\ISO\boot\fonts\wgl4_boot.ttf

C:\PE\winpe_x86\ISO\EFI\microsoft

C:\PE\winpe_x86\ISO\EFI\microsoft\boot

C:\PE\winpe_x86\ISO\EFI\microsoft\boot\bcd

C:\PE\winpe_x86\ISO\EFI\microsoft\boot\fonts

C:\PE\winpe_x86\ISO\EFI\microsoft\boot\fonts\chs_boot.ttf

C:\PE\winpe_x86\ISO\EFI\microsoft\boot\fonts\cht_boot.ttf

C:\PE\winpe_x86\ISO\EFI\microsoft\boot\fonts\jpn_boot.ttf

C:\PE\winpe_x86\ISO\EFI\microsoft\boot\fonts\kor_boot.ttf

C:\PE\winpe_x86\ISO\EFI\microsoft\boot\fonts\wgl4_boot.ttf

C:\PE\winpe_x86\ISO\sources\boot.wim

I would try uninstalling WAIKv3

Rebooting

Deleting the WAIK folder, and reinstalling waikv3

Share this post


Link to post
Share on other sites

Borrows from the installation guide distributed along with WAIK

Step 1: Set up a Windows PE build environment

In this step, you will create a directory structure that supports building a Windows PE image.

On your technician computer, click Start, point to All Programs point to Windows OPK or Windows AIK, right-click Deployment Tools Command Prompt, and then select Run as administrator.

The menu shortcut opens a command-prompt window and automatically sets environment variables to point to all the necessary tools. By default, all tools are installed at C:\Program Files\<version>\Tools, where <version> can be Windows OPK or Windows AIK.

At the command prompt, run the Copype.cmd script. The script requires two arguments: hardware architecture and destination location. For example,

copype.cmd <architecture> <destination>

where <architecture> can be x86, amd64, or ia64 and <destination> is a path to a local directory. For example,

copype.cmd x86 c:\winpe_x86

The script creates the following directory structure and copies all the necessary files for that architecture. For example,

\winpe_x86

\winpe_x86\ISO

\winpe_x86\mount

Copy the base image (Winpe.wim) into the \Winpe_x86\ISO\sources folder and rename the file to Boot.wim.

copy c:\winpe_x86\winpe.wim c:\winpe_x86\ISO\sources\boot.wim

Step 2: Add boot supportIn this step, you will add boot files to your Windows PE image. Before you can add files to the image, you must expand the image by using the DISM /Mount-Wim command.

At the command prompt, apply the image to the \mount directory by using the DISM tool. For example,

Dism /Mount-Wim /Wimfile:c:\winpe_x86\ISO\sources\boot.wim /index:1 /MountDir:C:\winpe_x86\mount

Add the appropriate boot support files and directory. For example,

copy c:\winpe_x86\ISO\bootmgr c:\winpe_x86\mount

mkdir c:\winpe_x86\mount\boot

xcopy /cherky C:\winpe_x86\ISO\boot C:\winpe_x86\mount\boot\

Step 3: (Optional) Add additional customizationsThis step is optional but recommended.

You can use ImageX to add applications and scripts to your Windows PE image that you might need while working in Windows PE.

ImageX is a tool for capturing and applying images during deployment scenarios. For example, at a command prompt, type:

copy “c:\program files\<version>\Tools\x86\ImageX.exe” c:\winpe_x86\mount

where <version> can be Windows OPK or Windows AIK and <architecture> can be x86, amd64, or ia64. In the previous example, the tools are not loaded into memory during a Windows PE RAM boot. The media must be available to access the tools.

Step 4: Configure BCD storeIn this step, you create a new boot-configuration file, called BCD, by using BCDEdit. BCD, which replaces Boot.ini, is a command-line tool designed to manage BCD stores. BCDEdit is available in Windows PE and Windows® 7. For example,

Del c:\winpe_x86\mount\boot\BCD

Bcdedit /createstore c:\winpe_x86\mount\boot\BCD

Bcdedit /store c:\winpe_x86\mount\boot\BCD -create {bootmgr} /d “Boot Manager”

Bcdedit /store c:\winpe_x86\mount\boot\BCD -set {bootmgr} device boot

Bcdedit /store c:\winpe_x86\mount\boot\BCD -create /d “WINPE” -application osloader

The last command returns a GUID value. Substitute this value for <GUID> in the following examples.

Bcdedit /store c:\winpe_x86\mount\boot\BCD -set <GUID> osdevice boot

Bcdedit /store c:\winpe_x86\mount\boot\BCD -set <GUID> device boot

Bcdedit /store c:\winpe_x86\mount\boot\BCD -set <GUID> path \windows\system32\winload.exe

Bcdedit /store c:\winpe_x86\mount\boot\BCD -set <GUID> systemroot \windows

Bcdedit /store c:\winpe_x86\mount\boot\BCD -set <GUID> winpe yes

Bcdedit /store c:\winpe_x86\mount\boot\BCD -displayorder <GUID> -addlast

Step 5: Create a bootable CD-ROM or DVD-ROMIn this step, you put a Windows PE RAM disk onto a CD-ROM or DVD-ROM. This option requires that you create an .iso file by using the Oscdimg tool.

On your technician computer, create an .iso file with the Oscdimg tool. At a command prompt, type:

oscdimg -n -m -o -bc:\winpe_x86\etfsboot.com c:\winpe_x86\mount c:\winpe_x86\winpe_x86.iso

To build an Advanced Micro Devices (AMD)—Extensible Firmware Interface (EFI) .iso file, use the following commands:

oscdimg.exe -bc:\winpe-x64-efi\efisys.bin -pEF -u1 -udfver102 c:\winpe-x64-efi\ISO x64-efi-winpe.iso

For Itanium-based architecture, replace Etfsboot.com with Efisys.bin. The Oscdimg tool is not supported on an Itanium-64 computer running Windows Server 2003.

Burn the image file (Winpe_x86.iso) onto a CD-ROM or DVD-ROM.

Share this post


Link to post
Share on other sites

In previous versions of the WAIK, including the one for Windows 7 beta, the C:\Program Files\Windows AIK\Tools\PETools\copype.cmd contained this line:

copy "%SOURCE%\winpe.wim" "%DEST%\%TEMPL%\sources\boot.wim"

The sources\boot.wim may have been automatically created to allow the rapid creation of an uncustomized Windows PE. For customized versions, the existing sources\boot.wim was deleted and replaced with the customized boot.wim file.

It seems that the WAIK for Windows 7 RC has dropped that line from copype.cmd, so that the boot.wim needs to be manually added to the sources folder. From 'Windows Preinstallation Environment (Windows PE) User's Guide' Build Date: 2009-03-04-182032:

The \ISO directory contains all the necessary files to build an .iso file by using the Oscdimg tool with the exception of a Windows PE image (boot.wim). You must create custom boot.wim using the default Windows PE image (winpe.wim) and then copy the boot.wim into the \ISO\sources folder.

Regards

Share this post


Link to post
Share on other sites
@Jazkal:

Thanks for your steps...

I tried the steps given in the help file for the new WAIK for Windows 7 RC and it works!!

So I've created a new topic with these steps. Please go through the same. Looking forward to your comments.

Link:

I am going to merge that post back into this one. The two topics too similar.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×