What did you mean with this? If I use RemApollo, kickstart survives reset and it is located to fast ram. Is it so that MuFastZero does it differently? But still using it locates my real rom to Apollo's 32 bit fast ram.
You are confusing two things. The location of the ROM, and the location of "struct ExecBase". The ROM contains the code and the functions, "struct ExecBase" contains the jump-table into the ROM. The ROM builds this jump-table, in the highest-prioriy memory available at boot time, which is any memory added to the system by Auto-Config, or - failing that - chip mem.
The ROM is remapped by MuFastROM, it mirrors the ROM contents into the highest-prioritized memory available at the time it is executed. But it does only that. It does not attempt to mirror "struct ExecBase" because - if the designer of the board did his job right - this structure *is* already in fast memory. If the job was not done right and they just "fiddled the memory into the system somehow", then "struct ExecBase" will end up somewhere, in worst case in chip mem. In that case, you need *in addition* use MuFastZero/MuMove4K. The latter "tags" the memory for execbase such that no graphics memory is allocated in its place, the former then performs the remapping to fast memory.
Once again: ROM != "struct ExecBase", and the only reason why you have this problem is because the designer of your turbo board was lazy and did not make the memory on the board auto-configuring, but fiddled it into the system in some non-documented way that bypasses the expansion library.
