Obtaining RTB and PAT files for KS 37.350

[gaula92]

Hi there,

In Skick aminet file, RTB and PAT files for some KS versions are missing. I need to softkick a particular KS version, 37.350, so I'm on a quest to obtain the PAT and RTB files to do so.

Using MKick included tools, I got this far:

-Using MakeKick on my kick205.rom file (wich is KS 37.350) I got the corresponding kick205.rom.kick. Good!

-Now, using Kick2RTB on kick205.rom (the file kick205.rom.kick is automatically detected and used), I get the PAT file, but no RTB.

It has to be 37.350, so... how can I get the RTB file for this KS?
Thanks!

[gaula92]

Hi Matt_h, thanks for trying to help me here.
I also found in skick docs that it's possible to use a KS file without using an RTB, so there I went:

skick kick205.rom ADR 00D0000 FORCE

It tries to softkick but ultimately all I get is a black screen. I tried ADR 00D00000 because that's where similar roms (KS 37.175) for wich I have RTB files are loaded.
HOWEVER, skick IGNORES the ADR parameter, since it says:

space found at address $00F80000

when loading the new kickstart, even if I cleanly specified ADR 00D00000 or ADR D00000.

[gaula92]

@psxphill: Ok, even if I accept there's no PAT/RTB for KS 37.350 and the available tools won't let me create my own RTB for it, there's still hope skick would allow me to softboot KS 37.350 without RTB, by using ADR parameter.
However, it's ignored, or so it seems.

[gaula92]

@psxphill: I've ust written him to a valid e-mail address I got from google. The one in the skick readme seems from..1993!

However, can you tell me how to set the loading address in an effective way? ADR isn't for relocation, I can understand that, but if I specify  "ADR 00D00000 FORCE"  then I should see: "space found at address $00D00000" instead of "space found at address $00F80000", as far as I understand it.

[gaula92]

Yes, Matt, I already tried. Skick checks the rom file cheksum, so it refuses to load 2.05 in place of 2.04.
Maybe the 2.04 (37.175) RTB file can be hacked to accept 37.350 checksum?

[gaula92]

Pavel Troller is a nice guy! He answered my email but he's retired from Amiga. He also told me his Amiga wouldn't boot anymore. So I guess I'm pretty limited to:

-Forcing SKICK to boot 2.05 without an RTB. Almost there! In FS-UAE, I can do "skick kick205.rom FORCE" and it boots to a guru. Then if I soft-reset the Amiga it boots to the softkicked KS... On the Minimig it won't softboot this way. I suspect it COULD work if I could set the KS loading address manually: isn't the ADR parameter for this? But it's ignored...

-Using a different softkicking solution that can softboot 2.05. I don't know any. Any ideas?

[gaula92]

Can't you just select the kickstart 2.05 in the minimig configuration?

Yes, but I'm making a dedicated Minimig HDF (suitable for other stock-class Amigas with low RAM) where people don't have to go switching KS and guessing what version goes with what game: per-game scripts will do the job.
I have came up with a solution to auto-launch the game after softkicking into a given KS version.
I just need a way to softkick into a 2.x version with A600-compatible scsi.device...

[gaula92]

I'm pretty sure there isn't a way to do it without manually creating the RTB file. You could start with kickstart 2.05/3.1 selected in the minimig and softkick 1.3 for games that need it.

Every game that works in 1.3 only can either work on 2.x with or without patches, or works perfect with Whdload on the Minimig. I don't need to softkick 1.3, just 2.x with A600 scsi support.