Ok, so having spent quite a bit of time on this, I would have to downgrade my assessment to semi-successful - ha! I ended up having to install alot of emulators that I thought would still be on there as they were on my old build, and nearly all the other emulators had binary updates for me to run.

My RetroPie build is very basic really, with the only tweaks being those detailed in the official docs, so looking back I think if I was to do this process again, I would just start completely clean and go through each system one by one to check all is working correctly and updating/tweaking as appropriate. At least then I would know what needed to be done, rather than finding some things had copied over and other bits hadn't. This is most definitely due to errors on my part I'm sure.

On the plus side, on my 4.4 build my Sega CD and ZX Spectrum games wouldn't work (Sega CD would jump back to ES, and ZX Spectrum would crash the Pi) but now they do, so not sure what happened there but it's all good now - ha!

Please add some more info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

You shouldn't have removed rfkill, I suggest you reinstall it. What's the output of the following commands:

rfkill list all iwconfig

Another method to configure the Wi-Fi is to create a complete wpa_supplicant.conf cofiguration file, including the country, as explained here.

@grand_national to exit Atari 800 standalone emulator you have to use the keyboard (F9). F1 enters the configuration. Only retroarch emulators and a couple of standalone emulators like amiberry and mupen64 support exiting with the select+start combination. But the standalone Atari 800 emulator is a lot more functional than the libretro core.

@mitu. Hi, at first the omxplayer was on, as the tutorial suggested and then after reading a long winded forum about this issue, one of the things was to turn it off. So I did but still had stay issue.
I thought it could have been a bad skyscraper install, so I also uninstalled that but same issue.
So I left it a while to register on here and it wrack my brain around it.
Then, even though I did a script update and I knew I had the latest retropie installed cos I'd only just done it from the site a couple of days ago. I decided to do it again, the script took no time at all, the main update this time took 2 hours. I rebooted and for some reason it all works fine now, no freezing. So I put the omxplayer back on and it's still fine. Haven't yet re installed skyscraper but I don't know if it now works because of that or a second update after the preview videos where on.
Either way it works now.
Thanks for commenting anyway.

@buzz I've tried this before, but I've tried again just now, to make sure.

overscan_top=40 overscan_bottom=40 overscan_left=40 overscan_right=40 overscan_scale=0

While this does add the overscan on the console, it also adds it to EmulationStation and RetroArch while emulating.

Using Retropie on a Raspberry Pi

PSP games in .pbp format will work fine in ppsspp and lr-ppsspp

PSX games in .pbp format will work fine using lr-pcsx_rearmed

@lochnagar I know the music on Tomba II is glitchy and plays the wrong track on the default (and only emulator if on a pi) psx emulator. It’s old and buggy and hasn’t really been updated with any significance in a long time. But it runs very smoothly on low end hardware and runs most games just fine. There is no fix unless someone updates the emulator to fix said bugs.

@dunginhawk

I love your Iowa Hawkeye artwork. Would you be willing to sell or share it? I am building my own home arcade.

Thank you-
Matt
[link text](link url)

Does anyone know if the alternative Setup script from this repository https://github.com/valerino/RetroPie-Setup will help ?

Thanks for any help.

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

Please provide more information as detailed in link.

@buzz

Omg thank you so much. I have 2 Nes30 and 2 Nes30 Pro and the last freaking controller wouldnt match with my raspberry for several hours now.. it literally was the distance. I didnt come up with this idea, because all other 3, even the other nes30 pro, worked perfectly from far away. I put it right on the raspberry and it worked instant.
Maybe there are several version with different antenna or sthg?

Again: thanks, im a little mad about this garbage, but also happy it works now.

@mitu ye theres a boot drive on the sd card

@dankcushions yeah that theory makes sense. Good enough for me. Lol.

Is there an Apple emulation specialist here ?

@mitu said in Trouble with RetroPie after updating from Stretch to Buster:

@keks24 said in Trouble with RetroPie after updating from Stretch to Buster:

Could you elaborate this and provide some references, please?

I think every new Raspberry Pi OS (was Raspbian once) mentions this in their release notes. For instance, for the Buster release:

We do not recommend upgrading an existing Stretch (or earlier) system to Buster – we can’t know what changes everyone has made to their system, and so have no idea what may break when you move to Buster. However, we have tested the following procedure for upgrading, and it works on a clean version of the last Stretch image we released. That does not guarantee it will work on your system, and we cannot provide support (or be held responsible) for any problems that arise if you try it.

Ah, thank you for the link!

In my opinion, they are making it a little bit easy on themselves here, but I guess, that they do not want to let the (normal) user go through the entire partitioning resizing process of /boot/ here.

They also increased the partition of their official images, due to the large kernel files of Debian Buster:

$ fdisk --list * | grep "Device\|img1" | column -t Device Boot Start End Sectors Size Id Type 2020-12-02-raspios-buster-armhf-full.img1 8192 532479 524288 256M c W95 FAT32 (LBA) Device Boot Start End Sectors Size Id Type 2020-12-02-raspios-buster-armhf.img1 8192 532479 524288 256M c W95 FAT32 (LBA) Device Boot Start End Sectors Size Id Type 2020-12-02-raspios-buster-armhf-lite.img1 8192 532479 524288 256M c W95 FAT32 (LBA) (retropie) $ df --human-readable /boot Filesystem Size Used Avail Use% Mounted on /dev/mmcblk0p1 512M 47M 466M 10% /boot

@riverstorm said in MAME 2003 PLUS not letting me use Joystick:

456 123

From mame2003+ official documentation :
The recommended 6-buttons layout for mame2003+ should be this one :
this one
With device type set to 6-Button in Quick Menu > Controls

It should also match the layout FBNeo is expecting by default (when device type is set to Classic)

@alphabetapie you can see the supported MAME versions on same page: https://retropie.org.uk/docs/MAME

note .226 is current MAME or thereabouts. current MAME will perform badly on pi systems right now.

Run emulationstation --debug from a terminal window and post the output. My guess is that there's no HW accelerated GL support, but the log output would help confirming the assumption.

@peldiego7111 i used the lr-ppsspp but since your issue was the files were .zip that makes sense too. glad you got it figured out.

So I figured it out.

I should have set Retroarch.cfg to rotate 270 degrees.

I feel silly, but thanks in advance.