Validation OS feature packages reference
You can use predefined feature packages to add functionality to Validation OS.
Where to get Validation OS Feature Components
The Validation OS ISO contains pre-defined feature package definitions
in the <ISO_ROOT>:\GenImage\configs folder. These are simple text based configuration files with .pkg extesion can be opened in a text editor to examine their content. This content refers to the Validation OS optional packages contained on the redistributable ISO.
The top section of these files contains more information about the specific feature.
How to add Optional Features
You can use either the Customize with Validation OS Image Builder or the Customize using GenImage (Advanced) method to add optional features to the base Validation OS image.
Validation OS Features vs Validation OS Optional Components
Validation OS features packages consists of a collection pptional component (.cab) packages that can be added to an offline Validation OS .wim image. The optional component package files enabling these features are available on the Validation OS ISO in the <Root>\cabs folder.
- Each optional package has a language-neutral and language-specific version of the cab. Both versions need to be added to an image.
- Validation OS support WOW. If any of your applications rely on x86 binaries make sure to also add the WOW64 package.
When using the supported process to add Validation OS optional features to the base image, there is no need to worry about the neutral/lanugae disticntions, nor it is required to specify the WOW64 compoenents.
Available features
| Feature name | Description |
|---|---|
| Applications and Application Support | Adds redistributable packages for VC++ dlls, .NET Framework 4.5, COM support, disk management tools, limited number of fonts and basic applications (e.g. Notepad) |
| Audio | Enables audio playback and recording |
| Bluetooth | Enables Bluetooth support |
| Camera | Adds support for using cameras |
| Debugging | Adds kernel debugging support |
| Device provisioning and administration | Includes dism, bctboot, bcdedit, basic networking, PowerShell, other tools to allow device administration. Note 1: The WMIC utility provided by Validation OS currently supports all xsl formats except the TABLE format which is the default format. The supported formats are VALUE, LIST, RAWXML, HTABLE, HFORM, XML, MOF and CSV. When using wmic, use the /format switch to specify the format you want. E.g.: wmic bios get name /format:xmlNote 2: To configure EMS Once the image has been flashed to the device, use these commands from within the Validation OS command prompt: bcdedit /emssettings emsport:1 emsbaudrate:115200bcdedit /ems onbcdedit /bootems onImportant: EMS cannot run along with KD. |
| Graphics/DirectX support | Adds support to for running DirectX and OpenGL applications. Also includes GDI+ and provides modern windowing look (UXTheme) |
| Multimedia | Enables Multimedia playback using basic Windows CODECs |
| Optional File Systems | Enables support UDFS and adds chkdsk.exe |
| Peripherals and Network Adapters | Enhanced driver support, classdriver extensions, PnP infrastructure, common network adapters and other elements to enable device specific drivers to communicate with the hardware |
| Power management | Enables power management and various power states. Once the image has been flashed to the device, use this command from within the Validation OS command prompt to enable hibernation: powercfg /h /type Full |
| PowerShell (base executables without cmdlets) |
Includes PowerShell 5.1 and .NET Framework |
| Sensors | Basic sensors support |
| SMB | Enables SMB client, Lanman and multiple UNC provider (MUP) support |
| USB support | Includes minimal support for USB and HID devices |
| Virtualization Support | Adds basic virtualization support |
| Wi-Fi | Enables wireless LAN support Once the image has been flashed to the device, use these commands from within the Validation OS command prompt to list interface and available networks: netsh wlan show interfacenetsh wlan show networksOn a standard Windows machine that is connected to the Wi-Finetwork of choice, run: cd %TEMP%\netsh export profile name=\<profile name\> folder=. key=clear Note: The profile name is usually simply the name of the SSID. Copy the created file to a USB key and transfer it to device under test. Run the following commands on device under test. netsh wlan add profile filename=\<the profile XML\>netsh wlan connect name=\<profile name\>ping 8.8.8.8 |