Blizkick issue

[Amigaz]

Never fiddled with BlizKick until now when I got another A4000 with only 3.0 roms in so I want to softkick 3.1 roms until my 3.1 roms arrive.
The machine softkicks the roms but after the first reboot after the softkick nothing happens..the machine doesn't boot.
Have put the line: BlizKick KICKFILE DEVS:kick31 both first in my startup-sequence and just after sertpatch in startup-sequence but the same results.
Have also disabled the maprom feature on the Cyberstorm MKIII card I'm using

Feel like a real noob at the moment


 :-o

can someone with more experience with this please help me  :-)

[Amigaz]

Cyberstorm MKIII which died on me this morning  :-o
The system hanged on the yesterday but this morning it threw in the towel  :boohoo:

The card was once broken but JJ at Amigacenter fixed it for me but it seems like I have to send it back to him now..
Was planning to finally use my Cybervision PPC card I bought a year ago but now I'm standing without a graphicscard
Anyone got a spare Zorro III gfx card for sale?  :-D

[Amigaz]

platon42 wrote:
Which kickstart file are you using? You know there are different kickstarts for A1200, A4000 and A4000T (scsi.device, no workbench.library)? The A1200 rom file is likely to crash on A4000 (due to different IDE/Ramsey stuff). I might be wrong though...

Should be an A4000 kickfile I extracted from one of my A4000 some years ago
When I extract a new one now I only get the BB2 updated rom an d not the original 3.1rom..anyone know a prog which extracts the "real" rom?

[Amigaz]

doctorq wrote:
On a cold boot, just boot without startup-sequence and use SaveRom from the BlizKick archive.

understood  ;-)

Will try it now with my CS MKII '040 in my A4000 instead

Hope JJ at Amigacenter has some kind of warranty...my guess is that he have to change the whole CPU socket or the 68060 because the CPU becomes cool when  the computer hangs or isn't  working so it must die or something

[Amigaz]

Framiga wrote:
argh! that ##### socket again :-(

Good luck AMIGAZ :-)

Thanks  :-)

Seems like these CS MKIII and CS PPC's are crap..even if they're Phase 5
My P5 CS PPC is dead also, something on the 68060 side since that A4000 doesn't boot either
JJ is going to have two CS cards on his hands  :-D

BlizKick didn't work with ther CS MKII either even with a fresh rom image from my A4000 with TransRom from the UAE package..just got a grey screen after the kickrom was "kicked" by Blizkick and CyberMap doesn't work either jusy says the kickfile has an ivalid checksum
The softkickers are like russian roulette..either it boom! = works or doesn't..guess it's a matter of luck, lol

[Amigaz]

Still can´t get it to work with my Cyberstorm MKII
If I put the BlizKick command at the top of the startup-sequence the powerlight flashes after after the 3.1rom has been kicked and if I put the command after setpatch I just get a grey screen after the rom has been kicked.
What am I doing wrong???

This is my WB3.0 startup sequence with BlizKick at the top

; $VER: startup-sequence 39.9 (9.8.92)
C:BlizKick KICKFILE DEVS:kick31
C:SetPatch QUIET

C:AntiClick

C:Version >NIL:
C:AddBuffers >NIL: DF0: 15
FailAt 21

C:MakeDir RAM:T RAM:Clipboards RAM:ENV RAM:ENV/Sys
C:Copy >NIL: ENVARC: RAM:ENV ALL NOREQ

Resident >NIL: C:Assign PURE
Resident >NIL: C:Execute PURE

Assign >NIL: ENV: RAM:ENV
Assign >NIL: T: RAM:T
Assign >NIL: CLIPS: RAM:Clipboards
Assign >NIL: REXX: S:
Assign >NIL: PRINTERS: DEVS:Printers
Assign >NIL: KEYMAPS: DEVS:Keymaps
Assign >NIL: LOCALE: SYS:Locale
Assign >NIL: LIBS: SYS:Classes ADD
Assign >NIL: HELP: LOCALE:Help DEFER

