
The changes are mostly user-interface related, and the focus is on development and debugging features rather than accuracy of emulation, so it probably won't have broad appeal (outside of the millions of people who are already using X68000-based technology on a daily basis, of course).
In short: if you can't identify the humor in the name of this emulator, it's probably not the program for you.
Those who don't do anything more complex than inserting virtual floppy disks might prefer
XM6 Type G,
the WinX68k High-Speed Version,
or even XM6 version 2.06 (the final official version).
The WinX68k Tracer Version emulator
might also be worth a look thanks to some of its features (such as fast-forwarding and state saving),
despite being geared toward hacking.
Some features that I've finished thus far include:
|
| |
XM6 already had a professional interface with some pretty powerful debugging features,
so the above changes are just scratching the surface of what it can do. Play around with
version 2.06 if you're unfamiliar with it. Frankly, I've been using XM6 for years and am
still not conversant with all of its abilities.
While you're waiting (perhaps perpetually) for this to be released, you can send comments, requests, flames, threats, etc. to the email address found on the M.I.J.E.T. Home Page.
One thing I'd really like someone to tell me is if there are any games/demos that require the Mercury-Unit.
The source code to version 2.06 would also be great, although I doubt anyone but PI has it.
Loading a directory (recursively) as a disk image.
Here we've loaded Human68k from a directory and caused a double bus fault.
It's pretty common for 68000 emulators to lock up or crash when this happens,
and XM6's Starscream core was no exception (fixed here, as you can see).
The debugging windows can all be opened/closed and rearranged with single menu commands now.
You can also see one of the improvements added to the memory window, and backslashes instead
of the Yen sign (forced in SRAM on startup).
And yes, it's dual-language. Sort of.
(Pictured is the new RAM-dumping command.)