"I created Replay to be unique in that it was a generic emulator. By itself it would not emulate a single thing. However, it allowed emulations to be created, completely through a text file known as a .KEG.

"This meant that new games could be added to Replay without writing a single line of code or recompiling the Replay executable. In concept, I think this was a good idea, however it had a few shortcomings in practice:

1. Most of the people creating emulations are programmers and as such would rather create the emulation in a familiar language (i.e. 'C' drivers in MAME) than in something new (like the .KEG language).
2. .KEG language is interpreted and therefore much slower than a compiled language like 'C'.
3. I felt that the language wasn't quite flexible enough. For example, there would be no easy, generic way to add vector support.

OK then, so what's the difference between Replay and Replay+?

"Well, Replay+ tries to keep the spirit of Replay and add to it in the area of speed, flexibility and features.

Features:

• Written in C++ with a variety of C & ASM CPU cores.
• Support for 6502, Z80, 6809 and 68000 CPUs.
• Support for many classic arcade games from the 70's, 80's.
• Hi Score saving for all games.
• Game Saving/Loading for all games.
• Movie Record/Playback for all games.
• Network play for all games.
• Global/Local key configuration.
• Auto-saving of key configuration.
• Auto-saving of dip switch settings.
• A new fancy front-end.
• Screen Rotation/Flipping at any time at the touch of a key.
• Built-in support for cocktail modes.
• A developer's version with full source code.
• An integrated debugger for stepping through emulated CPUs (developer's).
• Game driver shared library support in Unix.
• Much more!

Supported Games:

• Replay+ v1.00 [644,268 bytes]

• Replay+ v1.00 [952,220 bytes]

• Replay v0.04 [1,143,542 bytes]

• Replay v0.01 (HPUX) [57,998 bytes]
• Replay v0.03 (SunOS) [100,344 bytes]

• Amigo Driver [3,612 bytes]
• Fixed Xevious Drivers [15,630 bytes]