@vretro said in Can’t Remove emulator choice for ROM:

@mitu that was quick, the directory flashes up so quickly, but I’ll try to record the screen to catch it.

Or try to catch it using the Pause key of your keyboard.

I don’t know how to repair permissions via terminal, will have to look that up.

It depends whether the owner is wrong or the actual access permissions. To change the owner, look up chown, to change the permissions, look up chmod. Or give us the output of this command after you found out the directory and we may tell you the necessary command(s).

ls -ld name_of_directory

@exarkuniv Thanks I will delete all the files and try changing the mode!

Thanks, I'll dig into it, I forgot to say I'm using Xin-Mo interface

@krokko unless there is a specific reason you need stretch you should be fine with using Jessie. If you for some reason want both OS's, Simple solution would be to have two separate sd cards as they are cheap enough. What is it that you're trying to do/want to do?

@mitu
Thank you it seems that your link get information to solve the problem :

Reicast cannot be built for Odroid XU4
So the issue here is that the script module for reicast is set to not allow building on the Odroid XU4 with the "!mali" flag.

Workaround/fix: Remove the !mali flag and build through RetroPie Setup.

This is all explained here:

https://retropie.org.uk/docs/First-Installation/

@lupin said in Runcommand:

So will I be need to add many "IF <emulator> = " lines to one script

Yes, if you need different actions for each emulator.

I have a similar problem trying to shrink my image with pishrink.

