View Single Post
Old 01 January 2016, 10:57   #8
Toni Wilen
WinUAE developer
 
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 42
Posts: 19,522
I think this is same problem as blizkick issue after Z3 RAM was made to work like real Z2/Z3 board (matches real world behavior), it will temporarily disappear at reset and re-appear when autoconfigured again. Unfortunately early ROM patches (before autoconfig) are loaded to this RAM region too..

Adding some "CPU board" RAM should fix it.

Having Z3 RAM is very rare in real world because it is very slow compared to mainboard/accelerator board RAM. It probably happens with real hardware too if real Z3 RAM board is in use _without_ any mainboard RAM (which is extremely rare, practically non-existing configuration).

It looks like this really needs a special case where emulation works differently than in real world, Z3 RAM is very common setting in emulation.
Toni Wilen is online now  
 
Page generated in 0.08329 seconds with 9 queries