> For the complete documentation index, see [llms.txt](https://wiki.retrobat.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.retrobat.org/systems-and-emulators/supported-game-systems/home-computer/ti-99-4a.md).

# TI-99/4A

Texas Instruments

<div align="left"><figure><img src="https://raw.githubusercontent.com/fabricecaruso/es-theme-carbon/52ff37c9e265587d006945a2ba695b5a962b3a3d/art/logos/ti99.svg" alt=""><figcaption></figcaption></figure></div>

Computer - Lifespan: 1981 - 1984

{% embed url="<https://en.wikipedia.org/wiki/TI-99/4A>" %}

## Information

<table data-header-hidden><thead><tr><th width="200"></th><th></th><th data-hidden></th></tr></thead><tbody><tr><td><strong>Emulators</strong></td><td><ul><li>libretro: mame</li><li>mame64</li></ul></td><td></td></tr><tr><td><strong>Games Location</strong></td><td><span data-gb-custom-inline data-tag="emoji" data-code="1f4c1">📁</span> roms \ <span data-gb-custom-inline data-tag="emoji" data-code="1f4c2">📂</span> ti99</td><td></td></tr><tr><td><strong>File extensions</strong></td><td>.rpk .zip</td><td></td></tr><tr><td><strong>Group</strong></td><td>MESS</td><td></td></tr><tr><td><strong>Emulated Model</strong></td><td>ti99_4a</td><td></td></tr><tr><td><strong>Softlists Available</strong></td><td>ti99_cart</td><td></td></tr><tr><td><strong>Media Types</strong></td><td>cassette, cartridge</td><td></td></tr></tbody></table>

## System Features

<table><thead><tr><th width="245">Retroachievements</th><th width="200">Netplay</th><th>Controller autoconfig</th></tr></thead><tbody><tr><td>NO</td><td>NO</td><td>NO</td></tr></tbody></table>

## BIOS

<table><thead><tr><th width="209.55555555555557">bios file</th><th width="189">Folder</th><th>md5</th></tr></thead><tbody><tr><td>ti99_cart.xml</td><td><code>\bios\mame\hash</code></td><td></td></tr><tr><td>ti99_4a.zip</td><td><code>\bios</code></td><td>See below</td></tr><tr><td>ti99_speech.zip</td><td><code>\bios</code></td><td>See below</td></tr></tbody></table>

### Content of BIOS files

```
ti99_4a.zip
- 994a_grom0.u500 "9bb51dfab49b9a7cf832cc1fb6f203e6"
- 994a_grom1.u501 "7f1864c3dac31c86e2ae6ce43ccead07"
- 994a_grom2.u502 "a1f77a07243a334e13509a89bff944f2"
- 994a_rom_hb.u610 "6f495eef767b3f2821a2ec32d0047891"
- 994a_rom_lb.u611 "0dcb961cf84c69b2171a565427c7c6c7"

ti99_speech.zip
- cd2325a.u2a "491c1195f6345cb6b725096b69d81ec9"
- cd2326a.u2b "206daf498ac5d0141de1d47d38afd899"
```

## Controls

Use [pad2key ](/controllers/pad2key.md)for the system.

{% hint style="danger" %}
In construction
{% endhint %}

## Specific system information

### Adding games

When not using .rpk files, it is recommended to use the "software list" for ti99, as MAME is very picky with this system's romset.

The file `ti99_cart.xml` located in the `\bios\mame\hash` folder will help you determine the right game roms to use.

<div align="left"><figure><img src="https://i.imgur.com/g53j20M.png" alt=""><figcaption></figcaption></figure></div>

The zip file must be named after the ***software name*** tag (e.g. `advent.zip`).

The content of the zip must contain the exact bin file accepted by mame visible after the ***rom name*** tag (e.g. `phm3041g3.bin`)


---

# 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://wiki.retrobat.org/systems-and-emulators/supported-game-systems/home-computer/ti-99-4a.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.