RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login
    Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

    Single Boot ROM

    Scheduled Pinned Locked Moved Help and Support
    single rombootretropi
    16 Posts 4 Posters 1.1k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • mituM
      mitu Global Moderator @Azurden
      last edited by

      @Azurden Launch the game as normal, then open the /var/shm/runcommand.log file to see the full command line used to start the ROM. Also, take a look in the docs.

      A 1 Reply Last reply Reply Quote 0
      • A
        Azurden @mitu
        last edited by Azurden

        @mitu Sorry new to Pi and all.. So do a..

        sudo nano /var/shm/runcommand.log

        mituM 1 Reply Last reply Reply Quote 0
        • mituM
          mitu Global Moderator @Azurden
          last edited by

          @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.

          1 Reply Last reply Reply Quote 0
          • A
            Azurden
            last edited by

            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?

            mituM 1 Reply Last reply Reply Quote 0
            • mituM
              mitu Global Moderator @Azurden
              last edited by

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

              1 Reply Last reply Reply Quote 0
              • A
                Azurden
                last edited by

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

                1 Reply Last reply Reply Quote 0
                • A
                  Azurden
                  last edited by 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...

                  mituM 1 Reply Last reply Reply Quote 0
                  • mituM
                    mitu Global Moderator @Azurden
                    last edited by

                    @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.

                    1 Reply Last reply Reply Quote 0
                    • A
                      Azurden
                      last edited by

                      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

                      mituM 1 Reply Last reply Reply Quote 0
                      • mituM
                        mitu Global Moderator @Azurden
                        last edited by

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

                        A 1 Reply Last reply Reply Quote 0
                        • A
                          Azurden @mitu
                          last edited by

                          @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.

                          1 Reply Last reply Reply Quote 0
                          • stoney66S
                            stoney66
                            last edited by

                            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

                            1 Reply Last reply Reply Quote 0
                            • H
                              hhromic
                              last edited by 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.

                              1 Reply Last reply Reply Quote 0
                              • H
                                hhromic
                                last edited by

                                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.

                                1 Reply Last reply Reply Quote 0
                                • First post
                                  Last post

                                Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

                                Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.