Details

Category: MAME

Last Updated: 28 September 2020

The MAME emulator is operated via the keyboard and a graphic menu. However, the system that it emulates also make more or less extensive use of the keyboard, so we should expect conflicts.

Hence, MAME defines two operation modes and two layout modes of the keyboard:

• Operation modes
  • Full keyboard mode
  • Partial keyboard mode
• Layout modes
  • Emulated keyboard mode
  • Natural keyboard mode

You can change the key for switching between the modes if your keyboard does not have a Scroll-Lock key: Change the UI mode key.

The natural keyboard

The natural keyboard posts complete strings for each keystroke but throttles the output.

Example:

• © -> (C) (three characters)
• ß -> ss
• æ -> ae

Alpha Lock: Caution must be taken that Alpha Lock is in the release state when starting the emulation. The reason is that the Alpha Lock state cannot be changed in natural keyboard mode. Instead, the case is controlled by the PC keyboard and its Caps Lock state. If Alpha Lock is on (from the last emulation run with emulated keyboard), all characters appear as upper case, regardless of the Caps Lock setting.

Details

Category: MAME

Last Updated: 02 February 2020

We're going to describe a fast way to install MAME on your Windows computer. If you follow these steps closely, there should not be any problem getting it running.

Check your Windows release

You should run a post-XP version (Vista, 7, 8, or 10). Do not try any older release like Windows 98, ME, or 2000. Windows XP is not recommended for security reasons, and MAME is not tested to run on it.

Get the MAME package

Download the most recent MAME release from the MAMEdev website from the section Official Binaries. You should use the 64 bit version (unless you know that your computer is 32 bit only).

Please do not attempt to install an older release, particularly not if its release number is much smaller than the current one. There have been changes in the meantime concerning the ROM formats, and this may make it impossible to run MAME.

Install the files

Run the exe file; this is just a self-extracting archive file. Choose your target directory; for easier configuration, a simple path like C:\prg\mame is recommended. The extracted files will be located in that directory.

Note that MAME does not alter your registry file. This means you can at any time simply remove the MAME installation, install another one in a separate directory, or reinstall it if desired. Uninstallation means that you have to remove that directory.

Configure it once

Open a command shell and type (in black)

C:\Users\Whoever> cd \prg\mame
C:\prg\mame> mame64 -createconfig
C:\prg\mame> exit

This creates a file C:\prg\mame\mame.ini. Open it in some text editor.

In the second section ("CORE SEARCH PATH OPTIONS") you will find a setting rompath. This is relative to your base directory C:\prg\mame; typically, you will find the value roms (i.e. it will be C:\prg\mame\roms). This subdirectory is already created by unpacking the zip file. If you like, you can append ;cartridges or similar in order to separate between modules and system roms. You must make sure that there is a directory C:\prg\mame\cartridges; if needed, create a new folder of that name in your explorer.

Scroll down to "OSD VIDEO OPTION"; change window to 1 to get a windowed output, otherwise it is fullscreen. In the next section "OSD PER-WINDOW VIDEO OPTION" you should set the first resolution property to 640x480 or bigger, as you find suitable.

Note that this configuration is only done once, when you install MAME, as we show it here.

Install system ROMs and cartridges

Go to our WHTech repository and download ti99_complete.zip from the directory /System ROMs/MAME. Unzip its contents into the roms subdir. Do not unzip the zip files inside.

Also from WHTech, download all_carts.zip from /Cartridges/MAME. It contains a collection of zip files, each one for a cartridge; do not unpack these cartridge zips.

Store the cartridge zips into the cartridges subdir if you added that location to the rompath, otherwise move all cartridge zip files to the roms subdir, too.

Create a starter batch

Create a small batch file to launch MAME. You may drop that on your desktop. For that, open some text editor and type

c:
cd \prg\mame
mame64 ti99_4a

Save it as ti99.bat to your desktop, or anywhere else as desired.