IF NOT EXISTS SYS:Fonts
  Assign FONTS:
EndIF

BindDrivers
C:Mount >NIL: DEVS:DOSDrivers/~(#?.info)

IF EXISTS DEVS:Monitors
  IF EXISTS DEVS:Monitors/VGAOnly
    DEVS:Monitors/VGAOnly
  EndIF

  C:List >NIL: DEVS:Monitors/~(#?.info|VGAOnly) TO T:M LFORMAT "DEVS:Monitors/%s"
  Execute T:M
  C:Delete >NIL: T:M
EndIF

SetEnv Workbench $Workbench
SetEnv Kickstart $Kickstart
UnSet Workbench
UnSet Kickstart

C:IPrefs

C:ConClip

Path >NIL: RAM: C: SYS:Utilities SYS:Rexxc SYS:System S: SYS:Prefs SYS:WBStartup SYS:Tools SYS:Tools/Commodities

IF EXISTS S:User-Startup
  Execute S:User-Startup
EndIF

Resident Execute REMOVE
Resident Assign REMOVE

C:LoadWB
EndCLI >NIL:

[Amigaz]

I'm using my real 3.1 rom I've grabbed from one of my other a4000 with SaveROM from the BlizKick package.

Going to install OS3.9 later on when I have my real 3.1 roms..just want to get some things working here meanwhile by using 3.1 softkicked but it's not working so I really need some advice..

Piru, where are you when I need you?  :-) please help a pour soul in your neighbouring country  :-D

[Amigaz]

^bump^

[Amigaz]

 :bump:

[Amigaz]

Ok, have 4 matching 32mb simm's

so there's nothing wrong with my Startup-sequence setup with BlizKick?

[Amigaz]

Ok, thanks for clearing that out Piru  :-)

Will try some older version of BlizKick first and with just kicking my 3.0 rom

[Amigaz]

AmigaMance wrote:

The machine softkicks the roms but after the first reboot after the softkick nothing happens..the machine doesn't boot.

How do you know that the ROM image is actually softkicked?
 I had problems with Blizkick and my Blizzard 1230IV because the remapper circuit was damaged from overheating or mechanical shock. The rest of the card was (and still is) working ok, but Blizkick didn't work because of this.
 I don't know if your accelerator has any kind of special remapping circuit like the Blizzards, though.

I can see BlizKick's output that it softkicks kick v40.68

[Amigaz]

alexh wrote:

AMIGAZ wrote:
Cyberstorm MKIII was once broken but JJ at Amigacenter fixed it for me

Out of curiosity how much did he charge?

Think it was 90 euro, not 100% sure

[Amigaz]

nadoom wrote:
I did have problems with blizkick but this was resolved when i  started using a real hard drive instead of my compact flash card as my boot device.. exactly the same installation but different drive.. and it worked. without a problem.

Maybe something like that could be the problem

yeah, I'm starting to wonder what's wrong here
Just tried with the 3.0rom which I've ripped with both TransROM and SaveROM and still the same errors
CyberMap doesn't work either, just tells me the rom's checksum is incorrect which is quite weird since I've ripped both 3.0 an d 3.1 roms from real machines and with different rom rippers...seems they get corrupted on my harddrive somehow  :crazy:

[Amigaz]

Piru wrote:
@AMIGAZ

CyberMap doesn't work either, just tells me the rom's checksum is incorrect which is quite weird since I've ripped both 3.0 an d 3.1 roms from real machines and with different rom rippers...seems they get corrupted on my harddrive somehow

Many of the ROM rippers are buggy and try to Write() directly from ROM. This is known to write corrupt data to HDD with many DMA controllers.

BlizKick's SaveROM doesn't have this problem. If you get corrupt files with SaveROM aswell, then you have real problems...

lol, think there's something wrong with the harddrive or the filesystem since I cannot unpack files either without getting errors
So there's nothing wrong with BlizKick...have to dig down deep here and solve the problem..I love troubleshooting  :lol: