pouët.net

@TomCat, used it recenty in loadbar and back then for the wiki article showcase for PC speaker output. I know it since i started coding because it appears as bright green in this overview which of course caught my attention ;) There are several reasons not to use HLT though. In a normal display loop with "stosb" you don't get a notification of a frame end, you have to check for yourself (test + jnz = 4 bytes). Then you need place for a framecounter (reg/mem) and you have to increment it (inc = 1/2 bytes). Also, if you're unlucky, you get 9.1 FPS instead of 18.2 because the last timer interrupt is just over :D Here, the carryflag is set twice per frame, so it's already down to 9.1 FPS but i figured this time it's okay ;) All these problems don't occur when just using the 0x46C way. HLT + framecounter produces clean frames (no value changes midframe) but i found that pseudorandomizing the screen location worked well as workaround and even stands out as a stylistic effect (+3 bytes, see lucy). So, yeah, i'm not using it much. I'm retrying from time to time to make it work though ;)

...carryflag is CLEARED twice per frame ^^
Additional note: when doing really small intros (8b - 32b) i almost always left out time sync completely, so in the places where i could have used HLT i just spared the byte ;)