No, you're not missing anything. Since the update to version 10—and especially since it became available on macOS—this feature is no longer included.
Why do you need it? Are there cases where scraping from ScreenScraper and Emumovies doesn’t yield results?

If you’d like, I could add this feature ...

I had run my tests on version 10.1... but the version I sent you earlier was the latest beta version!
It turns out that in that version, there was indeed a problem with the emulators that don't accept the full path to the ROM via the command line, but rather an identifier! (just like with Model 2 ...

No, no need to do all this, this is managed by default.
If you want, I'll do what I did last time: I'll send you a portable version with just one or two ROMs, and you can let me know if it works.

Is your ROM set correct? (I'm surprised to see the same game appear multiple times in your screenshots.)
I used this link (successfully) to TEST the ROMs:
https://archive.org/details/m2emu1.1a

I just checked... and everything is working as it should!
The only thing you actually need to do is specify the ROM folder within ‘M2emulator_1.1a’ itself.
Also, note that there's an application called ‘m2_configurator_v0.0.2’ (which needs to be placed in the emulator folder)...that lets you make ...

Are you sure you're using the x64.exe executable?
I just ran a test and didn't have any problems (recognized in Runway and launchable in mGalaxy)
Here's the link (available for 3 days) to the emulator and the two test ROMs I used.

https://we.tl/t-N6K5O1jdvmdQu4bw

Yes, absolutely! As you probably remember, all you have to do is drag the mGalaxy license file so that the next time you start the app, you'll be in premium mode.

No, I didn't do anything special. It's a basic version that was supposed to let me see if you had a hardware incompatibility!
The only thing that’s a little 'special' is that in the version I prepared for you, the links to the files and the emulator are inside the mGalaxy folder (so it’s a “portable ...

I just made you a portable version of mGalaxy. It contains a single system with 2–3 ROMs.
Unzip this file into your “Documents” folder, for example, then launch the mGalaxy application inside it and let me know if everything opens correctly (or even if the game launches).

https://www.mgalaxy.com ...

Wait a minute! If you don't have the license, you really can't access “DB Edit”... so it's normal that you don't see those items! So let's set that aside for now... because, yes, you really can't view the media for each game if you don't have the Premium license.

To check if the ROM database has ...

1. Where did you install mGalaxy? Is it installed in the Program Files folder? If so, install it outside of that folder—for example, in “My Documents.”
2. So, after creating the ROM database, did you receive any error messages, and can you see the game names listed in “DB Edit”?
2b. Are the media ...

I gather you're talking about mGalaxy itself, since you then ask a question about Runway (which seems to be working).
My first guess is that you're trying to run mGalaxy on an older system—and not in 64-bit mode! Is that the case?
Regarding media display: You do know, don't you, that first and ...

Thanks for your kind words :)
We are indeed working on the update!
Here's what's included:
[New] When using a screensaver that randomly displays games from the current system, you can now press the dedicated launch/select key (default: Enter) to stop the screensaver and display the selected game ...

I think I've pinpointed the “culprit” ;)
By default, when creating the database, users are given the option to exclude certain games from the database to make it smaller and speed up overall processing.
2026-09-04 142216.png
This is particularly true for MultiGame (/Mini-Games) titles...which most ...

Have you thought about placing the BIOS files for these systems in the “roms” folder in MAME (the steps are outlined in the Emulator tab)?