@jimmyfromthebay ,

They are different sizes:

pi@retropie:~/RetroPie/roms/atari5200 $ ls -lhart *Dig* -rw-r--r-- 1 pi pi 16K Jul 13 21:52 'Dig Dug (1983) (Atari).a52' -rw-r--r-- 1 pi pi 17K Jul 13 21:53 'Dig Dug c (1983) (Atari).a52'

@skylo By default, during boot, the native resolution of the screen will be identified, so I don't see any problems.

There are various adapters for classic controllers to USB - Mayflash has one, Raphnet technologies has a good one.

We don't support 3rd party images, as outlined in https://retropie.org.uk/forum/topic/3/read-this-first. So the best image is the one from https://retropie.org.uk/download.

We don't support 3rd party images - as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

@mitu Thanks, that works

@mud2005 Glad you like it too! The newer model is slightly squarer than the older ones and the resolution is a bit different, you might have an even better one.

I think I screwed something up on the pre-made retroie image. Because I re-flashed the pi and set I2C to be loaded through sudo raspi-config, now when I reboot it does detect my I2C. One step closer to my mobile retropie!

Don't use pre-made images, they're terrible. Plus you won't get any support here or anywhere.

Since I like to help anyway, I'll give you a hint: the most likely issue is that the init file is missing, the image is corrupted and you can't do much unless you reinstall over (and completely mess the messed up setup).

Another possibility is that there's an easier fix by running e2fsck on Putty but I hightly recommend to give up and build your own fruity cake :)

@mitu Thanks for the help, without your help I would have been stuck in the kiosk mode

@Thorr69 said in The Neo Geo emulator does not find the bios:

@Rubencn1234 Put it in the same directory as the roms. If you put it in the BIOS directory, it doesn't seem to find it. I had to put it in the roms directory (with the correct name) in order for it to work.

Which emulator are you using? FBA works fine without "neogeo.zip" in the roms folder. I have it just in the BIOS folder.

@Rubencn1234 Check to make sure you have the right BIOS file. neogeo.zip needs to be ~1.5 MB and CRC-32 should be 20F12195

@bagoflaxia said in mpg123 player works fine for BGM, but kills game audio.:

Is there a command I can put in to the mpg123 config to stop this from happening?

There is a topic on how to set this up in RetroPie - https://retropie.org.uk/forum/topic/9133/quick-and-easy-guide-for-adding-music-to-emulatonstation-on-retropie-noob-friendly.

Follow the instructions in the topic and add the commands to stop mpg123 when a game starts by editing the runcommand-onstart.sh script, this should stop the music from playing while the game runs.

@jonnykesh I apologize. I was in a hurry and it kept telling me I needed someone else to

OK, so I've been googling up a storm looking at the options. I think I'm either going to go with a piglow, and use some code folks have already put together. Seems like the three arms can show something like Temp, CPU Load, something else (I can't remember).

But what really looks like it'd be cool is the Displayotron. Seems I could set it up to show the system and ROM running on Retropie. And I figure the backlights could be setup to have a color that'd match the system (like Red for Nintendo or something). And then use the bargraph to show CPU load. But what I'd love to do is use the joystic on the Displayotron as a safe shutdown button. Could I do that? Does it sound at all reasonable?

@ithortureu alternatively you can just use a program like WinSCP to add roms etc.

https://github.com/retropie/retropie-setup/wiki/Transferring-Roms

@mitu @davidgrohl
Thank you guys! Unfortunately I have already ported from scatch

@reeebs said in [Rpi3] NDS touchscreen:

I don’t expect nothing in particular, as the two positions - the real one of my finger and the one of the pointer - are completely wrong: if I move, it moves too, but when I am in a corner it starts from the center and so on

That's very telling behavior and explains why the Dolphinbar wasn't recognized. The touchscreen is apparently being read in this case as a standard relative coordinates mouse. If it were being read as an absolute coordinates pointer device, the cursor would snap to wherever it was you touched at. Needless to say, this limitation combined with the wide area required to receive input really hinders precision.