You can now edit this starter batch or create copies. You can change the system name (e.g. geneve, ti99_8), add cartridges (-cart exbasic) or peripheral devices (-ioport peb -ioport:peb:slot8 hfdc), and add floppy disks (-flop1 mydisk.dsk).

If you prefer the 32 KiB internal 16-bit RAM expansion, you can turn it on in the "System configuration" menu of the on-screen display (OSD). You then have to remove the 32kmem configuration below in all examples, however.

Example 1

Plain console, cassette file inserted

Important: This and the following examples will only work if you actually offer the specified disk or cassette image files at the indicated paths (or in the working directory if no path is specified).

c:
cd \prg\mame
mame64 ti99_4a -cass1 cassette.wav

Example 2

External 32K memory expansion, TI floppy controller, myfloppyimage.dsk inserted in DSK1

c:
cd \prg\mame
mame64 ti99_4a -ioport peb -ioport:peb:slot2 32kmem -ioport:peb:slot8 tifdc -flop1 myfloppyimage.dsk

Example 3

Cartridge Extended Basic, external 32K memory expansion, RS232 card, HFDC controller, one drive, myfloppyimage.dsk inserted

c:
cd \prg\mame
mame64 ti99_4a -cart exbasic -ioport peb -ioport:peb:slot2 32kmem -ioport:peb:slot7 tirs232 -ioport:peb:slot8 hfdc -flop1 myfloppyimage.dsk

Example 4

Cartridge Editor/Assembler, external 32K memory expansion, Speech synthesizer, Horizon RAMDisk, HFDC, hard disk, one floppy image inserted

c:
cd \prg\mame
mame64 ti99_4a -cart editass -ioport peb -ioport:peb:slot2 32kmem -ioport:peb:slot3 spchsyn -ioport:peb:slot4 horizon -ioport:peb:slot8 hfdc -ioport:peb:slot8:hfdc:h1 generic -hard1 myharddisk.hd -flop1 myfloppyimage.dsk

Example 5

P-Code system, external 32K memory expansion, TI floppy controller, one drive, Editor/Filer inserted from folder C:\prg\mame\disks\UCSD

c:
cd \prg\mame
mame64 ti99_4a -ioport peb -ioport:peb:slot2 32kmem -ioport:peb:slot3 pcode -ioport:peb:slot8 tifdc -flop1 disks\UCSD\ucsd_pascal_editor_filer_1.dsk

Note: You must turn on the P-Code card in the DIP switches menu of the On-screen display (OSD). The card is turned off by default because it immediately takes over control on start.

Example 6

Geneve, Horizon RAMDisk, Speech, RS232, HFDC, one hard disk

c:
cd \prg\mame
mame64 geneve -peb:slot4 horizon -peb:slot5 spchsyn -peb:slot6 tirs232 -peb:slot8 hfdc -ioport:peb:slot8:hfdc:h1 generic -hard1 myharddisk.hd

Reconfiguration

If you do not plan to change your configuration too often, you may want to set it inside MAME using the OSD. You can use the menu selection Slot devices to change the peripheral box contents, for example. Note that this change is only temporary until you leave MAME.

If you want to keep changes after stopping MAME, you must set readconfig and writeconfig to 1 in mame.ini.

When you use this setting, be aware that your command-line arguments may be overridden by what you had set in the OSD menu before you exited MAME the last time.

Details

Category: MAME

Last Updated: 28 August 2019

While the simulation of hardware circuits is in no way problematic with respect to copyright (since we produce a new system by observing the behavior of the original one), the distribution of memory contents is generally subject to copyright, and unlicenced distribution is considered an offense by most jurisdictions. Some countries know exemptions in the case of legacy software that is not runnable without the hardware, when the hardware is not available anymore. Other countries do not have corresponding exemptions. So you have to be aware of the following:

Consequently, I will not provide links for downloading these files. Find out by yourself how to get them. The safest way (from a legal standpoint) is to dump the contents from the real equipment if you own such a system.

