RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login
    Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

    lrmame-2010 .139 roms / CHD question

    Scheduled Pinned Locked Moved Help and Support
    3 Posts 3 Posters 4.5k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • F
      Flex_Bacontrim
      last edited by

      The preferred .139 ROM set does not include .chd files, and I can't find any CHD set until version 0.161. As far as using with Retropie, am I best off to use the select .161 chd files with the .139 rom set or update the whole thing (or just the ROMs that need the .chds)?

      1 Reply Last reply Reply Quote 0
      • dankcushionsD
        dankcushions Global Moderator
        last edited by

        lr-mame2010 is very experimental and doesn't have a lot of useful features, so i wouldn't use it at all :)

        CHDs are the same as regular mame files in that the mame core will be looking for a specific checksum, and there are variety of CHD 'versions' that have been used in different mame sets, so CHDs from other sets may or may not work in .139. i think there are programs for changing a given CHD to a different version, but I've not used them before.

        1 Reply Last reply Reply Quote 0
        • RiverstormR
          Riverstorm
          last edited by Riverstorm

          I think 0.139 used CHD v4 (lr-mame2010) and 0.161 used CHD v5. You'll need a rollback file and use chdman from a command line (this can take a while for a whole set) if you can't find v4 CHDs.

          I think these are the correct CHD versions if not they are close.

          1. mame4all-pi (0.37b5) - N/A (CHD wasn't introduced until 0.62 or 0.63)
          2. lr-imame4all (0.37b5) - N/A (CHD wasn't introduced until 0.62 or 0.63)
          3. lr-mame2003 (0.78) - CHD v3
          4. lr-mame2010 (0.139) - CHD v4
          5. advmame-.94 (0.94) - CHD v3
          6. advmame-1.4 (0.106) - CHD v3
          7. pifba (0.114) - CHD v3
          8. lr-fba (0.154) - CHD v5
          9. lr-fba-next (0.173) - CHD v5
          10. gngeopi (0.138) - CHD v4

          Knowing the CHD versions could be useful as the Pi gets more powerful. :) I think some versions of MAME could use earlier versions of CHDs as "readonly" but if it was a CHD that could be written to for like high scores or something it doesn't work without the correct version.

          Instead of modifying the CHD directly (which would change the internal/external hash--MAME only cares about the internal hash which is data minus metadata) I believe MAME would auto-create a <game>.diff file and use it.

          I think current versions of chdman can verify older versions but not vice versa for obvious reasons. :)

          Newer versions command line:
          chdman verify -i area51.chd
          chdman info -i area51.chd (shows CHD version & other info)

          Older versions command line:
          chdman -verify area51.chd
          chdman -info area51.chd (shows CHD version & other info)

          1 Reply Last reply Reply Quote 2
          • First post
            Last post

          Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

          Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.