Remapollo - stuck in a reboot loop

[humppa]

I recently put Remapollo in my startup-sequence in order to remap Kickstart 3.1 to the Fast-Mem of my Apollo 1240.
Altough I went through the guide several times I unable to set it up correctly.

The problem is that I am stuck in a reboot-loop which seems to be caused by combining Remapollo with Setpatch.
I already tried to change the order of DRAP, Remapollo and Setpatch but it did not help:
Remapollo->Reboot->Setpatch->Reboot->Remapollo-> (...)

Do I have to use the Remapollo-modules for OS 3.9? Or do I have to SKIPROMUPDATES with Setpatch?

The best would be if somebody could post a startup-sequence in which Remapollo, Setpatch and OS 3.9 are combined.

Thanks for any help!

[Lemmink]

All those maprom tools for accelerators try to map the original physical ROM that sits in the sockets into RAM.
The ROM-Updates of OS 3.5/3.9 do the same but also modifiy the ROM by replaceing some parts with newer Versions.
After that you have two different ROM-Images in RAM that do collide and cause a reset.

So you either leave remapollo, when useing the ROM-Update of OS 3.5/3.9 as it is useless anyway, or you keep remapollo that maps Kick 3.1 and leave the ROM-Update by either set the option skipromupdate or deleting the ROM-Update file alltogether.

[humppa]

Thanks your for the answer! So that means that there is no advantage (speedwise?) of using Remapollo over the romupdate using Setpatch?
If that is true I see no point in using Remapollo since it even takes the "old" physical ROM instead of Setpatch which replaces some parts with newer versions/patches.