This paper synthesizes knowledge from scattered literature and practical implementations to define the design space of VXP emulators, with an emphasis on those that emulate platforms originally implemented as interpreters themselves (i.e., recursive emulation). The intended audience includes software preservationists, security researchers, and engineers dealing with legacy systems. 2.1 Rise of Bytecode Machines The 1970s and 1980s saw the rise of portable intermediate languages. UCSD Pascal’s p-Code (1977) allowed the same compiled code to run on any machine with a p-Code interpreter. Similarly, the Z-machine (1979) for interactive fiction games provided a stable target for Infocom’s text adventures across dozens of disparate home computers. These are early VXPs. 2.2 Proprietary Industrial VXPs Many industrial control systems, telecom switches, and arcade game boards used custom VXPs to reduce hardware costs. For example, the Namco C68 and other arcade sound drivers ran bytecode on a dedicated virtual CPU. When those hardware systems fail, an emulator that understands the VXP can revive the software. 2.3 Abandonware and Preservation A significant motivation for VXP emulation is digital preservation. Without the original interpreter or hardware, software becomes inaccessible. Emulating the VXP—rather than the entire original physical machine—can be sufficient to run the application logic, especially when the VXP abstracts away I/O differences. 2.4 Security Research Malicious software sometimes uses custom VXPs as obfuscation layers. A VXP emulator becomes a tool for dynamic analysis: by emulating the virtual CPU, analysts can observe the behavior of the decoded malware without executing it natively. 3. Core Technical Architecture of a VXP Emulator A VXP emulator is typically structured as an interpreter or a dynamic binary translator (DBT) operating at the virtual ISA level. 3.1 Instruction Fetch and Decode Loop The simplest architecture is a fetch-decode-execute loop over the virtual bytecode:
while (!halted) opcode = memory[pc++]; switch (opcode) case ADD: // virtual add case LOAD: // virtual load ... vxp emulator
However, many VXPs have become obsolete as hardware and software paradigms shifted. The software written for these platforms—often mission-critical or culturally significant—risks being lost. A VXP emulator addresses this problem by reimplementing the behavior of a given VXP on contemporary hardware, often at a higher level than full system emulation. Unlike full-system emulators (e.g., QEMU) that simulate entire physical machines, a VXP emulator targets only the virtual layer, potentially offering greater portability and simplicity. UCSD Pascal’s p-Code (1977) allowed the same compiled