> it should be enough to remove the diff files (from the diff/ folder inside the MAME
> folder)
> if the problem persists, you might need to use chdman with the command
>
> "chdman copy -i kinst.chd -o new.chd"
>
> and then to rename new.chd to kinst.chd
>
> the reason of the message is that we have updated the chd version to v5 and
> - v4 CHDs are now readonly (so in particular, diff files which contains data like
> unlocked characters, high scores, etc. cannot be written over the CHD at loading
> time)
> - v2/v3 CHDs are now unsupported
>
> you might also see around a lot of messages about issues with chdman, but they only
> concerns CHDs for laserdisc (or GDROM) games and hence have no effect at all on the
> kinst case
Then maybe that chd was built with the buggy cmpro version that came around right after 0.145 Whatever it is, I KNEW the 0.145 set was to be avoided.
|
Index 
Flat 
Re: false: there is nothing buggy about kinst
Reply
