|
Problems converting to CHD v5
#280683 - 03/28/12 12:59 AM
|
|
|
Anyone succeeded in converting all chd from v4 to v5...?
I succeeded with a few, not all yet, but :
ie: Super Major League / World Series Baseball (GDS-0010) [system: Naomi GD-ROM Bios - folder: wsbbgd]
if I keep it to v4, clrmame says that it has to be converted to v5.
if I try to do such (chdman copy -i gds-0010.chd -o new.chd, delete old then rename new.chd to its right name), clrmame wants to delete the resulted chd file and says i'm missing it...?
Any ideas...?
Thanks, MAMu_
|
|
|
|
Re: Problems converting to CHD v5
[Re: MAMu_]
#280693 - 03/28/12 01:42 AM
|
|
|
> Anyone succeeded in converting all chd from v4 to v5...?
>
> I succeeded with a few, not all yet, but :
>
> ie: Super Major League / World Series Baseball (GDS-0010) [system: Naomi GD-ROM Bios
> - folder: wsbbgd]
>
> if I keep it to v4, clrmame says that it has to be converted to v5.
> if I try to do such (chdman copy -i gds-0010.chd -o new.chd, delete old then rename
> new.chd to its right name), clrmame wants to delete the resulted chd file and says
> i'm missing it...?
>
> Any ideas...?
>
> Thanks, MAMu_
Same problem with gds-0011.chd (vtennisg)
Is there an issue with gd-rom chd files not converting correctly to v5...?
Seems that it's better to keep v4 for these...
|
|
|
| H@P |
|
Lurker in perpetuity
|
|
|
|
|
Reged: 09/22/03
|
|
Posts: 234
|
|
Loc: Seattle area
|
|
|
|
Send PM
|
|
|
Re: Problems converting to CHD v5
[Re: MAMu_]
#280694 - 03/28/12 01:42 AM
|
|
|
I'm waiting for 0.146 to let chdman bugs settle, but this probably has something to do with it.
From MAME 0.145u5 whatsnew:
Marked all GD-ROMs except Under Defeat as BAD_DUMP. These need to be re-converted to CHD from the .GDI source with current CHDMAN [R. Belmont]
H@P
Edited by H@P (03/28/12 01:49 AM)
|
|
|
|
Re: Problems converting to CHD v5
[Re: H@P]
#280695 - 03/28/12 01:44 AM
|
|
|
> I'm waiting for 0.146 to let chdman bugs settle, but maybe this has something to do
> with it.
>
> From MAME 0.145u5 whats new:
>
> Marked all GD-ROMs except Under Defeat as BAD_DUMP. These need to be re-converted to
> CHD from the .GDI source with current CHDMAN [R. Belmont]
>
> H@P
k thx 
will only convert under defeat and all non gd-roms then 
|
|
|
| John IV |
|
IV/Play, MAME, MAMEUI
|
|
|
|
|
Reged: 09/22/03
|
|
Posts: 1970
|
|
Loc: Washington, USA
|
|
|
|
Send PM
|
|
|
Re: Problems converting to CHD v5
[Re: MAMu_]
#280715 - 03/28/12 05:41 AM
|
|
|
|
|
|
Re: Problems converting to CHD v5
[Re: MAMu_]
#280725 - 03/28/12 10:10 AM
|
|
|
which chdman are you using?
the one built with the current source (u5) will convert the discs fine (even the dumps are currently bad, and the chd has to be recreated from raw gdi files)
the one built with u1-u2 source won't handle properly the gdroms
anyway, you can safely convert all chds but the laserdiscs to v5 at this point. the worst that can happen is that some disc make chdman to freeze but it seems to be happening at random (and only on windows) so it's not really easy to debug the problem 
|
|
|
|
Re: Problems converting to CHD v5
[Re: etabeta]
#280726 - 03/28/12 11:08 AM
|
|
|
Wasn't the LD issue fixed by Aaron in u4 already? IIRC there was something listed in whatsnew.txt....
|
|
|
|
Re: Problems converting to CHD v5
[Re: MAMu_]
#280727 - 03/28/12 12:07 PM
|
|
|
Sorry to hang this in the thread but this has picked my curiosity. Unless I misinterpreted it somehow, developers used to say CHD is not precisely an imaging format but a packaging (a container) one just like zip and 7z. That means if you compress a GD-ROM you would get the same GD-ROM if you extract it. If you take an estrange formatting ISO like PC Engine, you'll technically get the same file you used to create the CHD with on extraction (although in a single BIN/CUE instead of the separated file/tracks format most collections do).
What's to stop CHDs from extract them using the same chdman version, then create a new CHD with a current chdman?
|
|
|
|
Re: Problems converting to CHD v5
[Re: Roman]
#280731 - 03/28/12 02:07 PM
|
|
|
not completely: the conversion now completes and the hash remains correct, but still some laserdisks fail -verify after the conversion (cubeqst has been reported as a testcase)
so while the update procedure should be already correct, there is still something going wrong (probably with metadata or the header), so I don't suggest average users to convert laserdisks... you know: the larger are the files, the larger are the complaints if anything goes wrong
|
|
|
|
Re: Problems converting to CHD v5
[Re: BIOS-D]
#280732 - 03/28/12 02:11 PM
|
|
|
the fact that the old code to handle gdi files was not storing properly all the data, so extracting the content was not giving back the correct file
this is one of the reasons which pushed Arbee to add an "extractgdi" option to allow easier testing of the extraction (which is now fully correct)
of course, since chdman uses different code to handle different media (hd/ld/cd/gd) the above only applies to the gd-roms
|
|
|
| R. Belmont |
|
Cuckoo for IGAvania
|
|
|
|
|
|
Reged: 09/21/03
|
|
Posts: 9716
|
|
Loc: ECV-197 The Orville
|
|
|
|
Send PM
|
|
|
Re: Problems converting to CHD v5
[Re: MAMu_]
#280736 - 03/28/12 04:44 PM
|
|
|
> will only convert under defeat and all non gd-roms then
Conversion won't work. Under Defeat is special because it is a brand new re-dump using the new CHDMAN. Therefore it's not BAD_DUMP, and you can't create it by converting the old one.
|
|
|
|
Re: Problems converting to CHD v5
[Re: etabeta]
#280760 - 03/28/12 07:50 PM
|
|
|
> the fact that the old code to handle gdi files was not storing properly all the data,
> so extracting the content was not giving back the correct file
>
> this is one of the reasons which pushed Arbee to add an "extractgdi" option to allow
> easier testing of the extraction (which is now fully correct)
>
> of course, since chdman uses different code to handle different media (hd/ld/cd/gd)
> the above only applies to the gd-roms
I get it now, thanks.
|
|
|
|
Re: Problems converting to CHD v5
[Re: etabeta]
#280882 - 03/29/12 07:22 PM
|
|
|
> which chdman are you using?
> the one built with the current source (u5) will convert the discs fine (even the
> dumps are currently bad, and the chd has to be recreated from raw gdi files)
> the one built with u1-u2 source won't handle properly the gdroms
>
What is the proper way to convert these files then? I take it you just cant
use the copy comand in chdman then? do you take the original gdrom and convert
to raw then convert back to gdrom?
just trying to clarify so that I do it correctly.
thank you.
|
Only here to annoy...
|
|
|
Re: Problems converting to CHD v5
[Re: John IV]
#281006 - 03/31/12 12:08 AM
|
|
|
> Also clrmame now has an option to ignore version errors.
Where is this option?
|
|
|
| B2K24 |
|
MAME @ 15 kHz Sony Trinitron CRT user
|
|
|
|
|
Reged: 10/25/10
|
|
Posts: 2663
|
|
|
|
|
|
Send PM
|
|
|
Re: Problems converting to CHD v5
[Re: Smitdogg]
#281013 - 03/31/12 01:39 AM
|
|
|
settings tab then choose compressor
chdman tab
|
|
|
|
Re: Problems converting to CHD v5
[Re: B2K24]
#281014 - 03/31/12 01:41 AM
|
|
|
|
|
Index 
Threaded 
Problems converting to CHD v5
Reply
[Re: 
