Well, I managed to fix this issue. The fix is odd and probably specific to Dell machines but go into the BIOS and go to General -> Advanced Boot options, Untick Enable Legacy option ROMS

Machine now boots fine with joystick connected....

@acris I'll give it a go, thank you.

@bryceone I already have no suggestions ... how do you connect the PC to the monitor: VGA cable? Do you have an adapter? What is your monitor? Have you tried another?

I totally understand that. With the Storage option in Recalbox set to AnyExternal, Recalbox was writing boot profiles to every device I plugged in. Since a fresh boot profile gets written, so do basic Kodi files, and every time I'd inadvertently load a boot profile from a drive I didn't intend to, loading either RecalBox or Kodi resulted in my entire rom/media libraries getting overwritten.

I fussed with that option so much trying to get it to work that I was scared of booting into RecalBox with my external hard drives plugged in at all; which means I never saw the option to set a static individual drive as a Storage option.

@retrohpbox
Tu as pris quelle image recalbox ?
La PC 64 bits ou la PC 32bits

@najaray you're NOT the only user using an odroid C2, so instead of saying the img is corrupted, please give us more informations.

I found the solution. Get in the emulationstation config and set the font to "false".

@zhidd can you explain how to use plop ?
i have the same PC (SFF dc 7900 ) with a Sapphire HD5450. I do not manage to boot on USB Stick with last Recalbox :(
I try to boot with plpbt.img on usb Stick...but nothing.
Thx.

@voljega I thought of that. And I think they are good. I did get Pinball Dreams to boot as an adf on the 1200, so I'm thinking there might be some other issue going on.

here's a link to the launch attempts with several games.

https://file.ac/je5ldPbU4yY/

Die pc 64bit version lässt sich auf dem EeePC erst gar nicht starten also fällt diese schon mal weg. Hätte mich auch gewundert da die verwendeten Komponenten dort einfach zu alt schon sind.

@anonpebbles you should have 3 partitions, at least. What you mebtiin is the 1st partition used for boot. If you ever reach es, try to make a support archive. Otherwise you may have to laje an img of your sd, upload it si that i can check some logs. But insee no reason why it would reboot

@flibb 4.14 ? Nah, just get raspbians boot files but the kernel. Sonfar you're the 2nd one not being able to have a working screen

Hello,
Do not forget to put the right bios and flash files in the bios folder.
wiki

About Shenmue II, it does launch but crashes right after the intro.
Shenmue 1 is OK (with some glitches).

I am really impressed by the pi able to launch DC games. But the reicast emulator is far from stable and it only launches and emulates correctly less than 50 games (I tried more than 100 games, sometimes both .cdi and .gdi files). And then the pi lacks some power to play the remaining playable games at full speed. At the end only around 15 games are worth adding to the Recalbox.

Have fun !

@substring said in Not booting:

@thejim Hi

You're not telling much ... I guess your laptop has UEFI enabled. Try to boot in legacy BIOS moden, or disable UEFI security

Nope my computer isn't in UEFI. It's from 2008 ;)

I'm able to boot on USB to install Windows and Linux but not with recalbox

Never mind it was an issue with the hdmi cable being dirty oops

@Cecil because any ATI GPU is a pain so far

@subs

So here is what worked.

config_hdmi_boost = 10

hdmi_group=1

hdmi_mode=16

Uncommented hdmi_safe=1

When setting config_hdmi_boost to anything lower than 10 it bombed fabulously, at least on my 40" screen in my bedroom. And when I say bombed, I mean that it would boot up, and I could choose a rom. But as soon as the rom loaded, the pi would reboot and get stuck in a reboot cycle.

After setting it to 10, everything ran smoothly. I have only tested SNES and GBA roms at this point. We'll see how playstation and others work tonight =)

Thanks for all your help!

Edit your fstab file for the UUID of your HDD partition.  I prefer UUID as it doesn't tend to change by moving drives around.  You can edit the fstab file and change the mount point of the /dev/whatever to UUID=uuid of your partition  /share (partition type without parentheses<span style="line-height: 1.5;">) (options without parentheses)</span> That fixes any problems I've had with things moving around or mounting in the wrong place.