Loading an old Kickstart

[Sim085]

Hello, was wondering, if I have an Amiga with Kickstart 3.1, can I install Workbench 1.3 on a CF card and the first thing done is unload kickstart 3.1 and load kickstart 1.3 instead?

[emufan]

not really sure, but maybe using a patch from aminet:
Patch for Kick 1.3 to add scsi.device
this way it could access the internal ide of a1200/a600, not sure about the cf card.

if it works at all, you could use some rekick tool, which would enable the modified 1.3 rom.

[McTrinsic]

Depends. Replacing the Kickstart can be achieved via Softlick -> see Aminet.
If you can then boot from CF depends on the Autoboot-capability of your Hostadapter.

[Sim085]

You mean if the loaded kickstart is able to load from a disk?

I mentioned 1.3 but for example I know that Kickstart 2.0 was able to auto-boot as that is what my A500 had. So if I use this softlick to load kickstart 2.0 and then Workbench 2.1 on that ... would that work?

Originally Posted by McTrinsic

If you can then boot from CF depends on the Autoboot-capability of your Hostadapter.

[Sim085]

Can't find this on aminet...
Is "softlick" the name of the tool?

Did find this...
http://aminet.net/package/util/misc/softboot331

Originally Posted by McTrinsic

Depends. Replacing the Kickstart can be achieved via Softlick -> see Aminet.

[emufan]

I think it was a typo. searching for soft + kick - lists some tool.
blizkick you may try too.

do you have an accelerator board with MMU?
those MMU equiped amigas, can use a maprom function.
there were tool provided with those accelerator, to do a softkick using this maprom functionality.
maybe it is more reliable, than stndard softkickers. dunno exactly.

[Amiga1992]

The tool is skick
http://aminet.net/util/boot/skick346.lha

blizkick will only work on Blizzard accelerators.

[dirkies]

Originally Posted by Akira

The tool is skick
http://aminet.net/util/boot/skick346.lha

blizkick will only work on Blizzard accelerators.

I got quite some problems making sidekick work with certain kickstarts, they often needed to be patched before Sidekick would accept/load them. Not sure why but just be aware some kickstart images will be spit out by skick with some error message.

[Amiga1992]

It's not sidekick, it's just simply skick.

And yeah you need supported Kickstart images, it will have a hard time loading any old shit. But you shouldn't have a problem finding online exactly what you need. I can softkick 1.3 without issues with it.

[AMIGASYSTEM]

With TUDE You can create a floppy and turn your kickStart from kick3.1 to Kick1.3


[ Show youtube player ]

[Sim085]

So how does it work?

On boot amiga will automatically load kickstart from the physical rom chip, it then goes to boot from the first partition, at that point I would have an instruction to load the old kickstart and continue loading the OS?

Or you boot normally, use the tool, restart and when you restart you are using a different kickstart? if you switch off you get again what you have on board?

Originally Posted by Akira

It's not sidekick, it's just simply skick.

And yeah you need supported Kickstart images, it will have a hard time loading any old shit. But you shouldn't have a problem finding online exactly what you need. I can softkick 1.3 without issues with it.

[Sim085]

i believe he has to restart after kick 1.3 is loaded...

Originally Posted by AMIGASYSTEM

With TUDE You can create a floppy and turn your kickStart from kick3.1 to Kick1.3


[ Show youtube player ]

[Retro1234]

Tude is not really used for this kind of thing - Skick is and if you dont have a MMU probably the best and only option
they all reboot after loading the Rom.
but you cant load patched kickstart so Kickstart 1.3 wont have scsi.device you can try SKick Force or create a boot disk with a mount list to mount your HD or try Kick 2.x if the A600 version is supported by Skick.

[AMIGASYSTEM]

Originally Posted by Sim085

i believe he has to restart after kick 1.3 is loaded...

You just have to create a bootable floppy (FFS) with TUDE + Kickstart 1.3 (Renamed Rom1.3)

[Amiga1992]

Sim085, your main problem here will be your hard drive I think.
First you need a patched Kickstart 1.3, and then I think you need a special partition just for 1.3 because your FFS 3.1 partition will just not work.

I Would read up first about how to setup a 1.3 hard drive partition, I never done it so I cannot help you there. Softkicking the 1.3 Kickstart is the easiest part. Do you really want it to do it automatically though? That means you never get the choice.

What I would do:
Partition your drive with one FFS partition for 3.x and one OFS partition for 1.3.
Have the 3.x system check for a keypress on boot, if pressed, initiate softkicking of 1.3, on reboot, only the 1.3 partition should boot.

[AMIGASYSTEM]

Os 1.3 wanting can also support HD With FFS File System, TUDE you can also use it to start HD.

[Retro1234]

Can Tude boot the patched kickstart?

[AMIGASYSTEM]

Originally Posted by Retro1234

Can Tude boot the patched kickstart?

I was talking about AMiGA machines in general not IDE disks.

[emufan]

I patched a kickstart 1.3 (34.5) - replaced it with the kickstart 3.1 of my a1200 emulation.

it does boot my partition (FFS) - lists some early commands, but fails later.
it's all wb/kick 3.1 stuff of course.

#1) you need GetSCSI11 - to rip the scsi.device from current rom.

the one extracted using remus/romsplit did not work, size was different, but same version.

gpatch kick34005.A500 kick34005.A500.gpatch kick34005.A500_patched
gpatch scsi.device scsi.device_xx.xx(A1200)_rom.gpatch scsi_device.rom RECURSIVE
join scsi_device.rom kick34005.A500_patched TO kick1.3_scsi.rom

( xx.xx ---> choose patch file for your scsi.device version ---> c:version scsi.device )

rom size of the patched kick1.3_scsi.rom is 512 kb

#2) i think you have to create a startup-sequence with some menu, choosing 1.3 or 3.1
and execute either s:startup-sequence13 or s:startup-sequence31

#3) a folder on 1st partition: SYS:WB13 with C, L, DEVS ... and all the workbench 1.3 stuff.
in the ss13 you have to add some assigns first:

DH0:WB13/c/assign SYS: dh0:WB13
DH0:WB13/c/assign C: dh0:WB13/c
DH0:WB13/c/assign L: dh0:WB13/L
DH0:WB13/c/assign S: dh0:WB13/s
DH0:WB13/c/assign Fonts: dh0:WB13/fonts
DH0:WB13/c/assign Devs: dh0:WB13/devs
DH0:WB13/c/assign Libs: dh0:WB13/libs
...
followed by the standard WB13 startup-sequence content.

questions remains, does tude or skick start the patched rom?

[idrougge]

Originally Posted by Akira

Partition your drive with one FFS partition for 3.x and one OFS partition for 1.3.

Kickstart 1.3 has always used FFS.