I just created a group and checked it in Calcsys. It seems to be oredered like this:
-The first byte was $FC. I have no clue why.
-Next two bytes are the size of the group (little endian)
-Next comes the VAT entry (since it is archived)
**See below for a breakdown of archived syntax**
-After this is the size bytes of the data. This is two bytes in little endian
-After that it is like reading archived variables

Archived syntax: (the 00 means the first byte, 01 is the second byte...)
00-type
01-reserved for future OS changes
02-archived status. This will be 0 since groups can only have vars in RAM selected
03-Address where the var was before grouping. two bytes, little endian
05-forgot, actually, but this seems to be 0
06-size of the var name followed by the name
 n-After this is two size bytes, followed by data

Does this help?

At the "n" is where you will find it.

Also, I think we read minds, yeong I was working on an extractor (but written in assembly code). It was just going to let people run BASIC programs/ Assembly programs from groups and recall pictures.

O.o that would be so awesome, than even basic would become much more editable (like levels etc)

Quote from: TBO_Yeong on January 03, 2012, 01:43:33 pm

Can you add appvar support as well?

What do you mean by that? As in executing appvars from a group as BASIC or assembly programs or recalling them as pictures? Or do you mean extracting appvars?

I mean by extracting appvars.

Oh, cool! I could have some fun with this!