@hawkes_84 To not get too much into it, you will have to put in the full file path from the root folder to the pcx file as this tells the computer where to look. Just saying psx will not be enough. It should look something like this: /home/pi/RetroPie/roms/psx Then if you add your file name to the mix it will look like so: /home/pi/RetroPie/roms/psx/file.bin.ecm Note that this path will be dependant on your system set up. A short way of getting the path, however, is by simply right-clicking on your .ecm file and selecting "Copy file path(s)" if you are doing this in Raspberry OS.

@Brandon12345678 It works now. Thanks for your help.

I was instructed in one of the threads on here to make an alias to the folder on the usb drive containing the roms and just replace the folder in the retropie roms folder with the same named alias. That also works. One thing that I like about that is I could at any time just delete the alias and replace with a folder to return it to reading off the sd card, or you could have part of a folder on the usb and part on the sd (if you don’t mind having two subfolders in ES).

@danyo Got it running. Thanks!

@MartyH1988 First try to follow all these steps (all of them from the top!): https://retropie.org.uk/docs/Wifi/ Then to transfer roms over the network follow these steps: https://retropie.org.uk/docs/Transferring-Roms/#samba-shares Make sure you place the roms in the right folders! Read the documentation. For example for the SNES: https://retropie.org.uk/docs/Super-Nintendo-Entertainment-System/#roms If you cant find the network share, perhaps try this way of accessing your pi through SFTP. https://retropie.org.uk/docs/Transferring-Roms/#sftp I've been unable to connect to the network share on my pi. For me it turned out I'm having a problem that windows 10 had certain group policies disabled that blocked the share. The fix was explained here. Though, I didnt like the idea of leaving insecure policies open, so I decided to transfer roms with SFTP. Or alternatively, using an old windows 7 laptop, which could access the share.

@mitu Hi, that's great info thanks. I presume that if it isn't writable, then pastern.com will allow me to change it? The weird thing is that it was working so well, and then for no reason it stopped. Also, it is allowing me to do the first edit (ie try another emulator) and seems to write it to the config file, but then won't let me further edit it. Its the same in every emulator - PS1, SNES etc. Got me confused! Will try what you suggest tho. Thanks again, appreciate it. Glyn

There's also an easy way to transfer your ROMs automatically from an FAT32 or exFAT formatted USB stick. I don't know if NTFS will work with this, too.

@mitu thanks that worked a treat!

yes sorry meant "pi" . It was the password that had been changed but not sure when. Was able to change back through sudo raspi-config. Thanks for you help

ah yes, sorry my fault :)

@mitu omxplayer accelerator was already on so i turned it off to see if it worked but it didn’t

OK, works when i mount with option uid=1000 in autofs.network. Thanks for the hint.

Haha yes, it works :D Simple solution is: First of all - if you have your copy of .sav file (or any other containing your save state), backup it to have an original one in case of losing all saved data. Open rom in Visual Boy Advance, restore you save and create save state using built in saving mechanism. Now close the game and remove in-game save file - file which is a copy of your original state file. Next open game in Visual Boy Advance and load state saved in built it saving mechanism. Go to VBA Options > Emulator > Save Type and change it to SRAM Perform in-game saving. New .sav file will be created in folder when your game was stored. Rename file with extesion for "your_game_name.srm". Copy it to Retropie. After these steps I was able to open my save state from Pocket-Go on my GPICASE :) BTW: There is a possibility that @lostless sugesstion will work to but if not, you need to perfrom above steps. BTW2: Visual Boy Advance saves in-game states files as a .sav file, so you are able to copy you states from VBA to Retroflag also. Thank you guys!

You haven't added any details about your system - as detailed in https://retropie.org.uk/forum/topic/3/read-this-first. To get a detailed log file from the emulator, enable debug logging from Runcommand launch menu when launching the game, then exit the emulator and post the contents of the log file (/dev/shm/runcommand.log) on pastebin.com.

@renepela confirming lr-vice problems too, build fail on linux mint 19.3 x64 (RetroPie 4.6)

@mitu my bad

Full ack! IMO the retropie-project and ROMS/Images are two different things - even if they depend on eachother to make sense. And therefore retropie should never implant any direct channels to any sites or databases containing copyrightet material. It is no Problem to find enough food for the rom-folders by just searching the internet with Google or any other search-engine. The retropie-project should stay clean, there is no reason to offer any shortcuts to rom-collections imo.