> No, it just means Donkey Kong has wrong colors, incorrect sound, a few pixel-off > glitches, and a slightly incorrect gameplay speed. Most people probably won't notice, > but you don't want to train to beat Steve Wiebe on it either. MAMEdev has not sat > still on "the true classics" in the last 10 years. In that time nearly all the major > classics have been improved in some way or another: Pac-Man, DK, Space Invaders, > Galaga, Gyruss, Mappy, just to name a few, have all improved.
I'm curious RB. My understanding of the MAME code base is very limited, but I understand enough to know that the drivers have undergone many architecture revisions. Nevertheless, I could still be talking completely out of my ass here... Would I be correct in assuming that you can't take (for example) the current Donkey Kong driver and replace the one in the 0.37b5 source, and expect it to compile, much less work? I think part of what prevents MAME4All from adopting the improvements may be a lack of understanding on how to take the drivers in their current form, and retro them back to 0.37. As for why someone doesn't take 0.143 source code and adapt it to Android, would I again be correct in assuming that MAME was more portable (in the compiler sense) back in 0.37 than it is today? I thought modern MAME leverages x86 and x64 architecture much more so today than it did in the past.