Blizkick issue

[Amigaz]

^bump^

[Amigaz]

 :bump:

[Piru]

If CyberMap doesn't work then the problem is not in BlizKick at least.

It could be that the mapping requires some specific memory module setup or somesuch magic.

[Amigaz]

Ok, have 4 matching 32mb simm's

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

[Piru]

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

Nothing I can see. You could try BlizKick after SetPatch, but I doubt it makes any difference. Adding >NIL: or QUIET option would be advisable (so that it doesn't open of the console, do this at least if you get it to work).

If CyberMap doesn't work, BlizKick won't work either. Basically BlizKick is sort of CyberMap with stereoids.

[Amigaz]

Ok, thanks for clearing that out Piru  :-)

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

[AmigaMance]

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.

[alexh]

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

Out of curiosity how much did he charge?

[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

[nadoom]

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

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

[Piru]

@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...

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

[amigagr]

AmigaMance wrote:
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 had the bliz1230 back in 95 for about 7 months before i take the bliz1260 and at this period of time i never make it to softkick the rom, i had try all the tools that was available at the time.

-edit-
as far as i can remember 11 years ago...

[amigagr]

AMIGAZ wrote:
Just tried with the 3.0rom which I've ripped with both TransROM and SaveROM and still the same errors

i use grabkick and never had problems.
try blizzmagic to softkick, i used it before i discover blizkick and it was ok, just without all of those goodies of blizkick. just to see if the machine can softkick at all.

blizz magic
grabkick