@mitu Oh that makes sense then. Thanks a lot for clearing that up. And you're probably right that I should wait for the Pi4 to be officially supported before I begin again :)

It seems to download fine for me. We've had a few complaints over time with similar symptoms, it's usually something ISP related. Try downloading from another location or try a torrent download.

Nevermind I fixed it

@rpf5573 Did you try changing localisation options in sudo raspi-config?

@thelostsoul said in screenscraper.fr site not available anymore?: Does it have any impact on the scraper in RetroPie or any other scraper? Well, it did - at least for the internal ES scraper. For other scrapers, I don't think so, otherwise I image it would have been reported.

@Retrobat please add more info about your system - https://retropie.org.uk/forum/topic/3/read-this-first.

Thanks. I'll keep that in mind.

Yes. This is simply about waiting for the server to not be overloaded if not registered user. I've seen the 'V' now as well as messaging about not being a registered user. Evenings are working best in my particular time zone.

I was testing the controller parsing utility of LEDSpicer when I found that was not working for that emulator on the retropie, so I used a different approach, now is working, I found out that I cannot depend on other programs functionality.

@hostolis yep its gpu_mem=320.

user@host$ diskutil list /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *500.3 GB disk0 1: EFI EFI 209.7 MB disk0s1 https://freeaccountsonline.com/ 2: Apple_CoreStorage Mac HD 499.4 GB disk0s2 3: Apple_Boot Recovery HD 650.0 MB disk0s3 /dev/disk1 (internal, virtual): #: TYPE NAME SIZE IDENTIFIER 0: Apple_HFS Mac HD +499.0 GB disk1 Logical Volume on disk0s2 3BAC0F9E-19F8-4AAB-8752-6514B573B497 Unencrypted /dev/disk2 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: FDisk_partition_scheme *15.9 GB disk2 1: Windows_FAT_16 boot 59.8 MB disk2s1 2: Linux 15.9 GB disk2s2 user@host$

@The16BitGuy Please post the full error message and the step in the installation where you get it. What version of Ubuntu are you using ?

Glad that you got it fixed, but please, in the future: Add all of the information that is requested in the link @mitu gave you. It helps potential helpers to help you. You only added part of it in your first post. edit: It's better to post a new post to add the information, so that anyone following this thread will be noticed automatically. New posts trigger forum notifications, editing posts does not. (I only noticed the added information after I wrote the first version of my reply.) If you got it fixed by yourself, it would be nice to tell us how exactly you fixed it, so that others with the same problem can find a possible solution here. Edit your first post and add [Solved] before the title, so that it's clear that this thread is solved. Thanks, have fun with Retropie.

The PR was merged, so it's safe to go back to the master branch if you were testing. Don't forget to updateruncommandafter returning to the master branch (which is done automatically when you use the Update RetroPie-Setup script option of the script itself). Thanks to @mitu and everybody else who helped with troubleshooting & testing.

@mitu Well as I said, the Bluetooth functionality was working perfectly when setting up the 8bitdo controller and problems only began when the Pi was restarted. As regards the SD card, it's a 32GB card, branded 'Team' and was bought from a local computer store. To be honest, I've had my doubts about it, so I think I'm going to purchase a 32GB Sandisk Ultra card to replace it. I have also since sourced the official Raspberry Pi 5.1v 2.5A PSU to replace the one sent with my ABOX kit. So between the two new pieces of kit, I'll set up Retropie afresh and see how it goes. Thanks for your patience and help with this issue, it's appreciated.

@Greakon What command are you using to edit the file ?

@rmills55 Post your /boot/config.txt file to check for any overclock settings. and it can see i have about 60gb available. I was referring to the RAM allocated to the system, not the space on the card.

This topic has a lot of good info about migrating to 4.4 on a new image.

@keksninja Pi Model or other hardware: (B, B+, 2 B, 3, X86 PC etc..) Power Supply used: (If using a Pi) RetroPie Version Used (eg 3.6, 3.8.1, 4.1 - do not write latest): Built From: (Pre made SD Image on RetroPie website, Berryboot, or on top of existing OS etc.. - please provide the filename of any image used) USB Devices connected: Controller used: Error messages received: Log found in /dev/shm/runcommand.log (if relevant): Guide used: (Mention if you followed a guide) File: (File with issue - with FULL path) Emulator: (Name of emulator - if applicable) Attachment of config files: (PLEASE USE PASTEBIN.COM FOR LARGE LOGS) How to replicate the problem: Please copy the above and fill in the info. Otherwise we have no idea how to start helping you.