pi@pi-VirtualBox /media/sf_SD__images $ sudo ./pishrink.sh 64gb_Papberry_arcade.img
[sudo] password for pi:
tune2fs: Attempt to read block from filesystem resulted in short read while trying to open /dev/loop0
Couldn't find valid filesystem superblock.
tune2fs: Attempt to read block from filesystem resulted in short read while trying to open /dev/loop0
Couldn't find valid filesystem superblock.
mount: /dev/loop0 is write-protected, mounting read-only
mount: /dev/loop0: can't read superblock
md5sum: /tmp/tmp.JImqrA1mnE/etc/rc.local: No such file or directory
./pishrink.sh: line 63: [: !=: unary operator expected
umount: /tmp/tmp.JImqrA1mnE: not mounted
e2fsck 1.42.13 (17-May-2015)
e2fsck: Operation not permitted while trying to open /dev/loop0
You must have r/w access to the filesystem or be root
resize2fs 1.42.13 (17-May-2015)
resize2fs: Operation not permitted while trying to open /dev/loop0
./pishrink.sh: line 136: [[: Couldn'tfindvalidfilesystemsuperblock.: syntax error: invalid arithmetic operator (error token is "'tfindvalidfilesystemsuperblock.")
expr: syntax error
expr: syntax error
expr: syntax error
resize2fs 1.42.13 (17-May-2015)
resize2fs: Operation not permitted while trying to open /dev/loop0
Couldn't find valid filesystem superblock.
ERROR: resize2fs failed...
mount: /dev/loop0 is write-protected, mounting read-only
mount: /dev/loop0: can't read superblock
mv: cannot stat '/tmp/tmp.JImqrA1mnE/etc/rc.local.bak': No such file or directory
umount: /tmp/tmp.JImqrA1mnE: not mounted

@mitu running the command you said, this is the output:

pi@pi-VirtualBox /media/sf_SD__images $ parted -m 64gb_Papberry_arcade.img unit B print
WARNING: You are not superuser. Watch out for permissions.
BYT;
/media/sf_SD__images/64gb_Papberry_arcade.img:64021856256B:file:512:512:msdos::;
1:4194304B:63963135B:59768832B:fat16::boot, lba;
2:63963136B:63864569855B:63800606720B:ext4::;

(I don't know how to use the forum editor to make this code looks like yours, with black background)

@buzz thank you very much for the help! Quick question --

It seemed like the RetroPie setup script runs apt-get update and apt-get -y dist-upgrade before calling post_update and update_packages. Do I have that right? If so, should the order of the commands be?:

# do not run this often as it will put strain on our server - weekly should be enough cd ~/RetroPie-Setup/ git pull sudo __nodialog=1 ./retropie_packages.sh raspbiantools apt_upgrade sudo __nodialog=1 ./retropie_packages.sh setup post_update sudo __nodialog=1 ./retropie_packages.sh setup update_packages

Also, is there anything special about the raspbiantools apt_upgrade function(s) vs. just running?:

sudo apt-get update sudo apt-get -y dist-upgrade

Just trying to figure out what is best before calling this "done". Thanks again!

@supercatfooz Update: I just found an HDF file that seems to work fine, making the two .dim files I have obsolete. I'd still like to know if multi-disk mounting is possible for the future, though! (plus it'll help whoever else happens to have this problem)

I know this isn't an answer and doesn't advance you anywhere but I needed to ask, what advantage do you get from having noobs on the card? I thought the point of noobs was a lightweight first time installation tool. Given Retropie is already installed in the image, I'm not sure what you gain from converting it.

Can you explain step by step, as I'm sure you must be missing something?

I use win32diskimager and so I would

Download the file from http://retropie.org.uk/download
Use 7-zip to extract the .IMG file from the .gz file
Insert my SDCard, check I can see a drive on it. If not use diskmgmt.msc to check the card, delete old partitions and create a single fat32 partition.
Once I can read a drive in explorer then
Open Win32diskimager, select the file and the SD card drive letter to write to. Click write.

I'm probably over paranoid with regard to drive letter and partition checking. However, the reason I check the drive letter is that I have in the past accidentally imaged to a usb stick or portable hard drive by accident, doh! I once lost over 800gb of files including old pictures and videos as I wrote a Raspbian image to my external hard drive, not a pleasant experience .

Si

@vahnxdean Login via SSH or get to a command prompt by closing Emulationstation. Open the File Manager (mc) and browse the /home/pi/RetroPie/roms folder, which will contain your ROMs and save states - under each system (nes, snes, etcc).
Copy/move the saves (they have the .stateX extension, where X is a number) to a folder inside /home/pi/ - let's say /home/pi/saves.
Configure the save states folder to be /home/pi/saves. This way the save folder will be on the SD card, but your ROMs will still stay on the USB HDD.
The reason you're not seeing the ROMs from the SD card is that Windows doesn't know how to read the Linux partition on it, and you're only looking at the /boot partition, which only contains the bare minimum to start the RPI system (kernel files and device tree files).

Nevermind. I was able to test even though I'm away from it and I have an idea of how it works.

Thanks for the help.

i added the following lines to my controller autoconfig file:

(/opt/retropie/configs/all/retroarch/autoconfig/<controller>.cfg)

input_volume_up_btn = "h0up" input_volume_down_btn = "h0down"

then <hotkey>+Up/Down on the D-pad becomes volume control for all libretro emulators. not sure about kodi though.

I have very little experience with VGA 666 (in fact, I tried for first time today... ^_^U) but I have no problems with any emulator. I can give you some advices, maybe it works with you, if you still have problems.

Set dpi_mode in hexadecimal format, in your case 0x10 as it's listed in this table, just in case:
dpi_mode=0x10

Set framebuffer to your desiere resolution:
framebuffer_width=1024
framebuffer_height=768
Comment any HDMI config line:
#hdmi_force_hotplug=1
#hdmi_group=1
#hdmi_mode=1
#hdmi_drive=2

Kept this lines commented:
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on
Or if you want, uncomment turning off everything:
dtparam=i2c_arm=off
dtparam=i2s=off
dtparam=spi=off

Try some other VGA modes, like 75hz (0x12) or 800x600 (0x09, 0x0B).
Be sure emulators are not using special scaling resolutions than may be incompatible.

Last one, universal solution to any computer problems: install retropié again and try with default retropié configuration.