mGalaxy forum

General Discussions => Bugs Reports => Topic started by: yamzzz on February 18, 2014, 10:24:09 PM

Title: "mGalaxy has stopped working" before it even starts.
Post by: yamzzz on February 18, 2014, 10:24:09 PM

First off, I wanna say I love the look and what I know of this front-end. The problem is, I cannot get it to start in order to enjoy it!

Whenever I load the actual front-end, I get what you see in the attachment and this is what shows up in the Event Viewer:

Faulting application name: mGalaxy.exe, version: 5.2.0.0, time stamp: 0x52da69ff
Faulting module name: KERNELBASE.dll, version: 6.2.9200.16451, time stamp: 0x50988950
Exception code: 0xe0434352
Fault offset: 0x00014b32
Faulting process id: 0x1b2c
Faulting application start time: 0x01cf2d2996868abd
Faulting application path: C:\Program Files (x86)\mGalaxy\mGalaxy.exe
Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll
Report Id: d4822b9c-991c-11e3-beab-5404a6c23fcd
Faulting package full name:
Faulting package-relative application ID:

I've tried re-installing directx, .net, video card drivers, etc. Also tried administrative mode as well as compatibility modes... to no avail. Any ideas? I'd love for it to function so I could purchase a supporter skin!

Thanks!

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: mgalaxy on February 19, 2014, 06:14:01 AM

There's never been reported error implying 'Kernelbase.dll'!!
Could you try to get further information using the 'Event Viewer'?
http://www.howtogeek.com/123646/htg-explains-what-the-windows-event-viewer-is-and-how-you-can-use-it/ (http://www.howtogeek.com/123646/htg-explains-what-the-windows-event-viewer-is-and-how-you-can-use-it/)

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: yamzzz on February 19, 2014, 06:46:41 AM

Sure! I will paste the errors that show up at the time of the crash!

Quote

- System

  - Provider

   [ Name]  .NET Runtime
 
  - EventID 1026

   [ Qualifiers]  0
 
   Level 2
 
   Task 0
 
   Keywords 0x80000000000000
 
  - TimeCreated

   [ SystemTime]  2014-02-19T04:18:06.000000000Z
 
   EventRecordID 82735
 
   Channel Application
 
   Computer mrgrieves
 
   Security
 

- EventData

   Application: mGalaxy.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.Xml.XmlException Stack: at System.Xml.XmlTextReaderImpl.Throw(System.Exception) at System.Xml.XmlTextReaderImpl.Throw(System.String, System.String[]) at System.Xml.XmlTextReaderImpl.ThrowTagMismatch(NodeData) at System.Xml.XmlTextReaderImpl.ParseEndElement() at System.Xml.XmlTextReaderImpl.ParseElementContent() at System.Xml.XmlTextReaderImpl.Read() at System.Xml.XmlTextReader.Read() at mGalaxy.MainWindow.EmuInit() at mGalaxy.MainWindow.emuRefresh() at mGalaxy.MainWindow.detectMusic() at mGalaxy.MainWindow.loadInterface() at mGalaxy.MainWindow.excludeWords() at mGalaxy.MainWindow.keyInit() at mGalaxy.MainWindow.loadXmlEmu() at mGalaxy.MainWindow.checkDataFolder() at mGalaxy.MainWindow.Window_Loaded(System.Object, System.Windows.RoutedEventArgs) at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs) at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean) at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs) at System.Windows.UIElement.RaiseEvent(System.Windows.RoutedEventArgs) at System.Windows.BroadcastEventHelper.BroadcastEvent(System.Windows.DependencyObject, System.Windows.RoutedEvent) at System.Windows.BroadcastEventHelper.BroadcastLoadedEvent(System.Object) at MS.Internal.LoadedOrUnloadedOperation.DoWork() at System.Windows.Media.MediaContext.FireLoadedPendingCallbacks() at System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks() at System.Windows.Media.MediaContext.RenderMessageHandlerCore(System.Object) at System.Windows.Media.MediaContext.RenderMessageHandler(System.Object) at System.Windows.Media.MediaContext.Resize(System.Windows.Media.ICompositionTarget) at System.Windows.Interop.HwndTarget.OnResize() at System.Windows.Interop.HwndTarget.HandleMessage(MS.Internal.Interop.WindowMessage, IntPtr, IntPtr) at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.HwndSubclass.DefWndProcWrapper(IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.UnsafeNativeMethods.ShowWindow(System.Runtime.InteropServices.HandleRef, Int32) at System.Windows.Window.ShowHelper(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.DispatcherOperation.InvokeImpl() at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at System.Windows.Threading.DispatcherOperation.Invoke() at System.Windows.Threading.Dispatcher.ProcessQueue() at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame) at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame) at System.Windows.Threading.Dispatcher.Run() at System.Windows.Application.RunDispatcher(System.Object) at System.Windows.Application.RunInternal(System.Windows.Window) at System.Windows.Application.Run(System.Windows.Window) at System.Windows.Application.Run() at mGalaxy.Application.Main() 

