> A 100% clean set at this point will be a mix of V4 and V5 CHDs. There is no way
> around it and they are marked BAD_DUMP for a reason.
>
> Here is a list of what should stay at V4 because they change SHA1 when converted. You
> can manually move out these directories, convert what's left and then move them back
> in.
>
> http://pastebin.com/8QkbZzgS
My impression is that, at this time, it's impossible to update the chds based just on Cmpro (even the last one that Roman posted in the forum that can filter baddumps). Cmpro will give you an incomplete list of chds to update and at least four of these you should not update. I don't know where exactly the problem is, but I see two possibilities: the chds aren't well documented as bad or good dumps in Mame source or Cmpro's implementation for listing baddumps isn't yet well refined.
I made a batch with your (B2K24) list (it isn't completely tested since I'm half way in the update processes), that puts all these chds in a folder named 0gdroms (the name doesn't make much sense but I don't feel like changing):
http://pastebin.com/TJtj2STA
This is my understanding, don't take just my word in this, listen to user more experienced than me.
|
Index 
Flat 
Re: Is there a new chdman for 146u3?
Reply
