Found it. Forgot to trust the controller in bluetoothctl:

[bluetooth]# trust 1C:96:5A:53:C1:C3 [CHG] Device 1C:96:5A:53:C1:C3 Trusted: yes Changing 1C:96:5A:53:C1:C3 trust succeeded [CHG] Device 1C:96:5A:53:C1:C3 Connected: yes

It now stays on.

@rykardoo

We don't support third party images here.

the BIOS file seem to be automatically added by the install script anyway - you don't have to do anything: https://github.com/RetroPie/RetroPie-Setup/blob/master/scriptmodules/libretrocores/lr-ppsspp.sh#L61

@nibio74, whoever that is, made the change here. I'll revert it, having no means to contact them :/
https://github.com/RetroPie/RetroPie-Setup/wiki/PSP/_compare/b62096615b65075de1355213c380d30cf767fb61...5d7b9b5c9e234664da5b43c706f917a7855ec99c

@dankcushions thanks. Is there a way I can override the launch scripts?

@pcnoob90 try to find .spi file from your game (maybe your game is protect "epsxe").
I have the same problem for FF IX and FF VIII. Add the spi file solve the Black screen for me.

Jyu

@mitu Thanks! I was about ready to download a fresh image just to see if onstart would be there

@Clyde said in External Boot in my image:

@MPlay Thank you for sharing your solution.

you are welcome, my next step is set retropie to stream my game play (if possible in net play mode) in my youtube channel.

thank you and other friends for support.

Ubuntu 18.04 has 5 years of long term support (LTS, i.e. updates) for many of its software packages, whereas 18.10 only has 9 months. See https://www.ubuntu.com/about/release-cycle for more information. The number behind an LTS' version (e.g. 18.04.1) indicates the "point release" or "snapshot", a downloadable installation image which includes any previous updates. An installed Ubuntu LTS becomes the point release via the regular updates.

This may be negligible for a completely local RetroPie. But as soon as it's connected to a network and thus, prone to remote attacks, its system should be updated regularly, and an LTS strongly recommended.

@MaximStroud Have you tried adding the bios files and boot it that way ? Can you provide the log file (/dev/shm/runcommand.log) taken after starting the game ? What other games have you tried running ?

@John_RM_70 Aha! The key was renaming the BIOS file to dragon32.zip! (From d32.zip.) Many many thanks for that. Now I have the Dragon OS screen showing, if I could only figure out why the A key won't work (leaving me only able to type "CLODM") I'd be sorted...

@dudleydes Ha ha :D I'll have a go, but in my entire 18 months of using WinSCP I don't think its comedy search function has ever successfully found ANYTHING.

@Clyde
yes, i purcheased on ebay ;-)

@Aaronero It's not the emulator that's showing the splash images, it's the Runcommand, so there's nothing that the N64 core (or emulator) is doing. Runcommand is using fbi to display the image on the RPI, but it's not doing any scaling by itself, it just tells fbi to try and zoom the image as best it can.
You didn't say anything about your system - as requested by https://retropie.org.uk/forum/topic/3/read-this-first - so you may not even be using the latest RetroPie or there's some other configuration that might interefere with the image splash.

@mitu That seems to have fixed it! I've rebooted a few times and the sound works after each reboot! I really appreciate the help!!!!

@omg209 got it figured out. Had to use key bindings in retroarch. Bind all for player 3 and 4.

Thanks! This solved the issue for me - I had to copy rom.key file together with all the roms as indicated in one of the replies from above thread, then it started to work...

@mitu

Thanks for that. It worked perfectly. It is actually great news that the boxart splash screen is a separate location and separate file. It means I can create a specific "help" splash screen with the boxart and button mappings so that when I start a game it reminds me how to play the game.