Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Mame 0.78 database for MAME 2003 - FB Alpha updated to v0.2.97.38 - New Game and Watch database #139

Merged
merged 12 commits into from Jun 11, 2016
Merged

Mame 0.78 database for MAME 2003 - FB Alpha updated to v0.2.97.38 - New Game and Watch database #139

merged 12 commits into from Jun 11, 2016

Commits on Jun 8, 2016

  1. MAME dat file for Mame2003 libretro, based on 0.78 romset - cleaned v… 

    …ersion (without BIOS and issue with charset)
    @lollo78
    lollo78 committed Jun 8, 2016
    Configuration menu
    Copy the full SHA
    1afb2d8 View commit details
    Browse the repository at this point in the history

  2. MAME rdb file for Mame2003 libretro, based on 0.78 romset - cleaned v… 

    …ersion (without BIOS and issue with charset)
    @lollo78
    lollo78 committed Jun 8, 2016
    Configuration menu
    Copy the full SHA
    5e406d6 View commit details
    Browse the repository at this point in the history

  3. Final Burn Alpha dat based on v0.2.97.38 

    Considering that https://github.com/libretro/libretro-fba support v0.2.97.38, I decided to update the previous Kivutar FBA dat (v0.2.97.36).
The only romset v0.2.97.38 available on the Web is created from the same guy who released also the v0.2.97.36. But now, he use a different approach: now he merge the clones into the parents roms to save disk space.
Considering that most people who download this romset will not split the clones from the respective parents, I propose to update our dat/rdb on the new (merged) romset. 
For now, my dat calculate the CRC of the zip file (not the zip content). This because libretro-fba can't manage merged roms.
One day (adding merged roms support into the core), maybe, calculating the CRC of the content could be a best solution. Of course, in this case I'll update again the file.
    @lollo78
    lollo78 committed Jun 8, 2016
    2 Configuration menu
    Copy the full SHA
    1524113 View commit details
    Browse the repository at this point in the history

  4. Final Burn Alpha rdb based on v0.2.97.38 

    Considering that https://github.com/libretro/libretro-fba support v0.2.97.38, I decided to update the previous Kivutar FBA dat (v0.2.97.36).
The only romset v0.2.97.38 available on the Web is created from the same guy who released also the v0.2.97.36. But now, he use a different approach: now he merge the clones into the parents roms to save disk space.
Considering that most people who download this romset will not split the clones from the respective parents, I propose to update our dat/rdb on the new (merged) romset. 
For now, my dat calculate the CRC of the zip file (not the zip content). This because libretro-fba can't manage merged roms.
One day (adding merged roms support into the core), maybe, calculating the CRC of the content could be a best solution. Of course, in this case I'll update again the file.
    @lollo78
    lollo78 committed Jun 8, 2016
    Configuration menu
    Copy the full SHA
    6255a66 View commit details
    Browse the repository at this point in the history

  5. MAME dat file for Mame2003 libretro, based on 0.78 romset - cleaned v… 

    …ersion (without BIOS and issue with charset)

Sorry there was still a BIOS in the database.
    @lollo78
    lollo78 committed Jun 8, 2016
    Configuration menu
    Copy the full SHA
    0756198 View commit details
    Browse the repository at this point in the history

  6. MAME rdb file for Mame2003 libretro, based on 0.78 romset - cleaned v… 

    …ersion (without BIOS and issue with charset)

Sorry there was still one BIOS in the database
    @lollo78
    lollo78 committed Jun 8, 2016
    Configuration menu
    Copy the full SHA
    044d919 View commit details
    Browse the repository at this point in the history

Commits on Jun 9, 2016

  1. Restored the old MAME.dat

    @lollo78
    lollo78 committed Jun 9, 2016
    Configuration menu
    Copy the full SHA
    5d44a21 View commit details
    Browse the repository at this point in the history

  2. Restored the old MAME.rdb

    @lollo78
    lollo78 committed Jun 9, 2016
    Configuration menu
    Copy the full SHA
    2ca15a8 View commit details
    Browse the repository at this point in the history

  3. New MAME2003.dat - renamed to avoid overwriting of the previous MAME.dat

    @lollo78
    lollo78 committed Jun 9, 2016
    Configuration menu
    Copy the full SHA
    9d3267d View commit details
    Browse the repository at this point in the history

  4. New MAME2003.rdb - renamed to avoid overwriting of the previous MAME.rdb

    @lollo78
    lollo78 committed Jun 9, 2016
    Configuration menu
    Copy the full SHA
    abbc43c View commit details
    Browse the repository at this point in the history

Commits on Jun 11, 2016

  1. New "Game and Watch" DAT, updated according the last gw repository on h… 

    …ttps://buildbot.libretro.com/assets/cores/gw/
    @lollo78
    lollo78 committed Jun 11, 2016
    Configuration menu
    Copy the full SHA
    9411b4b View commit details
    Browse the repository at this point in the history

  2. New "Game and Watch" RDB, updated according the last gw repository on h… 

    …ttps://buildbot.libretro.com/assets/cores/gw/
    @lollo78
    lollo78 committed Jun 11, 2016
    Configuration menu
    Copy the full SHA
    340eab9 View commit details
    Browse the repository at this point in the history