Difference between revisions of "/shared2/sys/SYSCONF"
(Add type for IPL.NIK) |
(Correct the file format spec to match reality and conf.c) |
||
Line 1: | Line 1: | ||
The SYSCONF contains many Wii system settings. | The SYSCONF contains many Wii system settings. | ||
− | The format of the file is fairly simple. Its size is 0x4000, and | + | The format of the file is fairly simple. Its size is 0x4000, and it contains a header that reads "SCv0", followed by the number of settings in the file (be u16), and then a list of offsets of each setting (be u16). Each setting contains first a u8, specifying the type of the value, and the length of the name. The low-order 5 bits specify the length of the name, minus one. The high-order three bits specify the type of the value, as given by the table below. This is followed by a name, in ASCII, then a value. In the case of a BIGARRAY, the value begins with a be u16 specifying the length of the data, in bytes, which follows. In the case of a SMALLARRAY, the value begins with a u8 specifying the length. |
Conventions for adding or removing settings to the file are currently unknown, but shouldn't be too hard to determine--although that's not necessarily a useful function. | Conventions for adding or removing settings to the file are currently unknown, but shouldn't be too hard to determine--although that's not necessarily a useful function. |
Revision as of 20:46, 21 August 2008
The SYSCONF contains many Wii system settings.
The format of the file is fairly simple. Its size is 0x4000, and it contains a header that reads "SCv0", followed by the number of settings in the file (be u16), and then a list of offsets of each setting (be u16). Each setting contains first a u8, specifying the type of the value, and the length of the name. The low-order 5 bits specify the length of the name, minus one. The high-order three bits specify the type of the value, as given by the table below. This is followed by a name, in ASCII, then a value. In the case of a BIGARRAY, the value begins with a be u16 specifying the length of the data, in bytes, which follows. In the case of a SMALLARRAY, the value begins with a u8 specifying the length.
Conventions for adding or removing settings to the file are currently unknown, but shouldn't be too hard to determine--although that's not necessarily a useful function.
Types Template:Table Template:Table/Header Template:Table/Row Template:Table/Row Template:Table/Row Template:Table/Row Template:Table/Row Template:Table/Row Template:Table/Row |}
Some settings from the file:
BT Settings Template:Table Template:Table/Header Template:Table/Row Template:Table/Row Template:Table/Row Template:Table/Row Template:Table/Row |}
IPL Settings Template:Table Template:Table/Header Template:Table/Row Template:Table/Row Template:Table/Row Template:Table/Row Template:Table/Row Template:Table/Row Template:Table/Row Template:Table/Row Template:Table/Row Template:Table/Row Template:Table/Row Template:Table/Row Template:Table/Row |}
IPL.SADR values: Offset 0 is a Country Code and offset 1 seems to be a more localized region code.