The installer looks pretty simple - did it create the retrogame.cfg file in /boot ? Are you running the installer as root (via sudo), as indicated in the instructions ?

Well, you could download the new SDL2 based version and replace the existing one. Since it's better to unpack the archive on the Linux system, you can run from the terminal

wget http://spatula-city.org/~im14u2c/intv/dl/jzintv-20200712-linux-rpi-sdl2.zip sudo mc /opt/retropie/emulators/jzintv

This will download the new version and open up MC with the location of the existing jzintv version on the left pane. On the right pane, browse for the .zip file you downloaded and then just press Enter over the selected file, you'll see the contents of the archive and you'd be able to copy the new jzintv binary over to the left.

Next to mame2003, I can recommend its enhanced fork mame2003-plus and another arcade emulator called Final Burn Neo that is under ongoing development. But beware that every emulator needs its very own romset for the games to work, see Validating, Rebuilding, and Filtering Arcade ROMs.

@wiuenright said in Are you having problems running Roms from SSD Pi4???? + Question:

Whenever I plug into the USB 3.0 it just writes non stop. I don't know what the problem is. Could it be the enclosure??? Is the lack of USB speed going to make a noticeable difference in gaming? Any ideas why this could be happening?

Try looking at the system's messages when you plug in the drive, by running dmesg -w (CTRL+C to interrupt) on the console and see if any errors are displayed.

Make sure you've updated your system (sudo apt update && sudo full-upgrade) to get the latest stable USB firmware and kernel/firmware release.

There's a sticky topic in the RPI forums here for troubleshooting problematic USB3 SSDs, you might want to take a look and see if your enclosure's USB SSD adapter could be one of the models reported with issues.

Oh great, thank you! This is my first real try with using RetroPie so I'm not familiar with some of how it works 😄

The 'Auto Config Buttons' dialog allows selection of single keys for each of the control functions, then, right at the end, it asks for the 'hot key' button. Without a 'hot key' assignment the control buttons work on their own. If you hold a key down for more than 2 seconds while at any selection (including for 'hot key') the dialog will assign 'nul' as the button.

If you don't have very many buttons/inputs then the use of a 'hot key' + 'game button' is the only way to control Retropie. This also is the mode you will have to use if you use genuine console pads which do not have any control buttons, just game action buttons.

If you do have spare buttons/inputs then assign the control functions to unique buttons and set the 'hot key' to nul. This can be done by running the config buttons dialog manually with - 'Settings -> Inputs -> User 1 Binds -> User 1 Bind Default All' or by manually editing the file it creates at '/opt/retropie/configs/all/retroarch.cfg'

I'm also new to this and awaiting the delivery of extra hardware to experiment with how to add an extra Zero Config board that is used exclusively for the control buttons. (Maybe configure it as Player 5? does anyone know how to do this?)

bye for now ...

I remember seeing a fix for 1. in RetroArch's repository, but don't remember seeing 2. There's a similar issue for 2., that was fixed after 1.8.9, but it looks like it happens with the new graphical widgets.

I couldn't find any contact info for them.
I am very sorry, I was just looking for any help.

@MarkGryzwa If your problem is not not related to running the arcade roms included in the Atari Vault game package, then I suggest you open a separate topic and provide the info asked in https://retropie.org.uk/forum/topic/3/read-this-first

Is it really running too fast or is the analog sensitifity just set too high, press tab to check the controls.

It only works when the 'launch harpoon' message appears. Press left on the right analogue stick to trigger it.

@phineascage I have a similar problem. What did you do to get the controller input to work?

@stoogesfan87 here are some steps to get the job done:

Copy the PNG to a directory accessible to the pi user (like ~/RetroPie/ROMs/coco/media/images/ From ES, highlight the folder that you wish to display the image Hit your "Select" button Select "Edit this game's metadata" Select "Image" Type the path where the image is Restart EmulationStation

For number 6, I can't remember if you can use relative paths or even the tilde (~) so probably best to use the full path. So for step 1 above, the path would be:

/home/pi/RetroPie/ROMs/coco/media/images/<your_image>.png

@helloThere poor performance in mupen64plus-next is expected right now, i just wouldn't expect it to crash, so now that's fixed i'm happy :) i would use standalone mupen64plus-gliden64 until we have news on -next.

often youtube and other tutorials are wrong/outdated. please try starting again and following our official instructions: https://retropie.org.uk/docs/First-Installation/