@patrik
I think the problem is as simple as in 1.3 chip-memory per default had higher priority than fastmem (to aid in compability with som poorly written software and hence the reason for existance of the utility FastMemFirst) and because of that everything will be loaded info chipmem first. So try loading FastMemFirst very early in your S:Startup-Sequence and see if it makes a difference.
This is not true, chip memory always has lower priority than fast memory.
What FastMemFirst does is to have slower ranger memory ($C00000) *after* other fast memory. Ranger memory is pretty much as slow as chip memory, and some memory expansions don't have priority higher than this. So FastMemFirst is there to fix this condition. It's not needed if the expansion device is using proper priority (>0) for it's memory.
Thus FastMemFirst will not help in this situation.
