Skip to content

M65 C65 emulator differences explained

LGB edited this page Oct 11, 2021 · 4 revisions

M65 / C65 emulator differences explained

Currently, Xemu contains two "targets" (ie emulation targets): for Commodore65 (C65) and MEGA5 (M65).

C65 emulator

More information: main article about C65 emulation of Xemu

For the C65 emulator, the goal is to emulate a C65 without any M65 feature, maybe even at the price having incompatibility with M65 (or C64), if there is some C65-M65 difference at all. C65 emulation is much more simple, requires lower resources, and some different internal structure of the emulator fits better than implementing M65. Currently, the C65 emulator can handle D81 disk images directly, specified from the command line. Access is limited to read-only for now.

C65 emulator can "boot", can go into "C64 mode", and some software like the "K2 demo" partially runs at least.

M65 emulator

More information: main article about M65 emulation of Xemu

Though M65 emulator was basically a fork of the C65, however it strongly diverged into another direction, because of:

  • more and differently organized features, even if they seem compatible with each other from the surface
  • the stronger need of debug tools for M65 development which at the other hand, requires "deeper" level of things too
Clone this wiki locally