Ugh, it could be a translation table of some kind. Maybe they really are changing the value of 0xf3 and its kin, elsewhere in the prog.
Sadly, that doesn't explain the rest of the mess.
Ugh, it could be a translation table of some kind. Maybe they really are changing the value of 0xf3 and its kin, elsewhere in the prog.
Sadly, that doesn't explain the rest of the mess.