At least for the TI-99/8 we have a written consent from TI that the ROM contents may be freely distributed. For TI-99/8 ROMs have a look at Planet99.net (login required).

Rumours are that you should also try the FTP site of WHTech.

The ROM dumps used for the TI emulations can be identified by this list. The required files must be present when starting the emulation. If an optional file is missing, the emulation will run, provided that the affected component that needs the ROM is not accessed. You will get a warning message stating that ROMs are missing and that the emulation will probably not run correctly.

Systems may be parents of others. In that case, the child systems borrow the ROM files from the parents if they do not have them in their own ZIP file. This means that if you have the ti99_4a.zip file, you can always launch the European version ti99_4ae since all files are equal, and the ti99_4a is the parent of ti99_4ae.

• ti99_4 is the parent of ti99_4e (european version)
• ti99_4a is the parent of ti99_4ae and ti99_4ev
• ti99_8 is the parent of ti99_8e

MAME is tolerant about the file names inside the ZIP files; the only important key is the hash code. ROM contents are compared by their hash code to make sure that the contents are authentic. Files may be renamed within the ZIP files.

The following table refers to MAME versions 0.212 and higher. The ROM dumps are distributed over a set of ZIP files. Each ZIP file corresponds to a single system or peripheral extension.

Main systems

These are the ROMs for the consoles, the Geneve, and the SGCPU.

TI-99/4A (ti99_4a)

Also comprises the European version (ti99_4ae)

TI-99/4A modified for use with EVPC (ti99_4ev)

Inherits from ti99_4a

TI-99/4QI (ti99_4qi)

Inherits from ti99_4a

Geneve 9640 (geneve)

Geneve 9640 modified (genmod)

Reuses the boot EPROM from the Geneve 9640 (v1.00)

SNUG TI-99/4P aka SGCPU (ti99_4p)

Also requires a prepared HSGPL card and the EVPC.

TI-99/8 (ti99_8)

May use the HX5102 as storage. TI-99/4A expansion cards are not guaranteed to work.

TI-99/4 (ti99_4)

Less successful predecessor of the TI-99/4A.

TI-99/2 24K (ti99_224)

Uses 24K ROM; earlier prototype. Does not support Hexbus.

TI-99/2 32K (ti99_232)

Uses 32K ROM; later prototype. May use HX5102 as storage.

Peripheral Expansion Cards

These are cards that are plugged into the Peripheral Expansion Box (PEB).

SNUG BwG disk controller (ti99_bwg)

SNUG Enhanced Video Processor Card (ti99_evpc)

Runs on ti99_4ev, sgcpu

Myarc Hard and Floppy Disk Controller (ti99_hfdc)

Standard floppy and hard disk controller. Runs with TI-99/4A and Geneve. Supports 2 sides, single (9) and double (18) density, and 40 or 80 tracks.

Myarc Memory Expansion Card MEXP-1 (ti99_myarcmem)

Configured to run with Myarc Extended Basic II.

P-Code Card (ti99_pcode)

Card has a master enable/disable switch (check DIP settings).

TI Floppy Disk Controller Card (ti99_tifdc)

Supports 2 sides, FM recording (single density), and 40 tracks.

TI RS232/PIO Card (ti99_rs232)

Provides two serial interfaces and one parallel interface. May be used twice in the system to get two more serial interfaces and one more parallel interface. Check DIP settings for CRU base.

Other devices

GRAMKracker (ti99_gkracker)

To be used in the GROM port (cartridge slot).

Speech Synthesizer (ti99_speech)

Also used as a peripheral card (using an adaptor card)

HX5102 Hexbus Floppy Drive (ti_hx5102)

Used with TI-99/8 and TI-99/2 32K. Supports 2 sides, single (9) or double density (16 sectors) and 40 or 77 tracks.

Details

Category: MAME

Last Updated: 17 April 2021

Here are some instructions for building MAME from source.

Windows

TODO

MacOS

TODO

