A3000 Kickstart 1.4 Superkickstart

alexh · 20 November 2009, 18:54

Can anyone help me out locating the CRC

of a A3000 Superkickstart file for KS1.3?

It would be on device (not volume) named WB_1.3; in the devs directory, a file named kickstart.

It is different to the standard 16-bit kickstart 1.3 files for the A500/A2000 in that it has "the bonus code", fast RAM & SCSI support for A3000 SCSI controller as well as the extra KS1.4 bootcode attached to it. It will be either 282,624 or 283,136 bytes in size.

I already have the CRC's of KS2.04 & KS3.1 and have misplaced the KS1.3 file for A3000 KS1.4.

Thanks in advance.

Jope · 20 November 2009, 19:21

But what if it's 279552 bytes instead?

Suicide?! :-D

alexh · 20 November 2009, 19:23

Never seen one that size before....

Jope · 20 November 2009, 19:28

I think they only released three actual superkickstart disks, the rest of the developer superkicks came as files only to put in your wb_2.x:devs..

But even the three that I know of all have different bonus files. Amazing.

They're all bonus 1.18 however, just as the three different 2.x bonuses I've found are all bonus20 37.14.

alexh · 20 November 2009, 19:32

I'd be curious to know how you made your SuperKickstart 3.9

Jope · 20 November 2009, 19:37

I just made a normal rom based A3000 specific superkick 3.9 (you know, A3000 exec and scsi.devices) and concatenated the "best" bonus20 into it.

Naturally the bestness was just pulled out of a hat, I have a bunch of devel 3.x superkicks and they all seemed to have the same bonus.

That was a bit underwhelming, wasn't it. :-)

The superkick A3000 is a fun toy, but in the end, it's not worth your while making a dual boot 1.3/2.x setup with it..

As you remember, when the very first A3000s shipped, Commodore advised everyone to run 1.3 for production work. Thus if you have a dual boot setup, it will always default to kick 1.3 on cold boot.. If you're not ready with the mousebuttons after turning on the power, you end up with yucky 1.3. :-D

I guess it wouldn't be awfully difficult to patch the remapper part to default to 2.x, but then again, I'm quite hard pressed to find an actual use for a 1.3 machine with an 030 + 16MB 32bit fast.. ;-)

Ratte · 20 November 2009, 23:00

There are two versions of bonus out there ... v1.x and v2.0.
You must have WB_1.3: and WB_2.x: partitions to hold both OS-versions.
Depending the higher bootpriority(HD-Toolbox), you can choose your favorit (default) OS.
If you play with Remus, you can easily build a Kick3.9 Superkick ...
... research has been done together with Doobrey in 2006/2007.
Remus V1.0rc31 is able to handle this ...

alexh · 20 November 2009, 23:06

If you swap the names of the two devices wont that work?

i.e. put AmigaOS3.9 and Superkickstart 3.9 on the WB_1.3 device and vice versa?

Jope · 20 November 2009, 23:30

Might work when you swap the device names around..

The bootmenu messes around with the bootpri. you cannot affect the pri of wb_1.3 and wb_2.x, it will always set the special partitions as one higher than your highest normal partition. Thus my machine is now set up with a minimal wb_2.x partition that just reassigns sys and the other standard assigns to dh0: and jumps to the startup-sequence in there..

Reason being, dh0 is pfs3, but the superkick partition must be plain ffs.

Ratte, did you verify that it will load the ks from 2.x if it has a higher pri than 1.3? Maybe I'll try it if i get suitably bored one day, I still haven't figured out a reason for running 1.3 on my A3000... :-)

barryn · 25 May 2018, 02:46

I am currently running a kickstart 3.9 (ver 45.64) rom image that I got on an Amiga Forever 7 disk. I was able to save out the rom and add the bonus code and use it on my Amiga 3000. It seems to work fine. I also have both a wb_2.1 (really 3.x) and a wb_1.3 partition, and default is wb_2.1 which now boots my 3.9 kickstart. In addition to the option to boot 1.3 or 3.9 I also have a few other kickstarts which I can boot by copying them to SYS: Devs/kickstart. I have statements in Startup-Sequence that alter the startup depending on the version of the kickstart that is loaded.

barryn · 25 May 2018, 07:33

I have noticed one thing, before my startup-sequence runs, version displays a kickstart of 45.64, but after work bench loads, version and work bench about display a lower version of 45.57. I tried commenting out my setpatch lines but then work bench did not load, although maybe I introduced a syntax error in the startup-sequence or something. If I leave it alone it runs fine but the version of kickstart actually goes down after boot to 45.57. Odd.

alexh · 25 May 2018, 09:06

setpatch skipromupdates?

20 November 2009, 18:54	#1
alexh Thalion Webshrine Join Date: Jan 2004 Location: Oxford Posts: 14,432	A3000 Kickstart 1.4 Superkickstart Can anyone help me out locating the CRC of a A3000 Superkickstart file for KS1.3? It would be on device (not volume) named WB_1.3; in the devs directory, a file named kickstart. It is different to the standard 16-bit kickstart 1.3 files for the A500/A2000 in that it has "the bonus code", fast RAM & SCSI support for A3000 SCSI controller as well as the extra KS1.4 bootcode attached to it. It will be either 282,624 or 283,136 bytes in size. I already have the CRC's of KS2.04 & KS3.1 and have misplaced the KS1.3 file for A3000 KS1.4. Thanks in advance.

