The nodump - gooddump replacement only happens when the cache is being built. So each time the underlying dat or mame exe has changed. It doesn't happen when the cache is being loaded.

In other words, the dat/mame exe holds the problematic gooddump/nodump situation. While parsing they get optionally replaced and the cache is saved with the replacement. If the dat/exe changed again, the file is reparsed and the problem appears again.


...besides I'm on holiday and some thousand kilometers away from my pc........



Roman Scherzer