@McJones9631 https://retropie.org.uk/docs/Updating-RetroPie/#updatinginstalling-individual-packages

it's in the "optional" section

I have already downloaded several Tos files for Atari ST I still can't get the script to work if it is installed, what can I do?

@DavidDraper
put the hi resolution texture
in the bios mupen64plus cache folder.
htc files

I don't think stty would help here, but try adding quiet to the cmdline.txt line, this should suppress the boot messages. See more options at https://retropie.org.uk/docs/FAQ/#how-do-i-hide-the-boot-text.

this seems to be concerned to this thread,
have a look at the last posting: https://retropie.org.uk/forum/topic/27507/libretro-cores-wiped-out-restored

The EEPROM is outside the OS, so changing the OS wouldn't have helped.
As I said, you'll need to use the stable version to get USB-MSD boot working, by default rpi-eeprom-update will use the critical update version - as you found out in your latest update.

ok i reinstalled it.

everything is working so far now.

thank you very much for your time and your help.

best regards =)

@johnnytwolegs It entirely depends on your network setup.

If you NAS is connected to the internet, then I guess it's a matter of configuring the firewall to allow access to the CIFS ports and making sure that file sharing is enabled for the internet interface. If you have a router in-between, you might need to forward the CIFS ports from the network interface to your NAS box.

Again, a configuration I strongly suggest against, since it exposes your NAS to the internet.

@cyanxx. Will do Thanks

@sirhenrythe5th I'm not an expert so I'm not sure. I would assume that would also require a better gpu as well. I mainly use the Pegasus front-end and that got a boost in speed when I switched from a pi3b+ to a pi4.

Mitu- ok. That makes a lot of sense. Thanks.

David

If anybody comes accross this: Happened to me with version 4.6 (on raspbian buster), exactly same problem, like 3fps on all PS1 games. Tried different emulator (removed lr-pcsx-rearmed from main packages and tried pcsx-rearmed form optional). That ran well, but didn't see controller. So I decided to tweak with original lr-pcsx-rearmed, reinstalled it back and voilaaa, games at full speed. Don't know the reason, but for somebody just wishing running emulator it's worth trying I suppose.

@BuZz editing /opt/retropie/configs/all/runcommand.cfg did the trick, thankyou! :-)

that worked. thanks both of you @mitu @muldjord

What's the content of the file you deleted (es_input.cfg) ?

Apparently this is an issue with the SN30 Pro itself. I got it working. Here's what I did:

Deleted /etc/udev/rules.d/99-bluetooth.rules Deleted SN30 Pro from registered Bluetooth devices Powered on SN30 Pro with Start+B (Android mode) and held Pair button (top of controller) for 3 secs to immediately go into pairing mode. While in pairing mode selected Register and Connect Bluetooth Devices in RetroPie-Setup Script >> Setup >> Configure Bluetooth Devices Selected 8Bitdo SN 30 Pro from list and finished config Did NOT set up udev rule

Now the controller is working perfectly; I'm able to open Launch Menu or go straight into games ... no sitting at black screen for ~40 secs. Also no waiting required to navigate script menus either.

I did have to reconfigure controller layout ... and the L/R triggers are actually recognized now as well.

@nes yes, with the rest of the bin/(appropriately re-named)cue or chd files

@dudleydes Thank you for this Information!