Amiga.org

Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: doctorq on November 08, 2003, 02:42:11 PM

Title: Problems on rekicking a A1200 DKB 1240 accelerator
Post by: doctorq on November 08, 2003, 02:42:11 PM
Hi guys,

I recently bought a Viper accelerator for my A1200 Desktop. It's a 030 board, with MMU and FPU with 8 mb (the first thing I did was to put 128 MB in it instead), but sadly I can't find it under www.amiga-hardware.com.

The strange thing about this board is that it works 100 % on a Kickstart 3.0 A1200, but on a Kickstart 3.1 A1200 it won't boot at all. The seller told me that it will boot without the memory on it, but not on my machine.

The board came with a manual, but unfortuanately this manual doesn't say anything about the 3 jumpers, so I can't figure out if I can use MapROM feature to softkick the machine to Kickstart 3.1. I normally use BlizKick for this purpose, becuase it's easy to use.

I tried using SKick, but this program won't let my machine softkick the 3.1 rom, only the 3.0 :-(

Can anyone give me a clue on how to solve this problem (without having to buy a Blizzard board :-) ) or recommend an other program?
Title: Re: Problems on rekicking a A1200 viper board
Post by: Madgun68 on November 08, 2003, 02:58:44 PM
I think it might be best to identify the card first. Have you compared the accelerator to all the 1230 models from every manufacturer?
Title: Re: Problems on rekicking a A1200 viper board
Post by: doctorq on November 08, 2003, 03:02:47 PM
Yeah, that's why I did the following...

I looked at www.amiga-hardware.com again, and looked through all the A1200 accelerators. I found the matching one and it's made in 1994 by a company called DKB, and the board itself is called DKB 1240 (even though it's still a 030 board).

There where no link to an other manual though, so I'm stock at the moment :-( It would be nice to get OS3.9 running on my desktop Amiga aswell...
Title: Re: Problems on rekicking a A1200 viper board
Post by: Madgun68 on November 08, 2003, 03:07:41 PM
Maybe this isn't very good news, but take a look at this link (http://amiga.resource.cx/exp/search.pl?product=dkb1240) about the DKB 1240.
Title: Re: Problems on rekicking a A1200 viper board
Post by: doctorq on November 08, 2003, 03:29:33 PM
bummer, but nice to be informed though.

Well, I only use the board for my gaming A1200, so it's not that big a problem. The question at the moment is then, if it also concerns Kickstart 3.1 being softkicked? I am not sure I'm setting SKick up correctly...

Where can I get this firmware update? Is it like the FlashROM update on Phase 5 PPC boards?
Title: Re: Problems on rekicking a A1200 viper board
Post by: lempkee on November 08, 2003, 03:30:03 PM
i had one of theese crap cards, mine also never worked with 3,1, i sold it and never thinked about it after that...

(it was in 94? or something...i bought an blizz 1230/50 instead and 8-10 months later i bought the 1260/50 from phase5.... ;D

ahhh...the memories....

Title: Re: Problems on rekicking a A1200 viper board
Post by: lempkee on November 08, 2003, 03:31:55 PM
btw doesnt blizkick work on this card? , i think it does , check the site!

or ask PIRU ;)
Title: Re: Problems on rekicking a DKB 1240 accelerator
Post by: doctorq on November 08, 2003, 04:37:59 PM
I just tried all jumper settings one at a time, and no combination takes 512 KB out of my available ram :-( Damn.

I guess this means that I can't softkick using this board :-(
Title: Re: Problems on rekicking a DKB 1240 accelerator
Post by: adolescent on November 09, 2003, 04:25:09 AM
SKick should work with any system.  I even used it on my A500 back in the day.  Just make sure you're using the correct kickstart image for the A1200.
Title: Re: Problems on rekicking a DKB 1240 accelerator
Post by: doctorq on November 09, 2003, 10:11:42 AM
Well, then I can't set it up correctly. This is my commandline

C:SKick Devs:Kickstarts/kick40068.A1200

When it is executed it resets as it should, but then it only displays a yellow screen. It's descriped in the docs, but I can't fully remember it....

I tried using the option FAST to get the ROM loaded to fastmem; it didn't help either...