> Add this to your engine.cfg and you got internal M1 support (well...at least for
> the latest M1 version)
>
> engine (
> name M1
> cachefile _m1dat
> command -d
> )
>
>
> Roman Scherzer
> ClrMamePro

This is sweet! Will the new engine.cfg with M1 included be part of future ClrMamePro releases or do we need to make sure we don't overwrite our engine.cfg each time?

Cheers,
Tim