Manual
Installation
Linux
On Linux and other POSIX platforms, the emulator is installed from the source code, available at the SourceForge download page or the most recent state of the code can be downloaded from CVS with the following command:
cvs -z3 -d :pserver:anonymous@ep128emu.cvs.sourceforge.net:/cvsroot/ep128emu checkout -P ep128emu2
In addition to the standard development tools (a recent version of the GNU C/C++ compiler, binutils, etc.), you need the following packages:
- SCons (http://www.scons.org/)
- Python interpreter for running SCons
- FLTK 1.1.x (http://www.fltk.org/software.php?VERSION=1.1.10) NOTE: this library should be compiled with the —enable-threads ‘configure’ option - many Linux distributions include binaries of the FLTK library built without —enable-threads, so you may need to compile it from sources
- PortAudio (http://www.portaudio.com/download.html), version 18 and 19 are supported, but v19 is recommended
- libsndfile (http://www.mega-nerd.com/libsndfile/#Download)
- dotconf (version 1.0.13 from http://www.azzit.de/dotconf/, or 1.3 from https://github.com/williamh/dotconf/archives/master - the latter was not tested yet) (optional, but recommended as it is used for reading ASCII format configuration files)
- SDL (http://www.libsdl.org/) 1.2 for joystick input (optional); NOTE: on Linux, version 1.2.10 and newer do not work, so using 1.2.9 is recommended
- Lua (http://www.lua.org/ or http://www.luajit.org/) for scripting in the debugger (optional); version 5.1 is recommended, but 5.0 is also supported
Once these are installed, you can edit the file SConstruct in the top level source directory for setting compiler flags etc., and run the command scons for building the emulator. The resulting executable files (ep128emu and tapeedit) can be copied to any directory that is in the PATH; on MacOS X, an .app package is created in ep128emu.app. When installing the first time, you also need to set up configuration files and ROM images:
- download http://ep128emu.enterpriseforever.com/roms/ep128emu_roms.bin, and copy it to ~/.ep128emu/roms (or, in the case of MacOS X, ~/Library/Application Support/ep128emu/roms)
- after installing the ROM package, run makecfg, and click OK to the windows that pop up asking for the base directory of configuration and data files, and if configuration files should be installed
It is possible to reinstall configuration files later by running the makecfg utility.
Windows
A binary package with an installer is available at the SourceForge download page: http://sourceforge.net/projects/ep128emu/files To install, just run the executable, and follow the instructions. The installer can automatically download the ROM images needed for running the emulator, but these can also be installed manually by downloading http://ep128emu.enterpriseforever.com/roms/ep128emu_roms.7z, and extracting it to roms\ under the selected installation folder. When asked if configuration files should be reinstalled, click ‘OK’ when installing the first time, but this step can be skipped in later installations to preserve the configuration.
WARNING: on Windows, there may be timing problems when using some dual core CPUs, or power management features that change the clock frequency of the CPU while the emulator is running. These issues can result in slow or erratic emulation speed, not running at 100% speed in real-time mode, or temporary lockups. If you encounter such problems, forcing the emulator to run on a single core (by setting the CPU affinity for ep128emu.exe), and/or disabling dynamic changes to the CPU clock frequency by power management could fix the timing issues. Installing and using an utility like AMD Dual Core Optimizer may also solve the problem. Note that bad emulation performance might also be caused by display or audio drivers, so it is recommended to check (and upgrade, if necessary) those as well.
Usage
Command line options
- -h | -help | —help print the list of available command line options
- -ep128
- -zx
- -cpc select the type of machine (Enterprise, ZX Spectrum, or CPC) to be emulated
- -cfg
load an ASCII format configuration file on startup, and apply settings - -snapshot
load snapshot or demo file on startup - -opengl use OpenGL video driver (this is the default, and is recommended when hardware accelerated OpenGL is available)
- -no-opengl use software video driver; this is slower than OpenGL when used at high resolutions, and also disables many display effects, but should work on all machines; however, it will use a color depth of 24 bits, while in OpenGL mode the textures are 16 bit (R5G6B5) only, to improve performance
- -colorscheme
select GUI color scheme N (0: default, 1: Win2000, 2: plastic, or 3: Gtk+) - OPTION=VALUE set configuration variable ‘OPTION’ to ‘VALUE’; the available variable names are the same as those used in ASCII format configuration files
- OPTION set boolean configuration variable ‘OPTION’ to true
For more detailed and up to date usage information, see also the README file included with the emulator.