You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First off the number of issues is not a critique on the tool..it is awesome as-is. Just throwing ideas out there since I'm now using it in MODE.
Would it be possible to have the copier also allow for a complete internal back-up as opposed to one-off saves? Maybe with a timestamp function so you can save and restore off multiple instances? Obviously this wouldn't have made sense in the pre-ODE days, but with satiator and MODE using the tool now, it makes more sense.
The text was updated successfully, but these errors were encountered:
I have the "Dump Memory" and "Write to Memory" options. According to my notes Internal backup memory (address: 0x00180000, size: 0x001FFFFF) is that region. I believe that's the entire mirrored memory region so I think you would want 0x10000 as the size. I'm fairly confident you can dump the entire region. I'm not as confident what happens when you try to write back to the entire region...
You should also be able to dump your Saturn BIOS to MODE's SD card by dumping from address 0x80000 size: 0x80000. Unfortunately it will take forever as the BIOS is 512k
I know neodev from TO built an entire separate function outside of Copier to handle this and it both saves and restores but it only saves off one save at a time. Might be worth conferring with him on this one (or he can take a stab at it himself when he has time).
First off the number of issues is not a critique on the tool..it is awesome as-is. Just throwing ideas out there since I'm now using it in MODE.
Would it be possible to have the copier also allow for a complete internal back-up as opposed to one-off saves? Maybe with a timestamp function so you can save and restore off multiple instances? Obviously this wouldn't have made sense in the pre-ODE days, but with satiator and MODE using the tool now, it makes more sense.
The text was updated successfully, but these errors were encountered: