WHDLoad and 68060 issues with image corruption

[Betelgeuse]

I have an A4000 with Cyberstorm MK2 and 128MB of Cyberstorm RAM, 2MB Chip RAM, and I think another 16MB of A4000 Fast-RAM (all motherboard RAM slots populated), Picasso IV also acting as a flicker fixer for WHDLoad games. The problem is when running WHDLoad games with tooltips set to CACHECHIP and DCACHE, some games show image corruption, particularly in text. For some games the issue is minor, for others it makes the game unplayable (like ST: 25th Anniversary). Setting the flag CHIPNOCACHE solves the corruption, but makes some games a lot slower (like Tornado AGA or Robinson's Requiem AGA, Star Trek runs fine then and is plenty fast). There is no corruption when running these games from a regular install, not thru WHDLoad (the latter is more convenient though). Is there any way to avoid the corruption issue?

[Betelgeuse]

Of course. Chip memory is not cacheable simply because the data can change under the CPU any time by using the blitter without the CPU cache noticing the change. Caching requires that the memory contents does not change by any means but the CPU.

Hence, CACHECHIP is certainly a pretty bad idea - as you observe.

Makes sense, but why then have the option in the first place?

[Betelgeuse]

I looked through the docs, and only find "ChipNoCache"

http://www.whdload.de/docs/en/opt.html#ChipNoCache

http://www.whdload.de/docs/en/cache.html#chipmem

I think chip caching is on with the DCACHE tooltip, some readme files mention CHIPCACHE but I also didn't see it in the docs. So in the end DCACHE turns on all caching including chip caching. How does it differ from the CACHE command or what's turned on with SetPatch and the CPU command?