ATARI ++

ATARI 8 bit emulator

Online Manual

Find the complete online manual of the Atari++ emulator here:  man/manual/atari++.html

Os++ Manual and Memory Map

The built-in operating system of Atari++ comes with a System Disk containing various utilities and a disk-based menu. The documentation of Os++, the System Disk and the included tools, as well as a complete memory map of the operating system is available as PDF file for download as well.

Compiling the Emulator

Since I do not distribute binaries, either due to the size or due to the variety of different system setups I do not all want to support, you need to compile the emulator yourself. This sounds harder than it is; here is a step-by-step HOWTO:
  • Unpack the archive with 
    tar -xzf atari++.tgz 
  • Let the emulator figure out the configuration of your system. For that, change to the directory where the archive was unpacked into, and enter
    ./configure
  • Build the emulator by
    make
This builds a file named "atari++" which is the emulator executable. In case you should find any problem building the emulator, let me know.

Prequisites for compiling the emulator

A well-installed system should be able to build the emulator from scratch without requiring any additional installations. However, in case of doubt, you might want to check for the following packages:
  • The X11 development files should be available. Most noticably, the X header files in /usr/include/X11 must be available for any graphics output.
  • Optionally, the Oss development files must be available in sys/soundcard.h. Even without them the emulator will work, but Oss sound output will not work.
  • Optionally, the SDL development files must be available in /usr/include/SDL. The emulator will work without the SDL headers, but you won't be able to use the SDL graphics output and the SDL sound output without them.
  • Optionally, either the curses or the ncurses development files in /usr/include/curses.h or /usr/include/ncurses.h must be available. The emulator will work without them, but the built-in monitor will have a less user-friendly front-end without curses development files.
If the mentioned system headers are not at the precise positions mentioned above, the configuration file might still be able to figure their location out. If this does not work, run the configuration script like this:
./configure --includedir=<your_include_directory>
Optionally, you may also select a different compiler for building the emulator. For that, specify the C compiler with the CC=compiler and the C++ compiler with CXX=compiler flag. Note that you need to specify both. For example, to configure the emulator for the intel icc compiler, run the configuration script as follows:
./configure CC=icc CXX=icc
Then build the emulator with "make" as above.