@mitu Just wanted to say thanks for the help on this, it really means a lot. After losing some heart, I took another look over Christmas and the reset you suggested solved my joystick problem as well, so I've had a blast over the break playing on it.
Next stage is to go back into the retroarch.cfg and configure the second joystick when friends are around, and then it'll be good to go.
Thanks so much! And apols for not getting back sooner for your help :)

I see, thanks for trying

@sugarfree THANK YOU!
this is solved

never would have thought updating the retro-pie set up script was how I lost the external drive loading.
i got busy for a few days, was wondering what to do, this am I was able to get on the forum, seen others having same issue after the update of set up script, then remembered "I did that too!" I seen it's been fixed and re did the update, now i have the drive loading again.

thanks for taking the time and adding this info!
also thanks to all others who commented advice

SOLVED!!

I am not sure what to suggest, a Pi4 with 2GB would have been my answer in pre Pi5 times... and still, the Pi4 runs an official image, but the pi5 ain't such a newcomer nowadays and the official image is still based on (IIRC) buster and since then, even before the Pi5 was released, the discussions where about when there will be a "bullseye" image and whether it will be 64bit/32bit or still in support of 32bit ... sigh...

So the official image is missing debian 11, the 64 vs. and or 32 bit problematic still unsolved and now with the pi5 we are over the edge to 64bit and on bookworm as the current debian/raspi OS base...

I would say, it depends... if you want to play straight ahead and use the existing image, go for a pi4 with whatever mem you may need to reuse it after upgrading retropie to a newer device (for retropie on a RP4 2GB is IMHO more then enough, if you want to use it as a terraria or minecraft server afterwards, at least 4GB better 8 would be the way to go).

But if you are totally new to raspis and retropie... well, bad timing, if you simply can afford it, go for the above mentioned route of the pi4 and learn some *nix basics ... but be assured that all you learn for the nowadays official buster based image is void for the next official one, because too much on the underlying OS was changed (just to add a match of buzzword: config.txt vs. cmdline.txt) - if you are willing to experiment and learn on raspberry pi/*nix in general in the meantime, go for a pi5 with the memory you can afford!

@Lolonois said in Adding console Vircon32 to RetroPie:

Other than that I think your virtual console fits in well into Raspberry Pi and RetroPie universe as it allows everyone learning by inspecting and adapting the code.

That was my intention. The console is designed to be very simple and it is fully documented. All my programs and games are open source too. (And games are free, so no problem to distribute the roms).

About the Pi versions, this core has only been tested from Pi 3. I don't think the Pi 1 is powerful enough to run Vircon32. And I have no idea about the Pi 2.

My core builds for Pi 4 have always been done with flag -DENABLE_OPENGLES3=1, so that is what the binary at GitHub release v1.3 should be. In fact, if you try to build the core without GLES3 it will succeed, but it won't run (in my system at least). With GLES3 it does run the games.

EDIT: Still, if you need me to generate some other binaries from the Pi's I have (3 and 4), I will try to do it.

I swapped over to Hypseus, and was able to get everything running (tested on Dragon's Lair). Thank you again for the suggestion!

I have done exactly that myself because for some reason I couldn't get retropie to run on top the Lite OS. Long story short, I like it. You can set boot order to run Retropie first and you got a desktop environment as a bonus when you exit RP. I have yet to find any disadvantages to that... Space efficiency maybe, if you have a smaller SD card?

@mitu I would like to thank you for all your help it was helpful more than you know I appreciate what you mods do for free and how much time you spend helping people like me out. Thanks again Mitu

If you're wondering what I did all I did was format the SD card and start from scratch so anyone who buys the Raspberry Pi 5 Canakit please format your SD card first and then follow the guide I used and not the Os that is provided on the SD card.

You may also try the scriptmodules I put together a while ago, but do still work fine. These make ScummVM game setup and switching between ScummVM and the lr-scummvm a breeze.

https://retropie.org.uk/forum/post/275199

With that branch you just have to have a file structure like this in the ~/RetroPie/roms/scummvm/ folder:

... ├── Monkey-Island-1 The-Secret-of-Monkey-Island/ ├── Monkey-Island-1 The-Secret-of-Monkey-Island.svm ├── Monkey-Island-2 LeChucks-Revenge/ ├── Monkey-Island-2 LeChucks-Revenge.svm ...

The actual folder name and .svm filename do not matter per game, they just need to be matching per game like above. The *.svm can also be empty initially, the game id will be filled in by my scripts. Just put the required game files into the respective game folder as per ScummVM wiki.

Start a game with the native ScummVM once, then you may switch at the second launch to the libretro ScummVM in the runcommand menu. And switch back and forth. That's it, that's all. :)

@Gnatrgaming Ps1 games must be unzipped otherwise, they will not appear in EmulationStation menu.

@Retrodade What kind of Repository do you use for "retropie-extra", this ?
I think this works fine (but I haven't tested yet Philips CDI games):
https://github.com/Exarkuniv/RetroPie-Extra

But I tested it with many other emulators like:
"AetherSX2 - PS2 Emulators" runs in 60Fps with my Pi5.
"Sega Supermodel 3" runs very well with my Pi5.

Start a PSX game with verbose logging enabled and post the log file here using pastebin .

Are you playing it under NTSC or PAL settings? If the former, maybe try under PAL.

@YFZdude Yea, I entered kiosk mode on accident and it wasn’t reverting when I was setting it back to full.