Looks to me you're using an Enterprise edition of Win 10, which doesn't allow - by default - connection using the guest account to file shares.
You may try using WinSCP to connect to your Pi and copy your ROM/BIOS files over.

Retrostone is based on Orange Pi not raspberry pi. You can find some retrostone support on the Retro Orange Pi forums:
http://retrorangepi.download/forum/

@Smeg this is why we have it disabled by default. see https://github.com/RetroPie/RetroPie-Setup/wiki/Input-Lag#unsupported-tweaks. on a pi4 there seems to be the CPU headroom to disable it on the 16-bit cores at least, but i've not done extensive testing.

You have the emulators installed, but the systems will not show up until you actually copy games/ROMs on it - see https://retropie.org.uk/docs/First-Installation/#emulationstation.

EDIT: when using macOS to transfer ROMs, use the Finder's Go menu and then Connect to Server, type smb://retropie and then hit Connect. See https://retropie.org.uk/docs/Transferring-Roms/#samba-shares.

Thanks very much for the detailed reply, it seems like the benefits will outweigh the pretty minimal cost.

Thanks as always for the swift response.

If you have a 4k tv/monitor, then use raspi-config and change your default video resolution to 1080p.

@soldomino said in Questions about GPi:

I'm viewing the Pi using WinSCP, if that matters.

If you're using SSH to access your Pi, then you can look at/opt/retropie/configs/all/emulationstation/gamelists, it's basically the same folder.

Knowing that will help me whittle down what games I should put on there (SNES Doom, Star Fox, and really any Mode 7 stuff was lagging pretty bad)

I think that even with older/less accurate emulation, you won't be able to emulate SuperFX games full speed on a Pi 0.

@sonicman2020 with respect, your understanding of the runahead settings, and the audio latency settings are very wrong. if you want to get this working properly, please start again from the retropie image, and don't change such settings: https://retropie.org.uk/docs/First-Installation/

@grant2258
Yep, that was it. Thank you again.

@MISTERHOLLYW00D said in Press Hotkey twice to exit retroarch:

I’ve noticed on retroarch in hotkey binds it has the option to press hotkey twice to exit retroarch.

If you're referring to the new 'Confirm Quit' menu, then it's not 'press hotkey twice to exit', but press the 'Press the Quit Hotkey twice to quit', i.e. press the hotkey+Quit key to exit. This option is Off by default in RetroPie.

Anyway to change the coding on this for a hard press...holding the hotkey to exit instead?

That should be addressed upstream (RetroArch), but I'd say no, since it would be too easy to exit the emulator by holding 1 key.

@quicksilver

Thank you, my friend.

@raspnoobie if you have a newer set of mame roms than 078 all you need is the mame roll back roms to build older mame sets

There is a thread about this.

@Luddo183 i wouldn't think anyone has motivation to fix/investigate such an old version of FBA on hardware that can comfortably run current FBN. i would recommend you just get new ROMs for FBN.

@Unknown you've been told to stop bumping posts before. please take a day to absorb that message.

You can run xboxdrv only for the psp system, if that works for you. I think the Xboxdrv doc page has some examples on how to run it only on specific systems, by using the Runcommand's onstart/onend scripts.

@truglodite said in How can I boot RetroPie from NVMe or SSD (without SD)?:

I am guessing retropie still will write heavily to the sd card despite roms being on an external, correct? Not sure if sd wear is a big deal with retropie, so figured I'd ask if it was and if there's a similar way to mitigate.

Not really, gaming is not a write-heavy process. Game saves and save states are written to the ROM's folder by default and unpacking .zip ROMs is usually done in RAM.
There is no constant write load using RetroPie, like a monitoring/data collection/aggregation process entails, so a good sdcard and proper power source is usually enough.