Isn't it cleaner to use systemd / services in order to do so ? It is explained here how to cycle between 2 services: https://forum.kodi.tv/showthread.php?tid=288584 For kodi.service (configured as a user service not system wide service contrary to the above link) : [unit] ... Conflicts = emulstation.service ... [service] ... ExecStopPost = /usr/bin/systemctl --user start emulstation.service ... And for emulstation.service [unit] ... Conflicts = kodi.service ... [service] ... ExecStopPost = /usr/bin/systemctl --user start kodi.service ... Emulstation and kodi should not be services enabled/start by default at boot but rather autostart.sh start the first service by something like: systmctl --user start kodi.service if kodi is configured to be the first one. To go further we can also think about replacing the autostart script by a retropie service which is enabled at boot time. At start, it launches the first configured service. At stop it ensures that emulstation and kodi are stoped. If the service is run as pi user (which is more secure), the pi user must be lingered to enable autostart of the service at boot even if the user is not logged in. loginctl enable-linger pi systemctl --user enable retropie Advantages: All the services could be controlled, inspected, logged through the systemd tools Not need for automatic login It could be easily extended to any number of services not just 2.

The autostart.sh is located in /opt/retropie/configs/all/. It's started from /etc/profile.d.

The question I would ask myself in your place is if I'd rather do without or rewrite my scripts than trying to adapt many unfamiliar scripts that may break again with the next update.

@mitu Meanwhile every second posting is related to this "in da houz" images. Well after a few days of searching files and experimenting on the pi, I think I've got this figured out. What else could I say?

@mitu No problem. I literally just figured it out. I just updated everything, used a different BGM script and in raspi-config, I disabled and enabled the text splash screen, followed by using a custom splashscreen using the OFFICIAL script off emulation station. The custom scripts are trash, absolute trash. I have to be careful. So I have a totally new issue now, non-image related. I used SD Card Formatter to format my Micro SD to exFat, Windows 10 recognizes it....I used Win32 Diskimager to write my image, and now Windows 10 won't recognize it. Any idea how to fix this? I must fix this because I have to create a backup, now that I fixed it. I'd appreciate the help. Thanks.

So apparently I'm an idiot. Following the guide over at Reddit, I missed one thing. I had the mini-hdmi cable plugged into the second port and not to the port closest to the power supply. Looks like everything is working now.

@mitu Thanks a lot, it worked like a charm. I'm about to be done with my arcade cabinet!

@BuZz I removed the #emulationstation #auto line 2 of the autostart.sh, and it worked. I didn't think that line would matter since it doesn't effect mame2003 roms launched the same way. Why does multi lines cause this issue? Is there a way to include multiple lines?

Copied my tron.ini file to location /opt/retropie/libretrocores/lr-mame2003-plus/metadata.........it didn't work.

@mitu Yes, I did what you said and I succeeded to lower boot time to 11 seconds for libretro emulator but only through autostart.sh. However, non-libretro emulators still starts about 5 seconds faster through the rc.local script and I dont know what else I could do here. It seems runcommand is a problem, because for some reason it refuses to start through rc.local properly...

You gem. Cheers all sorted

@pyr0cide Just leave the exports on the server /volume1/roms 192.168.1.*(rw,async,no_wdelay,no_root_squash) And make sure you use the proper case when referring to the share name, i.e. not mixing upper-case with lower-case mount -t nfs -o vers=3 192.168.1.6:/volume1/roms /home/pi/RetroPie/roms

I was going to backup after I had sorted a couple of other things. I never messed about with autobash I don't even know what it does. Unless I have accidently done something while in settings.