Linux and other Unix variants

If you decide to build MAME from source code in Linux, you should probably directly use the git repository on Github since bugs are corrected very quickly (and new ones are as quickly introduced ...).

Version 0.210 and higher

You need

• gcc / gcc-c++ version 7 or higher
• git
• make
• Development package of alsa
• Development package of gconf2
• Development package of gtk2
• Development package of the SDL2 library
• Development package of the SDL2_ttf library
• Development package of the Qt5Core library
• Development package of Pulseaudio (since 0.230)

Use git to clone the repository to your local drive:

git clone https://github.com/mamedev/mame.git

Ubuntu

Ubuntu users need to make use of the apt-get command or check the software repository tools.

For Ubuntu 18.04 and newer, the following packages are required:

sudo apt install git
sudo apt install qt5-default
sudo apt install libsdl2-ttf-dev
sudo apt install libfontconfig1-dev
sudo apt install python

This set of package installations also imports gcc/gcc-c++ and make. You may put all package names in one single apt install call.

openSUSE

For an openSUSE installation, either use YaST or (if not already installed) follow this path:

sudo zypper install git-core
sudo zypper install gcc-c++
sudo zypper install libqt5-qtbase-devel
sudo zypper install xorg-x11-devel
sudo zypper install alsa-devel
sudo zypper install libSDL2_ttf-devel
sudo zypper install fontconfig-devel
sudo zypper install python-xml 
sudo zypper install libpulse-devel

Compiling

You can just build the complete MAME package by running make.

If you only want the TI systems to be included, you may specify them in the command line:

make -j4 SOURCES=src/mame/drivers/ti99_4x.cpp,src/mame/drivers/ti99_4p.cpp,src/mame/drivers/ti99_8.cpp,src/mame/drivers/geneve.cpp,src/mame/drivers/ti99_2.cpp REGENIE=1 TOOLS=1

REGENIE should be specified, since the GENie project generator tool is used for building. TOOLS will generate the additional helpers imgtool, chdman, and others. You probably don't need them if you use TIImageTool.

The -j4 switch is used to start 4 build jobs concurrently, which speeds up the compilation considerably. You must make sure that your build environment is not too old. GCC should be at least version 7. You can also use clang by

OVERRIDE_CC=clang OVERRIDE_CXX=clang++

When you want to get a current version, use the git pull command. Cleaning the build environment is optional, but if you experience problems when compiling, try to clean first.

git pull
make clean

After compiling has finished, you should have a freshly built mame64 executable file.

Details

Category: MAME

Last Updated: 02 May 2020

Actually, all Linuxes are alike. Almost. In the end, you run into problems because one system is by default installed with some library that another does not use. Since these libraries are installed only once, the challenge is to find out which libraries need to be installed and which are already there, and this is again different from system to system.

Thus, not the Linuxes are different, but their installation evolves over time. I will give some hints for installing MAME on different systems on this page.

Running MAME

MAME is dynamically linked against some libraries which may not be installed on your machine.

But fixing this is a simple job which you have to do only once. The following commands have been tested on a fresh installation. After installing, you should be able to run MAME. (Please report if you find a different situation.)

Unfortunately, different Linux flavors come with different package installers. And to make things worse, they use different package names for the same libraries.

openSUSE Tumbleweed

sudo zypper install libSDL2_ttf-2_0-0
sudo zypper install libQt5Widgets5

Ubuntu 19.10, 20.04

Linux Mint 19.3

sudo apt install libsdl2-ttf-2.0-0
sudo apt install libqt5widgets5

Details

Category: MAME

Last Updated: 24 November 2021

Important changes

MESS/MAME has undergone some rare, but important changes in usage that users should be aware of. In particular, when many releases are skipped, things may suddenly appear broken, but there may have been a change a while back.

These changes may require you to modify your existing MAME setup to achieve the same behaviour as before the release.

Detailed history

This version log of MAME specifically lists all TI-related changes in the code.