Strobe

Monitor fill, move commands affect both VDC and c128 RAM simultaneously

Confirmed fixed, thank you!

Monitor fill, move commands affect both VDC and c128 RAM simultaneously

Add MMU chip markings from Strobe's flat PAL c128.

Update with results from Strobe's flat pal 128 for tests 16, 18-21

Update NEWS with various stuff I poked at for 3.6, including one I forgot to add to the 3.5 notes.

Just tried one of the suggested examples, -moncommands with simply "m 1000" in a text file and trunk (r41107) hangs immediately using 100% of a core and has to be killed from task manager. A command that "waits" for the machine to be ready like the below works fine: autostart "myfile.prg" So maybe -moncommands should not be executed until the same conditions are met that autostart waits for? (which then makes it hard to debug things happening before then I suppose..)

Issue 1 is fixed in r40618 with some improvement to the VDC busy state emulation, cycles per line now varies slightly between runs as expected. Issue 3 would be resolved implementing R34/35 (horizontal blanking) support in the renderer. Last time I tried to do that the raster code got in the way by drawing the border when we didn't want it to, and raster is an undocumented pile of spaghetti code.