The header is alsó loaded into the memory as István pointed it, just it is loaded intő system segment, and intodifferent addresses in EXOS 2.0 and 2.1. You can check István's solution in squares256 topic
It is also used in the modified version of dither256
, and actually saves more space there. On the EP64, the header is loaded to BF0Ch instead of BF08h, so the first 4 bytes (00 05 F0 00 = NOP, DEC B, RET P, NOP) are run, but the RET P does not return because B is initialized to zero.