mGalaxy forum

When I use the database mGalaxy generates, everything seems to work but the actual rom names are used rather than the common name. I will email you the RomLister .xml right now!

Wait wait wait!! ;-)
When you generate a database in mGalaxy, check the 'Use Database' checkbox and launch mGalaxy, mGalaxy doesn't display the 'long' rom name...but doesn't crash!?
When you use the romlister generated XML database, mGalaxy crash!?...That's 'all' ?

Oops I think I mis-typed. I just tried with the mGalaxy-generated list and it does indeed show the proper rom names and seems to work successfully, but of course it doesn't have all the 'undesirable' roms filtered out which is why I was trying to use RomLister. Sorry about that!

mgalaxy wrote:

When I use the database mGalaxy generates, everything seems to work but the actual rom names are used rather than the common name. I will email you the RomLister .xml right now!

Wait wait wait!! ;-)
When you generate a database in mGalaxy, check the 'Use Database' checkbox and launch mGalaxy, mGalaxy doesn't display the 'long' rom name...but doesn't crash!?
When you use the romlister generated XML database, mGalaxy crash!?...That's 'all' ?

Thanks for sending the xml file. It appears that this is not a bug of mGalaxy but a problem with the xml file generated by Romlister.
I've just contacted Jeff, from Romlister and asked him to have a look at the mGalaxy xml exporter.
Jeff is a nice guy and I'm confident that this problem could be resolved quickly!

[quote="mgalaxy"]
Thanks for sending the xml file. It appears that this is not a bug of mGalaxy but a problem with the xml file generated by Romlister.
I've just contacted Jeff, from Romlister and asked him to have a look at the mGalaxy xml exporter.
Jeff is a nice guy and I'm confident that this problem could be resolved quickly!
[/quote]

That is very interesting! Sounds like an easy fix all around and I do remember how quickly he added in mGalaxy support in the first place so I'm excited to see where this heads. Thanks much for your response.

I got a reply from Jeff (that I'll show you in a few seconds) but first I have to tell you what's the problem is with the file you've sent me. Here is an extract of your file: "0.159 (Feb 25 2015) & 0.159 (Feb 25 2015)"
1. There's a duplicate version info in the header value and, above all, a '&' sign which is not allow at that place in an valid XML document

<game name="ar_argh" cloneof="">
<game name="ar_argh" cloneof="">
Then, there's the fact that some games appears twice in the list...which leads to an error with mGalaxy complaining that the key already exists!

This is Jeff's reply:

---

I'm not sure how this user got into this predicament.

This is a fresh mgalaxy XML file that I just generated:

<?xml version="1.0" encoding="utf-8"?>
<!-- This file generated by ROMLister -->
<dbase name="MAME" romset="Mame" version="0.159 (Feb 25 2015)">
<game name="005" cloneof="">
<description>005</description>
<genre>Maze / Shooter Small</genre>
<players>2P alt</players>
</game>
<game name="ind250cc" cloneof="">
<description>250 CC</description>
<genre>Electromechanical / Pinball</genre>
<players>Pinball</players>
</game>
<game name="30test" cloneof="">
<description>30 Test (Remake)</description>
<genre>Misc.</genre>
<players>1P</players>
</game>
...


No double game entries, no "&" in the XML header.

I think perhaps this person made an mgalaxy XML file and then used that
XML file as the input file that RL works from, using that file to make
another mgalaxy file?

Without knowing a few more details as to what they did, I cannot reproduce
this.  This isn't really a bug in RL's ability to generate mgalaxy files
either, this is more of a garbage in-garbage out.

Oh wow I had no idea my files were so screwed up. I don't know how they ended up in such a state but I re-did every step in RomLister from the beginning and then exported as an mGalaxy list and everything seems fixed! Thanks again for your great customer support. 

[quote="mgalaxy"]
I got a reply from Jeff (that I'll show you in a few seconds) but first I have to tell you what's the problem is with the file you've sent me. Here is an extract of your file: "0.159 (Feb 25 2015) & 0.159 (Feb 25 2015)"
1. There's a duplicate version info in the header value and, above all, a '&' sign which is not allow at that place in an valid XML document

<game name="ar_argh" cloneof="">
<game name="ar_argh" cloneof="">
Then, there's the fact that some games appears twice in the list...which leads to an error with mGalaxy complaining that the key already exists!

This is Jeff's reply:

---

I'm not sure how this user got into this predicament.

This is a fresh mgalaxy XML file that I just generated:

<?xml version="1.0" encoding="utf-8"?>
<!-- This file generated by ROMLister -->
<dbase name="MAME" romset="Mame" version="0.159 (Feb 25 2015)">
<game name="005" cloneof="">
<description>005</description>
<genre>Maze / Shooter Small</genre>
<players>2P alt</players>
</game>
<game name="ind250cc" cloneof="">
<description>250 CC</description>
<genre>Electromechanical / Pinball</genre>
<players>Pinball</players>
</game>
<game name="30test" cloneof="">
<description>30 Test (Remake)</description>
<genre>Misc.</genre>
<players>1P</players>
</game>
...


No double game entries, no "&" in the XML header.

I think perhaps this person made an mgalaxy XML file and then used that
XML file as the input file that RL works from, using that file to make
another mgalaxy file?

Without knowing a few more details as to what they did, I cannot reproduce
this.  This isn't really a bug in RL's ability to generate mgalaxy files
either, this is more of a garbage in-garbage out.
[/quote]