Anyway, regardless of why, 7.0 Favorites.ini MUST have the ROM name listed. The name displayed within mGalaxy will still be whatever you have in the <Description> tag in XMLOUT.
Yes, there was indeed a change in the way mGalaxy handles favorites from v6.2 (you actually participate to the discussion at the time http://www.mgalaxy.com/forum/index.php?topic=925.msg3844#msg3844)
...This is now indeed the rom name that is saved
This change is handled by the (internal) updater from version 6.0 to newer, so you shouldn't have to manually rename all your favorites...but there might be a bug , could you please try this:
1. Create a copy of your mGalaxy v6.0 folder
2. Install mGalaxy v7.0 in the same folder. DON'T LAUNCH ANYTHING
3. Download this test version of 'mg_filesupdater.exe' (attached to this message) and overwrite the one in the mGalaxy folder
4. Run mGalaxy_Runway
...and please report if the 'favorites.ini' file updates correctly
Thanks for the info! Ok, I did this and I think the problem with Runway being broken is stopping me from testing this.
Just to be clear, my 6.0 folder is not pure. I installed 7.0 into it already, and I ran mGalaxy, which seems to be connected to Runway not working. That's the folder I copied to try this. So even with the new mg_filesupdater file copied in, I can't open Runway to finish the test
The only way for me to get Runway to work is to install 7.0 into a new directory. Let me know if this process will help you test the Favorites issue:
1) I install 7.0 into a new directory and launch Runway
2) Setup MAME in Runway and then exit Runway
3) Copy my backup of Favorites.INI and XMLOUT.xml into the newly created MAME UserSystem folder
4) Copy the updated mg_filesupdater that you posted here to the mGalaxy directory.
5) Run Runway again