(02-16-2022, 12:31 AM)SirRockALot Wrote: I'd also be very interested in a solution to this. This is the only thing I'd really need. It's good to hear that there is extra room in your save slot. Otherwise I'd assume there's plenty of room left in the first flash slot to store & restore multiple saves. The menu is quite tiny.
I know plenty of x86 assembly, but not sure how this would be helpful since there's no x86 anywhere on the WonderSwan? :-)
Is there any roadmap / ETA for this? The last menu update is from 2016 (!), so it doesn't seem like there is active development on it? If you told me you'll implement any kind of on-device save swapping in the next 6 months or so I think I'd simply hold off playing my WS till then. 15 game flash slots is plenty for me, but it's all a bit useless if I have to tether to a PC every time I want to play a different game and not overwrite my save.
Thanks!
Actually, the WonderSwan CPU is is 80186/x86 compatible.
Here's the current situation. We have re-started developement on this a couple times. One problem with WonderSwan programming is the lack of good development environment. I was running up against this last time I created the structure for this new menu system.
Now, the main guy helping me work on this has decided to solve the development problem by first fixing up a working and open development platform that will create .wsc binaries.
This will greatly help the WonderSwan community in general, as it should result in a "devkit" that will work on any modern platform. At least, that's the direction it seems to be pointing, at the moment.
So, once that's working, the plan is to port the menu system (or maybe start from scratch again) to the new devkit.
I have also thought about doing an interim menu update that would just use the "extra" MRAM/FRAM space to create a backup of the previous savegame. This way you would sorta have 2 savegame slots to work with. However, this also suffers from the same devkit lacking problem.
You're right about the first ROM slot having room enough for all the savegames. This is the plan. The structure has been worked out here, and it should be fine to store everything in the flash memory. Anyway, it's mostly an implementation problem, at the moment.