Does anyone have any info on this? Looking through my Starfox Adventures ROM, there's several files that have a .zlb extension, and have one or more ZLB markers/headers in the files (some only have a .bin extension instead of .zlb). I've been googling for information related to this for a couple days, and it's been mostly fruitless so far.
At first, I thought it migh t've been some kind of packfile/compression marker. After googling for a bit, I found that ZBL is short for Zero-Length Body, which is basically a control packet with an empty L2PT header. After looking over the specs though, it doesn't seem to be valid as the "version" is set to 0, and the specs say it must be 2. It also says a ZLB is a control packet, yet the control bit is off.
Scoping out the data reveals that each of these ZLB "blocks" starts with:
"ZLB\0" (the letters Z, L, B, and a NULL byte) 0x00 0x00 0x00 0x01
From here, things start getting funky. According to this output, the further along you follow the data, the more likely it is to not be identical. Early on, it appears to be uniform and patterned in some way. About 16 bytes out, it appears mostly "random", however, some blocks remain identical for several more bytes (and by several, I mean around 32 more bytes or so). I see nothing indicating the length of these headers, or how to decode the individual blocks.
At this point, I have no real idea of where to go to figuring out this format. If anyone has any clues or information about what this might be, I'd love to hear.
At first, I thought it migh t've been some kind of packfile/compression marker. After googling for a bit, I found that ZBL is short for Zero-Length Body, which is basically a control packet with an empty L2PT header. After looking over the specs though, it doesn't seem to be valid as the "version" is set to 0, and the specs say it must be 2. It also says a ZLB is a control packet, yet the control bit is off.
Scoping out the data reveals that each of these ZLB "blocks" starts with:
"ZLB\0" (the letters Z, L, B, and a NULL byte) 0x00 0x00 0x00 0x01
From here, things start getting funky. According to this output, the further along you follow the data, the more likely it is to not be identical. Early on, it appears to be uniform and patterned in some way. About 16 bytes out, it appears mostly "random", however, some blocks remain identical for several more bytes (and by several, I mean around 32 more bytes or so). I see nothing indicating the length of these headers, or how to decode the individual blocks.
At this point, I have no real idea of where to go to figuring out this format. If anyone has any clues or information about what this might be, I'd love to hear.