"mGalaxy has stopped working" before it even starts.

[yamzzz]

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. 

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:

Code: (xml) [Select]

<?xml version="1.0" encoding="utf-8"?>
<!-- This file generated by ROMLister -->
<dbase name="MAME" romset="Mame" version="0.159 (Feb 25 2015) & 0.159 (Feb 25 2015)">
    <game name="ar_argh" cloneof="">
        <description>Aaargh (Arcadia)</description>
        <genre>Platform / Fighter</genre>
        <players>2P sim</players>
    </game>
    <game name="ar_argh" cloneof="">
        <description>Aaargh (Arcadia)</description>
        <genre>Platform / Fighter</genre>
        <players>2P sim</players>
    </game>
</dbase>
"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.

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

Code: (xml) [Select]

<?xml version="1.0" encoding="utf-8"?>
<!-- This file generated by ROMLister -->
<dbase name="MAME" romset="Mame" version="0.159 (Feb 25 2015) & 0.159 (Feb 25 2015)">
    <game name="ar_argh" cloneof="">
        <description>Aaargh (Arcadia)</description>
        <genre>Platform / Fighter</genre>
        <players>2P sim</players>
    </game>
    <game name="ar_argh" cloneof="">
        <description>Aaargh (Arcadia)</description>
        <genre>Platform / Fighter</genre>
        <players>2P sim</players>
    </game>
</dbase>
"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.

[yamzzz]

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!

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.

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

[yamzzz]

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 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' ?

[mgalaxy]

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' ?

[yamzzz]

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 seems to be okay.

From what I read, I understand that you have no problem running mGalaxy_Runway (and generating a database), correct?
I understand too that you don't have a problem when launching mGalaxy with 'Use database' disabled in mGalaxy_Runway, correct?
So the problem only occurs when you're trying to use the database?

Could you please send the database generated to info@mgalaxy.com

[mgalaxy]

Definitely! First I must say that when I generate a database with mGalaxy, it seems to be okay.

From what I read, I understand that you have no problem running mGalaxy_Runway (and generating a database), correct?
I understand too that you don't have a problem when launching mGalaxy with 'Use database' disabled in mGalaxy_Runway, correct?
So the problem only occurs when you're trying to use the database?

Could you please send the database generated by romlister?

[yamzzz]

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

I have whatever WMP comes with 8.1 and I believe that is version 12.

mGalaxy is installed to C:\Program Files (x86)\mGalaxy.

I have tried both the front-end and Runway with admin rights and nothing changes.

Thanks for the quick follow-up!

Here is the log:

Faulting application name: mGalaxy.exe, version: 5.5.0.0, time stamp: 0x54a3e620
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17415, time stamp: 0x54504ade
Exception code: 0xc000041d
Fault offset: 0x00014598
Faulting process id: 0x15a4
Faulting application start time: 0x01d063ffaa0a58f9
Faulting application path: C:\Program Files (x86)\mGalaxy\mGalaxy.exe
Faulting module path: C:\WINDOWS\SYSTEM32\KERNELBASE.dll
Report Id: e8af5a0e-cff2-11e4-8266-5404a6c23fcd
Faulting package full name:
Faulting package-relative application ID:

Could you once again post here the complete report from the 'Event Viewer'?
http://www.howtogeek.com/123646/htg-explains-what-the-windows-event-viewer-is-and-how-you-can-use-it/

Tells me:
1. Which windows version?
2. Framework 4.0 installed ?
3. Windows Media Player 10 installed?
4. Where's the main mGalaxy folder located?
5; Did you try running the application with Administrator rights?

[mgalaxy]

Could you once again post here the complete report from the 'Event Viewer'?
http://www.howtogeek.com/123646/htg-explains-what-the-windows-event-viewer-is-and-how-you-can-use-it/

Tells me:
1. Which windows version?
2. Framework 4.0 installed ?
3. Windows Media Player 10 installed?
4. Where's the main mGalaxy folder located?
5; Did you try running the application with Administrator rights?

