We don't support 3rd party images or systems bought with RetroPie - https://retropie.org.uk/forum/topic/3/read-this-first. Selling RetroPie is against the project's license. If you'd like to use RetroPie, get one of the images from retropie.org.uk/download and then follow the installation instructions from the Docs to use it.

https://github.com/RetroPie/RetroPie-Setup/wiki/FAQ#why-emulationstation-doesnt-start-automatically-after-an-update-

Ah! Just hit button A on the DosBox choice in Emulation Station. Silly question, sorry, I didn't see it. Solved. @edmaul69 Just wanted to run some batch files.

Path to locate BIOS can be found here! https://github.com/retropie/retropie-setup/wiki/Playstation-1 Usually if you got Network Connection the BIOS folder is shared and you can place file there. If you ask questions here in the forum then read our wiki first.

@THRobinson Oh well. It was worth asking. I would be very cautious about using any computer image that has no official source, especially with something as popular as RetroPie has become. For one thing, almost NONE of us have the same hardware configuration, so one size almost never fits all. Also, the work you describe that is already done for you is very likely work that makes the image totally illegal, violating all kinds of software licenses if not copyrights. If someone is willing to create, then post an image with ROMs on it, or with emulators downloaded and preconfigured where the license doesn't allow that, it isn't doing RetroPie any favors which is another reason folks are going to be reluctant to offer help.

@gotwood3001 If you exit emulationstation with F4, you will be taken to the command prompt. From there you can edit files with the nano text editor. There is a much easier way though to edit /boot/config.txt and that is to use winscp or putty to access it via the network. Read more. Video tweaks here.

Sincere thanks, guys. I finally got it to work last night by installing a completely different build (Steve Smith's triple-boot at http://www.multibootpi.com/). Still not sure what happened, as this setup just worked smoothly, ROMs transfer just fine, etc. THEN I had to learn about the wonders of HDMI sound being flaky on RPi, and adjusting the config file to activate it. Interestingly, it didn't work plugged directly into my small TV, but it works fine plugged through the receiver connected to my big TV.