Boot Loader Changes in Windows Embedded CE 6.0
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/27/2008
In previous releases, exception handling using __try / __except was not supported in boot loaders and KITL. These components are linked to the same limited functionality libraries. The libraries defined exception handling symbols that caused a link-time build break if exception handling was used.
In Windows Embedded CE 6.0, exception handling has been enabled for the KITL component, but not for the boot loader (which runs prior to kernel initialization). However, since boot loaders and KITL still use the same shared libraries, you can no longer use the above method to prevent linking with exception handling support.
To prevent random crashes in the boot loader phase, you must explicitly ensure you do not use exception handling in the boot loader code. This can be checked by scanning the boot loader MAP files for the __C_specific_handler string (which indicates the compiler has imported support for exception handling).
See Also
Concepts
Other Resources
Developing a Boot Loader
Migrating a BSP to Windows Embedded CE 6.0