Share via

6 Appendix A: Product Behavior

  • Article

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include updates to those products.

  • Windows 98 operating system Second Edition

  • Windows 2000 operating system

  • Windows 2000 Server operating system

  • Windows Millennium Edition operating system

  • Windows XP operating system

  • Windows Server 2003 operating system

Exceptions, if any, are noted in this section. If an update version, service pack or Knowledge Base (KB) number appears with a product name, the behavior changed in that update. The new behavior also applies to subsequent updates unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.

Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms "SHOULD" or "SHOULD NOT" implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term "MAY" implies that the product does not follow the prescription.

<1> Section 1.3: The Microsoft implementation of the Microsoft NetMeeting Protocol exists in the Windows NetMeeting feature. This implementation is backwards-compatible with the ITU T.120 protocols, as specified in [T128-06/08] and the S20 protocols.

<2> Section 2.2.2.1.3: The version of Windows being used is defined by one of the following values. The OSVersion field is always set to one of these values by Windows.

Value

Meaning

CAPS_WINDOWS_31

0x0001

Windows NT 3.1 operating system

CAPS_WINDOWS_95

0x0002

Windows 95 operating system, Windows 98 operating system, or Windows Millennium Edition

CAPS_WINDOWS_NT

0x0003

Windows XP, Windows 2000, or Windows Server 2003

<3> Section 2.2.2.4.2.3: The hot spot of a cursor is the point to which Windows refers when tracking the cursor position.

<4> Section 2.2.2.4.2.3: The hot spot of a cursor is the point to which Windows refers when tracking the cursor position.

<5> Section 2.2.2.4.2.5: The hot spot of a cursor is the point to which Windows refers when tracking the cursor position.

<6> Section 2.2.2.4.2.5: The hot spot of a cursor is the point to which Windows refers when tracking the cursor position.

<7> Section 2.2.2.4.5.1: The NetMeeting application obtains various information about fonts used between application sharing from the following Windows GDI data structures:

  • TEXTMETRIC: The TEXTMETRIC structure contains basic information about a physical font. All sizes are specified in logical units; that is, they depend on the current mapping mode of the display context.

  • GetTextMetrics: The GetTextMetrics function fills the specified buffer with the metrics for the currently selected font.

<8> Section 2.2.2.4.5.1: The NetMeeting application obtains various information about fonts used between application sharing from the following Windows GDI data structures:

  • TEXTMETRIC: The TEXTMETRIC structure contains basic information about a physical font. All sizes are specified in logical units; that is, they depend on the current mapping mode of the display context.

  • GetTextMetrics: The GetTextMetrics function fills the specified buffer with the metrics for the currently selected font.

<9> Section 2.2.2.4.5.1: The NetMeeting application obtains various information about fonts used between application sharing from the following Windows GDI data structures:

  • TEXTMETRIC: The TEXTMETRIC structure contains basic information about a physical font. All sizes are specified in logical units; that is, they depend on the current mapping mode of the display context.

  • GetTextMetrics: The GetTextMetrics function fills the specified buffer with the metrics for the currently selected font.

<10> Section 2.2.2.4.5.1: The NetMeeting application obtains various information about fonts used between application sharing from the following Windows GDI data structures:

  • TEXTMETRIC: The TEXTMETRIC structure contains basic information about a physical font. All sizes are specified in logical units; that is, they depend on the current mapping mode of the display context.

  • GetTextMetrics: The GetTextMetrics function fills the specified buffer with the metrics for the currently selected font.

<11> Section 2.2.2.4.5.1: The NetMeeting application obtains various information about fonts used between application sharing from the following Windows GDI data structures:

  • TEXTMETRIC: The TEXTMETRIC structure contains basic information about a physical font. All sizes are specified in logical units; that is, they depend on the current mapping mode of the display context.

  • GetTextMetrics: The GetTextMetrics function fills the specified buffer with the metrics for the currently selected font.

<12> Section 2.2.2.4.5.1: The NetMeeting application obtains various information about fonts used between application sharing from the following Windows GDI data structures:

  • TEXTMETRIC: The TEXTMETRIC structure contains basic information about a physical font. All sizes are specified in logical units; that is, they depend on the current mapping mode of the display context.

  • GetTextMetrics: The GetTextMetrics function fills the specified buffer with the metrics for the currently selected font.

<13> Section 2.2.2.4.5.1: The NetMeeting application obtains various information about fonts used between application sharing from the following Windows GDI data structures:

  • TEXTMETRIC: The TEXTMETRIC structure contains basic information about a physical font. All sizes are specified in logical units; that is, they depend on the current mapping mode of the display context.

  • GetTextMetrics: The GetTextMetrics function fills the specified buffer with the metrics for the currently selected font.

<14> Section 2.2.2.4.5.1: The NetMeeting application obtains various information about fonts used between application sharing from the following Windows GDI data structures:

  • TEXTMETRIC: The TEXTMETRIC structure contains basic information about a physical font. All sizes are specified in logical units; that is, they depend on the current mapping mode of the display context.

  • GetTextMetrics: The GetTextMetrics function fills the specified buffer with the metrics for the currently selected font.

<15> Section 2.2.2.4.5.1: The NetMeeting application obtains various information about fonts used between application sharing from the following Windows GDI data structures:

  • TEXTMETRIC: The TEXTMETRIC structure contains basic information about a physical font. All sizes are specified in logical units; that is, they depend on the current mapping mode of the display context.

  • GetTextMetrics: The GetTextMetrics function fills the specified buffer with the metrics for the currently selected font.

