mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 10:23:37 +00:00
CI Update
This commit is contained in:
@ -19,12 +19,12 @@ ms.topic: article
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
Windows® provides several *compatibility modes*, groups of compatibility fixes found to resolve many common application-compatibility issues. While working with Compatibility Administrator, you might decide to group some of your individual compatibility fixes into a custom-compatibility mode, which you can then deploy and use on any of your compatibility databases.
|
||||
|
||||
@ -38,10 +38,10 @@ A compatibility mode is a group of compatibility fixes. A compatibility fix, pre
|
||||
|
||||
The Compatibility Administrator tool has preloaded fixes for many common applications, including known compatibility fixes, compatibility modes, and AppHelp messages. Before you create a new compatibility mode, you can search for an existing application and then copy and paste the known fixes into your custom database.
|
||||
|
||||
**Important**
|
||||
**Important**
|
||||
Application Compatibility Toolkit (ACT) installs a 32-bit and a 64-bit version of the Compatibility Administrator tool. You must use the 32-bit version to create custom databases for 32-bit applications and the 64-bit version to create custom databases for 64-bit applications.
|
||||
|
||||
|
||||
|
||||
|
||||
**To search for an existing application**
|
||||
|
||||
@ -54,10 +54,10 @@ Application Compatibility Toolkit (ACT) installs a 32-bit and a 64-bit version o
|
||||
|
||||
If you are unable to find a preloaded compatibility mode for your application, you can create a new one for use by your custom database.
|
||||
|
||||
**Important**
|
||||
**Important**
|
||||
A compatibility mode includes a set of compatibility fixes and must be deployed as a group. Therefore, you should include only fixes that you intend to deploy together to the database.
|
||||
|
||||
|
||||
|
||||
|
||||
**To create a new compatibility mode**
|
||||
|
||||
@ -67,23 +67,25 @@ A compatibility mode includes a set of compatibility fixes and must be deployed
|
||||
|
||||
3. Select each of the available compatibility fixes to include in your custom-compatibility mode and then click **>**.
|
||||
|
||||
**Important**
|
||||
**Important**
|
||||
If you are unsure which compatibility fixes to add, you can click **Copy Mode**. The **Select Compatibility Mode** dialog box appears and enables you to select from the preloaded compatibility modes. After you select a compatibility mode and click **OK**, any compatibility fixes that are included in the preloaded compatibility mode will be automatically added to your custom-compatibility mode.
|
||||
|
||||
|
||||
|
||||
If you have any compatibility fixes that require additional parameters, you can select the fix, and then click **Parameters**. The **Options for <Compatibility\_Fix\_Name>** dialog box appears, enabling you to update the parameter fields.
|
||||
|
||||
4. After you are done selecting the compatibility fixes to include, click **OK**.
|
||||
~~~
|
||||
If you have any compatibility fixes that require additional parameters, you can select the fix, and then click **Parameters**. The **Options for <Compatibility\_Fix\_Name>** dialog box appears, enabling you to update the parameter fields.
|
||||
~~~
|
||||
|
||||
The compatibility mode is added to your custom database.
|
||||
4. After you are done selecting the compatibility fixes to include, click **OK**.
|
||||
|
||||
The compatibility mode is added to your custom database.
|
||||
|
||||
## Related topics
|
||||
[Compatibility Administrator User's Guide](compatibility-administrator-users-guide.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
Reference in New Issue
Block a user