Reicast VMU saving and "Boot to BIOS"-Crash

Libretro Cores
#9

While the BIOS time and date setup bug is still present, you can fix the VMU loading/saving. As DK999 said it works for Demul, it also works for NullDC.

Take a save file from NullDC called vmu_data_port01.bin and copy/overwrite it to vmu_save_A1.bin, vmu_save_B1.bin, vmu_save_C1.bin and vmu_save_D1.bin in /system/dc of Retroarch.

#10

You can work around that bug by placing this file in system\dc: https://github.com/libretro/reicast-emulator/blob/master/WorkDir/data/dc_nvmem.bin

#11

Didn’t work for me. It is still asking for date/time. Using Reicast from 09-24-2016 since the latest core is broken for Nvidia as it seems.

#12

Huh, it worked for me originally, but now trying again I’m getting the time enter screen every boot :confused:

#13

Did you figure any other solutions out?

#14

Nope. The guy who originally provided the nvmem file said it stopped working for him too :confused:

#15

Bummer. Also doesn’t look like RetroArch recognized AHK keystrokes. Was going to try to script my way around it

#16

Use SetKeyDelay, -1, 110 before any Send AHK commands and they will work with Retroarch.

#17

Can you post a full example? Thanks so much for sharing!!!

#18

; Pause 4Joy20:: SetKeyDelay, -1, 110 Send {p} Return

I use this small AHK script to map button 20 of my 4th gamepad to send P (Pause) to Retroarch through the Launchbox frontend.

The SetKeyDelay AHK command keeps the button pressed for 110ms so Retroarch can read the key. Without SetKeyDelay some emus can’t register the key-presses because they happen too fast.

(MAME is a special case which requires the command line parameter: -keyboardprovider dinput so it can recognize the AHK dinput commands.)

#19

Hey guys! I had the same problem, and renaming files and stuff did not work for me, I found a thread of somebody that shared his dc_flash.bin file with everybody. Since then its been working flawlessly for me.

Just download this dc_flash.bin and override the one you have. Should not ask for the date/time anymore:

Let me know how it goes!

1 Like
#20

Be careful with BIOS files from unknown sources! For example the dc_flash.bin you posted does not match any of the known MD5 posted here: https://github.com/retropie/retropie-setup/wiki/Dreamcast

Check with: http://onlinemd5.com/

#21

MD5sum is not listed because the dc_flash.bin was modified from a dc_nvmem.bin to override this time/date scenario. If you do not trust the file, you can give it a try in a sandboxed environment. Just my two cents for everybody struggling with this matter.

Cheers!

#22

Hmmmm. This didn’t work for me

) :

#23

Any tips to get it working? Could you share all your system files for DC? Maybe one of my other files conflicts?

#24

Hey newoski! I have zipped my system/dc folder in the below link; make a backup of your folder first just in case, and give it a try. You can run antiviruses or whatever you want on it. Hope it works for you :slight_smile:

1 Like
#25

Thanks! Will post results of test in AM

#26

THANK YOU SO MUCH!!

Worked perfectly. No more date/time prompts.

1 Like
#27

Glad to hear newoski :smiley: If more people having the time/date issue can check my upload and see if it gets resolved, maybe we can leave it posted somewhere that won´t expire.

2 Likes
#28

That’s awesome someone fixed this. It’s not a huge annoyance, but it was an annoyance for sure. I’ll be sure to try this out later tonight.

Thanks for posting that :smiley: