EMULAB Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

The new forum is online, hope you enjoy it!

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - sTo0z

Pages: [1]
1
Completely understood, thanks for that.

I guess I have a lot to learn, I appreciate the detailed info.

In my first approach to MAME, I found and used roms from a "non-merged" set. I was able to simply grab a title (galaga), toss it on my mame setup, and load the game no problem.

Later, I found myself needing other specific set versions, and was able to follow the upgrade process (using your awesome tool), and attempted to get back to "drop the set in there, done" as before.

Reading what you say, and folks like me who don't have all the info and still trying to learn, the definition of "non-merged" is incredibly mis-leading:
Quote
Non-Merged Sets   All rom files will have all the necessary roms to run them.

It makes it sound like you can drop the single set and have it run, no matter what. But what I guess what I've failed to realize, is that the keyword "rom" here does not apply to files such as 50xx.bin. You're saying this file is not a "rom", it is something else, yes?

I guess I liked the idea that if I really wanted to, I could build such a set with automation, where all I would possibly have to ever do is find a single title I want, and copy it over. But now, I'm always going to be potentially troubleshooting every single set I put into my MAME environment, one by one, to see if I've missed some random external set.

Wasted space is truly not an issue, convenience is, but if you're saying I'm off my rocker and this is a very un-common approach, that's fine too. But it's a little strange that others agree and place these files inside sets to make truly independent sets, and I doubt they manually did that, so I was very curious how they did. Maybe not your tool?

Anyways, thanks very much again for the important info, you seem to take a lot of care in your replies, it's great to see.

2
Hi Roman,

Thanks so much for the reply.

I guess I don't understand...

If Namco files are meant to be in an external set, and galaga is meant to not include them, what is the appropriate/correct way to load galaga?

If they are meant to be separate, why are other full sets out in the wild including the required namco files inside galaga?

3
Originally posted on MAME Reddit: https://www.reddit.com/r/MAME/comments/6uhitk/how_can_i_achieve_completely_independent_rom_sets/

I am working with MAME and romset 0.174.

I am trying to create rom sets that are completely independent of other sets, and have everything they need within their own .zip to run.
I have tried:
* Scanning
* Rebuilding
* Turning OFF/Un-checking "Separate BIOS..."
* Split sets
* Non-merged sets

I don't know what else to do.

An example offender is galaga.zip. I have tried to re-build, scan, fix, and complete this set in every way that I can find. No matter what I do, it refuses to pack in the required Namco files, and thus the rom set cannot run on its own.
Of course I could manually fix this, but that is not a long term or sustainable solution to the potential number of rom sets that face a similar issue.

I can see that other collections that you can find out there have the namco files included in the galaga set, so I know someone is able to do this somewhere, somehow (and I don't think they have done it manually).

Would absolutely love some help on this, I've spent 2 weeks and staring at loading bars for hours and hours trying to figure this out... :)

Thank you, community!

Pages: [1]

Page created in 0.147 seconds with 21 queries.