A technical white paper comparing WES7 and WES2009 in regards to building and deploying a fully-functional Windows Embedded image on a target device.

1. Implications of Migrating from WES2009 to WES7
in Embedded Applications
Kushal Koolwal
Operating Systems R&D Engineer, VersaLogic Corp.
kushalk@versalogic.com
1

2.  Introduction to WES7
 Methodology
 Differences
 Example: Adding ISA-based Serial Ports
 Implications
 Conclusion
2
Agenda

3. 3
 What is WES7?
– Latest in Windows Embedded Family
– Based on Windows 7 / Vista technologies
 Predecessors of WES7
– WES2009
– XP Embedded
– Both based on Windows XP technologies
Introduction to WES7

4. 4
 Target Platform
– Intel Montevina-based
embedded board
– Intel® Core™2 Duo (64-bit)
– I/O: USB 2.0, PS/2, PCIe, PCI, Mini PCIe, ISA, etc.
 Configuring and Building Images
– WES2009
– WES7
 What are the differences between the two?
 Derived Implications
Methodology

5.  1.0 Installation Requirements
 2.0 File System Support
 3.0 HAL Independence
 4.0 ACPI Support
 5.0 Toolkit
– Driver Support
 6.0 Image Building Model
– FBA vs. Configuration Passes
5
Differences

6.  7.0 Image Deployment
– Sysprep Image
– Other Deployment Methods
 8.0 Log Files
 9.0 Localization
 10.0 Image Management
– WIM, ImageX and DISM
 11.0 Application Development
– Dependency Analysis
6
Differences
(continued)

7. 7
Requirement WES2009 WES7
Development (Host) System
Host OS Windows XP/Vista Windows7/Vista
CPU Speed (min.) 1 GHz 1 GHz
RAM (min.) 512 MB 1 GB
.NET Framework 3.0 3.5 SP1
SQL Server Express 2005 or later N/A
Storage (min.) 5 GB 7 GB
Target System
Processor Architecture 32-bit only 32-bit and 64-bit
SMP Yes Yes
CPU Speed (min.) 728 MHz 1 GHz
RAM (min.) 256 MB 512 MB
Storage (min.) 126 MB 1 GB
Differences
1.0 Installation Requirements

8. 8
WES2009 WES7
Installs On FAT32, NTFS NTFS
Read/Write Support FAT32, NTFS FAT32, NTFS
Differences
2.0 File System Support

9. 9
WES2009
 Supports ACPI and non-ACPI
HALs
– ACPI Uni/Multi-processor PC
– Advanced Configuration and
Power Interface (ACPI) PC
– MPS Uni/Multi-processor PC
– Standard PC
Differences
3.0 HAL Independence
WES7
 No HALs. Just one HAL - Requires
APIC and ACPI v2.0+
 Common Image for different
architectures
– P4 – Single Core
– Core™2
– Intel Atom
 Separate image for 32-bit and 64-
bit architectures
 No support for non-ACPI HALs 
Upgrade hardware

10. 10
WES2009 WES7
Installs with ACPI Yes Yes
Installs without ACPI Yes No
ACPI Version Any v2.0 or greater
Differences
4.0 ACPI Support

11. 11
Pop Quiz
Question:
Based on what we just learned about ACPI and APIC support, let’s
say for example, why does a x86-based embedded board that
does have ACPI and APIC, but still does not support WES7
(though it does support WES2009/XPe)?
Answer:
ACPI < 2.0

12. 12
WES2009 WES7
Target Designer + Component Designer Image Configuration Editor (ICE)
Component Database + Repositories Distribution Share (32-bit/64-bit)
SLX (project file) Answer File (project file – xml based)
9000 drivers (as Components) 1000 Drivers
1000 OS Components 150 OS Feature Sets
Differences
5.0 Toolkit

13.  eCore Package (built-in)
– Boot critical and bus enumerator drivers
– 100 drivers
– Must have OS to boot
 In-Box Drivers (built-in)
 Out-of-Box Drivers (3rd
party)
– Imported drivers from .cab files
– INF-based drivers (.inf, .sys, .dll)
13
Differences
5.0 Toolkit: Driver Support

14.  $OEM$ Folders (3rd
party)
– MSI-based drivers
– Use “/quiet” option
14
Differences
5.0 Toolkit: Driver Support (continued)

15. WES2009 WES7

16. Image Building Model WES2009 WES7
(ICE/Advanced method)
WES7
(IBW/Express method)
1. System Analysis Tap.exe  Devices.pmq
 Import into TD
