💾 Archived View for 68k.myfirewall.org › docs › lm.vs.bk.differences.gmi captured on 2023-09-08 at 15:38:08. Gemini links have been rewritten to link to archived content

-=-=-=-=-=-=-

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:

MuMove4K NOREBOOT
LoadModule L:System-Startup NOMEMFKICK REVERSE ROMUPDATE
...
MuFastZero ON FASTEXEC MOVESSP
MuFastRom ON PROTECT
MuProtectModules ON REMAP

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):

LoadModule L:System-Startup NOMEMFKICK REVERSE ROMUPDATE
MuMove4K

2. Using BlizKick / MuMove4K

Snippet of Startup-Sequence:

BlizKick DEVS:Kickstarts/kicka1200.rom QUIET
MuMove4K
...
MuFastZero ON FASTEXEC MOVESSP

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:

    MuMove4K is not installed, can't remap ExecBase.
    MuFastZero failed returncode 10

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

3. Using BlizKick only

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:

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