I think I found the answer to the hard drive install. Apparently you can use etcher and write the image to a hard drive. There isn't a whole lot of details but I think I can figure it out.
I tried running recalbox on a shuttle PC (sb61g2) which I believe came out in 2004 and has a 3ghz P4 in it but either it can't run it or the initial setup is taking a really long time. :0
Not to be argumentative but Intel has had 3ghz cpu's since 2003.
What about my other question; can you install recalbox to a hard drive instead of a USB drive?
I haven't seen a lot of documentation on the PC version of recalbox so if you have a link to something with more detail, it would be appreciated.
https://github.com/recalbox/recalbox-os/wiki/Install-and-Run-Recalbox-from-USB-stick
So I'd like to install recalbox on an old PC but it looks like it's meant to be ran off of USB instead of the hard drive. Is it possible to install recalbox to the hard drive instead? If so how?
I've searched but I couldn't find anything definitive but does recalbox have a minimum spec PC for the various emulators? More specifically, I'd like to run the newest emulation systems possible (ps2 and PSP would be new in my mind). I know my pi3+ can barely run PSP but what about on PC? All I've seen is that anything 2009 or higher should be enough.
Thanks
I'm testing the netplay functionality and then I host a game (launch with X) it loads the rom, a message appears on the bottom of the screen that I've joined a player 1, the title spears, and then it kicks me out to the game list menu. I can play the game locally just fine.
What issues do I need to look for? If it matters I'm trying super Mario kart for snes and I've tried super street fighter ii as well.
I'm on a 100mb wired connection.
There are a lot of fake SanDisk cards out there. Have tried testing the cards with a counterfeit program?
I'm not sure how it can work but still give you a missing bios error, unless the game and bios are from a different region.
Maybe you can post your log file.
The md5 hash (a series of numbers) is posted in that link I posted.
Download and install this program:
http://www.winmd5.com
Run the program and drag the bios file you have onto the top box of the program. It will process the file and then display a hash # and if your bios is the same as the required one then your number should match the # on the page I posted earlier.
What's the name of the bios file you are using (type it exactly as it appears on your recalbox)? Also paste the md5 hash for the file you have.
Lets focus on one psx game for right now. What game are you trying to play and what file format is it in?
Does any game on any system work? What about the games that come preinstalled?
The bios files are very particular and its easy to not have the correct ones.
This page tells you the correct names and case the bios files should be in. It also has the md5 hash so you can see how it compares to your file.
https://github.com/recalbox/recalbox-os/wiki/Add-system-bios-(EN)
So it turns out it was a combination of things.
For one, I had the wrong name for the bios file and flash file.
Two, the bios files I had did not match the recalbox md5 checksums (although I never found a checksum that matched for the dc_flash.bin file).
And finally, apparently the bios files need to go into the actual system folder and not the folder labeled "bios" (although I put them in both locations).
So far it played every image I put on it and they ran at anywhere from semi playable to playable at stock speeds on the pi3. Overclocking to 1350 yielded slightly better performance. The emulator still has a ways to go though.
For anyone looking for the correct md5 hashes you can go here, it will also tell you the correct name and location for your bios files.
https://github.com/recalbox/recalbox-os/wiki/Add-system-bios-(EN)