<16> Section 2.2.2.4.7.1.1: WM_KEYUP Notification: The WM_KEYUP message is posted to the window that has the keyboard focus when a nonsystem key is released. A nonsystem key is a key that is pressed when the ALT key is not pressed, or a keyboard key that is pressed when a window has the keyboard focus.

WM_SYSKEYUP Notification: The WM_SYSKEYUP message is posted to the window that has the keyboard focus when the user releases a key that was pressed while the ALT key was held down. It also occurs when no window currently has the keyboard focus; in this case, the WM_SYSKEYUP message is sent to the active window. The window that receives the message can distinguish between these two contexts by checking the context code in the lParam parameter.

<17> Section 2.2.2.4.10.1.7: Ternary raster-operation codes define how Windows GDI combines the bits in a source bitmap with the bits in the destination bitmap.

Each raster-operation code represents a Boolean operation in which the values of the pixels in the source, the selected brush, and the destination are combined. Refer to [MSDN-TRO] for additional information.

<18> Section 2.2.2.4.10.1.9: The NetMeeting application obtains various information about fonts that are used between application sharing from the following Windows GDI data structures:

  • TEXTMETRIC: The TEXTMETRIC structure contains basic information about a physical font. All sizes are specified in logical units; that is, they depend on the current mapping mode of the display context.

  • GetTextMetrics: The GetTextMetrics function fills the specified buffer with the metrics for the currently selected font.

<19> Section 2.2.2.4.10.1.9: The NetMeeting application obtains various information about fonts that are used between application sharing from the following Windows GDI data structures:

  • TEXTMETRIC: The TEXTMETRIC structure contains basic information about a physical font. All sizes are specified in logical units; that is, they depend on the current mapping mode of the display context.

  • GetTextMetrics: The GetTextMetrics function fills the specified buffer with the metrics for the currently selected font.

<20> Section 2.2.2.4.10.1.11: Ternary raster-operation codes define how Windows GDI combines the bits in a source bitmap with the bits in the destination bitmap.

Each raster-operation code represents a Boolean operation in which the values of the pixels in the source, the selected brush, and the destination are combined. Refer to [MSDN-TRO] for additional information.

<21> Section 2.2.2.4.10.1.12: Ternary raster-operation codes define how Windows GDI combines the bits in a source bitmap with the bits in the destination bitmap.

Each raster-operation code represents a Boolean operation in which the values of the pixels in the source, the selected brush, and the destination are combined. Refer to [MSDN-TRO] for additional information.

<22> Section 2.2.2.4.10.1.21: Ternary raster-operation codes define how Windows GDI combines the bits in a source bitmap with the bits in the destination bitmap.

Each raster-operation code represents a Boolean operation in which the values of the pixels in the source, the selected brush, and the destination are combined.  Refer to [MSDN-TRO] for additional information.

<23> Section 2.2.2.4.10.1.28: Ternary raster-operation codes define how Windows GDI combines the bits in a source bitmap with the bits in the destination bitmap.

Each raster-operation code represents a Boolean operation in which the values of the pixels in the source, the selected brush, and the destination are combined. Refer to [MSDN-TRO] for additional information.

<24> Section 2.2.2.4.10.1.29: The NetMeeting application obtains various information about fonts that are used between application sharing from the following Windows GDI data structures:

  • TEXTMETRIC: The TEXTMETRIC structure contains basic information about a physical font. All sizes are specified in logical units; that is, they depend on the current mapping mode of the display context.

  • GetTextMetrics: The GetTextMetrics function fills the specified buffer with the metrics for the currently selected font.

<25> Section 2.2.2.4.10.1.29: The NetMeeting application obtains various information about fonts that are used between application sharing from the following Windows GDI data structures:

  • TEXTMETRIC: The TEXTMETRIC structure contains basic information about a physical font. All sizes are specified in logical units; that is, they depend on the current mapping mode of the display context.

  • GetTextMetrics: The GetTextMetrics function fills the specified buffer with the metrics for the currently selected font.

<26> Section 2.2.2.7: If the nameData field is not supplied by the user in a Windows implementation, the computer name is taken from the Windows WMI Instrumentation API function GetComputerName().

<27> Section 2.2.9.3: Microsoft NetMeeting implementations do not use the h245address field. On NetMeeting implementations, this field is set to zero and ignored.

<28> Section 2.2.9.3: NetMeeting implementations do not use the h245SecurityMode field. On NetMeeting implementations, this field is set to zero and ignored.

<29> Section 2.2.9.3: NetMeeting implementations do not use the Tokens field. On NetMeeting implementations, this field is set to zero and ignored.

<30> Section 2.2.9.3: NetMeeting implementations do not use the cryptoTokens field. On NetMeeting implementations, this field is set to zero and ignored.

<31> Section 2.2.9.3: NetMeeting implementations do not use the fastStart field. On NetMeeting implementations, this field is set to zero and ignored.

<32> Section 3.1.2: The NetMeeting implementation has a time-out mechanism for connection establishment, which is to wait 20 seconds for a callee to respond. If no response is returned, the implementation MUST declare a time-out and notify the user.

<33> Section 5.1: The Microsoft implementation uses TLS as specified in [T123].