I'll first list the problems I'm having and then my step-by-step of what I did up until now.
My problems are:
- mGalaxy overwrites Favorites.ini for MAME (see solution above)
- mGalaxy Runway won't open after I run mGalaxy.exe once
- No Logo artwork on new Arcade Room theme (see solution above)
- I installed 7.0 in the directory I had 6.0 installed in to save information. I ran runway and it was all there. With the new license copied in, I selected the new theme and pointed Logos to the big folder of PNG logo art that I have.
- After saving in Runway, I ran mGalaxy and it loaded fine, except my Favorites went from 208 to 54. I went back out and re-copied my 6.0 backup of Favorites.ini and XMLOUT.xml into the MAME data folder in UserSystems, overwriting the files there.
- I re-ran mGalaxy and the same thing happened. Favorites.ini was overwritten to 54 games. At this point I realized that my logo art never showed.
- I went back out and double-checked the Favorites.ini files. My 6.0 backup does have 208 entries. The current one in mGalaxy 7.0 has 54. I noticed Zoo Keeper was a missing game, re-ran mGalaxy and went to it in the main list. Marquee, Snap, Video all ran, and the game runs.
- I tried opening Runway and I would get the white box like it was about to turn on, and then it crashed. The box just goes away and nothing happens. Runway won't open. I rebooted, and the same thing happens.
- I installed 7.0 into the 6.0 directory again. Runway still won't open. I install 7.0 into its own directory and Runway there opens fine. I set up MAME again. I copy my 6.0 backup Favorites.ini and XMLOUT.xml again. Everything is setup, including the license file and 6.0 directory's catver.ini and nplayers.ini in the main mGalaxy directory. I quit and run mGalaxy.
- Same problem. 54 favorites....no logo art....When I exit and try running Runway in the 7.0 folder, it now won't open just like the Runway in the 6.0 folder. It seems to me that Runway breaks as soon as mGalaxy runs for the first time.
But that's the least of the issues at this point.
I'm running Windows 10 Home version 10.0.17134 Build 17134 on an x64 PC