@leanne No problem. The unallocated space will actually be expanded on first boot of Retropie and brought into use. The image you download is compressed you see, so that there is not wasted empty space in it.

@jamrom2 said in Issues with Mausberry shutdown script.:

Have a safe and prosperous New Year!

Glad you sorted it out and thank you for the nice words - Happy New Year to you too !

I recommend you post your splash screen here:

https://retropie.org.uk/forum/topic/29132/splash-screen-ideas-discussion

@mitu
ok I did it so as not to be repetitive

@zera said in Display Problem with CM4 Board:

We combine CM4 and the DPI display, however, we cannot enter the emulator and it only stuck in booting. It can work normally if we change to an HDMI display.

This seems like a problem with the DPI configuration/driver. Does Raspbian Lite works normally with the configuration - does it boot to a text console/terminal ? What emulator are you starting ? By default, RetroPie boots to EmulationStation, not to an emulator.

There is also a solution that we install retropie in Raspbian image, however, it also has a problem. It will flash the desktop of Raspbian when starting, begin the game, or exit from the game.

RetroPie is based on Raspbian Lite (not the Full/Desktop), running RetroPie (EmulationStation) under a desktop env on a Pi is not a supported or tested configuration.

@chrisdrackett I reinstalled from source and now have sound again.

That depends on what you mean by finished

if you mean by installed software to get the basics to work, I've already done that like many others have.

But then I've started getting new ideas on what I want to do with my RetroPie on the P4, and now I'm beginning to see why people like making them. One idea that has popped into my head recently is connecting a Retrode 2 to it with some woodwork to make an artificial game console. With a keyboard and mouse trackpad combo glued onto it, it would be a beast of a retro setup which doubles as a basic PC for web browsing and music.

Hello and welcome to this forum.

Can you enter the RetroArch menü? (normally via Hotkey + X) Then it might be this problem with the Multitap settings.

If not, we'll need the information markyh44 asked about.

P.S.: I guess you're German, right? Then just a friendly advice: You can't translate "spinnen" (acting crazy) with "spinning" (drehen). It makes your sentence above sound a little weird. 😉

@mitu ooops, did not know that.
Sorry :/

You should post issues with beta firmware on the Raspberry Pi forums, since you'll get better support there. If you want to get back to a working EEPROM, I suggest you use Raspberry Pi Imager and flash the latest stable EEPROM image.

@mitu said in How to donwngrade PPSSPP to v1.5.4 (solved):

@stumcbill said in How to donwngrade PPSSPP to v1.5.4 (solved):

Ah ok, is there anyway I can reinstall the version that comes with 4.7 to see if it makes a difference?

Since PPSSPP isn't installed on the 4.7 image by default, even if you download the 4.7 image, installing from binary will still get you the current/last version. So, no - you can't reinstall the old version from RetroPie-Setup.

Ah, I never realised that. Sounds like I’m out of luck then.

Thanks

@mitu that make sense .. thanks for the help.

@wsamael I had problems with the SSD in the Nespi 4 but slightly different, I assume though because I use Attract Mode not Emulationstation. Maybe it is the same problem though. Games showed up ok for me, but the romlist is on the SD card so it should. Scrolling through it, so loading media, would be slow then freeze for a decent time before coming back. I followed the guide below and it fixed it for me, maybe it might fix your issue too?

https://www.reddit.com/r/RetroPie/comments/i9f45b/retroflag_nespi_4_ssd_boot_slowness_and_workaround/?utm_source=amp&utm_medium=&utm_content=post_body

@amook11

I had the same problem and with my pi in the network and under

\\retropie\configs\amiga\amiberry\conf\

I opened and edited this file:
rp-a500.uae
it has a line:

kickstart_rom_file

there goes the exact name of your 1.3 rom in the bios folder.
of course you can also rename your existing rom to name that's already there.

same procedure needs to be done for the 3.1 kickstart I 've just noticed..

for people unsure about the correct roms: https://github.com/midwan/amiberry/wiki/Kickstart-ROMs-(BIOS) there you can find information about the versions needed including a crc check code, to see if you've got the right file.

The reason that Retropie isn't visible in the Win10 Network folder is due to the fact that netbios discovery isn't supported by windows anymore.
But it is possible to make samba shares again visible by the Web Services Dynamic Discovery Method.
I am currently using a little python3 script from Steffen Christgau on my Debian Buster NAS Server which makes WSD available und thus browsing Samba Shares much more conveniant.

https://github.com/christgau/wsdd

@mitu
Might it be possible to make this a standard addon to retropie ?

Just updated a bug in the RetroPie installation script, which did not take into account the move to the new carbon-2021 theme from RetroPie v.4.7.19 and onwards.

Should work now for both newer and older RetroPie versions. Sorry for any inconvenience.

No, the binary packages are not versioned and downgrading is not an option.