Tap.exe  Devices.pmq 
Import into ICE
1. Boot from WinPE IBW DVD
2. IBW runs tap.exe
3. IBW maps corresponding drivers from
DS based on tap file.
4. IBW gives option to select an
application template or manually select
Feature Sets and driver packages
from the DS.
5. A valid Answer File is created based
on the selection.
6. IBW starts assembling and building
the image.
2. Image Configuration Configured on developer
machine using TD
Configured on developer
machine using ICE.
3. Image Customization Using Component
Designer
Using ICE
4. Project File SLX file is ready Valid Answer File is ready
5. Image Building
(Image Builder in WES7
replaces winnt.exe and
winnt32.exe in WES2009)
Build on developer
machine using TD
Always build on target device
using IBW
6. Adding Components
Post-Build
Requires rebuilding of the
entire image
Can be added offline and
online using DISM
Can be added offline and online using
DISM
16
Differences
6.0 Image Building Model

17. 17
Pop Quiz
Question:
Do you see any major problems with WES7’s image building
process as compared to WES2009/XPe?
Answer:
Online Build Method - Target boards with low resources (CPU,
RAM) will take a very long time to build and deploy image.

18. 18
WES7
Image Builder
Logical Phases
Configuration Pass Executed
by IBW
WinPE Pass 1 windowsPE Yes
Pass 2 offlineServicing Yes
Pass 3 generalize No
Online Configuration Pass 4 specialize Yes
Pass 5 auditSystem No
Pass 6 auditUser No
Windows Welcome Pass 7 oobeSystem Yes
WES 2009
FBA phases
Description
0 to 8500 Reserved for FBA. System use.
8501 to 12,000 Any FBA commands that you edit or
define
12000 to 20,000 Reseal and Reboot for Cloning
20,000 Join a network domain at the end of
FBA
Up to 65535 For running commands, scripts,
applications, etc.
Differences
6.0 Image Building Model: FBA vs. Configuration Passes
WES 2009
Answer Files
WES 7
Answer File
Unattend.txt
One single Answer File
called “Unattend.xml” for
streamlined unattended
installation.
Sysprep.inf
Winbom.ini WINPE
Winbom.ini FACTORY
Winbom.ini OOBE
Oobeinfo.ini

19. 19
Differences
7.0 Image Deployment
WES2009
1. Build Image using Target Designer
2. Make target storage device (hard drive, CompactFlash, etc.) bootable
3. Attach the storage device on development computer
4. Copy build directory (C:Windows Embedded Images) to root of storage
device
5. Attach to target system and boot
6. FBA runs

20. 20
Differences
7.0 Image Deployment (continued)
WES7
1. Create Answer File using ICE
2. In ICE do Tools  Create Media  Create IBW Image from Answer File
3. Option 1: Make a bootable USB Flash Drive (UFD)
– Use diskpart.exe. No longer need udfprep.exe. NTLDR vs. BOOTMGR
– Copy the contents from Step 2 on the NTFS formatted UFD
– Option 2: Make a bootable CD-ROM
- Using contents from Step 2, oscdimg.exe create an ISO file
- Burn the ISO on a CD/DVD-ROM
4. Boot from prepared UFD or CD-ROM on target device with storage media
attached

21. 21
Pop Quiz
Question:
What if your target device does not have a USB port or DVD-ROM
drive? How do you install WES7?
Answer:
Use network share!

22. 22
Steps WES2009 WES7
1. Image Configuration Target Designer on development machine ICE on development machine
2. Add Sysprep tool Add “Sysprep Component” component N/A
3. Configure Sysprep tool Right-clicking on the component N/A
4. Booting image on target device Your preferred method to boot Your preferred method to boot
5. Locate sysprep tool directory on
target image
C:sysprepsysprep C:WindowsSystem32sysprep*
6. Sysprep your target image sysprep.exe –reseal –reboot
-- or --
fbreseal.exe (if you are using the “System
Cloning” component)
sysprep.exe /generalize /oobe /reboot
-- or --
sysprep.exe /generalize /audit /reboot
* Do not forget to delete the sysprep directory after final deployment
Differences
7.0 Image Deployment: Sysprep Image

23. 23
Pop Quiz
Question:
What if your target device does not have any kind of display port
i.e. it is a headless system? How do you install WES7?
Answer (maybe*):
 AutoUnattend.xml
 Offline building
* Lacks headless VGA driver

24. 24
Method WES2009 WES7
PXE+RIS boot Yes No (Replaced by WDS)
Remote Boot Yes No
USB Boot Yes Yes
CD/DVD* Yes No
WDS No Yes
* Running OS directly for CD/DVD
Differences
7.0 Image Deployment: Other Deployment Methods

25. 25
Installation Phase Log files location User Interaction
Autorun
(WinPE load)
No log files are created Before clicking "Build an Image" or "Deploy an
Answer File or WIM"
WinPE X:WindowsSourcesPanthersetupact.log
X:WindowsSourcesPanthersetuperr.log
Before clicking "Next" on the disk configuration
screen
During Installation C:Windows.~BTPantherSourcessetupact.Log
C:Windows.~BTPantherSourcessetuperr.Log
Once disk partition is selected
After Installation C:WindowsPanthersetupact.Log
C:WindowsPanthersetuperr.Log
C:Windowsinfsetupapi.Dev.Log
C:Windowsinfsetupapi.App.Log
After installation completes and windows
prepares to start for the first time
Roll Back (optional) C:Windows.~BTSourcesRollback* If fatal error occurs and setup fails
Sysprep (optional) C:WindowsSystem32SysprepPanther - Generalize
C:WindowsPantherUnattendgc - Unattended actions
When you execute Sysprep command with
different parameters
 WES2009 Log files
