@lostless Yep, the wireless router, PS5, pi, Nintendo Switch and smart TV are all within a couple meters of each other in the living room. Like I said, I didn't experience any issues using the pi upstairs. Thanks for your help here, I never would have considered that to be the issue.

I might just have to go wired when using the pi in the living room as I don't have an option to move the wireless router.

Thanks you I'll give that a try.

Just started working not sure why? Maybe just needed a good reset.

@mitu it's the macintosh folder, and here's the contents:

-rwxrwxrwx 1 pi pi 0 Nov 15 02:31 Desktop -rwxrwxrwx 1 pi pi 209715200 Nov 20 11:22 disk.img drwxrwxrwx 1 pi pi 131072 Nov 19 13:41 .finf -rwxrwxrwx 1 pi pi 1048576 Sep 14 2010 mac.rom drwxrwxrwx 1 pi pi 131072 Nov 19 13:41 .rsrc -rwxrwxrwx 1 pi pi 0 Nov 19 09:18 start.txt

Inside of the .finf directory appears to be a duplicate (symlinks?) of the macintosh directory:

-rwxrwxrwx 1 pi pi 32 Nov 20 11:22 Desktop -rwxrwxrwx 1 pi pi 32 Nov 19 11:38 disk.img -rwxrwxrwx 1 pi pi 32 Nov 19 11:38 mac.rom -rwxrwxrwx 1 pi pi 32 Nov 19 13:41 start.txt

Inside of the .rsrc directory has another Desktop and start.txt file:

-rwxrwxrwx 1 pi pi 321 Nov 18 23:32 Desktop -rwxrwxrwx 1 pi pi 0 Nov 19 13:41 start.txt

I checked the start.txt files and they are both empty, so it must be in the basiliskii.cfg or other config file to dictate which backend it's using, and maybe if I'm lucky... I can manually define my resolution there? And maybe I can clean up the "start" listings and/or rename that? Can you point me somewhere to teach me about the use of start.txt files in RetroPie? I can't seem to find it in the docs.

@WhiteT982

Nice, thank you.

Can you please add the full details about your setup asked in https://retropie.org.uk/forum/topic/3/read-this-first ?

Try running EmulationStation manually from the command line (after it crashes) with

emulationstation --debug

and post the last error shown on the screen when it crashes ? I still suspect there's a connection issue with the controller, the crash is usually indicating a bad connection (controller disconnects immediately after being detected).

@windg insert the roms in the snes folder, the games start....thanks

@sleve_mcdichael Awesome! Thanks so much.

@wec777 Try running sudo apt update && sudo apt upgrade before installing RetroPie again. Your problem looks similar to this issue, which seems to be a timing issue in the update list.
RetroPie doesn't install any repositories, it uses the ones provided by your Linux distribution.

@Darksavior AWESOME DUDe thankyou

@Retro-Arcade-Fan Nevermind. Found the answer. Had to change it to c16 for some reason.

@mitu
Guess I'll just live without packages, thanks man.

Edit:
I got it to work, I managed to install Kodi and steamlink!

You were right it was something with the DNS settings, I changed it to 8.8.8.8 using this guide through terminal and it just immediately worked.

@mitu Well, as always thanks for the help. I don't think it's underpowered given my new 3.5a CanaKit PSU made specifically for the Pi4 and it's a powered USB hub. But I can't rule out an unseated cable or something because now it's back to working correctly. I'm going to keep the USB HDD connected directly to the Pi, since if that isn't seen on boot, then it won't have access to the romsets which explains why they wouldn't show up, and if the USB cable to the hub got jostled then that would also explain why the gamepad wasn't detected.
#OccamsRazor

@dookieshooter I don't have a lot of programming/code experience to help people here, but I do have a fair amount of audio expertise and this is a fairly simple issue to solve. It's called an "audio ground loop" and it's because the audio signal isn't grounded to the same ground as the rest of your components. Perhaps it's plugged into a different outlet or surge protector. The reason your second amp worked is because it probably has a ground loop filter built-in and the first one didn't. The easiest and cheapest way to minimize or get rid of the hum is to buy a Pyle PHE300 or similar device that (depending on the model) either connects to the signal that's going to the speakers or to the audio OUT from the Pi. It intercepts the signal and 'cleans' the hum from it by grounding the signal again.

@mitu I'm not seeing any option for dispmanx in the Configuration/Tools menu. Has that been removed in more recent versions? I'm trying to figure out where to set my BasiliskII settings/configs so that it will open as a scaled (fullscreen) 640x480 (or something else that's less than the 1600x1200 default) so that I can see larger icons and menus. If I set the screen to 640x480 in either the run command options or within the Mac emulation itself, it just uses a portion in the upper left of the screen that's the same scale of icons, etc.
EDIT: For anyone else who's been confused by this, I discovered where to find the dispmanx settings in Configurations/Tools. It's under 197 backendsthen select basilisk to change it to use dispmanx if you want to.

@mediamogul I've been seeing this on the forum here about this mysterious basilisk config file that needs to be in basilisk but I haven't seen anything in the docs about this. Seems like the docs could use a lot more information about basilisk. Where can I find out how to create and use this config? I have my os 7.5.3 Macintosh img and rom working fine, all I'd like to do now is make it be 640x480 and full screen. If I do anything lower than 1600x1200 in the run command options or within the emulator using the screen settings, it displays in a smaller window in the upper left corner of the display.

Hi,

Did you ever find a solution for this in the end?

Cheers

@sleve_mcdichael Awesome, many thanks! I will not bother with it further, then. Not worth the hassle, I reckon.