[<Message Object Section>] Section

[This is preliminary documentation and subject to change.]

A message object section provides a mechanism for you to associate one or more message objects (such as file, directory, and registry location) with a message specified in the [Incompatible Messages] section. The [Handled] section describes how to specify a message object.

The section name is defined by your migration DLL. Each line has the following syntax:

<Message Object> = <Identifier Type>

Message Object

Specifies a Windows 95 or Windows 98 file, path, or registry entry. A file or path must be specified in long file name format.

Identifier Type

Identifies the type of <Message Object>. It can only have one of the following three values:

File

The object specified refers to a long file name (including the full path to the file).

Directory

The object specified refers to a directory (including the full path to the directory).

Registry

The object specified refers to a registry key (including the full path to that key).

• Setup uses the value for Message Object Section to develop a hierarchy for incompatibility messages. The use of the section name enables your migration DLL to organize multiple incompatibility messages in the same format that Setup uses. Setup processes the section name in one of two ways:
  1. If the name of the section matches ProductID, Setup displays the message at the root level of the incompatibility message tree. The ProductID itself is listed in a tree control, and when the user clicks on the root item, the incompatibility message is shown in an edit control.
  2. If the name of the section contains one or more backslashes, Setup separates the string at the backslashes to create the hierarchy. Setup limits the number levels in the tree to 10. Optimally, you should organize your messages into 3 levels.

  Using the section name in this way achieves unique children for each migration DLL, organized under a single item at the root. Because ObjectSection is used for display purposes, your DLL must provide localized strings.

• Setup treats all objects in a section as a set. If every object in the set is found in any [Handled] section (including ones provided by other vendors), no incompatibility message will be displayed for the particular object, even if the message is listed in [Incompatible Messages]. If only some or none of the objects are handled, the message will be displayed.