@ballboff I tried what you mentioned but nothing shows up but the same 2 options:
0
H hidden ESSID

I honestly don't think its something that simple. I logged in to my router to see if it would even pick up the Pi, unfortunately it's not.
Thanks for your input, I appreciate ALL the help I can get.

I checked in my network to see if the Pi would show up but it does not. Either way I get no wifi regardless on the PiZero W. In regards to the GBA, I forgot how the frame rates were on it lol but it seems to be normal. I will check up on a few more Roms on the SNES when I get back home to confirm if it's only a few games being affected.
Thanks for your input

@gpr17 4.1 is not the latest version, but I've not tested this on OSMC. I will need a complete build log to see the failure. I would recommend you use the last RetroPie image if you wish to use the experimental modules.

Doh! I did read the documentation but overlooked this. I checked it again after your answer and you're right, it's definitively there. Sorry, my bad.

If you have the files, then you could run them under dosbox.
Such as, if you had the files to run I dunno, Jazz Jackrabbit. You could run it on DosBox.

You don't necessarily have to rename all the files. If you use UXS it will scrape all the cover art and also create a gamelist.xml. That XML file should contain the proper meta data for your roms in it, which is what emulation station displays...

Yes..you can expand the filesystem in Raspi Config in the Retropie menu.Then the additional space will be seen and used.

The Problem was located:
When using pbp files with sbi files the extension both must be lower or uppercase.
Having them mixed will result in the emulator not finding the sbi file since linux systems are casesensitve.

multidisc PBP Systax is as described in the sourcecode comment above.

Github issue:
https://github.com/libretro/beetle-psx-libretro/issues/241

haha, you would be suprised, as a kid we enjoyed listening to the music and loking at the splash screen while it loaded, I loaded one game up the other day, and the splash screen actually brought back vivid memories that I had fully forgotten up till that point.

@insidious611 also remember any time you set it up changing the 8-bitdo hack option and sync, you need to re setup your controller in emulationstation so it correctly installs all the controller configs.

I was asking if this ever got resolved, I then stated what I did on 2 different occasions that resulted in NO WIFI on PiZeroW which falls in line with this thread, I don't see what I did wrong in asking if this got fixed.... But I will post a new thread, thanks

@djjujuvi Please click "Docs" above and do a little reading. Trust me--this will help you as much as it helps us. The Pi is a teaching/learning/educational device and we all use slightly different configurations, not to mention, we all have a different idea about what systems we want to run. The more you read the documentation, the easier it will be to provide information, find answers, and ask meaningful questions.

@mitu

Thank you! Your advice was golden! Working with Qtcreator is so much better.

Lr-snes9x is more accurate and uses more resources than lr-snes9x2010. The pi may not be able to keep up with a more accurate emulator. The popping is just the emulation pausing for a split second waiting for the cpu to keep up. To our ears is sounds like a crackle. So even if it’s delaying a frame or 2 which may not be notable to our eyes, our ears can hear the delay. Stay with snes9x2010 as it runs most games fine.

Ahh bummer. Hopefully it finds its way back at some point. Thanks!

i have the same problem with last retropie, copying movies in kodi

@darksavior I understand that, but there is no environment running to support a window in the first place, so the setting is meaningless. Either way, it is still filling the screen. The way I read the description was that it looks stretched.

it's working after reinstallation retropie.

@spud11

Best advice here is to make your troubleshooting as simple as possible. I would recommend "sudo cp autostart.sh autostart.sh.original, and the same with the "onstart" and "onend" files - that way you can climb back down the tree if you get into trouble.

Next, clear out those files and populate them per the instructions; there's just not a chance of it not working then. I'll attach my working ones to this post and you can just drop them in for a test if it will help.