lr-MAME2010 Update Issue / Update Startup Script Fails

hooperre

Pi Model or other hardware: Pi 3
Power Supply used: 5v Canakit
RetroPie Version Used 4.2 w/ latest updates to main (retroarch, ES, etc.)
Built From: Pre made SD Image on RetroPie website
USB Devices connected: DS4
Controller used: DS4
Error messages received: N/A
Emulator: lr-MAME2010
How to replicate the problem: ~~Assume just update~~ Unsure how to replicate :/

I remember reading a while back that there was a build issue during MAME2010 that was resolved. I attempted to update MAME2010 (accidentally) and have been unable to get any of my 0.139 romset to work with MAME2010. I remember a year ago when there was talk of a build issue, I would have to update the core 3-4 times before eventually the ROMs would end up working again. I've updated 3-4x (at least) from both source and binary with no luck.

Is anyone else having this issue currently?

hooperre

I am starting to think this is a startup script issue? I attempted to update and got the following message:

Update failed:

error: Your local changes to the following files would be overwritten by merge:

platforms.cfg
scriptmodules/admin/images.sh
scriptmodules/archivefuncs.sh
scriptmodules/emulators/atari800.sh

Followed by a long list of recognizable emulators. I also attempted updating after exiting emulationstation, as I found this with a search as suggested by @TMNTturtlguy . All of this started with an accidental 'Install All Optional Packages' click. So then I went through and removed a bunch of emulators.

herb_fargus

@hooperre delete all the above listed files and update your setup script again. You've made manual edits that break the update.

hooperre

@herb_fargus Thanks, Herb. Is there a way to see maybe where I made edits to break those? Not sure really where I would have done that.

mitu

This post is deleted!

BuZz

@hooperre you can check the files listed (or from commandline do git diff from within ~/RetroPie-Setup) which will show the differences. If you didn't edit any files, you might have some sdcard corruption or something.

hooperre

@buzz Thanks. I certainly didn't make any manual edits to platforms.cfg, images.sh, etc. I forgot until now when I accidentally hit the install all packages it stalled out in the middle somewhere (or was updating from source now that I think about it) and I shut it off. I could have corrupted the SD there. I have a backup that isn't too old.

Should I just go ahead and delete the files and update again as Herb suggested, or would it be safer to just revert to the backup in your opinion? Only changes I've made to the SD (roms and gameslists on USB) are some shader presets on RA and game specific default emulator choices I can write down before updating. Thanks!

mitu

@hooperre Try running a git --reset hard from within ~/RetroPie-Setup and try updating again. Maybe the card is not corruputed by some files got transferred incompletely when you interrupted the previous update.

hooperre

@mitu I'm reading about the git --reset command now and want to make sure I absolutely understand what you're saying before proceeding as I'm a noob when it comes to both Linux and GitHub. I would want to run git --reset hard from within the ~/RetroPie-Setup folder with no additional file information?

BuZz

@hooperre ~~yes.~~ no. you need to run git reset --hard

BuZz

@mitu it's git reset --hard

mitu

@buzz I stand corrected, it seems my git-fu neads more practice.

hooperre

Thank you, @BuZz, @mitu, and @herb_fargus. This fixed the Startup Script Issue. Appreciate all y'all's help. MAME2010 issue in my OP still persists. Just goes to a black screen. Probably not more info to give than that, unfortunately.

I should note that it worked with my ROMs previously and the ROMs work in MAME2014 despite being from the 0.139 romset, leading to my working thought that it is indeed the lr-MAME2010 at fault.

hooperre

Is there a way to clean any files associated with MAME2010 from my SD? I've updated the startup script successfully, but still not getting MAME2010 to install correctly. I've tried removing and re-installing it from source and binary multiple times. Thanks.

dankcushions

@hooperre said in lr-MAME2010 Update Issue / Update Startup Script Fails:

Is there a way to clean any files associated with MAME2010 from my SD? I've updated the startup script successfully, but still not getting MAME2010 to install correctly. I've tried removing and re-installing it from source and binary multiple times. Thanks.

what makes you think it hasn't installed correctly? do you get an error during build/install?

hooperre

This post is deleted!

hooperre

@dankcushions I haven't got an error but all my roms that were previously working with lr-MAME2010 no longer work after an accidental 'update all' that stalled and required a hard reset during update. (Could I have SSH'd and safely rebooted? I think I tried.) So I've attempted to rebuild with source and binary since with no luck. About 6 times a piece. In the past, specifically with lr-MAME2010 I would have to rebuild (and I think I was only successful with building from source) about 3 times before I would get it to work. The other times it would go to a black screen, then back to ES. I've tested the roms in MAME2014 and the all seem to work... Maybe I just roll with that for now until I start fresh.

dankcushions

@hooperre i'm sorry i still don't understand. when you update something (from binary or source), it has two results: it either completes successfully, and goes back to the setup script, or it fails, and says it has failed. what exactly happens when you try and update it? i'm not talking about when you run a game - one step at a time.

hooperre

@dankcushions Sure thing. I appreciate your patience with me and willingness to help me here.

When I update from binary or source, it returns to the setup script without an error.

dankcushions

@hooperre sounds good so far! i think everything will be installing correctly.

now could you try and launch a game that previously worked, and then after it fails, could you please retrieve /dev/shm/runcommand.logand paste the contents here?