20 November 2009, 19:28	#4
Jope - Join Date: Jul 2003 Location: Helsinki / Finland Age: 43 Posts: 9,885	I think they only released three actual superkickstart disks, the rest of the developer superkicks came as files only to put in your wb_2.x:devs.. But even the three that I know of all have different bonus files. Amazing. They're all bonus 1.18 however, just as the three different 2.x bonuses I've found are all bonus20 37.14. Last edited by Jope; 20 November 2009 at 19:34.

20 November 2009, 19:37	#6
Jope - Join Date: Jul 2003 Location: Helsinki / Finland Age: 43 Posts: 9,885	I just made a normal rom based A3000 specific superkick 3.9 (you know, A3000 exec and scsi.devices) and concatenated the "best" bonus20 into it. Naturally the bestness was just pulled out of a hat, I have a bunch of devel 3.x superkicks and they all seemed to have the same bonus. That was a bit underwhelming, wasn't it. :-) The superkick A3000 is a fun toy, but in the end, it's not worth your while making a dual boot 1.3/2.x setup with it.. As you remember, when the very first A3000s shipped, Commodore advised everyone to run 1.3 for production work. Thus if you have a dual boot setup, it will always default to kick 1.3 on cold boot.. If you're not ready with the mousebuttons after turning on the power, you end up with yucky 1.3. :-D I guess it wouldn't be awfully difficult to patch the remapper part to default to 2.x, but then again, I'm quite hard pressed to find an actual use for a 1.3 machine with an 030 + 16MB 32bit fast.. ;-) Last edited by Jope; 20 November 2009 at 19:45.

25 May 2018, 02:46	#10
barryn Registered User Join Date: May 2018 Location: Miami, Florida, USA Posts: 6	I am currently running a kickstart 3.9 (ver 45.64) rom image that I got on an Amiga Forever 7 disk. I was able to save out the rom and add the bonus code and use it on my Amiga 3000. It seems to work fine. I also have both a wb_2.1 (really 3.x) and a wb_1.3 partition, and default is wb_2.1 which now boots my 3.9 kickstart. In addition to the option to boot 1.3 or 3.9 I also have a few other kickstarts which I can boot by copying them to SYS: Devs/kickstart. I have statements in Startup-Sequence that alter the startup depending on the version of the kickstart that is loaded. Last edited by barryn; 25 May 2018 at 07:29.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Odd A3000 SuperKickstart/SCSI behavior	rhester72	support.WinUAE	4	30 September 2011 14:55
A3000 SCSI/1.4-based SuperKickstart 1.3 boot fails	rhester72	support.WinUAE	7	31 December 2009 15:15
A3000 Kickstart	desantii	support.Hardware	2	19 October 2009 17:07
Need A3000 Superkickstart file(s)	r.cade	support.Hardware	3	06 May 2009 02:26
Where to find A3000 Superkickstart 3.1	r.cade	support.Hardware	6	24 January 2008 16:26

20 November 2009, 19:21	#2
Jope - Join Date: Jul 2003 Location: Helsinki / Finland Age: 43 Posts: 9,885	But what if it's 279552 bytes instead? Suicide?! :-D

20 November 2009, 19:23	#3
alexh Thalion Webshrine Join Date: Jan 2004 Location: Oxford Posts: 14,432	Never seen one that size before....

20 November 2009, 19:32	#5
alexh Thalion Webshrine Join Date: Jan 2004 Location: Oxford Posts: 14,432	I'd be curious to know how you made your SuperKickstart 3.9

20 November 2009, 23:00	#7
Ratte Registered User Join Date: Sep 2008 Location: Germany Posts: 331	There are two versions of bonus out there ... v1.x and v2.0. You must have WB_1.3: and WB_2.x: partitions to hold both OS-versions. Depending the higher bootpriority(HD-Toolbox), you can choose your favorit (default) OS. If you play with Remus, you can easily build a Kick3.9 Superkick ... ... research has been done together with Doobrey in 2006/2007. Remus V1.0rc31 is able to handle this ...

20 November 2009, 23:06	#8
alexh Thalion Webshrine Join Date: Jan 2004 Location: Oxford Posts: 14,432	If you swap the names of the two devices wont that work? i.e. put AmigaOS3.9 and Superkickstart 3.9 on the WB_1.3 device and vice versa?

20 November 2009, 23:30	#9
Jope - Join Date: Jul 2003 Location: Helsinki / Finland Age: 43 Posts: 9,885	Might work when you swap the device names around.. The bootmenu messes around with the bootpri. you cannot affect the pri of wb_1.3 and wb_2.x, it will always set the special partitions as one higher than your highest normal partition. Thus my machine is now set up with a minimal wb_2.x partition that just reassigns sys and the other standard assigns to dh0: and jumps to the startup-sequence in there.. Reason being, dh0 is pfs3, but the superkick partition must be plain ffs. Ratte, did you verify that it will load the ks from 2.x if it has a higher pri than 1.3? Maybe I'll try it if i get suitably bored one day, I still haven't figured out a reason for running 1.3 on my A3000... :-)

25 May 2018, 07:33	#11
barryn Registered User Join Date: May 2018 Location: Miami, Florida, USA Posts: 6	I have noticed one thing, before my startup-sequence runs, version displays a kickstart of 45.64, but after work bench loads, version and work bench about display a lower version of 45.57. I tried commenting out my setpatch lines but then work bench did not load, although maybe I introduced a syntax error in the startup-sequence or something. If I leave it alone it runs fine but the version of kickstart actually goes down after boot to 45.57. Odd.

25 May 2018, 09:06	#12
alexh Thalion Webshrine Join Date: Jan 2004 Location: Oxford Posts: 14,432	setpatch skipromupdates?

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)