my MT15.DRV reverse engineering project goes very well - when i find free time to work on it

DONE:
- fully disassembled Stunts 1 and 1.1 MT15.DRV with script based building and binary comparison to original drivers - producing 100% identical drv files
- build flags to keep the drvs binary compatible or to allow remove of dead code/data etc.
- C/asm stubs, my base for the C port - does mimic the original drv layout for beeing loadable - also builded with scripts
i've found some functions that are not in use (dead code) in both drv versions, and init data that is also not used
its very relevant for the C port to test these "cleaned-up" versions if there is anything strange happen (both work on my side so far)
attached are the re-assembled versions without the dead code/data stuff
anyone interested in testing?
NEXT:
- more analyse of the parameter/data-segment dependencies in the functions, use constants for Port/IO/MPU401 port accesses, more documentation
- combine the two driver versions into one asm source - with a flag to switch between versions - but still 100% identical drv files in the end - for history preserving reasons

- port that old dirty asm over to C - at this point only function identical - binary equality is hard to reach using a C compiler
- understand the known bug in the 1.1 version
- port the other drivers also this way
im using Dosbox Staging for testing - the lastest development version integrates the MT32 stuff so its easier to get it going
download the alpha here if you got a github account:
https://dosbox-staging.github.io/downloads/devel/ (clicks windows link and the the bottom dosbox-staging-windows-x64-v0.77.0-alpha-856-g2e93f file)
your dosbox staging config should then contain
[midi]
mididevice=mt32
[mt32]
romdir=rom-dir # use the mame roms
model=mt32_old # for original stunts release version of MT32
#model=cm32l_102 # or the new one