When you have a Blizzard card in your Amiga, chances are high that exec.library ends up in Chip memory. This impacts speed drastically and to be able to get the important stuff in Fast memory, you would want to use MuMove4K and MuFastZero. Below scenarios describe three methods to reach this goal comparing LoadModule with BlizKick:
Snippet of Startup-Sequence:
MuMove4K NOREBOOT LoadModule L:System-Startup NOMEMFKICK REVERSE ROMUPDATE ... MuFastZero ON FASTEXEC MOVESSP MuFastRom ON PROTECT MuProtectModules ON REMAP
Cons:
Remarks:
LoadModule L:System-Startup NOMEMFKICK REVERSE ROMUPDATE MuMove4K
Snippet of Startup-Sequence:
BlizKick DEVS:Kickstarts/kicka1200.rom QUIET MuMove4K ... MuFastZero ON FASTEXEC MOVESSP
Requirements:
Cons:
- using MuMove4K as first entry in Startup-Sequence (like with LoadModule)
- using the NOREBOOT argument after MuMove4K
Remarks:
- it complains it cannot find resident modules
MuMove4K is not installed, can't remap ExecBase. MuFastZero failed returncode 10
- Consequence: exec.library in Chip, not in Fast
Snippet of Startup-Sequence:
BlizKick * EXTRESBUF=600000 audio.device battclock.resource bootmenu card.resource console.device exec.library FastFileSystem FileSystem.resource gameport.device graphics.library icon.library input.device intuition.library keyboard.device layers.library mathffp.library mathieeesingbas.library Ram-Handler ramdrive.device scsi.device Shell-Seg syscheck timer.device trackdisk.device utility.library workbench.library BBlank LocalFast NoClick QUIET
Cons: