Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Idea: Use bookmark.device to back resload_SaveFile #5

Open
timfel opened this issue Dec 14, 2023 · 1 comment
Open

Feature Idea: Use bookmark.device to back resload_SaveFile #5

timfel opened this issue Dec 14, 2023 · 1 comment

Comments

@timfel
Copy link

timfel commented Dec 14, 2023

First, thanks for reviving this awesome project, it's a joy to be able to use WHDload slaves on my CDTV from CD :-)

I was thinking, what about those games that want to save relatively small savegames or highscores? Afaics whdload's resload_SaveFile redirects to WriteFileHD. Could we add the required routing to try to save it as a CDTV bookmark instead?

Since bookmarks aren't really addressable like a filesystem, but there are 32bits, so mapping the slave into the 16 "manufacturer id" bits and doing a CRC for the filepath into the 16 "product id" bits might give few enough collisions for most game's purposes to be feasible. Then it only depends on how big the savegame is. IIRC the CDTV has only 4K of bookmark memory built-in, of which it will refuse to hand out more than 256 bytes to any one bookmark. But with a memory card, more would be available, and the code is analogous (just trying to open "cardmark.device" instead of "bookmark.device")

Is that something you think would be feasible and worth trying?

@jotd666
Copy link
Owner

jotd666 commented Oct 9, 2024

Hi,

Unfortunately, specially on CDTV JST is taking over the system not to ever return. So it means that this bookmark device would need to be hardware banged on top of everything, and I'm not ready for that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants