This confusion happened over the course of weeks after I disabled the onscreen help. Forgive me. I've got some grey hair in my late 30s. :D

I´m learning too to do some things, but Thank you anyway.

@mitu
Sure! I will post all my findings to help others as well.
Thanks for your time.

@mitu Off course this will work. However each time I want to change another item have to create the retroarchcfg file again. When I use a simple copy script all other settings can't be changed anymore. So each time I go to the retroarch menu and change something the retroarch.cfg gets overwritten. So using two files (one with and one without the disabled hotkey) just isn't a working solution. I really want to be able to make it independent of other changes in the file I sometimes do using the retroarch menu.
A script that edits that single line is the best solution, however I'm just not clever enough to make the script.

@chipsnblip Argh, I thought there was something wrong with the link, but the target was the problem. 😳

Again, thanks!

edit: typo

@cyperghost Alas, I don't now how ES and its emulators will react to this on runtime. I didn't use it myself (yet), but researched it only because of this thread and a general interest for future use.

As for specific drivers, I don't have any experience in that either, but as long as they depend on the devices in /dev/input/, they should react to disabled devices there accordingly, I suppose.

@mitu Thank for that info. I did remove the !kms and it build with no errors, but I get this when I try to run dosbox

DOSBox version 0.74
Copyright 2002-2010 DOSBox Team, published under GNU GPL.

Exit to error: Can't init SDL Unable to open mouse

So it's a start...

@caver01 Of course :) I will definetly post. I took a few photos during the build, and its still not finished yet. Should be done in a week :)

@ben-almonte Update to retropie 4.3. Reconfigure your controller. The last button to configure is the hotkey, so you can assign that to something other than select.

@salvaliebana install joystick selection. Go into retropie menu. If you see joystick selection then it is already installed and go to paragraph 2. If it is not read paragraph 1.

In the retropie menu, go into runcommand. In there install joystick selection. Exit. Restart your pi.

Go into retropie menu, then into joystick selection. In option number 1 you can select which joystick is each player.

I have simply deleted the /dev/input/js* and /dev/input/event* link so that the system does not use it as Joypad.
I have made a little script that delets the links and put it into rc.local so the links get deleted every boot. Somehow a udevrule did not work for me.

This issue can be closed

Ahh ok. I thought about doing this, but thought there might be a "better" way to do it (like a setting or menu option). Thanks for your help!

@Loren said in 2 questions.:

How do I completely remove the powerblock software (per say) from retropie. I built a SNES with one, but then flashed my image to another card for a different build and I don't need/want it on that build. Is there any way this can be done?

You can find instructions for uninstalling the PowerBlock driver at https://github.com/petrockblog/PowerBlock#uninstalling-the-service-andor-the-binary.

@Hype built-in bluetooth works fine for me with my 8bitdo NES30 Pro controllers without lag.

@Concat said in Run Command:

I didn't realize runcommand requires a specific naming convention

I think this convention was made to match the scraper one.