Return to previous page | Return to menu | Go to next page

2> System regulations

The basic system flow is shown in Appendix 1-1. The processes, functions, and messages shown in this flow must be included.

− Figure Separate Volume 1-1. Basic Backup System Flow −

* The flow may differ depending on the application.

Initialization check

Be sure to check the initialization of the main unit RAM and cartridge RAM before the main game starts.
If either one has not been initialized, do not start the game. In this case, inform the user to that effect and urge the user to perform the initialization work directly in the application or to perform the initialization process on the saved data management screen in the Sega Saturn main unit BOOT ROM.

* Be sure to use the BACKUPRAM BIOS when accessing the backup RAM.
* Do not format the main unit RAM, cartridge RAM, or extended memory using any method other than the SEGA SATURN_BACKUP_FORMAT method.

Existence / capacity check

Before the main game starts, check the existence of data that can be used by your application, and check the remaining capacity of each backup RAM.
If your data does not exist or the remaining capacity is insufficient, a warning message will be displayed depending on the situation. (Specific message content will be described later)

Load

Always check for data corruption when loading data.
If the data is in an unusable state, the user must be notified and the data must be displayed in some way distinct so that it can be seen as unusable.

save

=== Regulations for recording ===

<About format>

• Do not divide the record unnecessarily. (In principle, one record for each save)
• Do not format it so that you will not be able to play completely if any one of the records is missing (it is possible to have records for each independent mode)
• The maximum number of records for each type is 99 (_01 to _99).

<About the name>

• In order not to use the same record name in different games, the "record name" at the time of saving is managed by SEGA (Second Design Department).
• Only numbers, uppercase letters, and underscores can be used in record names. However, do not use numbers for the first letter. (See Appendix 1-1)
• Be sure to use 11 characters for the name of the record. If it is 11 characters or less, fill it with an underscore (_) to make it 11 characters. No space is allowed.
• When saving multiple records in one game, the first 8 letters are unified, and the 3 changeable letters are composed of underscores (_) and numbers.
• The number of records is limited to 99, and the three characters that can change the name of the record are from _01 to _99.
• Do not use generic names that are difficult to identify, such as GM_DATA_000.

  Example) In the case of "Panzer Dragoon" (3 saves are required)
  1st place: PANZER_D01
  Second place: PANZER_D02
  Third place: PANZER_D03
  └─┬──┘ └┬┘
  │ Only 3 characters can be changed 8 characters are common

<About usage>

• When describing the "usage" of the record (data), use the value calculated according to the following formula.

  Usage = ([Number of bytes used] +32) ÷ 64

• In principle, the unit of usage is not attached , but if it is absolutely necessary to write it, use the word "block".
• The amount of recording used should not exceed 256 Kbytes. (Restrictions due to the program specifications of the copy function of the main unit BOOT ROM)
• If the recording usage inevitably exceeds 256 Kbytes, be sure to handle it so that the application can copy it.

Comment support

Be sure to include any comments. Be sure to use ASCII characters (half-width alphanumeric characters, numbers, kana, see Appendix 1-1) for up to 10 characters.
Comments are for knowing the contents of save data in more detail, so make effective use of them in each application. If you cannot find the intended use, enter the game name (information that can be identified) in katakana.

Example) Example of effective use of comments PANZER_D_01: 5 Men-Boss (Continue information)
PHANT_ST_01: Alefcardo Nomachi (name of the saved town)
SEGARACE_01: Time Attack M (mode name)
DERBY_ST_01: Mochikane 69 (ranch name)

* It is up to the user to freely rewrite the content of the comment.

Supports time stamps

The time stamp must be included and cannot be rewritten by the user. In principle, the records are displayed in ascending order of this time stamp (newest order of saved dates).

Main unit RAM / cartridge RAM selection

All backup-enabled applications must ensure that their records can be stored in either the main unit RAM or the cartridge RAM. In principle, even if the amount of recording used is too large to fit in the main unit RAM, the main unit RAM can be supported by a simple storage method.

* Except for extremely trivial recorded contents (only high scores of shooting games, etc.) * There is no particular rule as to where this selection should be made in the sequence.

* All characters can be used for "comments". Only the part of can be used for "record name".

− Table Separate Volume 1-1. Record Name / Comment Usable Character ASCII Table −

Return to previous page | Return to menu | Go to next page