@yuke Just make a backup of your config.txt file before changing anything. You need to get your Hdmi timings right before changing anything in the service menu.

Now that your Hdmi timings are as best as you can get them then go over to overscan settings.

We'll worry about the service menu later.

This is taken from the Video timings script readme file.

*Video timings script
*Version - 2.0

hdmi_timings=320 1 20 20 44 240 1 6 7 10 0 0 0 60 0 6400000 1

-Use ARROW keys to position screen
-Press Q to toggle test image
-Press I to input timings
-Press L to load timings from timings_load.txt
-Press B to load timings from boot/config.txt
-Press S to save timings to timings_save.txt
-Press C to save timings to boot/config.txt
-Press D to display current timings
-Press F to calculate frequencies
-Press SPACE or ENTER to reset timings
-Press M to display this menu
-Press X to exit to shell

Program first reads and displays hdmi_timings from /boot/config.txt

-Arrow keys | shift the screen left/right/up/down

-Q | displays a 320x240 test PNG image to visually aid in centering the screen (defined by $TEST_IMAGE variable)

-I | allows user to manually input and generate custom hdmi_timings

-L | loads timings from 'timings_load.txt' (defined by $LOAD_FILE variable)

-B | loads timings from 'boot/config.txt' (defined by $BOOT_CONFIG variable)

-S | saves and parses timings to 'timings_save.txt' (defined by $SAVE_FILE variable) and also saves and replaces timings to 'timings_load.txt'

-C | saves timings to 'boot/config.txt'

-D | displays current timings

-F | calculates and displays horizontal scan rate and vertical refresh rate frequencies

-SPACE or ENTER | resets timings (defined by $SAFE_TIMINGS variable)

-M | clears the screen and displays the main menu

-X | aborts the program and exits to shell

Edit: It's important that you center the image as perfect as you.

Edit 2: Read here here for an explanation about what each hdmi_timings settings mean.

Maybe @maxriptide @Dochartaigh can help out?

@jim1973 said in Unable to dowoad retropie:

I've tried to find a torrent but none are active.

Have you tried this one specifically? I'm getting a little over 3.5 MB/s from only four seeders, so it seems to be pretty solid.

Edit: In the interest of being fully transparent, the magnet link originates here.

@mgrabow Thank you for sharing your solution.

please fill out the template in the sticky thread above to provide us with information about your setup. having basic info on your pi model, retropie version, and power supply etc. will help with troubleshooting.

have a look here in the wiki where it outlines using jstest to determine the button values.

also in this case, it would help to see the output of the command lsusb before and after you connect the wireless receiver.

@winteriscoming Looks like a mismatched partition - re-format the SD card so there's nothing on it and re-write the image.

@lupin Check if you script has UNIX end-of-line, instead of DOS - https://superuser.com/questions/479756/eol-in-notepad-and-notepad.

@darkside1305 said in Cant Acces SD Card without formatting on my PC:

Access the file from an PC?

Yes, it's posible, as long as the PC is running Linux.

@pobs
'I've made sure that none of the other roms are in the .bin format'

What do you mean by this?

You could try replacing the bios file with one downloaded from another source.
You can also try some eboots (ps1 games in a psp compatible format, also known as psx2psp). These are just one file each (.pbp) and should work fine.

@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)