Get into Fastram you naughty EXEC

[matthey]

Build your own custom ROM with Remus...

http://www.doobreynet.co.uk/beta/index.html

Apply patches and updates like these...

http://amikit.amiga.sk/patches.htm

and kick the ROM image into your FastROM with this...

http://aminet.net/util/boot/BlizKick.lha

[matthey]

Seems like it might not be such a good idea to move expansion.library into FASTRAM

Yes. I BlizKick my own custom kickstart and the expansion.library is NOT in fast ram. It's the only library not in fast ram.

[matthey]

I run MuFastZero in my startup-sequence and my expansion.library in still not in fast ram. I expect there is a good reason for this. Probably because chip ram is always at the same location and doesn't go away at reset which makes life at startup much easier.

[matthey]

@Piru

Interesting. Obviously, with MAPROM, one copy of the expansion.library would be in fast ram. If that copy were used then what program would map it into the lower memory address? The MAPROM code? The AmigaOS doesn't touch the MMU as far as I know. You would probably know if BlizKick did it. I wouldn't think there would be any need to do so by the time the 680x0.library starts. Maybe the address is in the ROM and not chip ram. I'll have to have a look at the address again. If the expansion.library in the ROM is always used then maybe the expansion.library would be unnecessary in the MAPROM kickstart. I'll have to do some investigating.

[matthey]

My expansion.library memory address ($46CC) shows up as being in chip memory in Scout.

$0-$200000 chip memory
$F00000-$1000000 motherboard ROM

The MMU would have to map some of chip memory somewhere else and then fast memory to the old chip memory location for the expansion.library being used to be in fast ram. I highly doubt that. It looks to me like the expansion.library is actually in chip ram.