Thanks man!!!!

@mitu
Ah ok.
Yes I meant simply a hard link but didn't realize it wouldn't work due to crossing over to a separate filesystem.

@sad_muso if mame2003 (aka mame 0.78) is complaining about a set supposedly made for mame2003, then your set is crap.
clrmamepro is your friend.

@clockwork42 I know this thread is a few months old but figured out how to do exactly what I believe you are trying to do and I wanted to post it in case you or anyone else is still looking like I was up until recently.

I separated MSU-1 into a distinct system from the rest of SNES called "snesmsu1". Here is what my "/roms/snesmsu1" folder looks like:

alt text

For this setup you would also need to make a folder called "snesmsu1" at "/opt/retropie/configs/snesmsu1". You could copy the "snes" folder from "configs" as a starting point. I removed all emulators from "emulators.cfg" except for lr-snes9x and replaced the reference to "snes" with "snesmsu1" so that it looks like this:

lr-snes9x = "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-snes9x/snes9x_libretro.so --config /opt/retropie/configs/snesmsu1/retroarch.cfg %ROM%" default = "lr-snes9x"

I also edit "retroarch.cfg" replacing the reference to "snes" with "snesmsu1" so that it looks like this:

# Settings made here will only override settings in the global retroarch.cfg if placed above the #include line input_remapping_directory = "/opt/retropie/configs/snesmsu1/" #include "/opt/retropie/configs/all/retroarch.cfg"

The crucial part that will make runcommand execute your 'rom.sh' files as scripts instead of trying to open them with the default emulator is the command node in your "es_systems.cfg" file. Here is what my system node for "snesmsu1" looks like, including the command:

<system> <name>snesmsu1</name> <fullname>Super Nintendo MSU1</fullname> <path>/home/pi/RetroPie/roms/snesmsu1</path> <extension>.sh .SH</extension> <command>bash %ROM%</command> <platform>snes</platform> <theme>snesmsu1</theme> </system>

With the above in your "es_systems.cfg" and a folder named snesmsu1 in your "roms" folder, you will have a separate section in EmulationStation for SNES MSU-1. You will also have to use a theme that has an "snesmsu1" section. Otherwise, you will have a blank, unthemed section for "snesmsu1".

Only '.sh' files in your "snesmsu1" folder will be displayed in this section in EmulationStation. Notice in my screenshot that the names of all the folders that contain the actual game files begin with a dot which makes them hidden in Linux so they aren't displayed in EmulationStaion. Your "gamelist.xml" file points to one of the '.sh' files in the "path" node for each game and then you can have all your metadata and media set up as well and everything will look pretty in EmulationStation.

Other than that, here is an example of what my 'Chrono Trigger (MSU-1).sh' looks like for launching the game:

#!/bin/bash "/opt/retropie/supplementary/runcommand/runcommand.sh" 0 _SYS_ "snesmsu1" "/home/pi/RetroPie/roms/snesmsu1/.Chrono Trigger (MSU-1)/Chrono Trigger (MSU-1).sfc"

Because of the different commands in "es_systems.cfg" for launching regular SNES ROMs vs. running shell scripts, you really do need to separate MSU-1 into a different system from regular SNES. Actually, you could combine them, but if you want to keep things organized as described then you would have to create a similar shell script for each regular SNES ROM as well. I prefer to have them separated for aesthetics, organization and ease of use.

With everything configured as I described, EmulationStation looks nice and tidy and so does my "/roms/snesmsu1" folder. I hope this helps.

@mirko Hi! Please supply this info so we can help you better:

Pi Model or other hardware: (B, B+, 2 B, 3, X86 PC etc..)
Power Supply used: (If using a Pi)
RetroPie Version Used (eg 3.6, 3.8.1, 4.1 - do not write latest):
Built From: (Pre made SD Image on RetroPie website, Berryboot, or on top of existing OS etc.. - please provide the filename of any image used)
USB Devices connected:
Controller used:
Error messages received:
Log found in /dev/shm/runcommand.log (if relevant):
Guide used: (Mention if you followed a guide)
File: (File with issue - with FULL path)
Emulator: (Name of emulator - if applicable)
Attachment of config files: (PLEASE USE PASTEBIN.COM FOR LARGE LOGS)
How to replicate the problem:

@mitu Yeah, I saw that as well. But there is a ccd file with the same name besides it and that it does support. So shouldn't it work anyways?

Hm, I tried with R-type (the .tzx file) and it took almost 3 minutes to load (after changing the option for Fuse), with the cassette buzzing and all. I think it depends on the tape file. I tried Fred and I think it has also it's own loading routine.

Thanks @hhromic .

I knew that it's not easy to migrate from Jessie to Stretch.

Maybe, I should wait for the next evolution of Raspberry Pi... For me, do this migration is a vast amount of time moving files out and in the system.

Thank you!

@skullgazing That's not enough info. Please answer the questions outlined in https://retropie.org.uk/forum/topic/3/read-this-first.
The message Errors are logged to /dev/shm/runcommand.log is the default message shown by the Runcommand before running any game. If there's an error somewhere, it might be logged in that file, so you could paste the contents of the files when you answer the questions from the page above.

@dankcushions

When I try to open select file manager while it’s loading from the sd card reader, it freezes up bad for a while

Are you suggesting I load up file manager first and then insert the memory stick?