Difference between revisions of "Talk:83Plus:OS:Variable Storage in the User Archive"
From WikiTI
m |
(→Application size) |
||
| Line 7: | Line 7: | ||
It'd be nice if someone who know about this sort of thing to explain how to do this in more detail. For that, we need more general information on parsing headers. | It'd be nice if someone who know about this sort of thing to explain how to do this in more detail. For that, we need more general information on parsing headers. | ||
[[User:Dr. D'nar|Dr. D'nar]] 22:17, 10 October 2009 (UTC) | [[User:Dr. D'nar|Dr. D'nar]] 22:17, 10 October 2009 (UTC) | ||
| + | |||
| + | As far as I know, every fields in app header (save for the date stamp) start with $80 and a byte whose first nibble indicate field type and second nibble indicate field size. The only exception appears to be the two fields of size four for which the "size nibble" if F... Some investigation in the OS implementation of field search might clarify this... [[User:fuulmetalcoder]] 14:59 13 October 2009 (GMT+2) | ||
Revision as of 05:01, 13 October 2009
Application size
BrandonW had this to say on the page:
<BrandonW> That "401Ch" thing for the app size, that's completely wrong. <BrandonW> You have to use the field search routines to find it. <BrandonW> Just because it's at 401Ch on one doesn't mean it'll be there on another.
It'd be nice if someone who know about this sort of thing to explain how to do this in more detail. For that, we need more general information on parsing headers. Dr. D'nar 22:17, 10 October 2009 (UTC)
As far as I know, every fields in app header (save for the date stamp) start with $80 and a byte whose first nibble indicate field type and second nibble indicate field size. The only exception appears to be the two fields of size four for which the "size nibble" if F... Some investigation in the OS implementation of field search might clarify this... User:fuulmetalcoder 14:59 13 October 2009 (GMT+2)
