EMULAB Forum

clrmamepro [English] => clrmame Discussion => Topic started by: adabo on 30 March 2012, 09:39

Title: convert newer collection to older? (139 > 119)
Post by: adabo on 30 March 2012, 09:39
Would it possible to convert (downgrade?) a rom collection 139 to 119? Thanks in advance.

So far I was able to get most, but there are many more that didn't rebuild correcly. Thanks -adabo
Title: Re: convert newer collection to older? (139 > 119)
Post by: Roman on 30 March 2012, 09:49
Sure it's possible...well...if you understand what usually "updating" means, you see why downgrading is a bit more complex.

An update includes:
- reorganization of sets (place change, parent/clone behaviour)
- renames of files
- new additions of files
- ...
- removal or replacement of bad dumps  ...and there you go...of course if you downgrade you need to find such replaced files again.

So you simply load an old dat/mame in your profiler and rebuild your 'new' set to an old one....everything missing then did simply change in the past (bad dumps replaced with new ones or complete removals)....so find such old files and you're done.

Personally I think there is no reason to downgrade anyway....but...it's your choice...
Title: Re: convert newer collection to older? (139 > 119)
Post by: adabo on 30 March 2012, 17:21
Roman, thank you very for you're insight. I wasn't aware there wasn't a reason to downgrade. I thought new collections wouldn't work with older mame versions or something. As it stands, I'm using MAME32k++(Plus! Plus!) because of it's netplay support. And that build is 119.

Oh well, thanks again for the response :)
Title: Re: convert newer collection to older? (139 > 119)
Post by: adabo on 02 April 2012, 02:29
Roman, I have another problem. The MAME vs I'm running does not work with the neogo bios files I have. I have all the necessary roms in the zip file, but the checksums don't match. Would it be possible to reverse patch these to the 119 crc's?
Title: Re: convert newer collection to older? (139 > 119)
Post by: Roman on 02 April 2012, 08:08
Different crc32 usually mean different roms.
There might be a chance that it's only a byte ordering change or a padding (which cmpro could handle if you enable "scanner->checksum->Run analysis/fix file if possible") but I doubt that...you need to find the old files and replace them.