> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-hardware/credentials/encoding-solutions/encoder-3/supported-operating-systems-and-requir.md).

# Encoder 3 system requirements

Review supported operating systems, security dongles, encoding devices, and serial connection requirements.

What Encoder 3 runs on, the security dongle it requires, and the encoding devices it drives.

### Supported operating systems

* **Officially supported:** Windows 2000, Windows XP, Windows Server 2003.
* **Known to work:** Windows 7, Windows 8.1, Windows 10.

### Windows 11

The USB Security Dongle works and the application will run. However, support of the USB MIFARE encoders SDI010 and SDI011 is not good. Encoding is very slow and reading of cards fails.

{% hint style="warning" %}
Windows 11 does not support the MIFARE encoder drivers for the SDI110 and SDI011 encoders. Gallagher will not be updating the Encoder 3 software to support newer USB MIFARE encoders.
{% endhint %}

125kHz encoding through a USB-to-serial converter appears to be functional.

### Licensing requirements

Encoder 3 requires either a Parallel or USB security dongle to operate.

### USB Security Dongle

* Currently supports the Rockey 4 dongle, purchased through Gallagher Sales.
* Part number: 2M1503 - DONGLE ROCKEY4 64 BIT (POA).

![Rockey4 USB security dongle for Encoder III](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-b11c76545334ddc78c14b363be9a3ba605074b18%2FSECHUB-ENCODING-ENC3-06-rockey4-usb-dongle.jpg?alt=media)

### Parallel Dongle

* No longer available.
* Will **only** work on Windows 2000 and earlier operating systems.
* Sites upgrading from a much older OS to Windows 10 must replace the parallel port dongle with a USB version.

### Encoding devices

| Technology              | Supported device                      | Notes                                    |
| ----------------------- | ------------------------------------- | ---------------------------------------- |
| MIFARE Classic          | SDI010 and SDI011 USB MIFARE encoders | Discontinued 2015; ACR1252 not supported |
| 125kHz                  | Gallagher C197800 Serial encoder      | Discontinued 2023                        |
| Magnetic stripe / Tiris | Neuron CT-891-3A                      | Serial connection                        |

### Serial connections

The 125kHz and stripe encoders use serial ports, and can communicate via USB-to-serial converters. Some experimentation may be required.

Serial cables must be Serial Null modem cables. The straight-through connection variant is recommended. Note that several versions of the Null modem standard exist.

***

🔗 **Related**

* [Encoder 3 Overview](/knowledge-hub/products/cc-hardware/credentials/encoding-solutions/encoder-3/encoder-3-overview.md). The encoder hardware units and why Encoder 3 is now a legacy product.
* [Installing Encoder 3](/knowledge-hub/products/cc-hardware/credentials/encoding-solutions/encoder-3/installing-encoder-3.md). The install and first-run procedure.
* [Frequently Asked Questions](/knowledge-hub/products/cc-hardware/credentials/encoding-solutions/encoder-3/frequently-asked-questions.md). Moving the database to a new PC, and why an old parallel dongle stops working.


---

# 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://help.security.gallagher.com/knowledge-hub/products/cc-hardware/credentials/encoding-solutions/encoder-3/supported-operating-systems-and-requir.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.