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-11 13:10:11 +02:00
2017-06-15 18:52:22 -04:00
2017-07-07 16:44:38 -07:00
2017-06-06 16:27:52 +02:00
2017-06-06 16:27:52 +02:00
2017-06-28 11:22:10 +02:00
2017-06-28 11:22:10 +02:00
2017-06-28 11:22:10 +02:00
2017-04-25 09:20:09 +01:00
2017-03-27 23:46:19 -04:00
2017-06-06 16:27:52 +02:00
2017-06-07 01:20:48 -04:00
2017-03-18 21:13:12 -04:00
2017-01-12 21:30:11 +01:00
2017-06-28 11:22:10 +02:00
2017-06-28 11:22:10 +02:00