I had issues with Pi4 wifi too. In my case I was noticing it when sending files over Samba from W10 or using FTP, and also scraping problems. I'd get constant disconnects and transfer speeds of around 200kb/s even when it would stay working. I found mentions online of known issues where noise from the HDMI output can disrupt the wifi signal. Every instance I saw talked about said it was only over a certain resolution (1440 I think), but I decided to try disconnecting my 5" screen anyway, which runs 800x480, and as soon as I did that the speeds went up to around 3-5MB/s and the connection stays stable.

I removed the Windows features for old SMB, rebooted, tried mapping with IP and it worked. Thanks!

@Clyde said in Storing ROMs and other data on a remote drive: You can set it in the file /home/pi/.emulationstation/es_settings.cfg via the line <bool name="ParseGamelistOnly" value="true" />. Finally got around to try that out. I didn't notice any real difference in starting time. It spends 80%-ish of the EmulationStation load screen with "Loading system config". The total time from console to be in the UI is ~1 minute regardless if ParseGamelistOnly is set to true or false. It might be my setup, because there's no es_settings.cfg file available so I had to create it myself: <?xml version="1.0"?> <bool name="ParseGamelistOnly" value="true" />

@mitu edit. I had a / rather than a comma. No error.. That it working now 👍

OK, works when i mount with option uid=1000 in autofs.network. Thanks for the hint.

@henryjfry said in Certain systems dont work from NFS share: Would adding async to my fstab improve things do you think? The async option would be ok, but I don't know if it would solve anything. You can just try different mount options - the less mount options you have, the easier it would be to test different combinations.

Ok, thanks. I found a script to cleanup gamelist.xml files in emulationstation. I think I'll give it a go. Thanks for your help!

@mitu great!, thank you so much (another time 😊) Mitu! I searched the Internet before asking here, but did not find such an answer that really explains it. Thx Sir and have a nice sunday evening!

You can get a set of verified mount options from the docs. Try it - in your /etc/fstab file - and see if work with those options.

Yeah, the \\IP-ADDRESS-HERE\McArcade\RetroPie\ROMs\Nintendo\Super Nintendo Entertainment System UNC style paths are Windows specific, they won't work on Linux. Glad you got it working, happy gaming !

Today I tried again with a new reflashed image on my pi zero w, I just added Wifi and autostart.sh entry and it worked fine. Guess I will just start over with my pi 3 to get the actual system running from network. Thank you for your support

@2fst4u You can use the fstab to mount server shares on availability as well but I have never done this. Nor have I learned about layering filesystems. the ubuntu fstab help page, example //server/share /media/samba cifs user=user,uid=1000,gid=100 0 0

@mitu Yes I can access the share no problem if I mount it manually with the pi user. It's just not mounting at boot. I'll have a check of mount later as I'm out all day. Thanks Rob

I verified its loading roms from my shared drive, thanks so much for the help!

Are you running the most recent version of Windows 10? They removed all the homegroup stuff back in the spring. Smart move on their part since it would also cause issues with non windows shares.

Sorry for my late reply. Unison and rclone are programs to sync local or remote directories. Both are available in the official software repositories of Debian and thus, also in Retropie. Both can be used over an ssh connection, see Transferring ROMs how to enable ssh on Retropie. You can install them easily with these commands: sudo apt install unison sudo apt install rclone Further reading: Unison Manual: Remote Usage Rclone Docs: SFTP Finally, @jandalf81 has made a Setup script to sync saves to cloud services. Maybe it can be modified for your needs.

The ports folder was missing so I copied it from my USB to my network location and now I can start Kodi again

:D means the double click on a file doesn't open the associated program... ;) Well, that sounds logical. I edited the smb.conf and it works perfectly. Thanks so much!!!