> Probably not without editing and recompiling the source code. MAME is still in its
> infancy regarding modular devices, with only certain drivers having such a thing;
> it's much more common for a driver to still have fake "dip switches" or machine
> configuration toggles with several hard coded options which were known to be valid on
> real hardware, and with no real concept of emulating faulty hardware such as bad RAM
> or a mandatory device left unconnected. In some cases, MAME's emulation is too
> high-level (in before MAME-haters say MAME is already too slow!) so things like
> out-of-spec voltages, bad capacitors or faulty glue logic (e.g. 74xx chips) causing
> random errors won't show up in MAME.
This is an excellent explanation. I would add that MAME exists to emulate working hardware, not non-working hardware, even though most drivers don't work when they're first added to MAME and despite the fact that many PCBs were not in working condition at the time they were obtained for dumping. Generally it isn't worth the effort to emulate incomplete or faulty hardware, though MAME does allow you to do things like removing slotted keyboards from PCs that will complain about their absence. It is, however, often possible to force the emulated CPUs down incorrect code paths by fiddling with debugger features such as watchpoints and state registers, if you know what data to modify and when to modify it; this method can be used to force memory tests to fail, for example.
Edited by AJR Hacker (04/15/23 04:37 AM)
|
Previous 
Index 
Next 
Flat 
Re: How do I (is this even possible?)...
Reply
