Details

Category: MAME

Last Updated: 18 February 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, Linux Mint 19.3

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

Details

Category: MAME

Last Updated: 18 February 2020

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

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 

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 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: 04 February 2020

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