|
Killer instinct brags about "unsupported chd file"
#279322 - 03/15/12 05:29 PM
|
|
|
mame ui 145.4 x64 ,i updated the whole romset,downloaded the whole .145 chd fileset and i still get the "kinst error unsupported chd file"...i'm going nuts,i changed folders,scanned all the roms again..nothing,both this and kinst 2 give same error..why?
|
|
|
|
Re: Killer instinct brags about "unsupported chd file"
[Re: Solstar]
#279324 - 03/15/12 05:50 PM
|
|
|
Wasn't 0.145 release buggy? You should have waited 0.146 to update your set.
|
|
|
|
Re: Killer instinct brags about "unsupported chd file"
[Re: ReadOnly]
#279325 - 03/15/12 05:56 PM
|
|
|
d'oh..:( oh well mame 0.145 seems to work fine so far...
|
|
|
| mesk |
|
@ the arcade
|
|
|
|
|
Reged: 03/03/11
|
|
Posts: 484
|
|
Loc: Rhode Island
|
|
|
|
Send PM
|
|
|
Re: Killer instinct brags about "unsupported chd file"
[Re: Solstar]
#279329 - 03/15/12 06:28 PM
|
|
|
It may be based on where did you get the roms from (dont post it here)
Since KI was the very first CHD game it may very well be a v2 or even v1 chd,which MAME doesnt support anymore.
Although I could be 100% wrong here as well.Just my .02 
|
|
|
|
Re: Killer instinct brags about "unsupported chd file"
[Re: mesk]
#279331 - 03/15/12 06:31 PM
|
|
|
I highly doubt that v1, 2 or 3 chds which are already included in MAME are still floating around....(besides of maybe 2 which were updated anyway within the 145u circle already).
a correct v4 kinst chd should work flawlessly in current MAME.
|
|
|
|
false: there is nothing buggy about kinst
[Re: ReadOnly]
#279333 - 03/15/12 06:35 PM
|
|
|
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
|
|
|
|
Re: Killer instinct brags about "unsupported chd file"
[Re: Roman]
#279335 - 03/15/12 06:35 PM
|
|
|
> a correct v4 kinst chd should work flawlessly in current MAME.
not if he has diff files, because now the v4 chds are read only 
|
|
|
|
Re: false: there is nothing buggy about kinst
[Re: etabeta]
#279336 - 03/15/12 06:38 PM
|
|
|
> 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.
|
|
|
| B2K24 |
|
MAME @ 15 kHz Sony Trinitron CRT user
|
|
|
|
|
Reged: 10/25/10
|
|
Posts: 2663
|
|
|
|
|
|
Send PM
|
|
|
Re: false: there is nothing buggy about kinst
[Re: ReadOnly]
#279340 - 03/15/12 07:08 PM
|
|
|
> 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.
ClrMamePro does not rebuild CHDs
|
|
|
|
Re: Killer instinct brags about "unsupported chd file"
[Re: etabeta]
#279342 - 03/15/12 07:13 PM
|
|
|
well....I was talking about a clean environment of course...
cleaning cfg, diff and nvram is a must....
|
|
|
|
Re: false: there is nothing buggy about kinst
[Re: B2K24]
#279343 - 03/15/12 07:20 PM
|
|
|
Did I say it does? OK I said the word "built" but I meant updated with cmpro, I thought it didn't require an explanation.
|
|
|
|
Re: Killer instinct brags about "unsupported chd file"
[Re: etabeta]
#279348 - 03/15/12 07:54 PM
|
|
|
deleting the diff solved everything...o_O
|
|
|
| Sune |
|
Connected
|
|
|
|
|
Reged: 09/21/03
|
|
Posts: 5648
|
|
Loc: Lagoa Santa, Brasil
|
|
|
|
Send PM
|
|
|
Re: false: there is nothing buggy about kinst
[Re: ReadOnly]
#279359 - 03/15/12 09:53 PM
|
|
|
> Did I say it does? OK I said the word "built" but I meant updated with cmpro, I
> thought it didn't require an explanation.
Okay then have it your way, cmpro does not "update" CHDs.
S
|
|
|
| Naoki |
|
|
|
|
|
|
Reged: 11/10/09
|
|
Posts: 1998
|
|
Loc: United Kingdom
|
|
|
|
Send PM
|
|
|
Re: Killer instinct brags about "unsupported chd file"
[Re: Solstar]
#279365 - 03/15/12 10:41 PM
|
|
|
Yeah because the diff is from the older mame and the newer one cant read the old diffs correctly AFAIK
|
----
On a quest for Digital 573 and Dancing Stage EuroMix 2
By gods I've found it!
|
|
|
Re: false: there is nothing buggy about kinst
[Re: Sune]
#279377 - 03/15/12 11:49 PM
|
|
|
Weird, I was pretty sure there was a problem either on mame/chdman part or on cmpro part when the new format came out. I clearly remember many complains about chd being corrupted or permanently deleted. Ha*e posted something about that also I think. I don't think I have imagined all of this.
|
|
|
| R. Belmont |
|
Cuckoo for IGAvania
|
|
|
|
|
|
Reged: 09/21/03
|
|
Posts: 9716
|
|
Loc: ECV-197 The Orville
|
|
|
|
Send PM
|
|
|
Re: false: there is nothing buggy about kinst
[Re: ReadOnly]
#279386 - 03/16/12 12:26 AM
|
|
|
> Weird, I was pretty sure there was a problem either on mame/chdman part or on cmpro
> part when the new format came out. I clearly remember many complains about chd being
> corrupted or permanently deleted.
chdman can't corrupt or permanently delete anything. Worst it can do is convert your old working v4 chds to incorrect v5 ones. And AFAIK most people had the presence of mind not to delete their old chds after conversion so no harm was possible.
|
|
|
Index 
Threaded 
Killer instinct brags about "unsupported chd file"
Reply
[Re: 
