Single Boot ROM

mitu

@Azurden I don't understand what you're trying to say. If you need to look at that file, exit Emulationstation and use nano to open the file and take a look at it.

Azurden

So tried to run it and says the file is not there. Did a WINSCP to the pi and I do not see the shm folder in the var folder?

mitu

@Azurden Sorry, I meant /dev/shm/runcommand.log - I probably copied your input by mistake.

Azurden

Ok found the dir but no runcommand.log in there. Just a rpmanager.log

Azurden

Sorry has to refresh...

This is what it had...

Parameters:
Executing: /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-picodrive/picodrive_libretro.so --config /opt/retropie/configs/megadrive/retroarch.cfg "/home/pi/RetroPie/roms/megadrive/FixItFelixJr.bin" --appendconfig /dev/shm/retroarch.cfg'|'"/home/pi/RetroPie/roms/megadrive/FixItFelixJr.bin.cfg"
Failed to open /home/pi/RetroPie/roms/megadrive/FixItFelixJr.srm: No such file or directory

What I dont understand is it does launch when I do this via retropi...

mitu

@Azurden said in Single Boot ROM:

/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-picodrive/picodrive_libretro.so --config /opt/retropie/configs/megadrive/retroarch.cfg "/home/pi/RetroPie/roms/megadrive/FixItFelixJr.bin"

So the command line is

/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-picodrive/picodrive_libretro.so --config /opt/retropie/configs/megadrive/retroarch.cfg "/home/pi/RetroPie/roms/megadrive/FixItFelixJr.bin"

You can use that as your command to boot a single ROM.

Azurden

Here is what it puts out in the log when I try to boot right to the .binand it fails to launch

Parameters:
Executing: /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-picodrive/picodrive_libretro.so --config /opt/retropie/configs/megadrive/retroarch.cfg "/home/pi/RetroPie/roms/megadrive/FixItFelixJr" --appendconfig /dev/shm/retroarch.cfg

mitu

@Azurden You forgot the .bin extension of the ROM in the command line.

Azurden

@mitu yea I tried it both ways, with and without the .bin

I did use this that you posted

/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-picodrive/picodrive_libretro.so --config /opt/retropie/configs/megadrive/retroarch.cfg "/home/pi/RetroPie/roms/megadrive/FixItFelixJr.bin"

and it did work. Awesome way to find out what the path is... Thank you!

I do keep getting this message when it booted still.

Failed to open /home/pi/RetroPie/roms/megadrive/FixItFelixJr.srm: No such file or directory

Anything I can do to remove or suppress this? Building a custom cab for this and would like it to just boot direct without the message showing.

stoney66

srm is a save file (not saved state file), maybe launch the game and do an in game save if it has that option? Not sure if you can just create a blank file with that name and have the error go away e.g. touch /home/pi/RetroPie/roms/megadrive/FixItFelixJr.srm

hhromic

You can also redirect all errors to a file like runcommand does, this will keep it clean on the console and still let you see/inspect if something goes wrong:

# Launch FixItFelixJr
/opt/retropie/emulators/retroarch/bin/retroarch \
    -L /opt/retropie/libretrocores/lr-picodrive/picodrive_libretro.so \
    --config /opt/retropie/configs/megadrive/retroarch.cfg \ 
    "/home/pi/RetroPie/roms/megadrive/FixItFelixJr.bin" \
    2>&1 >/dev/shm/fixitfelixjr.log

Edit: btw not finding srm files is normal if the games don't save to nvram.

hhromic

On a second thought, even better would be to actually use runcommand, taking advantage of its goodies such as video mode settings and emulator selection:

# Launch FixItFelixJr
/opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ megadrive "/home/pi/RetroPie/roms/megadrive/FixItFelixJr.bin"

Runcommand also prepares the console like hiding the cursor and even can display a splash screen art if configured. This is the way EmulationStation launches games and you also get the benefit of error messages being logged to /dev/shm/runcommand.log for debugging.