> For some reason, its still not updating v4 CHDs to v5. Using CHD_Man FE (I'm lazy).
>
> ** It appears to be a problem with CHD_Man FE as using CHDMAN worked fine using CLI.
> Problem now is CLRMAME is bitching that sfiii now has the wrong SHA1. I thought only
> Naomi stuff was screwed up moving to v5????
Just like i said before....
Wait for clrmamepro do the job and ask for new v5 chd's!
Without that you will get a lot of problems....
Make a backup of v4 before is to late.
This is the way to do it.
In the next updates if mame updates offcially the CHD it will go to the backup files, and ask to update.
So grab the CHD from backup folder, and then you need to update. Without that you can´t do nothing.
|
Previous 
Index 
Next 
Flat 
Re: Did you update CHDMAN?
Reply
MAME_0.146u1b_32-bit...
