Blizkick infinite loop

I'd like to get some advice.
I have an A1200 for a short "visit" to make some photos, etc as it is for sale.
The config itself is an A1200 rev1d4 mobo, KS3.0, BlizzardPPC (040@25mhz and 603@240 Mhz), 64 MB ram, UWSCSI, FastATA, two CDRoms on the SCSI chain and 2 HDDs on the IDE.
Now, to install OS3.9 I want to softkick the 3.1 Kickstart rom. I was inserting the following line to the very beginning of the Startup-sequence:
C:Blizkick Devs:ROM3.1

If I start the machine to boot, it does the kick remap, but after reset, it tries to do it again... and again.
What did I miss to set as argument or attribute for the Blizkick command?
If I edit the Startup-sequence with ; on the Blizkick line, it boots fully the OS. I've been working on stuff like these so many years ago, just can't recall what is wrong.

Thanks in advance.

@Reynolds

BlizKick may be doing what it's told and reloading the Kickstart. It really should check. Does the guide mention how to insert the proper line in startup?

Also, OS3.9 itself patches and reboots the system, so I don't know if that would interfere.

In any case try this. It doesn't exactly solve it but it should work around the issue for now. This checks Exec version and will only softkick an older version.

@Hypex

I will try this out, thank you!

@Hypex

Tried out last night, worked as I expected.

Many thanks!