I have the idea of hosting my roms on an SMB share on my NAS so that save game files and such are all synchronized across multiple computers. I’ve modified the es_systems.cfg file to point to the correct paths for the roms, but whenever I try to run the rom, I get an error that the rom failed to load. I’ve tried running a super nintendo rom using snes9x-rpi from the shell and it fails to launch the rom too.
I don’t really want to copy the rom files to the pi, as this defeats the whole synching idea. Is there a way to get this working?
This has mapped the server share/subfolder to the Roms directory so the RetroPie install does not think anything is changed, it takes a bit longer to boot but im planning on leaving it on as much as possible and once i have finished testing i will be setting it up so no logon credentials are in the fstab folder (this was a quick dirty test to see if it was possible)
This is pretty much what I did short of clearing out the directory and mounting to that location. I mounted the share elsewhere and changed the path for the system in es_system.cfg. This appears to have worked for all systems but Super Nintendo. Nes is fine and playstation 1 is fine. I haven’t tested any others. Can you confirm that your solution works with snes files?
A word of warning though if you run the scraper to pull game details when it has finished browsing your games is frustratingly slow so if you are going to run over the network dont have scraped game data – Also to help speed up navigation i would reccomend under the emulators directory you have folders 0-9 a-c etc etc and put your ROMS into the respective folders
Alright. I’ll try this, but I don’t understand why it would work to mount the share in one location but not another. Separating the roms into separate folders sounds like a good idea. I planned on keeping the scraped data locally on the pi. As long as the images are small, it should still work without much slowdown in browsing.