@cyperghost I am curious what line you read in the OP's text that leads you to believe that. He said '40GB of custom games/settings', but I think he means that he has put a lot of work into his current setup and wants to fix it without starting all over again.
To quiesce those messages, either start the script independently (not part of the autostart.sh) or redirect the script's messages to /dev/null:
my_script 2>&1 1>/dev/null &
Thanks, yes i add this to hide the script messages.
And i add the line before emulationstation, like that it works.
I don't understand before that this file output are appearing on the user's terminal.
@mitu I think no. But i dont really know if something change or not... or if i did it wrong when I writed that lines (no error message, just go down to the next line) but still having the same problem with the blue menu "in game"
Just another stupid question for my part, .how I can restart the rasp, or the system in the command menu (this one we are working) because I don't know if need to restart or save the changes.
In what way is your solution better than using the RetroArch GUI?
Now I'm at my laptop and I'm able (have patience) to type better than on my Android phone...
My solution pleases my own taste because when using RGUI RetroArch dumps the current status of every single option of the running instance in the retroarch.cfg, overwriting the previous content. All those useful comments explaining what the options do will disappear.
We all know that RetroArch documentation is very scarce and scattered. I think that the retroarch.cfg skeleton is a good resource of information about the RetroArch options.