|
Boot Configuration Data in Windows Vista
|
bet | 12/20 | Sana | 21.03.2017 | Hajmi | 297.76 Kb. | | #1081 |
Description
|
Value
|
Description
|
Library
|
0001
|
Elements can be applied to all boot environment applications.
|
Application
|
0010
|
Elements can be applied to only a particular class of boot environment applications, such as boot loaders.
|
Device
|
0011
|
Elements can be included only by device objects.
|
BCD elements are structured data. The following table shows the formats and their associated numerical code.
Element Formats
Description
|
Value
|
Description
|
String
|
0010
|
For example, kernel debugger on or off.
|
Object
|
0011
|
For example, NX policy.
|
Integer
|
0101
|
For example, the boot menu default value.
|
Boolean
|
0110
|
For example, the path to the operating system loader.
|
The techniques for adding, deleting, or modifying BCD elements depend on the particular tool.
BCDEdit and the BCD WMI API provide well-known names for the standard elements. However, for custom element types, Figure 8 shows the layout.
Figure 8. Layout of the BCD element type
The BCD store is in a binary format and can be modified only by tools that are designed for that purpose. The first two discussed here are designed for regular users and provide limited access to BCD. The BCDEdit tool is designed for developers and support professionals. It provides fairly complete access to BCD, including the ability to create BCD stores. The most flexible and powerful approach to managing BCD stores is programmatically, with the BCD WMI API. This API is discussed later in this paper.
|
| |