@jak75 Start reading the docs: https://retropie.org.uk/docs/Controller-Configuration/

@clyde

You have been Most helpful

I followed all your basic instructions and everything seems to work

Your wonderful clyde

Thank you

Nothing here:
933e1f42-a621-4781-a983-41c06fdf791d-image.png

Here:
4dab9d7a-4e9d-426d-968a-bdf89ad1056d-image.png

@nemo93 Many thanks for the reply. I found the site I was using has 'empty' WHDLoad. I switched to another source (I won't post it here), but now working fine. Many thanks.

Peter

Hello and welcome to this forum.

Alas, you won't find much support for a third-party RetroPie installation here, because we can't know how much its makers changed the official installation image. On top of that, RetroPie's licence and the licences of many of its components don't allow commercial use, including selling it as part of a commercial product. The people who sold it to you broke those licences.

So, you'll have to either ask the vendor about the problems with their product, or install the official image from https://retropie.org.uk/download/. In the latter case, you should make a backup of your old system and its games as described here – or just use another SD card.

We'll be happy to help you with any problems you may have with the official image. As a side effect, you may learn a bit or two about the inner workings of the wonderful retrogaming box of bricks that RetroPie is. 👍

Be sure to read https://retropie.org.uk/forum/topic/3/read-this-first to get more useful information to start in this forum.

@chaoseffect I think I got it, Win32DiskImager says something about formatting the E: drive after it writes, this time I selected nothing and put the SD card in the Pi4. Everything boots up as expected. I will use this new SDcard for a while to make sure everything is good.

@dank-cushions CDMage looks like some sort of disc extraction/manipulation tool. There shouldn't be anything inherently wrong with consolidating the .bins, but maybe it was done incorrectly. That's why we should see if the original files work before we start pointing fingers at the conversion.

But a single .bin or multiples shouldn't matter as long as the .cue is correct; as I understand it, they both represent the same raw binary data stream to recreate the original optical disc. I ended up with one when trying to apply the English patch to Rondo of Blood for the TG-CD, that worked fine (as far as I can tell. I've only played through the first level but it works at least that far.)

Before I knew that chdman would work on .iso/.wav./.cue sets, I thought you had to have .bin/.cue. So, starting with the multiple .bin/.cue set I:

Burned the multiple .bin/.cue set to a disc. Re-ripped the resulting disc to .iso/.wav/.cue using TurboRip (the included binchunk tool that was originally meant to do this conversion gave a divide-by-zero error on Win10, and in compatibility modes for Win7 and XP.) Patched the resulting .iso/.wav/.cue set with the included instructions. Burned the patched .iso/.wav/.cue set back to another disc. Ripped that disc to .bin/.cue using ImgBurn.

This gave me a single .bin file. At first I was worried I had messed it up, but I put the .cue through chdman, dropped the resulting .chd in my tg16 (pcengine) folder, fired it up, and was pleasantly surprised when it worked just fine.

@cherbakalite @ChaosEffect an alternative if you don't want to bother changing device types for console games (including megadrive) is to use FBNeo : every emulated console game has the "optimal" controller settings hardcoded.

@w1ck3rm4n we need the log file.

https://retropie.org.uk/docs/Runcommand/#launch-with-verbose-logging

Launch with verbose logging. Copy the log and post it here (via pastebin.com).

An easy way to access the log file (if your Pi is on your home network) is copy it to your roms folder, where you can access it from the network share. Press F4 on your keyboard to exit EmulationStation, then copy the log file with the command:

cp /dev/shm/runcommand.log /home/pi/RetroPie/roms

Then you can access it through the network share from a Windows computer on the same network, by navigating to \\retropie (if your network doesn't recognize hostnames, you can try \\your.pi's.ip.address) in a File Explorer window (you'll have to open "roms," the log file will be inside it.)

@mitu Would one land in another shell, then? If so, a quick emulationstation should restart ES, which may be a little less invasive than to restart the whole system with REISUB. (Just hypothesizing.)

@jhstoke what image did you install? please fill out all of https://retropie.org.uk/forum/topic/3/read-this-first

config_hdmi_boost is ignored for raspberry pi 4 btw.

Here is the part of /opt/retropie/supplementary/runcommand/runcommand.sh that displays the launching image using either feh or fbi. If you're good with scripting, maybe you could jigger it to play a video with vlc or omxplayer, instead:

function show_launch() { local images=() if [[ "$IS_SYS" -eq 1 && "$USE_ART" -eq 1 ]]; then # if using art look for images in paths for es art. images+=( "$HOME/RetroPie/roms/$SYSTEM/images/${ROM_BN}-image" "$HOME/.emulationstation/downloaded_images/$SYSTEM/${ROM_BN}-image" "$HOME/.emulationstation/downloaded_media/$SYSTEM/screenshots/${ROM_BN}" "$HOME/RetroPie/roms/$SYSTEM/media/screenshots/${ROM_BN}" ) fi # look for custom launching images if [[ "$IS_SYS" -eq 1 ]]; then images+=( "$HOME/RetroPie/roms/$SYSTEM/images/${ROM_BN}-launching" "$CONF_ROOT/launching" ) fi [[ "$IS_PORT" -eq 1 ]] && images+=("$CONFIGDIR/ports/launching") images+=("$CONFIGDIR/all/launching") local image local path local ext for path in "${images[@]}"; do for ext in jpg png; do if [[ -f "$path.$ext" ]]; then image="$path.$ext" break 2 fi done done if [[ -n "$image" ]]; then # if we are running under X use feh otherwise try and use fbi if [[ -n "$DISPLAY" ]]; then feh -F -N -Z -Y -q "$image" & &>/dev/null IMG_PID=$! sleep "$IMAGE_DELAY" else fbi -1 -t "$IMAGE_DELAY" -noverbose -a "$image" </dev/tty &>/dev/null fi elif [[ "$DISABLE_MENU" -ne 1 && "$USE_ART" -ne 1 ]]; then local launch_name if [[ -n "$ROM_BN" ]]; then launch_name="$ROM_BN ($EMULATOR)" else launch_name="$EMULATOR" fi DIALOGRC="$CONFIGDIR/all/runcommand-launch-dialog.cfg" dialog --infobox "\nLaunching $launch_name ...\n\nPress a button to configure\n\nErrors are logged to $LOG" 9 60 fi }

You can see where it shows the paths and filename-patterns to look for art, (near the top) and where it defines the accepted extensions (for ext in jpg png; do). You'd want to change this part to include mp4, or whatever format your videos will be in, and possibly also add paths above to include ${ROM_BN}-video or similar if that's how you'll name them.

Then there's the part where the image is displayed with the feh or fbi commands. You'll need to craft a command with the proper options to show your brief video snap, probably with either vlc or omxplayer. Probably also a check on which extension is used to determine whether to use the video or image command, unless you're going to only have videos, and then you'll need to remove the parts referencing images at all, including the "ports" and system-wide launch images (or change them to use the videos too.)

@greenhawk84

Click on the thread below. It should solve your problem.

RetroPie - Convert Non-Functional videos to functional videos - Easy free batch method on Windows - also size reducer