Jump to content
LaunchBox Community Forums

Exporting MAME Roms from LB


The Papaw
Go to solution Solved by JoeViking245,

Recommended Posts

Can you export MAME roms from a Merged set like you can with a non-merged set. Like shown in last youtube video? Going to build a new setup using 0.273 and need to be able to export them for NAS. I do use chd files as well if that matters

Edited by The Papaw
Link to comment
Share on other sites

  • The Papaw changed the title to Exporting MAME Roms from LB
52 minutes ago, The Papaw said:

Can you export MAME roms from a Merged set like you can with a non-merged set.

Depends.  If your main ROM file (default game) is the parent ROM, then yes.  If it's a clone (located inside the parent ROM zip file [in a merged set]), then no.  

i.e.  path/to/1942.zip (parent ROM)  vs.  path/to/1942b.zip (clone ROM) 

In a merged set, 1942b.zip does not physically exist.  But that's the [non-existent] filename that gets pointed to.  (and it works [plays], because MAME is smart and knows how to handle it)

 

Note: "Only the main ROM files will be copied and not any additional applications."

 

1 hour ago, The Papaw said:

I do use chd files as well if that matters

Regarding exporting, it does matter. Regardless of the set.  A lot. ;)  

Again. "Only the main ROM files will be copied..".   When imported, the path to the 'game' is (i.e.)   path/to/area51.zip.  It will export that [Parent] ROM.  But it won't touch the other required path/to/area51/area51.chd

Link to comment
Share on other sites

4 minutes ago, JoeViking245 said:

Depends.  If your main ROM file (default game) is the parent ROM, then yes.  If it's a clone (located inside the parent ROM zip file [in a merged set]), then no.  

i.e.  path/to/1942.zip (parent ROM)  vs.  path/to/1942b.zip (clone ROM) 

In a merged set, 1942b.zip does not physically exist.  But that's the [non-existent] filename that gets pointed to.  (and it works [plays], because MAME is smart and knows how to handle it)

 

Note: "Only the main ROM files will be copied and not any additional applications."

 

Regarding exporting, it does matter. Regardless of the set.  A lot. ;)  

Again. "Only the main ROM files will be copied..".   When imported, the path to the 'game' is (i.e.)   path/to/area51.zip.  It will export that [Parent] ROM.  But it won't touch the other required path/to/area51/area51.chd

Thanks Teach, so I should probably use non-merged set to import into LB, then export them to be added to NAS to save HDD space on NAS. Less chances of them not working and less headache, other than time. Would you agree? BTW, hope all is well with ya Joe

Edited by The Papaw
Link to comment
Share on other sites

  • Solution
21 minutes ago, The Papaw said:

so I should probably use non-merged set to import into LB, then export them to be added to NAS to save HDD space on NAS

Not sure if this falls under a double entendre or an oxymoron.  ;) 

Merged          - (0.273) 76.54 GB
Non-Merged - (0.273) 141.6 GB

That is course is for the Full set(s) and you'd only be exporting some of those.  So "to save space.."?  In the end.. Probably not.  To have the export feature [more so] work in-your-favor and "Less chances of them not working and less headache"? Most likely.

  • Thanks 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...