Hello and thanks for the answer again. Every emulator, even if I enter Retroarch to move between commands I have to use the controller 2 instead of 1. Image the last one, 4.4 and about the retropie version don't know what you mean, I have updated the script but don't know about the version, how do I see it? Sorry and thanks again.

I managed to get it working. I uninstalled amiberry, cleared the /opt/retropie/configs/amiga/amiberry folder. Reinstalled from sources, recopied various bios roms and ended up with this rom working:

kick40068.A1200 -> /opt/retropie/emulators/amiberry/kickstarts/Kickstart - 391773-01 (USA, Europe) (v3.1 Rev 40.068) (A1200).rom

I also ensured 755 permissions on the kickstart roms - they were 744 before. Not sure which of these steps actually fixed the issue though.

@ivankahl What image are you installing? How did you install it? This matters because nobody can second guess a third party and the current image is 4.4 - you say 4.1?? Only the official image is supported. Second, you cannot use a charger to reliably power a raspberry pi, especially that one as you need a minimum of 2.5A at 5V. Finally, which SNES emulator are you using, there are 7!?

Thank you very much, your suggestion was right. Without the nespi case everything works fine. Thank you so much. Now I have to solve another problem that I don't have in my cabinet. Don't know why the controllers swap themselves after some reboot. I don't touch anything, simply turn off, turn on and magically pad 1 becomes 2 and 2 becomes 1..... howhever, don't wanna go out of post, I'll post it in another one. Thank you again.

One clarification: I did not compile from command line, I just used the package manager of the script. From the command line I used the script module install command just for recovering the situation without having to recompile again (that takes 4 hours)

Guys, give a try to the lr-scummvm libretro-based core for ScummVM I put for testing here: https://retropie.org.uk/forum/topic/19693/lr-scummvm-request-for-comments-and-testing/

You can do mappings via RetroArch and customise for each game too easily with RA. Also you can use any RA-supported shader. So far it has been working nice for me, would appreciate feedback from other ScummVM players.

Please give more details about your installation - https://retropie.org.uk/forum/topic/3/read-this-first. Please note that we don't support 3rd party images.

Ahhh shoot. Thanks both.

Out of interest, is there any way to set the Logitech as the 'primary' controller - so that when I plug in the RetroFlag one the Logitech continues to be the one that can access the RGUI menu?

@JeZxLee said in Running RetroPie From Raspbian Stretch & Encrypted ROM USB Flash?:

Is the above supported?

Yes, it's supported - you just can't run the RetroPie from the desktop, that's all.

First of all, thanks for all the great work on RetroPie. I'm really looking forward to getting it up and running on my very first Raspberry Pi (3B+), but unfortunately I've hit many problems.

@BuZz said in Unable to work on 256Gb sd from scratch:

Note that the system will run a bit slower on the first boot while the filesystem is expanded to fit - it can take a little while on a larger card. Check /var/log/syslog for progress.

This was the cause of the mysterious filesystem corruption I kept encountering during my first 3-4 times trying to set up RetroPie. It runs asynchronously (so basically unknown to any first-time user), and it can slow the system down to the point of seeming unresponsive/hung, which makes the user more likely to interrupt it by hard power-cycling. And it takes a long time on larger microSD cards (mine is 256GB, and it took at least 20 minutes). This really needs to be called out in the "first install" instructions so that first-time users won't accidentally interrupt a critical process that they didn't even realize was happening.

And ideally, this would lead to a UX improvement in a future RetroPie release: on first boot, while the expansion is happening, the system should put up some modal UI to explain that an expansion is being performed, display some kind of busy/progress indicator while it's happening, and then wait for the expansion to complete successfully before loading up EmulationStation.

@Clyde thank you for your reply.
And i do unterstand the point that lr-mame of course is much easier to handle with the preset retroarch-configurations.
As i mentioned my first touch with MAME was back in 1997, so i am used to edit Mame by the infamous TAB-Menue, so it is not new to me or even an disadvantage.
In fact i remap the input for a lot of games, using the Shoulder-Buttons for Pinballs or Gear-Shifting in Racing-games and so on, so i dont need the retroarch presets.
Of course i could remap them also per-game in Retroarch but imo this is more complex.
But as you said: everyone has got his favs and so shall it be.
In the end what counts is that MAME is awesome and works great on a Pi. Nethertheless which Version you use 😊
Kind regards!

I have the same issue. Some PCSX2 team members have made a request about exiting from a gamepad buttons, while some others say "this is not a priority for the project" :
https://github.com/PCSX2/pcsx2/issues/2364

I find it ridiculous, but... well, this is how some people think

@mitu thank you

That's easy - download the image from retropie.org.uk/download and install it. We don't support 3rd party images - like the one you seem to have installed.

@mitu Nope, I'm using the dev build on my Pi as well. And the other two setups on my PC, which worked, used the same build. I assume it has something to do with my es_systems.cfg and/or the way I've set up the dummy files. Maybe I see if I can rework the setup but like I said, I currently don't care.

@moonston333 As far as I know the custom collections don't even exist in the original Emulationstation. Use the RetroPie version which has this feature added.

@RetroFreak89 One way to make sure that the extra space really doesn't contain any data is to shrink the second partition on the original sd card by 1 GB. But since this partition contains a Linux file system, you need a Linux partitioner like GParted for that (or a Windows partitioner that can shrink Linux partitions with the file system ext4 on them, if such a tool exists).

If you're not using Linux anyway, you could use the GParted Live image that boots from a CD or a USB medium into a graphical Linux system with GParted pre-installed.

After shrinking the second partition on your card, you would make a new image that has guaranteed no data in its last 1 GB and should be safe to write to your new card. After confirming that the new card works and has all the data on it, you could then grow its second partition with GParted to the maximum size of the new card.