> > Just a note. Not everybody knows they can follow progress of a game or driver by > > browsing the GIT source code. > > I think this info could be put somewhere either in this forum or in mamedev > website, > > so people would stop asking about progress in a game/driver. > > MAMEDEV.ORG already has an area that someone goes through great lengths to attempt to > keep updated periodically with information as related towards machines which have > condition flags: > http://wiki.mamedev.org/index.php/Non-Working_Drivers > > You can either search for a driver (sometimes a specific setname) and come up with > the reason why something is flagged. Once a condition changes, these are adjusted. > > Outside of that, the users themselves owe it to themselves to do a little research by > reading whatsnew.txt document with monthly releases to see if a particular issues has > been resolved/improved. Of course, we always encourage all who are able to view up to > the minute GIT progress which can be seen here: > https://github.com/mamedev/mame/commits/master
Sounds like this one's gonna be changing in the future:
ghox, ghoxj, whoopee - No sound because of missing sound MCU dump. Chip is protected. It's a QFP80 Hitachi HD647180. Whopeee misses the dump too, but is currently using one from a bootleg.
"Note to Noobs:
We are glad to help you but simply posting that something does not work is not going to lead to you getting help. The more information you can supply defining your problem, the less likely it will be that you will get smart-alec replies.