Quote

- System

  - Provider

   [ Name]  Application Error
 
  - EventID 1000

   [ Qualifiers]  0
 
   Level 2
 
   Task 100
 
   Keywords 0x80000000000000
 
  - TimeCreated

   [ SystemTime]  2014-02-19T04:18:06.000000000Z
 
   EventRecordID 82736
 
   Channel Application
 
   Computer mrgrieves
 
   Security
 

- EventData

   mGalaxy.exe
   5.2.0.0
   52da69ff
   KERNELBASE.dll
   6.2.9200.16451
   50988950
   e0434352
   00014b32
   1b2c
   01cf2d2996868abd
   C:\Program Files (x86)\mGalaxy\mGalaxy.exe
   C:\Windows\SYSTEM32\KERNELBASE.dll
   d4822b9c-991c-11e3-beab-5404a6c23fcd

Quote

Version=1
EventType=CLR20r3
EventTime=130372570865081590
ReportType=2
Consent=1
UploadTime=130372570865507923
ReportIdentifier=d4822b9d-991c-11e3-beab-5404a6c23fcd
IntegratorReportIdentifier=d4822b9c-991c-11e3-beab-5404a6c23fcd
WOW64=1
NsAppName=mGalaxy.exe
Response.BucketId=1de96686563c6d6f8a3f71d7e982662a
Response.BucketTable=5
Response.LegacyBucketId=94501756980
Response.type=4
Sig[0].Name=Problem Signature 01
Sig[0].Value=mgalaxy.exe
Sig[1].Name=Problem Signature 02
Sig[1].Value=5.2.0.0
Sig[2].Name=Problem Signature 03
Sig[2].Value=52da69ff
Sig[3].Name=Problem Signature 04
Sig[3].Value=System.Xml
Sig[4].Name=Problem Signature 05
Sig[4].Value=4.0.30319.18331
Sig[5].Name=Problem Signature 06
Sig[5].Value=520a36ac
Sig[6].Name=Problem Signature 07
Sig[6].Value=976
Sig[7].Name=Problem Signature 08
Sig[7].Value=27
Sig[8].Name=Problem Signature 09
Sig[8].Value=System.Xml.XmlException
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.2.9200.2.0.0.256.103
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=530e
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=530e8b847071fd32e4c3220a7aaa1c5f
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=05f8
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=05f8c8fa01f078fd562e7aa3d9e0b9c9
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\apphelp.dll
LoadedModule[6]=C:\Windows\SYSTEM32\ADVAPI32.dll
LoadedModule[7]=C:\Windows\SYSTEM32\msvcrt.dll
LoadedModule[8]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[9]=C:\Windows\SYSTEM32\RPCRT4.dll
LoadedModule[10]=C:\Windows\SYSTEM32\SspiCli.dll
LoadedModule[11]=C:\Windows\SYSTEM32\CRYPTBASE.dll
LoadedModule[12]=C:\Windows\SYSTEM32\bcryptPrimitives.dll
LoadedModule[13]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
LoadedModule[14]=C:\Windows\SYSTEM32\SHLWAPI.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\MSVCR110_CLR0400.dll
LoadedModule[21]=C:\Windows\assembly\NativeImages_v4.0.30319_32\mscorlib\cf0c209df74c672dfdbd31f9c3e15195\mscorlib.ni.dll
LoadedModule[22]=C:\Windows\SYSTEM32\ole32.dll
LoadedModule[23]=C:\Windows\SYSTEM32\combase.dll
LoadedModule[24]=C:\Windows\system32\uxtheme.dll
LoadedModule[25]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System\42f19eab7abb6a12442e3a9572ad370d\System.ni.dll
LoadedModule[26]=C:\Windows\assembly\NativeImages_v4.0.30319_32\WindowsBase\f2a2946b32d4fc47249c80e045275bd6\WindowsBase.ni.dll
LoadedModule[27]=C:\Windows\SYSTEM32\CRYPTSP.dll
LoadedModule[28]=C:\Windows\system32\rsaenh.dll
LoadedModule[29]=C:\Windows\assembly\NativeImages_v4.0.30319_32\PresentationCore\5210b9890e0e5831ff787669aba09913\PresentationCore.ni.dll
LoadedModule[30]=C:\Windows\assembly\NativeImages_v4.0.30319_32\Presentatio5ae0f00f#\43863df1358d124d8f26a87d02e6a227\PresentationFramework.ni.dll
LoadedModule[31]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Xaml\7b986cec878db3a6ab533de03fc552be\System.Xaml.ni.dll
LoadedModule[32]=C:\Windows\SYSTEM32\dwrite.dll
LoadedModule[33]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\wpfgfx_v0400.dll
LoadedModule[34]=C:\Windows\SYSTEM32\OLEAUT32.dll
LoadedModule[35]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\PresentationNative_v0400.dll
LoadedModule[36]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll
LoadedModule[37]=C:\Windows\SYSTEM32\dwmapi.dll
LoadedModule[38]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Xml\66e122de5ff2bad83e6150461fd1f3a4\System.Xml.ni.dll
LoadedModule[39]=C:\Windows\SYSTEM32\dxva2.dll
LoadedModule[40]=C:\Windows\SYSTEM32\clbcatq.dll
LoadedModule[41]=C:\Windows\system32\wmp.dll
LoadedModule[42]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.9200.16518_none_ba1cf6b7e09f1918\gdiplus.dll
LoadedModule[43]=C:\Windows\system32\wmploc.dll
LoadedModule[44]=C:\Windows\System32\MMDevApi.dll
LoadedModule[45]=C:\Windows\SYSTEM32\DEVOBJ.dll
LoadedModule[46]=C:\Windows\SYSTEM32\cfgmgr32.dll
LoadedModule[47]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Core\da992d52d7366e7ab6029df24852135b\System.Core.ni.dll
LoadedModule[48]=C:\Windows\assembly\NativeImages_v4.0.30319_32\Microsoft.V9921e851#\99bf496406f49aca8747f56294fd0096\Microsoft.VisualBasic.ni.dll
LoadedModule[49]=C:\Windows\SYSTEM32\MFPlat.DLL
LoadedModule[50]=C:\Windows\SYSTEM32\AVRT.dll
LoadedModule[51]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Configuration\aaadf3ca1bcec0c03ce992dec33a45fa\System.Configuration.ni.dll
LoadedModule[52]=C:\Windows\SYSTEM32\AUDIOSES.DLL
LoadedModule[53]=C:\Windows\SYSTEM32\powrprof.dll
LoadedModule[54]=C:\Windows\SYSTEM32\urlmon.dll
LoadedModule[55]=C:\Windows\SYSTEM32\iertutil.dll
LoadedModule[56]=C:\Windows\SYSTEM32\WININET.dll
LoadedModule[57]=C:\Windows\SYSTEM32\Secur32.dll
LoadedModule[58]=C:\Windows\SYSTEM32\VERSION.dll
LoadedModule[59]=C:\Windows\SYSTEM32\SHELL32.dll
LoadedModule[60]=C:\Windows\SYSTEM32\SHCORE.dll
LoadedModule[61]=C:\Windows\SYSTEM32\d3d9.dll
LoadedModule[62]=C:\Windows\SYSTEM32\nvd3dum.dll
LoadedModule[63]=C:\Windows\SYSTEM32\PSAPI.DLL
LoadedModule[64]=C:\Windows\system32\nvspcap.dll
LoadedModule[65]=C:\Windows\SYSTEM32\CRYPT32.dll
LoadedModule[66]=C:\Windows\SYSTEM32\MSASN1.dll
LoadedModule[67]=C:\Windows\SYSTEM32\nvapi.dll
LoadedModule[68]=C:\Windows\SYSTEM32\SETUPAPI.dll
LoadedModule[69]=C:\Windows\assembly\NativeImages_v4.0.30319_32\Presentatioaec034ca#\6be3ef596146aaafc2feab2ddc96fc03\PresentationFramework.Aero2.ni.dll
LoadedModule[70]=C:\Windows\SYSTEM32\WtsApi32.dll
LoadedModule[71]=C:\Windows\SYSTEM32\WINSTA.dll
LoadedModule[72]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll
LoadedModule[73]=C:\Windows\SYSTEM32\xinput1_3.dll
LoadedModule[74]=C:\Windows\system32\msctfui.dll
LoadedModule[75]=C:\Windows\assembly\NativeImages_v4.0.30319_32\UIAutomationTypes\d482e1a1b950158456bbf22abfdc4eaf\UIAutomationTypes.ni.dll
LoadedModule[76]=C:\Windows\SYSTEM32\UIAutomationCore.dll
LoadedModule[77]=C:\Windows\SYSTEM32\sxs.dll
LoadedModule[78]=C:\Windows\SYSTEM32\WINTRUST.dll
LoadedModule[79]=C:\Windows\SYSTEM32\WINMM.dll
LoadedModule[80]=C:\Windows\SYSTEM32\WINMMBASE.dll
LoadedModule[81]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Deployment\a2eb01b7dcc241d342f6442f4532c580\System.Deployment.ni.dll
LoadedModule[82]=C:\Windows\SYSTEM32\WindowsCodecs.dll
LoadedModule[83]=C:\Windows\SYSTEM32\mscms.dll
LoadedModule[84]=C:\Windows\SYSTEM32\USERENV.dll
LoadedModule[85]=C:\Windows\SYSTEM32\profapi.dll
LoadedModule[86]=C:\Windows\SYSTEM32\WindowsCodecsExt.dll
LoadedModule[87]=C:\Windows\SYSTEM32\icm32.dll
LoadedModule[88]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\diasymreader.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=CLR20r3
AppName=mGalaxy
AppPath=C:\Program Files (x86)\mGalaxy\mGalaxy.exe
NsPartner=windows
NsGroup=windows8

