Unable to build working SNES database roms not getting added

[Beowulf62381]

perfect thanks.

[mgalaxy]

I assume the rom path gets scanned files with select extensions are getting added to the data base while others are skipped

Exactly! You can see the file extension allowed for each system in mGalaxy_Runway (under the 'Rom Path' field)

To add a new extension to that list:
mGalaxy folder > Data > Systems.xml (open this file with a text editor)
Find that block (search for 'snes') and add '.jma' to '<Extensions>' tag (no spaces in this line!):

Code: (xml,12) [Select]

<System Type="Console">
<Name>Nintendo SNES</Name>
<AppPath/>
<RomPath/>
<SnapPath/>
<VidPath/>
<Emu selected="0">
<Cmd id="0" name="ZSNES" value="-m -k %volume(0,100) &quot;%path\%file%ext&quot;"/>
<Cmd id="1" name="Snes9x [Script]" value="-fullscreen &quot;%path\%file%ext&quot;"/>
<Cmd id="2" name="Higan" value="&quot;%path\%file%ext&quot;"/>
</Emu>
<Extensions>.fig,.gd,.mgh,.sfc,.smc,.swc,.zip</Extensions>
<Active>False</Active>
<Script>True</Script>
<Database>False</Database>
</System>

[Beowulf62381]

To save a bit of space I compressed all of my SNES roms as JMA archives. They play fine snes9x, and do take up less space than zip or uncompressed, but they don't show up in Mgalaxy any longer. I re-ran runway to build a new snes database. The action completed just fine i.e. no error, but nothing was added. I assume the rom path gets scanned files with select extensions are getting added to the data base while others are skipped. If this is the case is there a config file can simply add JMA to?