> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/installation/install-central-manager-multi-store/backward-compatibility/backward-compatibility-installation.md).

# Install the Backward Compatibility Extension

This topic describes how to install the Backward Compatibility Extension on a store computer.

For non-Flash stores, you must install the Backward Compatibility Extension **on the same computer** where your installed both the RMH Central Flash Server app and the non-Flash RMH Central Server app.

1. Go to the location where you extracted the release package files.
2. Double-click **Setup.exe** to open the setup wizard.

{% hint style="info" %}
You must have administrative privileges on the computer to install RMH apps.
{% endhint %}

<div align="left"><img src="https://2921455087-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjgsd9U4TRO2qgcIBegi7%2Fuploads%2Fgit-blob-c17036c8d1401b42bc58842a7ab1cde921cecf3a%2Fsetup-wizard.png?alt=media" alt=""></div>

3. Under **RMH Flash Backward Compatibility**, click **Install Flash Backward Compatibility**.

{% hint style="info" %}
Alternately, you can go to the **RMH Flash Backward Compatibility** folder and double-click **RMH.FlashBackwardCompatibility.Installer.msi**.
{% endhint %}

4. Click **Next**.

<div align="left"><img src="https://2921455087-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjgsd9U4TRO2qgcIBegi7%2Fuploads%2Fgit-blob-c49f4e543d6c7e3af962226ccce6e1ba339968d5%2Fsetup-wizard-rmh-backward-welcome.png?alt=media" alt=""></div>

5. On the **End-User License Agreement** screen, select **I accept the terms in the License Agreement** and click **Next**.

<div align="left"><img src="https://2921455087-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjgsd9U4TRO2qgcIBegi7%2Fuploads%2Fgit-blob-0950b69880a0ee3af9d5d69cfe79ac728a0cede2%2Fsetup-wizard-rmh-backward-license.png?alt=media" alt=""></div>

6. On the **Destination Folder** screen, select the installation folder for the Backward Compatibility Extension and click **Next**.

<div align="left"><img src="https://2921455087-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjgsd9U4TRO2qgcIBegi7%2Fuploads%2Fgit-blob-59e8054cf5102f5f29b243b23e78cdbfe6b67db5%2Fsetup-wizard-rmh-backward-destination.png?alt=media" alt=""></div>

7. Click **Install**.

<div align="left"><img src="https://2921455087-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjgsd9U4TRO2qgcIBegi7%2Fuploads%2Fgit-blob-0d55975da8893f3063689a1064ad0bc953882c1c%2Fsetup-wizard-rmh-backward-install.png?alt=media" alt=""></div>

8. Wait while installation is completed. This may take a few minutes.
9. Click **Finish**.

<div align="left"><img src="https://2921455087-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjgsd9U4TRO2qgcIBegi7%2Fuploads%2Fgit-blob-cd55efa7916c5f4af52dd74f87ae351585a4ac2a%2Fsetup-wizard-rmh-backward-install-complete.png?alt=media" alt=""></div>

10. Complete the setup of the Backward Compatibility Extension. Refer to Identify the stores that are Flash and non-Flash and Turn off the worksheet processor service for more information.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rmhpos.com/installation/install-central-manager-multi-store/backward-compatibility/backward-compatibility-installation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
