@avih7531 The Wii emulator (dolphin) is only available for the PC builds, it can't run on a Raspberry Pi.

@mitu said in Removed emulationstation-dev help: @paffley Just install Emulationstation (the regular package) from the core packages section. Thanks @mitu I installed a fresh ES from binary then had to re-add es_systems.cfg content from an old backup I had (modified). All working now thank you! keep up the super work!

@BillyH If you haven't fiddled with the RA's configuration, the save files would stay alonside your ROM files, in the roms sub-folders. Once you access the file shares (\\retropie\roms), you can easily check the contents of those folder and see your save files (most of them have the .srm extension).

@Jareth247 Glad you got it working; I don't think the power switch script had anything to do with it - although the incorrect file that was causing the problem for apt could have been produced by an improper shutdown in the middle of an install operation.

Thank you @mitu You're a star :) Rob

@jareth247 You should open a new topic and provide the latest update log, as described in this topic. And please also add more information about your system - https://retropie.org.uk/forum/topic/3/read-this-first.

This is not implemented, you either update all installed or individually.

@mitu Thank for that info. I did remove the !kms and it build with no errors, but I get this when I try to run dosbox DOSBox version 0.74 Copyright 2002-2010 DOSBox Team, published under GNU GPL. Exit to error: Can't init SDL Unable to open mouse So it's a start...

@proxycell said in Building packages with retropie_packages.sh has terrible results!: it comes with some packages I'd rather avoid Which can easily be uninstalled through the setup script too.

@mitu and just to add a lot fo experimental packages are source only so it would make sense it takes a really long time to update if there are lots of experimental packages installed.

Hi both, Thank you for your responses. Popped out for a couple of hours, and it seemed to have completed. This ties in with the 3-4 hours stated above (Pi 3 Model B, Overclocked to 1.35ghz)

What about using a USB stick, would that work for you? Check out the documentation, in the Getting Started section there is a whole page on Transferring Roms: https://retropie.org.uk/docs/Transferring-Roms/ EDIT: Sorry re-read your post, emulators, not roms.....never mind

@BuZz That explains a lot, thanks ! My Murphy curse was at it again... @Darksavior you were right anyway ;)

Hello fellows. I would like to say thanks! The cec-utils package is pretty handy. The udev rules are perfect! The only addition I've made on my arcade build was adding a turn off monitor.sh script in RetroPie Menu. #!/bin/bash # turn off monitor.sh ################# # Actually puts the monitor on stand by mode. echo standby 0 | cec-utils -s -d 1

Installed version 4.1 and all seems good so far. Thanks for looking, Sam

There is Kodi 17.1 final/stable available at PiPplware's unstable repo: https://retropie.org.uk/forum/topic/6308/testing-kodi-17-0-stable-final-available-for-retropie It is in the unstable because it needs newer firmware/kernel (which you can get with rpi-update), at least to play h265 videos. This newer firmware/kernel wasn't tested, by me very much in emulators, so if you do it, you have been warned. Newer firmware/kernel should come very soon to Raspbian and RetroPie. Anyway, the 17.1 RC2 available in RetroPie is pretty much 17.1 stable/final like BuZz said, if the update warning appears just choose "no" and it won't appear again.

@Cybermen I think you are over-thinking this. RetroPie is updated incrementally. Every few days. Sometimes twice in a day. Only a few minor changes happen between each version. Even between 4.1.x and 4.2. It is the stock image that is updated to the "new version" That was previously last done back in November 16. The new image is 4.2 but even if you install that updates have been implemented since that version of the image was done. The last update for example was 2 days ago.

Which system? When you post about a problem try to be specific. I think its the MAME games who don't work? You did update the emulator which requires a newer romset. You need to rebuild the romset to the required version for the emulator and it will work. Please read this article and you'll fix it https://retropie.org.uk/docs/Validating,-Rebuilding,-and-Filtering-Arcade-ROMs/

@tribunal88 only by following progress on github etc.