[digi_owl]

Part of it came from the cartridge based system.

I think part one touched on how later carts would have an arrangement of RAM and ROM so that what the NES thought was graphics ROM was actually RAM that would be fed from different ROM segments based on signaling from the game logic.

This allowed later games to have very complex worlds as the graphical elements were replaced over time.

The SNES pushed this even further by allowing carts to carry coprocessors that connected to the SNES board via a special row of pins.

I suspect the last hurrah of this kind of hardware over software thinking was with the PS3 and its Cell architecture.

Both the PS4 and Xbox One use "bog standard" AMD APUs (basically CPU and GPU on a single die) by comparison.

[sopooneo]

I thought something like the ROM/RAM mixing in cartridges must be the case. But then how on earth do people make files of those games that can then run on emulators?

[pcwalton]

People have assembled lists of all known cartridge configurations (as many games tended to share the same overall configuration), and assigned them IDs. The ROM specifies, in its header, the ID of the cartridge configuration it needs. (In NES jargon these are called "mappers" [1].) The emulator is expected to hard-code support for every single mapper; this is, of course, a huge nuisance and source of complexity, but there's little that can be done about it.

[1]: http://wiki.nesdev.com/w/index.php/Mapper