@tubadog said in Problem uploading files through retropie manager:

I know this thread is 3 years old.... but.

I had the same problem, but it was inconsistent. I wanted to add Rugrider to the Commodore 64 emulator. I was dragging and dropping and everything but no luck. I was able to drag and drop plenty of other games though.

SOLUTION:
The file extension was .D64 and was failing. I changed it to .d64 and it succeeded. Seems that the file type is case sensitive for this instance at least.

Best of luck!

Maybe worth noting for folks who may not be aware - Linux is case sensitive, unlike Windows.

@mediamogul Thanks for taking your time to reply. Alright i thought it was something i did. Will do exactly what you said Mediamogul from now on when using that emulator. Thanks again.

@svayra said in What buy to play??:

For the first installation a wireless keyboard is ok or not??

If you can have SSH access to the device, then it will work, but you'll need to connect to the PI over SSH and pair the keyboard so it will be connected to the PI.

@buzz thank you so much and I will read the forum advice

@octopus3535 said in Which Station To Use?:

Also is there any where that describes what cores are best?

yes, retropie's defaults :) you can look at individual system wiki pages to see more information about what the different cores entail.

@mitu What I mean't was instead of using a connected monitor, use Wifi/bluetooth android phone screen inorder to play retropie without wires.

@Swampy , @mitu

Thank you for your help. I am back on RA 1.6.9 from binnary and everything is ok :)

Wiimote + Dolphinbar should work with RetroArch emulator cores as of the latest releases of RetroPie and RetroArch.

@chinjw 3rd party images are not supported - please download and install the RetroPie image from retropie.org.uk/download and see if you still have problems with Reicast.

@jpod1003

Good to hear. What was the issue?

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.

@kal-el-1981 Same to you! Did you notice that there already is a Merry Christmas thread?

Merry Christmas, y'all! (Or I guess Boxing Day, considering when I'm posting this.)

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)

@alucard_xs
Try these in your /boot/config.txt file:

# Uncomment to help remove white noise (if needed) disable_audio_dither=1 # Uncomment to completely remove white noise over 3.5mm connection audio_pwm_mode=2

@anasazi29 said in Arcade game service mode settings:

Do you think if I copied the game and the .nv file over to another Raspberry Pi with a new installation of Retropie that potentially those "service mode" setting would carry over, correct?

Yes.

Post update: I made two alternative versions of this splash! One uses blue stripes (to match the default RetroPie splash screen), and the other uses gray stripes (to match Carbon). Enjoy!

Click me to preview/download the blue variant!
Click me to preview/download the gray variant!

Thanks @dankcushions I didn't knew that I needed the parent rom. Problem solved. It's up and running. Now I can save my progress in Pacman.

Thank you all.
@mitu and @jonnykesh

You've been a great help.

@edmaul69 Hello! Well I've got Boulderdash running with vice (not lr). But Im going to re-install Lr-vice again. But heres what works for me. in case anyone has the same difficulty.

[All from the ViceMenu GUI]

1- Restore defaults from 'settings management' (this is a different pref set than the package, you can tell as it changes the display filter to emu crt display)
2 - Set Machine settings / Joystick settings / Joystick device 1 -> Joystick
3 - Set Machine settings / Joystick settings / Joystick 1 mapping -> !Go set this!
4 - Save your settings in 'settings managment'

I think my naviety was !assuming! that because I've configured controllers for retropie that the mapping would naturally carry over to the emulator. Not for vice it seems. Lesson learned.

On the keyboard front, I loaded up the mac version of Vice, found the symbolic and positional keyboards for mac. I then loaded those into the C64 rom section. Then loaded those keyboard layouts in vice. However this made no difference. Unless you have to save the keyboards .kvm's in a specific location I think keyboard mapping is broken in vice

What worked was the virtual keyboard. And knowing that you have to press f1 to start the game. Yep pressing fire button wont do jack (it's 1984) https://ia600707.us.archive.org/20/items/Boulder_Dash_1984_First_Star_Software/Boulder_Dash_1984_First_Star_Software.pdf

Thanks Edmaul for the tips to keep lookin.

Nice, it looks pretty. But it seems that it has no support for the video and kidgame tags.