Soft Loading Kickstart ROM from "startup-sequence"

[antiriad76]

Is there a reliable Tool for softloading a kickstart ROM similar to relokick or Maprom function of various Accelerators during the startup sequence of the Amiga OS.?

I have seen a few potential tools on Aminet, but most are from late 90s.

Thanks

[enigma776]

MuFastRom if you have a MMU. Can be found on aminet on its own or apart of MMULib also on aminet

[patrik]

Which accelerator do you have?

[alexh]

If you don't have an MMU the only thing is ReloKick/Mkick/Skick and while it is ok it's not particularly compatible for Workbench, really only to allow games which use OS ROM routines to work.

[Retro1234]

Skick

[Retro1234]

Skick should be ok for OS stuff - Obviously you lose 512kb

[hooverphonique]

I used to use one all the time around 1990 timeframe (for OS stuff, not games) on my A2000 with 2MB fast ram to softkick to 2.0.

I can't remember what tool it was, although it doesn't seem to fit any of the above - Skick looks most likely, but my A2000 had kick 1.3 rom, and it says 2.0 is needed.

[Retro1234]

Probably MKick

[antiriad76]

Originally Posted by patrik

Which accelerator do you have?

Not specific accelerator related. I am trying to somehow reverse engineer the "ApolloBoot OMNI" from the Vampire in order to make it work with a non vampire system.

On a very high level the ApolloBoot script is using 2 vampire specific CLI tools.

Tool #1 recognizes what system you have (A500V2, A600V2, A1200V4 etc or UAE) and based on this allows you to Boot the OSs(Vampire Hardware) or build the partitions for UAE.

The script won't allow the system to boot from any partition for non Vampire systems.

Tool #2 on the other hand loads the Proper Kickstart ROM during the startup-sequence of each OS type and in this way it allows the vampire systems to boot into each OS.

I can get the "Script" fooled so that it allows non Vampire systems to boot but none of the OSs boot properly because ApolloBoot is using a customized AROS ROM which doesn't work with any Workbench.

For that reason I need to find a way to load the proper Kickstart ROM within the startup-sequence for any Amiga

[antiriad76]

Originally Posted by Retro1234

Skick

Wouldn't there be a need to create for PAT and RTB for the newer kickstart ROMs 3.1.4 & 3.2?

[Retro1234]

O yeah and no-one knows how to create them, So you're ok to use the pre made PAT files UpTo 3.1.

[Thomas Richter]

In general, using LoadModule to load specific modules is the best alternative since it does not have "quirks" or problems with specific boards such as MuMapRom or SKick. So the question should probably be "why do you think it is necesary to load an entire kickstart and not just individual modules"

[Mikeywikey]

You can create new RTB files to boot with skick, I’ve booted Hyperion ROMs and r37.350 with new RTB files.

[Mikeywikey]

Originally Posted by antiriad76

Wouldn't there be a need to create for PAT and RTB for the newer kickstart ROMs 3.1.4 & 3.2?

Here's a couple of RTB files, one for the A600 v2.05 r37.350 and one for a A1200 v3.2.1 r47.102, no PAT files, not always needed

Any use?

[Retro1234]

Interesting maybe the PAT file is when you try and load a 500 Kickstart on a 1200 and it then needs patching or something like that. I know I tried to load Kick 1.3 with Scsi.device on my 1200 and never could.

[Mikeywikey]

Originally Posted by Retro1234

Interesting maybe the PAT file is when you try and load a 500 Kickstart on a 1200 and it then needs patching or something like that. I know I tried to load Kick 1.3 with Scsi.device on my 1200 and never could.

Yea, the PAT files typically are for fixing something in the ROM that's wrong in the first place, and I think the only RTB that came bundled up without a PAT file was r37.175, these RTBs work fine in WinUAE, got a vid somewhere.

I've got a recipe for KS1.3 with scsi.device, but I've not tried it on a real Amiga, I have a Kipper2k A508 that I want to test it with.

[Retro1234]

That should work but if you tried to load it on a A1200 or A600 I don't know, iirc there is a FORCE parameter.

[Mikeywikey]

Originally Posted by Retro1234

That should work but if you tried to load it on a A1200 or A600 I don't know, iirc there is a FORCE parameter.

Ah, yes, if you have a custom KS1.3 ROM then you'll have to have additional data in the RTB, for the BCPL relocs and also the additional ones for the scsi.device, possible, but the original RTB and PAT files won't work at all on a 512k v1.3 with scsi.device as the ROM starts 256k earlier.

Sounds like a fun challenge!

[Retro1234]

Rather you than me

[fisken uno]

Originally Posted by Mikeywikey

Ah, yes, if you have a custom KS1.3 ROM then you'll have to have additional data in the RTB, for the BCPL relocs and also the additional ones for the scsi.device, possible, but the original RTB and PAT files won't work at all on a 512k v1.3 with scsi.device as the ROM starts 256k earlier.

Sounds like a fun challenge!

You would be my hero if you solved this

I am trying to get softkicked scsi modded 1.3 to work on my CD32 and ran into exactly the same problem as Retro1234 described. Well, it would need a custom RTB file.

I followed this guide and got a kickstart with md5 8B7754639928AE0DE506D27F32FFBC27 (so far, so good). The kickstart works fine with UAE, and it seems people have success with it when burning it and using on real Amiga's. But I need to be able to softkick it, and it seems impossible...