kickstart3.5

[xeron]

This is 1 of 3 things:

1) A ROM that has been mislabeled by someone who doesn't know about Amiga Kickstarts

2) A 3.1 ROM that has been patched with the 3.5 ROM modules

3) Junk :-)

[xeron]

You cannot patch a ROM file with the OS3.5 modules. There is not enough space in the ROM chip for all the new modules.

Not technically true; I suggest you consult the BlizKick docs :-) on my Amiga 4000, I use BlizKick to boot a pre-patched "Kickstart 3.9" image, with a couple of BlizKick module extras.

This "Kickstart 3.5" ist quite old. It is a fake, a 3.1 ROM with version numbers patched. And a virus perhaps.

Yeah, I doubted it would be anything useful.

[xeron]

mdma wrote:
Gimme, Gimme, Gimme!! ;-)

*tschh* you should know better than that! Download BlizKick and read the docs

[xeron]

Thomas wrote:
I suggest you consult the BlizKick docs yourself, it describes very detailed why it is not possible to create a patched ROM chip from all the new modules.

Ummm... so what? I'm not talking about a ROM chip, i'm talking about a ROM image, which is just a file on a disk.

[xeron]

DWolfman wrote:
 but the applypatch program won't apply them to the rom image.  How did you get it to work?

What I did (I *think*, this was ages ago), was use BlizKick to load a normal KS3.1 image, and apply all the OS3.9 patches and modules I wanted using EXTRESBUF to create extra space. IIRC, BlizKick has an option to save the new ROM it creates back out to disk, and thats what I used.

I think thats what I did, anyway. It was ages ago now. It doesn't really help if you use WinUAE, though.

[xeron]

This won't work, I'm afraid. The EXTRESBUF is outside the ROM image itself. Modules placed on EXTRES area are not saved to the image.

There is no way to get the EXTRES modules included in the 512K image.

Hmm... I must be going mad. I was absolutely sure I had created a 3.9 pre-patched image that was >512Kb, but I just checked, and I'm not using one. Weird. I don't know where I got that idea from tbh. :-?