yeah i no, i though hard about setting mess up, but didn't even try in the end to be honest, not got enough time to try and get it setup, just for gx4000

thanks all who replied

It's actually a really bad idea to modify a linux text config file with a rich text editor.
The best option is to use a linux text editor (vim, nano, ...), or a simple MS notepad (or better, notepad++).
You're lucky only the sound was impacted :)

Sorry found my answer. won't let me delete.
https://retropie.org.uk/forum/topic/10250/famicom-folder/3
Will this allow the same emulators to show up to? What size does the image have to be?
Wish they made it easier.

Got It! I gladly appreciate the time and effort you took in explaining what packages were :) Thanks!

It was solved by updating all installed packages from the Retropie setup tool.

@bifelix89 set the "a" button as your hotkey in emulationstation start menu controller configuration. Just so the hotkey option gets generated. Now open up the file /opt/retropie/configs/all/retroarch/autoconfig/NameOfYourController.cfg . Find the part for exit and hotkey. Assign the number that is your start key to the hotkey and change the exit to another key. (Not b or x as they are used for other options)

@muehltime

are your extensions capitalized? .NES will not work , but .nes will

Capitalized extensions are set to be acceptable in /etc/emulationstation/es_systems.cfg and should work fine. Below is an excerpt from the NES system entry.

<system> <name>nes</name> <fullname>Nintendo Entertainment System</fullname> <path>/home/pi/RetroPie/roms/nes</path> <extension>.7z .nes .zip .7Z .NES .ZIP</extension> <command>/opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ nes %ROM%</command> <platform>nes</platform> <theme>nes</theme> </system>

@thewinterdojer Binary, I believe.

I haven't updated at all since March until now, so could be why it took so long. Emulators/Emulationstation/Retroarch etc. only took about 20 minutes to update.

It was just the kernel headers which took a very long time.

@sadtraxx What they meant was that you don't unzip the roms themselves, maybe there was some miscommunication.

The files you're expected to have in the folder must match these:

https://docs.google.com/spreadsheets/u/1/d/1GaqIIoiWbzKHwZ52S2xCSDQXILo81Ls1mHK6czKGAtM/edit?usp=sharing

So, the power source is really such an important point that in no case should not be neglected? And let's say if I want to use an external HD that does not have its own power, then it is desirable to buy a USB hub with its own power supply? But even so, I still can not understand what would be so terrible if the external HD is powered by the pi itself.

@benzine78 dont forget # is a £

@tmntturtlguy yeah that answers it. I was just going to test if i had any issues with some of the same games just in case but you more than answered the question.

@red2blue

Yes it is, because it's supported by every system. But if you got it fixed up, good. But if not, you should try it out with other USB stick instead, so don't yet format your main drive, if it's not going to work in the end.

Thanks guys. Yes - I'm using a Mac to copy over the files. Will use windows from now on.
Thanks again.

I've found a solution:

Install attract frontend, then i can configure my two joypads manually for the frontend.

For the backend(retroarch) i had the next line with value "linuxraw" so i changed it to udev and autoconfig worked!

input_joypad_driver = "udev"

The buttons were previously mapped so only configuring retroarch/all/retroarch.cfg was enough, now the two joypads work.

Hope this post helps someone!

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