SD Save Sector Reservation List: Difference between revisions
mNo edit summary |
mNo edit summary |
||
| Line 29: | Line 29: | ||
For the "Small Saves" spot, denote bytes used as ".start_bit..end_bit". This is for games only requiring a few bytes to store the last level completed or such and avoid wasting most of a sector. | For the "Small Saves" spot, denote bytes used as "sector_id(sector_id_hex).start_bit..end_bit". This is for games only requiring a few bytes to store the last level completed or such and avoid wasting most of a sector. | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
Revision as of 06:21, 8 April 2016
The SD Save API functions are based on reading and writing sectors in a common fixed size SD save file for all games named "_HISCORE.DAT. This allows games to use the smaller SD libraries that do not support creating new files while simultaneously easing pressure on limited EEPROM. As a usage example sector 0 is reserved for the kernel and would start at SD offset 0, whereas sector 143 would start at SD offset 143*512=73216. Reserve one or more sectors for your game here. To view, edit or remove the sectors on your SD card, see the emuze tool. For examples of implementing SD Saves see [Implementing SD Saves]
| Sector | Owner | Game |
|---|---|---|
| 0(0x00)-7(0x07) | Kernel | Reserved |
| 8(0x08)-15(0x0F) | Emuze | (EEPROM swap space) |
| 16(0x10) | D3thAdd3r(Lee Weber) | Toorum's Quest |
| 17(0x11) | Free Use | Small Saves |
| 18(0x12) | Free Use | Small Saves |
For the "Small Saves" spot, denote bytes used as "sector_id(sector_id_hex).start_bit..end_bit". This is for games only requiring a few bytes to store the last level completed or such and avoid wasting most of a sector.
| Offset | Owner | Game\ |
|---|---|---|
| 17(0x11).0..5 | D3thAdd3r(Lee Weber) | Alter Ego |