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. :D :D [quote="mgalaxy"] I got a ...

[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 ...

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! When I use the ...

Everything you said is correct. 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! Thanks! Definitely! First I must say that when I generate a database with mGalaxy, it ...

Definitely! First I must say that when I generate a database with mGalaxy, it seems to be okay. I have the force close the instant I load up mGalaxy after importing and using a database I created in RomLister. Would it help if I sent you the .xml it generated? I am on W8.1 64bit. .NET framework 4.0 ...

So I went to try using the newest version of this front-end and a database generated from RomLister and am still getting the "...stopped working" message before mGalaxy even boots up. Was there ever any progress with this issue? Thanks! EDIT: Does this help at all? Version=1 EventType=APPCRASH ...

I would also like to request this feature, please.

I was using genuine MS Xbox 360 controllers when I ran into this bug, so I don't think that's it...

Well actually it was the first time I ever ran mGalaxy on this particular machine... it's possible I was doing something wrong, but I don't recall it happening whenever I closed console emulators. Just MAME. I'll give it another go in the next few days to try and narrow some things down.

Did anyone ever figure out a solution to this bug? It was happening to me over the weekend with a stock MAME64 0.153 and an official XBOX 360 controller. It seemed like every time I closed MAME, I would have to press all sorts of buttons to regain control of mGalaxy.

Thanks!

No more luck with anything relating to this, I suppose? :\

Or maybe even http://www.mgalaxy.com/forum/index.php?topic=574.0 as a workaround?

Is it possible to use something like RomLister (http://www.waste.org/~winkles/ROMLister/) to generate a very custom database and import that into mGalaxy? I don't know if the mGalaxy xml format is the same as any others. I know RomLister can produce quite a few variants for other front-ends like ...

Actually, hold that thought. :\ As it turns out, on one of my computer, the new Runway works... However, on my second computer, neither the old nor the new one works. They BOTH give me the force close! Any other ideas?

[quote="mgalaxy"] No yamzzz, you're not too late!! :-) I was actually creating the database for you when I isolated a change in the MAME app database itself!! Would you please do a test, creating the database by yourself, with that version: http://www.mgalaxy.com/other/mGalaxy_Runway.exe Simply ...

[quote="mgalaxy"] Glad to see that you finally get the database working! :-) Would you by chance have a 'catver.ini' file v0.151...so that I can build a database for you? [/quote] Oh for some reason I hadn't seen this reply until now! Would it be possible to just use a 0.152 catver.ini file for this ...