6 Appendix A: Product Behavior

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 2000 operating system

• Windows XP operating system

• Windows Server 2003 operating system

• Windows Vista operating system

• Windows Server 2008 operating system

• Windows 7 operating system

• Windows Server 2008 R2 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.4:  Applications typically interact with an OLE DB interface wrapper, such as a protocol client, and not directly with the protocol. For more information, see [MSDN-OLEDBP].

<2> Section 1.6: This protocol is implemented on Windows 2000 Server operating system, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2. However, the Content Indexing Services Protocol is deprecated on Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2. That is, the Windows implementation of the Content Indexing Services Protocol is still available on Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, but is not installed by default and will not be available in future releases after Windows 7 and Windows Server 2008 R2.

<3> Section 1.8: Windows uses only the values specified in [MS-ERREF].

<4> Section 1.8.1: See [MSDN-PROPSET] for a list of supported property sets.

<5> Section 2.2.2: The client always sets the _status field to 0x00000000.

<6> Section 2.2.3.1: This value is usually zero except immediately after indexing has been started or after a notification queue overflows.

<7> Section 2.2.3.4: If a value other than UPD_INCREM (0x00000000), UPD_FULL (0x00000001) or UPD_INIT (0x00000002) is set for the _flag field, the server acts as if the _flag field was set to UPD_INIT (0x00000002) and perform a full scan.

<8> Section 2.2.3.6: On Windows clients, the _iClientVersion is set as follows.

<9> Section 2.2.3.6: OLE-DB properties are frequently used.

<10> Section 2.2.3.12: Windows does not use this message.

<11> Section 2.2.3.19: Windows sets this field to 0x00004000.

<12> Section 2.2.4: The same pipe connection is used for the following messages except when the error is returned in a CPMConnectOut message. In the latter case, the pipe connection is terminated.

<13> Section 3.1.1: The catalog state begins in the CICAT_WRITABLE state. But when the catalog is stored on a read-only media such as a CD-ROM, the catalog state begins in the CICAT_READONLY state.

<14> Section 3.2.4.2.4: For a 32-bit client talking to a 32-bit server or a 64-bit client talking to a 64-bit server, this value is set to a memory address of the receiving buffer in the application process. This allows for pointers received in the Rows field of CPMGetRowsOut to be correct memory pointers in a client application process. Otherwise, the value is set to 0x00000000.