@Unknown To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first

Looks to me you're using an Enterprise edition of Win 10, which doesn't allow - by default - connection using the guest account to file shares. You may try using WinSCP to connect to your Pi and copy your ROM/BIOS files over.

@mitu said in RetroPie Setup no Longer Working After Failed Update.: The error message is quite clear - have you tried running the commands recommended ? I honestly didn't even notice that until after you pointed it out lmao. Thank you, it worked!

I was seeing the same and it was the errors being thrown by the audio issues introduced with Raspbian Buster: https://retropie.org.uk/forum/topic/26628/audio-issues-after-latest-raspbian-updates

This looks promising. Thank you. I will try this. I could be wrong, but this looks like it's specific to RetroPie on a rasberry pi. Does anyone know if this works on RetroPie X86 and how to install it on that platform?

@thiagodophp said in does not open is on a black screen: Hello good night, could you help me I'm new and I don't understand the forum, I have this problem There's no need to re-post the same information twice or post in other topics to get my attention. Please read https://retropie.org.uk/forum/topic/3/read-this-first and provide the information asked there, as much as you can - this will help us understand what's wrong with your setup.

@mitu yes definitely all working now Just can’t get any controls to work apart from a plugged in keyboard!?

@ChaosFox or like @mitu says, install Ubuntu and then Retropie...

@akamming said in RetroPie setup reverting cmake to 3.13: i noticed however that when i run the Update command from the RetroPie setup script, cmake is reverted to 3.13 again. Apparently it does not detect that a higher version is already installed, cause i also noticed that cmake and cmake-data are installed again as raspbian packages. It does not detect it, because it's not installed from a .deb package. RetroPie installs the cmake package that's available in the distro - whatever version is available in the Raspbian repositories. As a general rule when installing from source - in order to not get your installation overwritten by a distro package, don't install into the system directories (/usr/bin, /usr/sbin, etc.) - use /usr/local or /opt.

@mitu Thanks, but I had to re image the sd card and now everything is back to normal, just can't see my retropie in my network

@ratedrguy said in Error running any script including RetroPie-Setup: Module /home/pi/RetroPie-Setup/scriptmodules/ports/openbor-6xxx.sh is missing valid rp_module_desc It looks like you created this file incorrectly - this file is not part of RetroPie - attempting to install another version of openbor. Deleting the file would have fixed the problem.

Oh, yeah, forgot it's using $md_inst for user data.

We don't support 3rd party images or systems bought with RetroPie - https://retropie.org.uk/forum/topic/3/read-this-first. Selling RetroPie is against the project's license. If you'd like to use RetroPie, get one of the images from retropie.org.uk/download and then follow the installation instructions from the Docs to use it.

Neat!

Try adding the / before the relative path, so it becomes <image>/home/pi/RetroPie/boxart/nes/3-D WorldRunner (USA)-image.jpg</image>

You can check using the jstest utility if the buttons are registering correctly in Linux, outside or RetroPie. Attach a keyboard and exit Emulationstation (F4), then run from the command line: jstest /dev/input/js0 It will show you the gamepad buttons/joysticks and you can press them one by one to see if the input values change on the screen. You can exit the test by pressing Ctrl + C. If there is no reaction when pressing a button, either the wiring is faulty or the controller. You can also try connecting the encoder to a PC and test it there also.

https://retropie.org.uk/docs/Transferring-Roms/#samba-shares

@mitu Thank You! I realize it is not supported but there is usually a way!

Thanks! I think I'll probably go the imaging route then. Any suggestions on a good imaging tool? Or do the same tools we use to write images, such as Win32 Disk Imager or balenaEtcher, create them as well?