我知道这个问题有点老了，但我想在讨论中补充一些东西。这里的大多数答案都围绕模拟器解释它们所模拟的系统的机器指令。

然而，有一个非常著名的例外，称为“UltraHLE”(维基百科文章)。UltraHLE是有史以来最著名的模拟器之一，它模拟了商用任天堂64游戏(在家用电脑上表现不错)，当时人们普遍认为这是不可能的。事实上，当UltraHLE诞生时，任天堂还在为任天堂64制作新游戏!

这是我第一次在印刷杂志上看到关于模拟器的文章，而以前我只在网上看到过它们的讨论。

UltraHLE的概念是通过模拟C库调用而不是机器级调用来实现不可能。

模拟可能看起来令人生畏，但实际上比模拟容易得多。

任何处理器通常都有一个编写良好的描述状态、交互等的规范。

如果您根本不关心性能，那么您可以使用非常优雅的面向对象程序轻松地模拟大多数老式处理器。例如，X86处理器需要一些东西来维护寄存器的状态(简单)，需要一些东西来维护内存的状态(简单)，还需要一些东西来接收每个传入的命令并将其应用到机器的当前状态。如果您真的需要准确性，您还可以模拟内存转换、缓存等，但这是可行的。

In fact, many microchip and CPU manufacturers test programs against an emulator of the chip and then against the chip itself, which helps them find out if there are issues in the specifications of the chip, or in the actual implementation of the chip in hardware. For example, it is possible to write a chip specification that would result in deadlocks, and when a deadline occurs in the hardware it's important to see if it could be reproduced in the specification since that indicates a greater problem than something in the chip implementation.

当然，电子游戏的模拟器通常关心性能，所以它们不会使用简单的实现，它们还包括与主机系统的操作系统接口的代码，例如使用绘图和声音。

考虑到老式电子游戏(NES/SNES等)非常缓慢的性能，在现代系统上进行仿真相当容易。事实上，更令人惊讶的是，你可以下载一套SNES游戏或Atari 2600游戏，考虑到当这些系统流行时，免费访问每个卡带都是一个梦想。

我写过一篇关于用JavaScript模拟Chip-8系统的文章。

这是一个很好的开始，因为系统不是很复杂，但你仍然了解操作码、堆栈、寄存器等是如何工作的。

我将很快为NES写一篇更长的指南。

当你开发一个模拟器时，你是在解释系统正在运行的处理器组件(Z80、8080、PS CPU等)。

您还需要模拟系统拥有的所有外设(视频输出、控制器)。

你应该开始为简单的系统编写模拟器，比如旧的Game Boy(使用Z80处理器，我是不是没有弄错)或C64。

在创建了我自己的80年代BBC微型计算机模拟器(类型VBeeb到谷歌)后，有许多事情要知道。

You're not emulating the real thing as such, that would be a replica. Instead, you're emulating State. A good example is a calculator, the real thing has buttons, screen, case etc. But to emulate a calculator you only need to emulate whether buttons are up or down, which segments of LCD are on, etc. Basically, a set of numbers representing all the possible combinations of things that can change in a calculator. You only need the interface of the emulator to appear and behave like the real thing. The more convincing this is the closer the emulation is. What goes on behind the scenes can be anything you like. But, for ease of writing an emulator, there is a mental mapping that happens between the real system, i.e. chips, displays, keyboards, circuit boards, and the abstract computer code. To emulate a computer system, it's easiest to break it up into smaller chunks and emulate those chunks individually. Then string the whole lot together for the finished product. Much like a set of black boxes with inputs and outputs, which lends itself beautifully to object oriented programming. You can further subdivide these chunks to make life easier.

Practically speaking, you're generally looking to write for speed and fidelity of emulation. This is because software on the target system will (may) run more slowly than the original hardware on the source system. That may constrain the choice of programming language, compilers, target system etc. Further to that you have to circumscribe what you're prepared to emulate, for example its not necessary to emulate the voltage state of transistors in a microprocessor, but its probably necessary to emulate the state of the register set of the microprocessor. Generally speaking the smaller the level of detail of emulation, the more fidelity you'll get to the original system. Finally, information for older systems may be incomplete or non-existent. So getting hold of original equipment is essential, or at least prising apart another good emulator that someone else has written!

是的，你必须“手工”解释整个二进制机器码的混乱。不仅如此，大多数情况下，您还必须模拟一些在目标机器上没有等效硬件的外来硬件。

简单的方法是一个接一个地解释指令。这工作得很好，但是很慢。一种更快的方法是重新编译——将源机器码转换为目标机器码。这比较复杂，因为大多数指令都不是一对一映射的。相反，您将不得不制定涉及额外代码的详细变通方案。但最终还是要快得多。大多数现代模拟器都是这样做的。