Building a Kernel Baseline Configuration (Windows Embedded Standard 2009)

  • Article

4/23/2012

A kernel baseline configuration includes only the basic components that are required to operate your device. For information about what is supported in a Kernel baseline configuration, see Kernel Baseline Configurations.

To build a kernel baseline configuration

  1. From the Program Files\Windows Embedded\Utilities folder, run the Target Analyzer probe file, TAP.exe. By default, TAP.exe creates a file named Devices.pmq.

  2. Create a new configuration by using Target Designer, and then import the Devices.pmq file. For more information, see How to Add Hardware Information to a Configuration.

  3. If the C drive is not your target drive letter for your run-time image, change the target drive path. For more information, see Configuration Settings in Windows Embedded Standard Studio Help.

  4. With the exception of the keyboard and mouse, delete or disable all device components that are not required to boot your run-time image.

  5. Remove or disable the Plug and Play (PnP) Software Device Enumerator component, if it is included in your configuration.

  6. This component depends on the PnP (User-mode) component, which depends on the Win32 subsystem.

  7. For the smallest image, replace any ACPI-based PC component, for example, the Advanced Configuration and Power Interface (ACPI) PC component, with the Standard PC component located in the Software\System\System Services\Base component folder.

  8. You can then disable all ACPI components.

  9. Select the FAT component located in the Software\System\System Services\Base component folder.

  10. NTFS volume compression does not decrease footprint for images this small because of the 2-MB log file that NTFS requires.

  11. Check and resolve dependencies. For instructions, see Checking Dependencies in Windows Embedded Standard Studio Help.

  12. When you are prompted to select a session manager, choose the Session Manager (Kernel-only configuration demo) component.

    This includes a demo Smss.exe that continuously displays "Hello World" to the debugger console. Later, you can replace Smss.exe with your own application.

  13. Build the run-time image.

    This image should range from 4.5 to 6.5 MB, depending on the devices and file system you selected.

  14. Use the following Boot.ini scripting sample to configure your run-time image to support kernel debugging:

    [boot loader]
timeout=0
default=multi (0)disk(0)rdisk(0)partition(1) \WINDOWS
[operating system]
multi (0)disk(0)rdisk(0)partition(1) \WINDOWS="Microsoft Windows Embedded Standard" /fastdetect
multi (0)disk(0)rdisk(0)partition(1) \WINDOWS="Microsoft Windows Embedded Standard" /fastdetect /debug /debugport=com1 /baudrate=57600

  15. Two menu choices appear on your boot menu. Choose the second menu item to enable kernel debugging through the serial port of the device. The actual parameters may differ for your device. For more information, see the Windows XP Device Driver Kit (DDK) documentation.

  16. Run the debugger in your debugger system.

  17. Boot your run-time image from the FAT partition in your run-time image.

    When "Hello World" continuously prints to the command window in the debugger system, you have successfully booted Windows Embedded Standard on your device. If your device has a display, it remains blank.

See Also

Other Resources

Baseline Configurations