Get into Fastram you naughty EXEC

[NovaCoder]

I'm confused....again.

Specs: A1200, OS3.9 + BB2, Blizzard 030 Mk4

I've just noticed that my Exec.library is not getting loaded into FAST RAM and 'appears' to be stuck in CHIPRAM along with expansion.library.

I've got my maprom enabled and I'm using BlizKick to load exec V45.20 as a module but both SysInfo 3.24 and SysSpeed tell me that it's still in CHIP RAM?

I normally run SETPATCH with the SKIPROM update flag.

[NovaCoder]

You need to use the 'LocalFast' module in BlizKick to move the Exec.Library to FAST RAM with Blizzard 1230 boards.

Ok, thanks but what about that expansion.library, any chance of 'getting it up' and is there even any performance advantage in doing so?

[NovaCoder]

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

Fast_Exe

Interesting.....

[NovaCoder]

Actually AFAIK it is. You just can't see it from the address (it's remapped with MMU).

Hi Piru,

Is it even a good idea to try and map the expansion.library to FASTRAM?

I assume that BlizKick doesn't do it is because it's a bad idea?


Thanks

[NovaCoder]

By conventional means it is a bad idea. With MMU it is possible, assuming at the whole MMU page worth of chip memory is allocated for it. I believe this is what the "prepare" tool in mmulib method is doing.

However, expansion.library is rarely used so it doesn't really matter that much. exec.library and supervisor stack is much more important to have in fast mem, and this is possible even without mmu.library.

Ok, thanks for the info