I hope those are some help! Thanks!

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: mgalaxy on February 19, 2014, 12:37:30 PM

Would you please try to install mGalaxy outside of the 'Program Files (x86)' folder (let's say at the root level of c: !) and do a test on it AND mGalaxy_Runway?

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: yamzzz on February 19, 2014, 07:20:16 PM

Alright, I just gave it a try in C:\mGalaxy. First off, the data folder still installed to C:\Program Files (x86)\mGalaxy\Data so I initially received the error you see as the attachment. Then I moved the data folder to the mGalaxy folder and after I created a MAME database,  mGalaxy_Runway would crash with the same error as before. However, if I DON'T click "Use database file," mGalaxy will start but is obviously not usable because my ROM names are all sorts of ugly and messed up. So perhaps it's something related to using a database file? I'm using a vanilla MAME 0.151 exe for what it's worth.

Thanks!

EDIT: Yep, it appears to work just fine without using a database, but as soon as I click that box and the save in mGalaxy_Runway, mGalaxy.exe will crash upon opening. Curious!

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: yamzzz on February 19, 2014, 08:19:43 PM

I have also tried both the 32-bit and 64-bit versions of MAME and creating a database for them in mGalaxy causes the crash.

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: mgalaxy on February 20, 2014, 05:54:08 AM

Quote

First off, the data folder still installed to C:\Program Files (x86)\mGalaxy\Data so I initially received the error you see as the attachment.

By default the mGalaxy data folder is installed in users/.../appdata/mGalaxy
...so the folder you saw was the one from the previous install (this folder isn't removed by the uninstaller to keep your previous data saved).
Anyway ;-)
It seems that you get an error while trying to load the 'xmlout.xml' file from the Mame folder inside of your mGalaxy data folder...would you please send me this file?!
If you can live with it, I would advice you to install mGalaxy with the default settings (thus not installing data folder it inside the mGalaxy application folder)

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: yamzzz on February 20, 2014, 07:06:34 AM

I was thinking that too but according to the error message I had received, that folder didn't exist anywhere other than the wrong directory. I've re-installed quite a few times and have tried to be vigilant when it comes to cleaning up the leftover files! :D

And unfortunately, there is no xmlout.xml file because mGalaxy_Runway crashes when I try to generate that database with MAME 0.151. All I have is icon and temp. :(

Is there anything else I might try doing in order to help?

Thanks for your support!

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: mgalaxy on February 20, 2014, 08:36:57 AM

Would you please try to generate an xmlout.xml file like explained here http://www.mgalaxy.com/forum/index.php?topic=513.msg1770#msg1770 (http://www.mgalaxy.com/forum/index.php?topic=513.msg1770#msg1770) and see if that works!!

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: yamzzz on February 20, 2014, 07:13:07 PM

Alright, I generated that file and it ends up being about 150mB. I can import it into Runway and then mGalaxy starts successfully with that database... except then it shows 0 roms. Aahh!

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: Aeliss on February 21, 2014, 04:28:21 AM

Check the filter but for me you have a path folder problem. Mame don't use same path than mGalaxy for exemple. Or you sill have a folder in windows system part.

For information C: is for windows, It s a good thing to never install application on it if you want to avoid autorisation problem.

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: mgalaxy on February 21, 2014, 05:24:27 PM

Quote

For information C: is for windows, It s a good thing to never install application on it if you want to avoid autorisation problem.

This is actually the inverse! Install your application outside of Program Files if you want (have) to avoid permission rules associated to this folder...in a simple way....(but I agree that you shouldn't try to bypass restrictions imposed by the Operating System!!)
C: is of course available to the user...where would you put your files otherwise!?
The installation directory have no influence on the program whatsoever. There is nothing special about the Program Files directories, just they are defined in the registry as the default locations to install applications (...and have super-duper protections on them)
Program Files is intended to store files that do not change during run of application. Files stored there should be changed only during installation/update.
Files to be changed during application run (profiles, settings etc.) should be stored in "Application Data" directory in users folder....and this is the actual default behavior of mGalaxy.

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: Aeliss on February 22, 2014, 05:04:35 AM

Yep sorry, it s that I want to said, avoid "Program Files" but It s better avoid "C:"

Without speaking about the "window security system", it s a better idea to make a partition for system (and applications usefull for it, like virtual drive), one other for applications, and one other for data.

It s really more easy to make maintenance, to repair or to make backup. Even you are carefull, your partition with system will be crappy, bad uninstalls, out of date installation, useless DLL, etc. Better idea to have a clean partition for applications and no comment for the utility to have all your data on an other partition.

Have you already take a look on a computer belong to a person that know nothing in computer ? C:/ take 500 G (with more than 100 folders with incomprehensible name in "program file" and ofc without defragmentation) full craps and he have D:/ 10%full E:/ Totally empty, ect ..

For me, and I think lot of emulator user, portability is more important than security, and for me "Application Data" is an horror too. But I can understand why it s usefull for devs.

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: mgalaxy on February 22, 2014, 07:33:37 AM

Quote from: Aeliss on February 22, 2014, 05:04:35 AM

Without speaking about the "window security system", it s a better idea to make a partition for system (and applications usefull for it, like virtual drive), one other for applications, and one other for data.

It s really more easy to make maintenance, to repair or to make backup. Even you are carefull, your partition with system will be crappy, bad uninstalls, out of date installation, useless DLL, etc. Better idea to have a clean partition for applications and no comment for the utility to have all your data on an other partition.

Have you already take a look on a computer belong to a person that know nothing in computer ? C:/ take 500 G (with more than 100 folders with incomprehensible name in "program file" and ofc without defragmentation) full craps and he have D:/ 10%full E:/ Totally empty, ect ..

I second that...totally agree with you Aeliss!!

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: yamzzz on February 22, 2014, 04:34:59 PM

I think I'm out of ideas.  :o :(

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: Aeliss on February 23, 2014, 09:19:21 AM

Try to make a fake database. Make a file called xmlout.xml (in Mgalaxy\Data\MAME) with inside

Code: [Select]

<?xml version="1.0" encoding="utf-8"?>
<dbase name="MAME" version="0.148 (Jan 11 2013)">
  <game name="Game-name" cloneof="">
    <description>blablabla</description>
    <genre>Labyrinthe</genre>
    <players>2P alt</players>
  </game>
</dbase>
with a real game name without extension.
If that don't work, I see only a bad path in mGalaxy_Runway for ROM.

Edit: Wich one extension have your roms ?

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: b_jammin666 on February 25, 2014, 04:10:02 PM

I am having the exact same problem. I cannot get mGalaxy to run at all, even if disabling MAME. I have tried all the other options in this thread.

It is installed at c:\emulators\mgalaxy\

Any other ideas..?

The following is in the event viewer:

Faulting application name: mGalaxy.exe, version: 5.2.0.0, time stamp: 0x52da69ff
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18229, time stamp: 0x51fb1116
Exception code: 0xe0434352
Fault offset: 0x0000c41f
Faulting process id: 0x105c
Faulting application start time: 0x01cf3274fd491e0a
Faulting application path: C:\emulators\mgalaxy\mGalaxy.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 3b8f62c4-9e68-11e3-8a85-00197edb9ab0

And this one too:

Application: mGalaxy.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Windows.Markup.XamlParseException
Stack:
   at System.Windows.Markup.WpfXamlLoader.Load(System.Xaml.XamlReader, System.Xaml.IXamlObjectWriterFactory, Boolean, System.Object, System.Xaml.XamlObjectWriterSettings, System.Uri)
   at System.Windows.Markup.WpfXamlLoader.LoadBaml(System.Xaml.XamlReader, Boolean, System.Object, System.Xaml.Permissions.XamlAccessLevel, System.Uri)
   at System.Windows.Markup.XamlReader.LoadBaml(System.IO.Stream, System.Windows.Markup.ParserContext, System.Object, Boolean)
   at System.Windows.Application.LoadBamlStreamWithSyncInfo(System.IO.Stream, System.Windows.Markup.ParserContext)
   at System.Windows.Application.LoadComponent(System.Uri, Boolean)
   at System.Windows.Application.DoStartup()
   at System.Windows.Application.<.ctor>b__1(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
   at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
   at System.Windows.Threading.Dispatcher.Run()
   at System.Windows.Application.RunDispatcher(System.Object)
   at System.Windows.Application.RunInternal(System.Windows.Window)
   at System.Windows.Application.Run(System.Windows.Window)
   at System.Windows.Application.Run()
   at mGalaxy.Application.Main()

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: mgalaxy on February 26, 2014, 06:07:40 AM

Have you tried downloading the Mame database here:
http://www.mgalaxy.com/forum/index.php?action=downloads;cat=1 (http://www.mgalaxy.com/forum/index.php?action=downloads;cat=1)
Import it with the mGalaxy_Runway 'import' button inside the MAME tab...and tell us what happen!

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: yamzzz on February 26, 2014, 08:37:08 PM

Quote from: mgalaxy on February 26, 2014, 06:07:40 AM

Have you tried downloading the Mame database here:
http://www.mgalaxy.com/forum/index.php?action=downloads;cat=1 (http://www.mgalaxy.com/forum/index.php?action=downloads;cat=1)
Import it with the mGalaxy_Runway 'import' button inside the MAME tab...and tell us what happen!

Y'know... that actually worked for me! Which is awesome! Thanks. :D

But since I apparently can't generate my own database file from my MAME (0.151 or 0.152) that is quite a few versions ahead of this 0.145 one, is there anyone out there who has and would care to share? Thanks again.

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: mgalaxy on February 27, 2014, 12:16:09 AM

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?

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: yamzzz on March 22, 2014, 07:56:15 AM

Quote from: mgalaxy on February 27, 2014, 12:16:09 AM

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?

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 database? I can't imagine it would be a problem. If that's okay, it can be found at http://www.progettoemma.net/public/ccount/click.php?id=6

Thanks for the offer and I hope I'm not too late!

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: mgalaxy on March 22, 2014, 10:33:22 AM

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 (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 ;-)

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: yamzzz on March 22, 2014, 04:17:19 PM

Quote from: mgalaxy on March 22, 2014, 10:33:22 AM

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 (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? :D

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: yamzzz on March 22, 2014, 05:13:02 PM

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?

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: yamzzz on March 28, 2014, 07:04:16 AM

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?

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: yamzzz on March 21, 2015, 11:51:02 AM

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

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: mgalaxy on March 21, 2015, 12:47:08 PM

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/ (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?

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: yamzzz on March 21, 2015, 12:58:58 PM

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:

Quote from: mgalaxy on March 21, 2015, 12:47:08 PM

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/ (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?

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: mgalaxy on March 21, 2015, 01:16:48 PM

Quote

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?

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: yamzzz on March 21, 2015, 01:33:44 PM

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!

Quote from: mgalaxy on March 21, 2015, 01:16:48 PM

Quote

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

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: mgalaxy on March 21, 2015, 02:22:15 PM

Quote

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

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: yamzzz on March 21, 2015, 02:26:07 PM

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!

Quote from: mgalaxy on March 21, 2015, 02:22:15 PM

Quote

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

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: mgalaxy on March 21, 2015, 06:30:51 PM

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!

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: yamzzz on March 21, 2015, 10:40:49 PM

Quote from: mgalaxy on March 21, 2015, 06:30:51 PM

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.

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: mgalaxy on March 22, 2015, 02:41:41 AM

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.

Title: Re: "mGalaxy has stopped working" before it even starts.
Post by: yamzzz on March 22, 2015, 07:56:14 AM

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 from: mgalaxy on March 22, 2015, 02:41:41 AM

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.