Softkick an A4000/030

[fx]

Hi everyone

Does anyone know what program I can use to softkick an A4000 with the standard A3630 CPU card? I tried skick and used a standard A4000 3.1 (40.068) ROM and everything seemed to work but after WB was loaded it was back at 3.0 again.

[Piru]

Try BlizKick with CPUCARD option.

[TjLaZer]

skick works great.

[x56h34]

He needs at least an A3640 cpu card in order for BlizKick to work. Piru, have you forgotten how your own program works already? ;-)

[Piru]

@x56h34
Yes I have. :-)

I never had either A3630, A3640, A3000 or A4000. I coded the CPUCard support "blind". Considering, it works pretty well.

Anyway, if it doesn't work with A3630, I'm sorry for misleading.

[fx]

TjLaZer wrote:
skick works great.

Well, it doesn't for me ((

I tried most options and it always says:
"Everything went OK, rebooting" or something similiar but I always end up with Kick 3.0. (

Does anyone have any suggestion on which parameters to use or can suggest some other program which should/may work?

[x56h34]

@Piru:

BlizKick is an amazing piece of software. A3640 works quite well with it, with the CPUCARD option.

[Akira]

"Everything went OK, rebooting" or something similiar but I always end up with Kick 3.0. (

Are you sure you also have the correct relocation table  (RTB) file?

[Michael_D]

Hi,

try to change the memory type to use with skick:
Try "Fastram" or "32Bit-Ram". And disable "patching" the ROM.
Or give "SetCPU" (aminet) a try. It's a MMU based softkicker.
Ok, the A3630 has "EC" labeled CPUs, but some MMUs work.

[fx]

I finally got it working! Thanks for all the info guys!

To get it working I did hook up my old 1084 and start SKick before anything else was loaded. I use a VGA monitor normally so I couldn't access the Early Boot Menu without BootControl which adds a ROMTAG that I guess is no good when trying to softkick.

OS3.9 is up and running on this miggy now so I'm happy  :-P