@john1967 please fill out https://retropie.org.uk/forum/topic/3/read-this-first

booting to emulationstation is default behaviour for the official image, however here is how to configure it for a manual installation: https://retropie.org.uk/docs/FAQ/#how-do-i-boot-to-the-desktop-or-kodi

@folly Ah nice!!!

I've got a few other computer systems I'm wanting to try .. so this translate tool is awesome.

You're welcome.

On more thing: As a courtesy for other user here, please add [Solved] or similar to the topic of your original post.

Just for the record, this command removes write permissions from the file:

sudo chmod -w /boot/config.txt

Restore them only for the owner (the default) with u+w instead of -w.

But note that any script that runs with admin rights can change the file nonetheless.

edit: Ah, I noticed the logical flaw in this. The file is owned by the admin user root and it is already only editable by the owner. So removing w wouldn't make any difference in this case. 😇

Works like a charm

Thanks.

@mitu
Ah, got it. I thought my method might be out of date but I'm new to digging this deep, and it's a frustrating but fun learning process. Thank you a ton for the help, I'll check that out once I get the chance today.

@norbit911 Why do it backwards ? You can start the Desktop from EmulationStation, so leave EmulationStation running by default. If you wish to run the desktop also when exiting EmulationStation, modify the autostart.sh file and run the desktop startup command after the emulationstation line.

@Kaydron said in Emulation game-start scripts folder:

I will be reading into shell scripting a bit more to hopefully eliminate questions here relating to shell scripts. If anyone has a couple sites that would be good reference paste them here.

The canonical reference is https://tldp.org/LDP/abs/html/, highly recommended for anyone starting or learning Bash scripting.

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

@bluestang
Great, glad it's working.
I removed the vc4 workaround stuff since it's not needed, and changed the init_delay to use seconds rather than milliseconds, since it's totally more useful with seconds (if people use video splashscreens).

The installer script was also updated to have a brand new file/directory selector for the initial song and music directory options, making them actually usable without having to pull out the keyboard.

Also fixed an issue with spaces in file paths and fixed some smaller niggling things (stopping used to spit out "Terminated blah blah...").

The only thing I'm planning at the moment is to maybe dynamically come up with some nice volume step values based off of fade_duration and max_volume to make just that little more "user-friendly" and remove that config option.

@VaultDweller did you look at the booklet that came with the case? If you lost yours I remember another post around here with the instructions, if I can find it...

Thanks. As soon as I posted here, I found this topic and with a bit of modification I was able to get it working. :)

@dthgti said in Launch script with Joystick:

but, how do i autostart that on every boot?

triggerhappy runs as a service when your system starts. Unless you've disabled it, it should read the configuration file and do the actions configured.

@Asmodeus04 I'm going to drop this for now. unless you you are using a CRT, the 120 hertz mode is not worth messing with. It's too choppy.

@joesnow81 well you have the sources, the wiki/docs and the helpful guys in this forum. A comfortable start position I would say.

And for another piece of learning:
This is the beauty of git, you don't have to wait for a fork or merge into master.
See my notes here on how to try the PR by yourself.

@malingjc check content of your rc.local please. Can you post content of this file to pastebin.com please?

Thanks a lot, i solved it!!!

@ratedrguy said in Error running any script including RetroPie-Setup:

Module /home/pi/RetroPie-Setup/scriptmodules/ports/openbor-6xxx.sh is missing valid rp_module_desc

It looks like you created this file incorrectly - this file is not part of RetroPie - attempting to install another version of openbor. Deleting the file would have fixed the problem.