💾 Archived View for 68k.myfirewall.org › docs › lm.vs.bk.switching.gmi captured on 2023-01-29 at 15:25:57. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2022-01-08)
-=-=-=-=-=-=-
I would like to share some notes with you in relation to LoadModule and BlizKick and how to switch from one to the other without the need of powering down the system (and save on the power spikes on our aging hardware). Perhaps some of you may find this useful too.
Hardware: A1200, 3.1 ROM, Blizzard 1260/50, 64 MB, AGA, CF, Rys MKII, PCMCIA/CNET
When using LoadModule the startup of my system looks like this (roughly):
1. MuMove4K NOREBOOT
2. LoadModule L:System-Startup NOMEMFKICK REVERSE ROMUPDATE
3. MuFastZero ON FASTEXEC MOVESSP
4. MuFastRom ON PROTECT
5. MuProtectModules ON REMAP
6. MuForce <options>
7. MuGuardianAngel <options>
When using BlizKick it looks like:
1. BlizKick ROM
2. MuMove4K
3. MuFastZero ON FASTEXEC MOVESSP
4. MuForce <options>
5. MuGuardianAngel <options>
So this is the first important difference to be aware of: you need to have two versions of the Startup-Sequence available on demand.
To go from a 'LoadModule System' to a 'BlizKick System', I have scripted the following steps in specifically this order:
1. Copy clone the BlizKick Startup-Sequence to S:Startup-Sequence
2. MuGuardianAngel OFF
3. MuForce OFF
4. MuProtectModules OFF
5. MuFastRom OFF
6. MuFastZero OFF
7. LoadModule REMOVE NOREBOOT
8. MuMove4K OFF
Step 8. causes a 'cold reboot' with everything that LoadModule and MuMove4K put in memory removed. So when the Amiga boots up, it starts executing the BlizKick Startup-Sequence as if it was powered up for the first time.
Important in above scenario: everything is removed based on the "last in - first out" principle.
To go back from a 'BlizKick System' to a LoadModule System', I have scripted the following steps:
1. Copy clone the LoadModule Startup-Sequence to S:Startup-Sequence
2. MuGuardianAngel OFF
3. MuForce OFF
4. MuFastZero OFF
5. MuMove4K OFF NOREBOOT
6. BlizKick
Here, step 6. (just executing BlizKick without parameters) causes the 'cold reboot' and also here the script is based on "last in - first out". Everything is removed from memory and the LoadModule Startup-Sequence variant is executed as if the Amiga was just powered on.
Usually I'm working on a 'LoadModule' system, because then you can work with individual components better (although mixing is usually a no-go unless indicated by a developer). Another benefit of using LoadModule is that this method only needs one reboot when first powering up the Amiga, where BlizKick needs two (both BlizKick ROM and MuMove4K need a reboot).
Also a fair warning. Please consult the (MuTools) manuals of what you are doing exactly. The MuMove4K manual for instance mentions: "MuMove4K will reboot your system, you should finish all disk activities or you might invalidate your HD". To better be safe than sorry, I also introduced a Wait statement between step 7. and 8. in the script to go to a BlizKick System, so I'm certain there is no HD activity anymore. Same between step 5. and 6. when going to a LoadModule System.