Léo Lam c759739ee9 SysConf: Handle array entries properly
It turns out that the last byte of array entries isn't unused (as we
thought); instead, it looks like it's actually part of the main data,
and the length stored next to the name is in fact the length minus one.

Getting it wrong and always storing a null byte in there won't affect
most entries (since the last byte is zeroed most of the time), except:

- IPL.NIK: the length is stored in the last byte, and it must be kept.
- BT.DINF: u8 unknown[0x45] should be another Bluetooth device entry.
- Possibly other unknown affected entries.
2017-07-23 15:57:29 +08:00
..
2017-07-07 16:44:38 -07:00
2016-12-06 20:33:53 +01:00
2017-05-03 08:02:35 +01:00
2017-05-03 08:02:35 +01:00
2017-03-23 15:28:58 -04:00
2015-05-25 13:11:47 +02:00
2017-06-15 21:26:40 -07:00
2017-05-19 19:13:16 +02:00
2017-06-17 02:16:58 +01:00
2017-06-15 21:33:50 +02:00
2017-05-03 06:40:52 +01:00
2017-05-03 06:40:52 +01:00
2017-06-15 21:33:50 +02:00
2017-04-12 06:15:18 +01:00
2016-07-16 22:48:46 +02:00
2017-06-15 21:33:50 +02:00
2017-01-17 20:46:48 -05:00
2017-01-17 20:46:48 -05:00
2017-06-15 21:33:50 +02:00
2017-06-15 21:33:50 +02:00
2017-06-15 21:33:50 +02:00
2017-06-18 16:17:05 +02:00
2017-01-24 03:31:51 +01:00