Blizkick Command

[blade002]

Ive tried going through the Blizkick Documentation again tonight and i used a command he recommended for the Blizzard 030 III in the startup-sequence. Upon trying to reboot though, it gave me a failed return code 10.

I actually have a Blizzard 1230 IV 030/50 and not the III, but its the only that even comes close to configs you can use in the docs.

So my question to ANYONE on here running an A1200 with the same card as myself with kickstart 3.1 roms running 3.0 is what is what Startup-Sequence do "you" use to get Blizkick working properly?.

And are you supposed to remove the Jumper on the Accelerator? or do you just leave it there or swap it to the other 2 pins?.

I intend to update to 3.9 workbench after i get blizkick working.

I have had one problem solved about the HD tonight, to solve this one would be a HUGE

[patrik]

The maprom-function must be enabled for Blizkick to work.

If you look at the card, the documentation for the jumpers are printed on it and will tell you if it should be open or closed to enable it. You might have to remove the simm-module to see the text.

The other jumper is for setting if the simm-module is a 60ns or a 70ns one. The printed text on the card will also tell you what open/closed means for that one.

A simple line to get BlizKick working is "BlizKick my31romfile QUIET". The QUIET is needed if you intend to put it in your Startup-Sequence, if you are just testing, boot without Startup-Sequence (both mouse-buttons pressed at boot and the right button in the gui) and run it without the QUIET argument to see if it is working. If it is not working, it will then tell you what it is complaining about.

[rare_j]

Originally Posted by blade002

So my question to ANYONE on here running an A1200 with the same card as myself with kickstart 3.1 roms running 3.0 is what is what Startup-Sequence do "you" use to get Blizkick working properly?.

And are you supposed to remove the Jumper on the Accelerator? or do you just leave it there or swap it to the other 2 pins?.

Yes I use Blizkick on Blizzard 1230 IV 030/50 to run ks3.1 instead of ks3.0.
As Patrik says make sure the board is set to enable maprom. One of the jumpers is for maprom, the other jumper is for memory speed. If I remember correctly leave J1 open to enable maprom.
One way to tell if maprom is working is by looking at how much fast mem you've got in workbench. If it's 512K less than you expected chances are the machine's rom has indeed been mapped to ram and you're ready to try blizkick. Open up a shell and try

C:blizKick kickstart4068

This assumes the blizkick command is in C: and your kickstart 3.1 file is in DEVS:kickstarts and is called kickstart4068
The amiga will reboot. When workbench comes back up open a shell and type "version" which will display the kickstart and workbench versions. If Kickstart reads 40.68 then you're running kickstart v3.1

The blizkick documentation is really clear and well written. Give it another read.

[Angus]

oops - sorry, posted in error.

[macce2]

I have a 3660 card installed on my Amiga4000D,
and I assumed Blizkick to work,
because it is supposed to work with A3640 cards !?
However, with some quick-testing; Blizkick doesn't seem to work.
My processor card is with fpu & mmu and does have
a jumper for maprom option (currently enabled).
Should Blizkick generally work with A3660 cards..?!
Should I enable or disable the maprom jumper ?!

[daxb]

Check the BlizKick.guide for supported cards. It also should tell you about jumper settings.

[macce2]

I didn't find any mentioning of A3660 cards..

[No.3]

Of course not, BlizKick is from 2007...

but the A3660 is (said to be) a compatible rebuild of the A3640

[Jope]

It should work if you specify cpucard as one of the command line parameters.

[indigolemon]

Did you pass blizkick the CPUCARD argument?

[macce2]

Yes, I did try that and the app did reboot my machine,
so that's a good start I guess.
However, I'm currently having some serious problems
with my machine / OS3.9 setup;
I did alter my startup files after re-partitioning my
hard drive & restoring my system;
and I'm unable to make some devices&libraries
(from BB3&4, mostly) resident.
Thus I'm playing with Loadresident,
loadmodule & eFlash card (once again!);
and occasionally, I can't enter Dos anymore
(booting without s-s).
I suspect there are some module(-s)
resident that do cause that, but I'm not sure.
I would appreciate it, if someone would tell
me which devices/libraries (or other files !?)
should have a Pure bit set on a OS3.9 install ?!
I'm asking this because my system partition isn't of a fresh install;
the files have been copied from an older hd(-s) and
I do recall making some experiments with the protection
flags before..
So, for example: should workbench.library have protection
P flag set ?! How about: dos.library; graphics.library;
layers.library ..?!

Quickly back to the main topic:
i guess I could add even about 20 (or more !?)
modules to Blizkick (if I will get it to work properly;
I will do some more test with it in near future.)

UPDATE: Regarding the problem with Dos mode;
could that have something to do with my current HD setup & filesystem ?!
I have a HP 70 Gb Scsi drive connected to Fastlane controller ;
4 partitions total; using pfs_aio (standard version).
The system partition is about 3700 mb size, other
partitions about 15 Gb.
The two last partitions aren't auto-mounted.
Should I have used FastFileSystem with the first partition...?!
Sorry, just a little off topic