} SMBIOS_TABLE_TYPE1;\r
\r
///\r
-/// Base Board ¡ª Feature Flags \r
+/// Base Board - Feature Flags \r
///\r
typedef struct {\r
UINT8 Motherboard :1;\r
} BASE_BOARD_FEATURE_FLAGS;\r
\r
///\r
-/// Base Board ¡ª Board Type\r
+/// Base Board - Board Type\r
///\r
typedef enum { \r
BaseBoardTypeUnknown = 0x1,\r
///\r
/// Base Board (or Module) Information (Type 2)\r
///\r
-/// The information in this structure defines attributes of a system baseboard ¡ª \r
+/// The information in this structure defines attributes of a system baseboard - \r
/// for example a motherboard, planar, or server blade or other standard system module.\r
///\r
typedef struct {\r
} PROCESSOR_FAMILY_DATA;\r
\r
///\r
-/// Processor Information ¨C Voltage \r
+/// Processor Information - Voltage \r
///\r
typedef struct {\r
UINT8 ProcessorVoltageCapability5V :1; // Bit 0\r
/// Port Connector Information (Type 8)\r
///\r
/// The information in this structure defines the attributes of a system port connector, \r
-/// e.g. parallel, serial, keyboard, or mouse ports. The port¡¯s type and connector information \r
+/// e.g. parallel, serial, keyboard, or mouse ports. The port's type and connector information \r
/// are provided. One structure is present for each port provided by the system.\r
///\r
typedef struct {\r
/// Built-in Pointing Device (Type 21)\r
///\r
/// This structure describes the attributes of the built-in pointing device for the \r
-/// system ¡ª the presence of this structure does not imply that the built-in\r
+/// system - the presence of this structure does not imply that the built-in\r
/// pointing device is active for the system's use! \r
///\r
typedef struct {\r
///\r
/// This structure describes the attributes of the portable battery(s) for the system. \r
/// The structure contains the static attributes for the group. Each structure describes \r
-/// a single battery pack¡¯s attributes.\r
+/// a single battery pack's attributes.\r
///\r
typedef struct {\r
SMBIOS_STRUCTURE Hdr;\r
/// client's Pre-boot Execution Environment (PXE) boot image or OS-present management \r
/// application via this structure. When used in the PXE environment, for example, \r
/// this code identifies the reason the PXE was initiated and can be used by boot-image \r
-/// software to further automate an enterprise¡¯s PXE sessions. For example, an enterprise \r
+/// software to further automate an enterprise's PXE sessions. For example, an enterprise \r
/// could choose to automatically download a hardware-diagnostic image to a client whose \r
/// reason code indicated either a firmware- or operating system-detected hardware failure.\r
///\r