@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

Alright, update, it is still possible. I modified the code in the original post to create folders based on the game name instead of relying on ps_iso_tool to extract a game ID and creating folders based on that. Seems to be working perfectly.

(I have absolutely no idea how to code, so I'm kinda shocked I was able to figure this out.)

@stoney66 well - switched the roms and now they work. Centipede, Missile Command, Golden Tee 2 are all working now under AdvMame. Marble Madness is still unhappy, but I would assume that's still just a rom issue. I think this issue is likely resolved now. Thank you everyone for your help! @mahoneyt944 and @stoney66

@mitu
Ah ok.
Yes I meant simply a hard link but didn't realize it wouldn't work due to crossing over to a separate filesystem.

@sleve_mcdichael thanks

This continues to be an issue on x86 builds. I have opened an issue on the RA github but don't have much hope of it getting any traction.

https://github.com/libretro/RetroArch/issues/12312

I updated the original post to say that I am not seeing this issue on older versions of RA (specifically 1.7.3 anyway).

Is there ANYONE else that has 4x genuine PS sixaxis dualshock controllers that can verify what I am seeing? If so, this may give us enough ammo to push the issue with the Libretro team.

John

@chaoseffect you should ask at https://github.com/libretro/snes9x/issues and/or https://github.com/snes9xgit/snes9x