@jenslyn87 I'm probably the wrong person to ask about it as I'm a bit out of the dev loop with ES but possible it's caching them while you scroll for the first time so it doesn't have as much to reload when you continue scrolling but that's just a guess. I've just always kept my lists small cause full sets just get overwhelming to me.

Do you just want a different image for each system or do you want a random image for a single system?
Anyway, as far as I know there is no way to randomize any value that can be used as path/filename to images.
Having a different image for each system can be done by either using the system folder theme.xml or by using variables as paths/filename.
If you need/want to have different colors for each system as well, you have to use the old system folder theme.xml otherwise I would suggest to use variables.

I think I found the problem: something was wrong with my BIOS. I deleted the current BIOS-file and put in a new one - and now it works.

But thanks for your effort, @mitu

problem solved ,i was using a 360 pad and that was the problem, plugged in innext controller and worked 1st time . thanks for your help

I appreciate the help, guys.

@edmaul69 I have done that to. It is not a problem with the controllers.

I am curious why you would specifically want the Finder for this? Why not use a decent (S)FTP client like Cyberduck or Fugu?

@darkus I have the RPI system 24/7, but I don't have this problem. The TV turns off the screen after about 1h (2h maybe). I have the screensaver/power options active in EmulationStation, if that makes a difference.
One thing to try is to move the HDMI PI cable to a different TV port - if you have more than 1. Mine is set HDMI2, which is labeled PC, and has the Game mode active.

@jenslyn87

Very nice!

@mrbear2899 either bind the hotkey to the same button as fastforward, or disable hotkeys entirely.

@dankcushions ok thank you thats what i thought just didn't know if there was a way to load my pi zero image tru a terminal command or something. Ill just set up another one then.

@afunnyname Did you enable SSH on your Raspbian image ?

@benjaminjay I thought you were asking, and I quote:

What is the best way to fix these ROMs using a Windows PC?

But you fail to mention what kind of ROMs, so I assumed arcade, and the answer is that you need to obtain the right ROM version for the right emulator. They are not interchangeable.

Your second question is quite a bit different than that. I suspect Windows is only going to be able to read the boot partition of an SD card setup with the official image. You will need to load a certain kind of driver to let you read/mount linux drive partitions, or use Linux to read them.

<EDIT> @mitu above has a better suggestion that might work for you. Load the image on the system that is going to run it, then connect to the ROM folders over a network with your windows sysetem to add/remove/replace ROMs.

Ok, I think I know what my problem is now. It's because I'm using the XboxDrv software to override the inputs when I load certain systems. When I first started using it, it was my understanding that I could use configure settings to load on-demand as needed whenever I wanted to use a different controller. For instance, when I play a Sega Genesis game, it detects I'm loading that system and runs an additional driver to let me use my 6-button Pad and the MayFlash adapter. It does this as part of the runcommand-onstart.sh. When the gaming session ends, it unloads the driver. Apparently the problem comes from it ALWAYS loading the driver, rather than only when I connect a controller to it. I discovered this by testing the various controllers after moving the Xbox Dongle to the Pi's USB Port 0. I can replicate it every time, with the controllers I have configured.

The NES system is configured to use an NES controller. So when I try to launch and NES game, RunCommand is looking for input from that controller only. When I connect a controller to that port, I can now access the RunCommand window. The same is true with Sega games. I can only access the RunCommand windows by triggering it from a controller connected to that port.

In both scenarios, the Xbox Controller works fine in game and in RetroArch. But I can't navigate RunCommand with it. In fact, I can't navigate RunCommand with anything other than the keyboard on any systems I have configured with XboxDrv. I don't have a configuration for SNES, so when I'm using my Xbox controller, everything works like it should. I can trigger RunCommand and navigate with the Xbox controller jut fine.

I think I need to go back through and examine my runcommand-onstart.sh settings. I might be able to get it working by adding an Xbox controller configuration to the settings.

runcommand-onstart.sh

That's my current settings.