Editing Default.cfg file in rom Mame 2003 folder

leitmotiv

I recently edited my MAME 2003 default.cfg file to default.old to enable my tab key for remapping controls for some games. Worked great. Then I restored it by dropping in my backup copy because without it, my Retroarch remaps were "defaulted". I went to edit some more games with the tab key by doing the very thing I described above , by restarting the retropie. Now it doesn't work. I didn't check on my first run, but on the reboot it generates a new default.cfg file. Probably normal. I assume it happened the first time. Why am I unable to activate the tab key on my keyboard now?

Edit: Using B+, Retropie version 4.4.9
I have MAME 2000, 2003, 2003+, 2010, and 2015 cores installed.
PS3 controller

mitu

Please add more info about your system - https://retropie.org.uk/forum/topic/3/read-this-first.
What MAME emulator are you using ?

leitmotiv

@mitu I edited my post to reflect, sorry about that

mitu

@leitmotiv Which MAME emulator version are you using when trying to configure the Input ?
You don't need to restart RetroPie just because you changed the input binding for a game in MAME (or ther emulator). What's the location of the file you backed-up ?

leitmotiv

@mitu

/home/pi/RetroPie/roms/mame-libretro/mame2003 is the location of the file I am editing/backing up.

I assume by version you mean the "MAME 2003"? I didn't reboot for the input remapping, I rebooted to get the TAB key to work the first time around.

Now I have a new problem and none of my roms are booting... I may be detained for a bit

leitmotiv

holy heck, I don't know why my roms aren't booting now (for any system). The only thing I can think of, is I went to the retropie menu, clicked on retropie setup. It locked up and didn't load the setup menu so I had to turn it off and turn it back on.

mitu

@leitmotiv Do you have enough free disk space on the sd card ? You can check in the RetroPie welcome message, shown when you Exit Emulationstation.

leitmotiv

@mitu I am at 88% capacity on the SD card. Roms are on a flash drive.

mitu

Looks like either a permission problem or a disk reading issue - external flash drive may have errors if you cannot load any of the ROMs you have there.

leitmotiv

@mitu huh... I got Nintendo DS roms to run... but several other systems aren't.

mitu

Can you run with verbose logging enabled one of the failing ROMs and then put the contents of the /var/run/runcommand.log file on pastebin.com ?

leitmotiv

@mitu man, my blood pressure is rising and I may have to time myself out. haha....

Um... no? because that run command launch menu isn't popping up. Usually when I wanted to switch MAME emulators I with hit a button, so I JUST tried doing that to see if I could interact with an invisible launch menu and now it locked up again. I also see that there is a present mouse cursor on the screen that I'm not liking. I recently plugged in my mouse to interact as a stylus for the Nintendo DS rom I was fixing up. And strangely it is ONLY Nintendo DS roms I can boot. None of the other 24 systems are booting their roms. ayieee!!

leitmotiv

@mitu I just took my flash drive to my computer and it said it was "fixing some problems" and stuck the problem files in a Found folder, which is now holding FILE0000.CHK

I will eject the flash drive and reinsert it into the retropie. See if the problem resolves

leitmotiv

@mitu well... problem still persists. I ran a game with verbose logging enabled, but as a noob, I can't find the log file. It's not on my flash drive is it? I can't find it using WinSCP.

mitu

@leitmotiv The file is /dev/shm/runcommand.log, somehow I've posted the path wrong the first time.

leitmotiv

@mitu

https://pastebin.com/5GB611x4

mitu

@leitmotiv You didn't enable verbose logging. From the looks of it, the ROM file might be corrupted or incomplete. Enable verbose logging from the Runcommand launch menu and you'll get a more detailed log file.

leitmotiv

@mitu I'm confused. That link you sent for enabling verbose logging shows the option to enable it. I selected to Launch the rom with Verbose Logging. Is that not how it's done?

mitu

@leitmotiv Yes, that's the method and it looks like the verbose flag was added. The problem is that your RetroArch program is corrupted:

/opt/retropie/supplementary/runcommand/runcommand.sh: line 1009: /opt/retropie/emulators/retroarch/bin/retroarch: Permission denied

Try to re-install it from the RetroPie setup script, from the main packages section.

leitmotiv

@mitu all right, cautiously will... anything I can do to save controller remaps files and my setup? I've been pumping tons of hours into this thing trying to get it all set up and was getting close to being done. I would hate to spend another 40 hours+ redoing all the work I've done.

Or am I safe?