@Inkdork
On your desktop, open the file explorer and then select edit
File [Edit] View Sort Go Tools
"Preferences"
"Volume Management"
Then fill out all the checkboxes under auto-mount.
I guess if they are already checked, it may be worth a try to uncheck and reboot; then recheck them and reboot.

@ZioDarkmage
sudo fsck.fat /dev/sda1
I always have this where it says it was not properly umounted. I'm looking into it.
Oh well, It is probably nothing.

Excuse me
I was wrong.
I was using ARRM to sort gamelist. It worked perfect.
But I didn't close emulationstation and it didn't save the changes.

Now is perfect
Thanks

Glad you got it working.
You can mark the topic solved by editing your first post in the topic.

@mat
Element 14 is one of the main distributors for raspberry pi, it is probably as official as it gets.

Ok thank you it works.

Just wanted to drop a line to say changing the dash to an underscore solved the issue.

Thanks again!

@tuki_cat

And thanks again, I succesfully mapped the 1 to F1, 2 to F3 and 5 to F5. Although it required some steps.

First I mapped (as you told above) with the virtual keyboard the correct keys, and then saved it. After restarting the Vice emulator the keys weren't mapped anymore. When I loaded the keymap again the keys still didn't work. Then I thought maybe I can add the changed keys in the dsl-vicerc file (a bit like the F12 file) but then more like this "49 0 4 9" which is 1 to F1. That didn't work but I noticed that it would load the keymap according thje dsl-vicerc file, but somehow that didn't work.

Looking in the vice.log file I noticed that it says: Loading keymap `/opt/retropie/emulators/vice/lib/vice/C64/sdl_sym.vkm'
Now I wen to that file changed it according to the saved keymap and it works. Strange thing is that is doesn't look at the keymap it should load.

And what I did for the Dosbox is create .sh file. Not sure if it works for C64 but you can try this e.g:

roms\c64\frogger.sh

sc c64/frogger/keymap.vkm /opt/retropie/emulators/vice/lib/vice/C64/sdl_sym.vkm load frogger\frogger.crt

The problem is I don't know if there is a command to go from the .sh file to the crt/tap/etc file. Don't think 'load' wil do the trick haha.

Oh wait. You are using Raspbian Jessie.

It's no longer supported. It says this when you launch RetroPie-Setup. You will need to start from a RetroPie 4.4 based image.

Maybe I should have disabled the update mechanism, but I hoped the message saying no longer supported would be enough rather than forcing/removing functionality.

@mitu
Thanks sudo /usr/sbin/sshd -d to debug helped a lot.
It was the very first line /etc/ssh/sshd_config that had been uncommented, I noticed it wasn't in yours but it kind of blends in and I kept ignoring it for some reason.

@mitu Which folder can I find the code to edit? Would you please describe it in detail? Thanks!

@mitu said in How to modify the description of EmulationStation?:

@Leonard-Lin You'll have to edit the code and change it, then recompile.

Rewrite:
For people without a usb keyboard. On any android you can use an app like ConnectBot to SSH into your pi using RNDIS USB ethernet.

Activate SSH on the Raspberry Pi
navigate to raspi-config >> Interfacing Options >> SSH
or (untested)
create an empty file named ssh in the boot directory of the raspberry sdcard

Install the apps on your android
ConnectBot (or preferred ssh client)
LanDroid (optional)
F-Droid (optional - Free Open Source Software for Android)

Activate the RNDIS USB ethernet
use your phone charger to connect the Android device to the raspberry pi USB.
android settings >> network & internet >> Mobile Hotspot/Tethering >> USB tethering
or if you're phone provider has this service blocked
for android 2.3 - 4.4
Use an app like Notification Bar will sometimes allow you to enable tether using the widget. Or install an unbranded rom like cyanogen-mod.
for android ?5.0 - 8.0
android settings >> system >> about phone >> x7 build number (click on the build number 7 times)
with "developer mode" enabled
android settings >> developer options >> "select usb configuration" - RNDIS (USB Ethernet)
(This is a good way to turn your phone into a wifi adapter if your router allows internet connection sharing)

Aquire the IP address of the Pi using arp
navigate to "show IP" on the raspberry pi
or
using ConnectBot app; add a host; change protocol to "local"; or use local terminal emulator
type cat /proc/net/arp or ip neighbor into android terminal
look for the ip-address 192.168.42.*
or
open the app LanDroid, and select the ARP & ND Cache
or on windows
use commandline arp -a look for a dynamic address that is not listed in ipconfig

Open a SSH to the Raspberry Pi
Use ConnectBot to add a ssh host filling out the username "pi"(default) and host "ip.address"(from the arp cache)
other apps can be used and configured including sftp, I use the apps Total Commander and SFtp plugin for Total Commander
or on windows
windows 10 has ssh built in, simply type ssh ip.address
or use one of these programs
PuTTY(ssh)
BitVise SSH client with ftp (easy to advanced)
KiTTY (PuTTY with more features, easy)
WinSCP (scp, sftp, ftp, advanced)
FileZilla (sftp & ftp)
And many more inlcuding Terminus, Super Putty and the amazing though complex Cygwin

Android RNDIS creates IP addresses from the range 192.168.42.[1-255] these are generated randomly and will change when you reconnect the tether. When I figure out how to assign a static ip or save the dhcp or create some sort of order I will share. And if anyone know how to do this then please do.

Alternatively to setting up ethernet, import the wpa passkey (wifi passkey) create a wifikeyfile.txt with the contents

ssid="NETWORK_NAME" psk="NETWORK_PASSWORD"

save it to the main folder of the microsd with retropie installed using a microsd reader.
Reinsert the micro sd with RetroPie installed and power on the Raspberry Pi.
Navigate Emulationstation using your controller to WiFi and Import wifi credentials from /boot/wifikeyfile.txt

So it is possible with any android phone with a usb charging cable to tether and access configurations. or if you have a ethernet cable for your computer.

I'm happy to help. Feel free to practice and take notes. It is difficult to find memories like this from while travelling. @trekdrop

~Bon voyage.

For the RetroPie menu - check if you have a retropiemenu folder under the retropie-mount folder on the USB. If you don't, then re-install the retropiemenu package from the core packages section in the RetroPie setup script. Make sure you have your USB plugged-in.

For the 2nd problem - you'll have to be more specific: what does in game configurations can’t be saved ? The emulator configurations are not saved on the ROM folders.

@nosunlight Did this get fixed magically for you by the update? 'm using Kodi 18.1 on Retropie 4.4 and while all the games on retropie run fine, the controller has no response in Kodi. Any other things you might have changed that could fix it for me? Cheers!

Glad you git it working. One minor niggle - rpi-update is no longer a recommended way to update your kernel/firmware, this is taken care by the normal OS/package updates. For the time when the problem was reported - immediately after the 3B+ launch - I think some improvements w.r.t the 3B+ model were added that were only available through the latest development kernel/firmware versions.
Anyway, keep an eye on the disk space and happy gaming!

there is an option to select analog or digital in mame2003+ as it supports analog 2003 doesnt just go to your options and change you controller setting to digital.

it sin options->control mapping change it to digital and it will work for snes pads and arcade sticks ect with having to set all the inputs. The majority of people want real analog controls when available so thats the default.

I’m using the later version (3.1.4).

Think I’ve got it working, did a manual command and it’s doing it.

I used thegamesdb.

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$