CJ wrote on 17.02.09 at 08:57:40:

Yes, but I bet it detects the code and works due to a codepath rather than accurate emulation. that == FAIL!!!

I quickly looked at Hatari's C code (Why do they still code in pure C while with C++ you can produce better structured and maintainable object-oriented code? And nowadays C++ is available on nearly every platform so you don't really need C to be more portable.)

Anyway, there are functions for writes to the shifter's frequency and resolution registers. Depending on the screen location (cycle) where the write occurred and the previous state, it sets options in a bit field with line states (left border removal, right border removal, empty line/0 byte line, mid res overscan and several more.). This bit field is stored for each line which is used by the screen renderer to render the screen correctly.

Interesting read. I didn't knew there were so much options with border trickery. From the source I understand you can also make the screen smaller with 106 bytes? Which demo does that?

Robert