@heatseeker It is not so simple, dual boot with windows is very annoying, you have to redo grub, and originally the SHARE partition is not visible in Windows, as some imagine, because it is in a format that is only recognized by Linux.
The most complete tutorial I know is: https://forum.recalbox.com/topic/15678/dualboot-recalbox-windows-sur-pcs-laptops-avec-bios-ou-uefi
It's in French, but you can use google translator like I do.
If you google search, you'll find other tutorials too, but what I know is this. Recalling that developers do not recommend dual boot, for several factors, but it is possible.
I do not know the computer you're quoting, but are you sure it's compatible with Recalbox? I know the current BETA is getting very good, and very compatible, but I can not say it's compatible with the model you mentioned (I'm not saying it's not compatible, I'm making it clear that I do not know this computer model, and I do not know if it is), if you're sure it's compatible, great.
If you don't have a second system around, you could also boot the target system using any live Linux distribution available on CD or DVD, e.g. Debian or Ubuntu.
Then within that running Linux system, download the recalbox image and burn it (with etcher or any tool you like) onto the hard disk.
Okay je viens de comprendre. Je vais donc réinstaller RecalBox + Raspbian pour recommencer... car aucun jeu ne marche (MarioKart sur N64, mais aussi d'autres jeux sur SuperNintendo, etc.).
Si tu sais comment réinitialiser RecalBox sans avoir à le réinstaller, je veux bien ^^
@juhapik Thanks for the attention, but it always worked and this questioning was before installing the first unstable version made available through update 4.0.1, these doubts were resolved 2 months ago
The main reason it's easy on retropie and complicated on recalbox, is that retropie sits on top of an existing OS. That OS already has the compilers to add anything new, so they just have to script the copiling and tadaaaaa
That's not our case. We use something called buildroot which is something that can cross-build a linux for any system (pi, x86 allwinner etc ... anything almost). To add new softwares (don't expect buildroot to provide emulators haha), we need to write packages telling buildroot how to compile. That's the main difficulty. As long as an emulator/game exists on Linux, we have to write a package telling Buildroot how to cross compile it for our target architectures (so far : pi, xu4, and x86 is on its way). That can be tricky (most packages need some patching on their makefiles), takes days, sometimes weeks to be able to do that.
Next, to make the recalbox magic work (= coniguration-less emulator) you have to understand how the configuration files are generated, how they handle input devices, where they are stored etc ... Sometimes it's quite easy, sometimes it's a real pain in the @$$ (i'm talking about PPSSPP ... took me weeks). From time to time we have to patch the emulator to fit our directory structure.
It takes time, our free time that we spend (and even devote !) to recalbox to make the magic happen