To be honest I didn't expect it to work on the TT, I was merely seeing if it had the same behaviour on the UltraSATAN and internal SCSI disk, which it didn't.fenarinarsa wrote:It won't work on TT030 anyway, I use the blitter, STE full video addressing and I change the SR value during a rte (Timer B), which is not compatible with the 68030 AFAIK. Everything can be changed to be TT-compatible but I don't know if the instruction cache will allow to execute the generated code that is loaded from disk for each frame. Is data changed by DMA taken into account by the 68030 cache?susher wrote:Unfortunately it doesn't seem to work on my 4MB STE with UltraSATAN and HDDriver 10.10. It just stops on the intro screen with only a little of the "progress bar" showing.
It does the same from the UltraSATAN on my TT030 but runs until it tries to play the sound/video on the next screen (understandably) if run from the SCSI hard disk.
Maybe an HDDriver+ACSI+UtraSATAN issue?
As for the 68030 cache, this can be turned off but the instruction pipelines could be an issue with self-modifying code I imagine if the instructions are close to those already running.
It was, and still is, a mystery to me, especially given that as soon as I turned the write-verify on it started working!I don't have HDDriver so I couldn't test it, I only have Ppera's drivers. Since it's regular GEMDOS calls it's a bit of a mystery to me
Note that when I use Ppera's drivers on Hatari with an ACSI image, it also hangs during the first load.