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:

1. Using MuMove4K / LoadModule

Snippet of Startup-Sequence:

Cons:

No BlizKick modules active (BBlank, NoClick, ...) when booting without Startup-Sequence

Remarks:

When NOMEMFKICK is not used a lot of Chip memory is wasted

It doesn't work the other way round (like mentioned in the LoadModule readme):

2. Using BlizKick / MuMove4K

Snippet of Startup-Sequence:

Requirements:

When having a 3.1 ROM set, MaxTransfer of the boot partition needs to be 0x1FE00 (OS 3.2 defaults to 0xFFFFFF)

Cons:

Two reboots when powering on for the first time

MuFastZero FASTEXEC says MuMove4K is not installed when:

- using MuMove4K as first entry in Startup-Sequence (like with LoadModule)

- using the NOREBOOT argument after MuMove4K

BlizKick doesn't work with other modules (BBlank, LocalFast, NoClick) when the rom is kicked

Remarks:

Not able to use MuProtectModules

- it complains it cannot find resident modules

When MuMove4K is not installed, MuFastZero outputs the following:

- Consequence: exec.library in Chip, not in Fast

3. Using BlizKick only

Snippet of Startup-Sequence:

Cons:

Huge commandline with EXTRESBUF

BlizKick doesn't properly support 3.1.4+ (3.1 ROM is mentioned for instance in WB About)