@Arcuza I don't think that's quite correct. The SD card will have a few partitions on it already. 1 of them is readable by windows, the others are not. The Boot partition should be readable by windows.

@StonedEdge hi there
can you share the arm64 binary to test?

@txutxifel @windg Pi4 Bookworm 64bit Lite I could not install Kodi from RetroPie-Setup.
I ended up just installing v20.2 manually.

sudo apt-get install kodi kodi-peripheral-joystick kodi-inputstream-adaptive kodi-vfs-libarchive kodi-vfs-sftp #kodi-vfs-nfs

When you say menu things, do you mean access into the RetroArch menu when missing an X or Y button?

You can remap the controllers configs inside /opt/RetroPie/configs/all/ (think it's called joysticks or joypads) then edit the lines like "input_toggle_menu" to the a or b button so you can access that?

Assuming you only have a couple of controllers doing it once or twice would solve that. If you are mapping loads on emulationstation you could change the RetroArch.sh mapping file so when you map something in emulationstation it maps your chosen button to those hotkeys. For example button b being a reset hotkey, for button mashers that's a nightmare for me so I usually get rid of that mapping for the entire emulationstation -> Retroarch.sh mapping file.

@mitu Ah, looks like that was it, ta. Worked fine this morning. Weird that it only affected FBNeo.

When I tried to open the runcommand.log, it didn't exist. Could it be by another name?

No, there's only one name and location - as in my previous post. Note that /dev/shm is memory backed, so if you rebooted the Pi, the contents are gone. You need to open the log file just after you launched a game (and it failed) in order to see the exact error after the launch.

@arcadelover15 There wasn't a whole lot to it. The box itself is designed to be used as a controller if you want, so it was just a matter of hooking up BOTH usb cables to the Pi. (Each cable is one side of the control panel.) I think the setup tweak I used initially might be no longer needed in current versions of RetroPi.

Here is a thread I gave my info in:
https://retropie.org.uk/forum/topic/30623/pandora-box-used-as-game-pad

Check /dev/shm/runcommand.log for any errors, maybe there's a hint for why the game doesn't start.

@Striderx99 If you tried the file from both the atomic and megaton edition and the same outcome. Then it's eduke.

You can go on eduke GitHub and see what they say. Can't say they will do anything or not

@dankcushions Thank you so much for the support. I thought it must be a video problem but if it is emulating like this (the way it is supposed to be) then it is no problem. I am pretty sure Mario Kart 64 was intended for CRTs as well so that is why there are those lines. I also run PSX and N64 at a low res so that they perform well. I will probably dump some PSX Bios and configure some settings so that I get access to all the benefits of the system.

Once again thank you to everyone's support.

@Lord-Vek said in Trying to run Commodore plus/4:

What it would do if I wasn't the owner?

per the previous post:

Do check if /opt/retropie/configs/cplus4/ is owned by user pi (ls -l on that folder), else do as root: chown pi: cplus4.

@sleve_mcdichael that's been my thought all along.
I could be wrong but I think the 64bit version has different audio drivers then buster 10. And since StarCraft is a compiled program made specifically for buster so the chance of something not working is there

@retropieuser555 that's absolutely brilliant - thank you so much!

It appears that the original installation was done in Linux for some reason, so at least this way I can have a fiddle around and try to learn how it all works :)

Thanks once again - I'll get right on it.

@Icarium81
After a few hours this morning, I plugged in a keyboard via USB, and was able to navigate VERY VERY MINIMALLY, literally "emulationstation" and then made it so retropie auto boots without needing a command to do so.
I was able to get the retropie to recognize that there was a controller connected, by going into it's settings and connecting it via Bluetooth. (This was done by going in to retropie settings and that dumped me to a bios looking screen [not sure what that's called in Linux terms] and to have that connected there.
However this did not allow me to set it up in retropie (go figure).
All it does is recognize that there's a controller connected, nothing more. Can't configure anything though, it doesn't go past "hold a button to set up"
I've loaded roms on to the micro SD card, ONLY in a directory "snes".
Done similar to a USB stick, 4gb, in to both the main drive (no folder) as well as into a folder for each game AND also in a folder labeled "roms". Again in this roms folder I've loaded all 20 ish roms directly into the folder as well as in to sub folders with each games name.
NONE of the above worked to have the PI even notice that they were there.

So please assist me, the "progress" was made with a YouTube video. Certainly didn't have any epiphanies overnight lol

@cdaters You mean I can use png files also? And the naming, system.png instead of system.svg?

@oskeeeddie said in Can't change emulator:

This is what shows up.

That's after the RetroArch has started up and - as I said - you can disable the notification by modifying the configuration file.

It worked! I have to let you all know that when I tried with doom.wad and doom1.wad (as an IWAD), it loaded normally, but I knew there was an issue once I saw the pointer icon showed up as rabbit ears. It also produced the sounds from both Doom and Ultimate Doom as a result. The screen also showed stairs from each of those games and wall designs from Chex Quest 2. Once I switched the IWAD to CHEX, the pointer changed to a Chex icon. The walls appeared normal (with the regular Chex Quest 2 designs), so I'm going to guess that I did what was necessary to get Chex Quest 2 running correctly. Thanks for all of your help.