> 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/configuration-client/licensable-features/card-layouts-designing-printing-encoding/overall-process/editing-the-encoder-ini-file.md).

# Editing the Encoder.ini file

This topic describes how to edit the Encoder.ini file.

### Before you begin

Editing the Encoder.ini file should only be done under advisement from Gallagher Technical Support.

The Encoder.ini file references the encoding.dll used for each supported printer. If your printer is not a supported printer, you may be able to use the encoding.dll that belongs to a supported printer.

### Procedure

Use the following procedure to edit the Encoder.ini file to allow another printer to be supported.

1. On the workstation with the printer attached, open Windows Explorer.
2. Go to the directory C:\Program Files\Gallagher\Command Centre\Bin

   **Note:** This is the default directory on Windows 32-bit, but may differ depending on your installation.
3. Double-click on the **Encoder.ini** file and open in Notepad.
4. From the **Start** menu or **Control Panel** go to **Devices and Printers**.
5. Right click on the printer and select **Properties**.
6. Take note of the **Printer Name** from the **General** tab.
7. In Notepad, press < **Enter** > twice after the last entry (to leave a space), then add the following:

   **`[ Printer Name ]`**

   `MIFARE=encoding.dll`

   `Magstripe=encoding.dll`

   **Note:** Remember to enter the Printer Name inside the square brackets.
8. Depending on the type of card you have, either:

   * type **Magstripe** = and the name of the **dll** file you wish to try, (i.e. DCSP55Mifare.dll, Fargo.dll, FargoOmnikey.dll, CD800SingleWire.dll or SR300.dll)

     or
   * type **MIFARE** = and the name of the **dll** file you wish to try, (i.e. DCSP55Mifare.dll, XID8300Mifare.dll, FargoOmnikey.dll, CD800SingleWire.dll, MagicardRio.dll or SR300.dll)

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-0ad22056a2d6f09fe4ec0fa9f47f2adcf8f7d167%2Fencoderfile.png?alt=media)
9. Close Notepad and save the changes to the **Encoder.ini** file.
10. Try encoding and printing.

    If encoding is still unsuccessful, repeat this procedure but at Step 8 use the name of the other dll file. If still unable to print then, contact Gallagher Technical Support for further assistance.
11. Repeat this procedure to edit the Encoder.ini file located in the directories:
    * `C:\Program Files\Gallagher\Command Centre\Client`
    * `C:\Program Files\Gallagher\Command Centre\ClientSetup\Client` (server only)
12. Update **ClickOnceBuilder.exe** (server only).

    Once the **Encoder.ini** has been modified in the`ClientSetup\Client`directories, you will need to re-run the Click-Once executable ( **ClickOnceBuilder.exe** ) to include these additions in your next Click-Once deployment.

    The `ClickOnceBuilder.exe` is located in the directory `C:\Program Files\Gallagher\Command Centre\ClientSetup`
13. Update the Command Centre Client installation using Click-Once.

    Once the ClickOnceBuilder has been updated, you will need to update the Command Centre Client workstations that will be using the printer. When you launch the Command Centre Client you will be prompted to install the updated version. Click the **Install** button.


---

# 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/configuration-client/licensable-features/card-layouts-designing-printing-encoding/overall-process/editing-the-encoder-ini-file.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.