[yamzzz]

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
EventTime=130714303923907647
ReportType=2
Consent=1
UploadTime=130714303924415048
ReportIdentifier=c21561db-cfea-11e4-8266-5404a6c23fcd
IntegratorReportIdentifier=c21561da-cfea-11e4-8266-5404a6c23fcd
WOW64=1
NsAppName=mGalaxy.exe
Response.BucketId=4c487e3507ca69637ae6012f64e3f1a5
Response.BucketTable=1
Response.LegacyBucketId=73798506388
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=mGalaxy.exe
Sig[1].Name=Application Version
Sig[1].Value=5.5.0.0
Sig[2].Name=Application Timestamp
Sig[2].Value=54a3e620
Sig[3].Name=Fault Module Name
Sig[3].Value=KERNELBASE.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=6.3.9600.17415
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=54504ade
Sig[6].Name=Exception Code
Sig[6].Value=c000041d
Sig[7].Name=Exception Offset
Sig[7].Value=00014598
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.3.9600.2.0.0.256.103
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=7285
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=7285cbe87ce30fb4d8296faa9d227e98
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=2e47
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=2e47640dde005fbf2344ff9eb1e6bd3d
UI[2]=C:\Program Files (x86)\mGalaxy\mGalaxy.exe
UI[3]=mGalaxy has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files (x86)\mGalaxy\mGalaxy.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\SYSTEM32\MSCOREE.DLL
LoadedModule[3]=C:\WINDOWS\SYSTEM32\KERNEL32.dll
LoadedModule[4]=C:\WINDOWS\SYSTEM32\KERNELBASE.dll
LoadedModule[5]=C:\WINDOWS\SYSTEM32\ADVAPI32.dll
LoadedModule[6]=C:\WINDOWS\SYSTEM32\msvcrt.dll
LoadedModule[7]=C:\WINDOWS\SYSTEM32\sechost.dll
LoadedModule[8]=C:\WINDOWS\SYSTEM32\RPCRT4.dll
LoadedModule[9]=C:\WINDOWS\SYSTEM32\SspiCli.dll
LoadedModule[10]=C:\WINDOWS\SYSTEM32\CRYPTBASE.dll
LoadedModule[11]=C:\WINDOWS\SYSTEM32\bcryptPrimitives.dll
LoadedModule[12]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
LoadedModule[13]=C:\WINDOWS\SYSTEM32\SHLWAPI.dll
LoadedModule[14]=C:\WINDOWS\SYSTEM32\combase.dll
LoadedModule[15]=C:\WINDOWS\SYSTEM32\USER32.dll
LoadedModule[16]=C:\WINDOWS\SYSTEM32\GDI32.dll
LoadedModule[17]=C:\WINDOWS\system32\IMM32.DLL
LoadedModule[18]=C:\WINDOWS\SYSTEM32\MSCTF.dll
LoadedModule[19]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
LoadedModule[20]=C:\WINDOWS\SYSTEM32\MSVCR120_CLR0400.dll
LoadedModule[21]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\mscorlib\d1265d6159ea876f9d63ea4c1361b587\mscorlib.ni.dll
LoadedModule[22]=C:\WINDOWS\SYSTEM32\ole32.dll
LoadedModule[23]=C:\WINDOWS\SYSTEM32\kernel.appcore.dll
LoadedModule[24]=C:\WINDOWS\system32\uxtheme.dll
LoadedModule[25]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System\487c38839683ae7c3d773386adc02b18\System.ni.dll
LoadedModule[26]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\WindowsBase\d1803810045381c240efc847667a3bb4\WindowsBase.ni.dll
LoadedModule[27]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll
LoadedModule[28]=C:\WINDOWS\system32\rsaenh.dll
LoadedModule[29]=C:\WINDOWS\SYSTEM32\bcrypt.dll
LoadedModule[30]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\PresentationCore\45f5112aac22b8fea672e3d78fc09681\PresentationCore.ni.dll
LoadedModule[31]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Presentatio5ae0f00f#\d548a6a721558cb5a34c96e095af03cd\PresentationFramework.ni.dll
LoadedModule[32]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Xaml\9d7192b328a08155b6cbb2f3ec728407\System.Xaml.ni.dll
LoadedModule[33]=C:\WINDOWS\SYSTEM32\dwrite.dll
LoadedModule[34]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\wpfgfx_v0400.dll
LoadedModule[35]=C:\WINDOWS\SYSTEM32\OLEAUT32.dll
LoadedModule[36]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\PresentationNative_v0400.dll
LoadedModule[37]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll
LoadedModule[38]=C:\WINDOWS\system32\dwmapi.dll
LoadedModule[39]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Xml\e7dd54337058ee9fc1918ad615cdb185\System.Xml.ni.dll
LoadedModule[40]=C:\WINDOWS\SYSTEM32\dxva2.dll
LoadedModule[41]=C:\WINDOWS\SYSTEM32\clbcatq.dll
LoadedModule[42]=C:\WINDOWS\system32\wmp.dll
LoadedModule[43]=C:\WINDOWS\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.9600.17415_none_dad8722c5bcc2d8f\gdiplus.dll
LoadedModule[44]=C:\WINDOWS\system32\wmploc.dll
LoadedModule[45]=C:\WINDOWS\System32\MMDevApi.dll
LoadedModule[46]=C:\WINDOWS\System32\DEVOBJ.dll
LoadedModule[47]=C:\WINDOWS\SYSTEM32\cfgmgr32.dll
LoadedModule[48]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Core\ddd8d9bd947784a41ea75af98bb83183\System.Core.ni.dll
LoadedModule[49]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Microsoft.V9921e851#\e6708d7d33639d5c17c38ad25cc0b6ea\Microsoft.VisualBasic.ni.dll
LoadedModule[50]=C:\WINDOWS\system32\MFPlat.DLL
LoadedModule[51]=C:\WINDOWS\system32\RTWorkQ.DLL
LoadedModule[52]=C:\WINDOWS\system32\AVRT.dll
LoadedModule[53]=C:\WINDOWS\SYSTEM32\AUDIOSES.DLL
LoadedModule[54]=C:\WINDOWS\SYSTEM32\powrprof.dll
LoadedModule[55]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Configuration\4be244b3e99b278978c84a88c899e602\System.Configuration.ni.dll
LoadedModule[56]=C:\WINDOWS\SYSTEM32\urlmon.dll
LoadedModule[57]=C:\WINDOWS\SYSTEM32\iertutil.dll
LoadedModule[58]=C:\WINDOWS\SYSTEM32\WININET.dll
LoadedModule[59]=C:\WINDOWS\SYSTEM32\USERENV.dll
LoadedModule[60]=C:\WINDOWS\SYSTEM32\profapi.dll
LoadedModule[61]=C:\WINDOWS\system32\VERSION.dll
LoadedModule[62]=C:\WINDOWS\SYSTEM32\Secur32.dll
LoadedModule[63]=C:\WINDOWS\SYSTEM32\SHELL32.dll
LoadedModule[64]=C:\WINDOWS\SYSTEM32\SHCORE.dll
LoadedModule[65]=C:\WINDOWS\SYSTEM32\d3d9.dll
LoadedModule[66]=C:\WINDOWS\SYSTEM32\nvd3dum.dll
LoadedModule[67]=C:\WINDOWS\SYSTEM32\PSAPI.DLL
LoadedModule[68]=C:\WINDOWS\system32\nvspcap.dll
LoadedModule[69]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Presentatioaec034ca#\28b11cad8855404dab40ab22e154c76d\PresentationFramework.Aero2.ni.dll
LoadedModule[70]=C:\WINDOWS\SYSTEM32\WindowsCodecs.dll
LoadedModule[71]=C:\WINDOWS\SYSTEM32\WtsApi32.dll
LoadedModule[72]=C:\WINDOWS\SYSTEM32\WINSTA.dll
LoadedModule[73]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\PenIMC.dll
LoadedModule[74]=C:\WINDOWS\System32\wisp.dll
LoadedModule[75]=C:\WINDOWS\SYSTEM32\atlthunk.dll
LoadedModule[76]=C:\Program Files (x86)\Common Files\Microsoft Shared\Ink\tpcps.dll
LoadedModule[77]=C:\WINDOWS\SYSTEM32\xinput1_3.dll
LoadedModule[78]=C:\WINDOWS\SYSTEM32\SETUPAPI.dll
LoadedModule[79]=C:\WINDOWS\system32\msctfui.dll
LoadedModule[80]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\UIAutomationTypes\4ecc9a930ce584ca105857e68bad3c5f\UIAutomationTypes.ni.dll
LoadedModule[81]=C:\WINDOWS\SYSTEM32\UIAutomationCore.dll
LoadedModule[82]=C:\WINDOWS\SYSTEM32\sxs.dll
LoadedModule[83]=C:\WINDOWS\SYSTEM32\WINTRUST.dll
LoadedModule[84]=C:\WINDOWS\SYSTEM32\CRYPT32.dll
LoadedModule[85]=C:\WINDOWS\SYSTEM32\MSASN1.dll
LoadedModule[86]=C:\WINDOWS\SYSTEM32\WINMM.dll
LoadedModule[87]=C:\WINDOWS\SYSTEM32\WINMMBASE.dll
LoadedModule[88]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Deployment\b58d2d3b4becea7d4642f19fa9c118c8\System.Deployment.ni.dll
LoadedModule[89]=C:\WINDOWS\SYSTEM32\mscms.dll
LoadedModule[90]=C:\WINDOWS\SYSTEM32\WindowsCodecsExt.dll
LoadedModule[91]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\diasymreader.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=mGalaxy
AppPath=C:\Program Files (x86)\mGalaxy\mGalaxy.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=3ADF4B913AAC0A98C84D98AFEBB84D93

[yamzzz]

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?

[yamzzz]

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?

[yamzzz]

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 replace your previous version with this one...I think that you might be satisfied with it ;-)

Ohhh man! This version totally works! This rules! Thanks so much! What was the issue?! And will you be pushing out a new version to take care of this somewhat-serious bug for everyone?

[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 replace your previous version with this one...I think that you might be satisfied with it ;-)