1
clrmame Discussion / Re: Questions...
« on: Today at 07:34 »
1) chd version mismatch check will come soon in clrmame. SHA1 check won't solve the problem
2) Hmm..no, actually it detects the old ones as unneeded and sees them as fill ins for the "new" megacd. They get 'moved' to the new place. However, maybe you did not do a clean install of your MAME hash folder and still got the old hash files in their. clrmameui first takes all from -listsoftware and then scans the hash folder for additional ones which are not listed in the xml output (there are a couple which aren't included for whatever reason). So if you don't clean MAME's hash folder before unpacking the new version over it, you still get the old ones in there and clrmame will read them in as additional sl.
3)
? weird one. Unless the samples folder isn't listed as backup folder somewhere. You could check the settings.xml file for this....but the screenshot doesn't correspond to that. Is there a repeatable small scenario for it? I can try to build one based on that screenshot....
2) Hmm..no, actually it detects the old ones as unneeded and sees them as fill ins for the "new" megacd. They get 'moved' to the new place. However, maybe you did not do a clean install of your MAME hash folder and still got the old hash files in their. clrmameui first takes all from -listsoftware and then scans the hash folder for additional ones which are not listed in the xml output (there are a couple which aren't included for whatever reason). So if you don't clean MAME's hash folder before unpacking the new version over it, you still get the old ones in there and clrmame will read them in as additional sl.
3)