– C:Windowssetupapi
– C:WindowsFBAFBALOG.txt
 WES7 Log files
Differences
8.0 Log Files

26. 26
Localization Features WES2009 WES7
What can be localized?
- OS Image
- Developer Tools
- Documentation
Yes
No
No
Yes
Yes
Yes
Lang. Install Source MUI Language Packs (LPs)
Adding Lang. Offline No Yes
Included in Main Install Disc No Yes (in DS)
Language-Neutral Design No Yes
Languages Supported 23 36
OS Binaries Have to be fully localized Only apply relevant LP
Resulting OS Footprint Large Small
Differences
9.0 Localization

27. 27
Image Management WES2009 (.sdi format) WES7 (.wim format)
Tools SDI loader, sdimgr, sdi2hd ImageX, DISM
Capturing Image SDI loader (pre FBA) ImageX
sdimgr (post FBA)
Deploy Image sdi2hd, sdimgr ImageX/DISM
Maintenance (offline) sdimgr DISM
Add Components (offline) N/A (rebuild image) ImageX + DISM
Add Components (online) N/A (rebuild image) DISM
Differences
10.0 Image Management

28.  WIM Format
– “Hardware-agnostic” file-based format
– Can store multiple images in one single WIM file
– Only stores the differences between multiple images
– Refer to a particular image by indexing
 ImageX
– Capture WES7 image in WIM format
– Imagex /capture C: Z:WESImagesmyimage.wim “Drive C” /verify
– Supports WIM format
– Imagex /mount Z:WESImagesmyimage.wim 1 C:WESMountPoint
– Deploy from WIM format
– Imagex /apply Z:WESImagesmyimage.wim 1 C: ; bcdboot C:windows /s C:
 DISM
– Primarily a powerful CLI servicing tool
– Install/un-install drivers, packages, languages in offline and online mode
– Enable/Disable Windows settings
Differences
10.0 Image Management: WIM, ImageX and DISM

29.  Requirements to include in WES7 image
– Same as Windows 7
– Tools like Visual Studio 2008, etc.
– Static Dependencies (linked at compile time)
– Dynamic Dependencies (Runtime DLLs called)
 WES2009
– Chronic problem since XP Embedded days
– 3rd
party tools - Process Monitor and Dependency Walker
– Manually map the required binaries to the components in Target Designer
– Time consuming and frustrating process
– Lot of noise and unneeded binaries are found during analysis
Differences
11.0 Application Development

30.  WES7
– Built-in tool – SDA (Static Dependency Analyzer)
– .exe, .dll, .cab files
– Dynamic Dependency
– Process Monitor Package Mapper Answer File Build Image
– Automatically mapping of binaries to feature sets. Almost no noise.
– Compatible Application Template Website – Microsoft Initiative
– Ready-to-use templates like Adobe Flash, Silverlight, Windows Live, etc.
– In ICE: File Import  Import Template
– Add template to your Answer File.
– Community driven - Contribute your own templates
Differences
11.0 Application Development: Dependency Analysis

31. 31
 Windows does not detect automatically
– Even if set in BIOS
 Download Active Registry Monitor
– How about? devcon /r install C:windowsinfmsports.inf *PNP0500
– Diff registry changes between non-COM port installed system and COM port
installed system – AddCOM3.reg
– Pay attention to forced IRQ and base Addr. setting
 Download psexec.exe from sysinternal tools package
– Used to execute/install registry
 Create batch file – AddSerial.bat
– psexec /accepteula –s reg import C:AddCOM3.reg
 Add RunSynchronousCommand in Answer File
– AddSerial.bat
Example
Adding ISA-based Serial Ports

32. 32
 Upgrade to Windows 7 for development station and upgrade target
hardware
 Watch out for FAT32 support in your target application
 Start maintaining a single image for multiple systems
 Devices without ACPI are no longer supported
 eCore package - critical to booting
 Image building always happens on the target device
 Image deployed using UFD and CD-ROMs. No need to move
target media.
Implications

33. 33
 Various detailed log files at different locations depending on the
phase
 Streamlined localization process
 Add drivers, feature sets, etc. offline and online using DISM,
ImageX and WIM
 Improved dependency checking – SDA, Package Mapper and
template website
 Ease of adding drivers and other files to your image using ICE
Implications
(continued)

34. 34
Conclusion
 High degree of customization and flexibility
 Best of both worlds: Windows 7 + Embedded OS
 Reduces time to market – OEMs focus on core competency
 Lacks some features – Custom components, headless
device support, easy offline building, etc.
 Learning curve, but lots of benefits

35. 35
Thank You