Changes
/* On MiST version */
Games that doesn't run are :
*'''commando.dsk''': pixels that should be deleted are not deleted (only VRAM &C000-FFFF seems used)
*'''saboteur2.dsk''': freeze (nice music and then freeze)
*'''split ink demo.dsk''': (from cpcrulez) : may help about ink raster calibration.
*'''antiriad.dsk''': no keyboard/joystick since r004.5. Until r004.4 this game run fine... It's since I added pull-up, it is not due to "no-DMA" DATA_BUS refactor (removing INOUT does not affect it (hidden version r004.4.1 run fine (no-DMA DATA_BUS refactor removing only INOUT), hidden version r004.4.2 does fail (adding pull-up in PPI inputs, and adding pull-up in DATA_BUS)). Pull-up of DATA_BUS was verified as conform. So it was abnomal that this game runs before, so I think it will come back later.
'''crazycar2.dsk''' does use lowerVRAM=10 (&8000-BFFF and &C000-FFFF area for VRAM) while overscan presentation, and lowerVRAM=00 (&0000-3FFF and &C000-FFFF area for VRAM) during play.
'''superski.dsk''' : don't forget to disable autofire, in jump, do press fire+up or down.
*'''protext.rom''': All right since r004 (before, in edit mode, if I pressed continuously one key, it did write ten letter and freeze/crash. Do note that a number is incremented in live at top right, so this is a complex software, good for keyboard vector stability tests)
*'''atomdriv.dsk''': unlocked since r004.5 (the game and music did freeze)
*'''rtypeee.dsk''' : unlocked since r004.7. Does use special read FDC cmd, with BOT different of EOT (begin of track/end of track), so reading several 512 bytes blocks in one FDC command only.
{| class="wikitable"
