kickstart3.5

[lionstorm]

Hi all,
I found on emuchina a kickstart3.5. I thought latest is 3.1. Will I get any benefit over my KS3.1/amigaOS3.9 ?
Lio

[lionstorm]

ok I found it myself : it is a fake, kickstart 3.5 was never released, and if so would work on walker prototype only.
Lio

[lorddef]

It'll just be an image of the patched version of 3.1, 3.5 patched the 3.1 rom on boot, hence the reeboot during a first boot in os 3.5.

I doubt it'd help, although a similar version of the 3.9 patched rom might speed up boot times...

[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 :-)

[Thomas]

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.

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

Bye,
Thomas

[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.

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.

Gimme, Gimme, Gimme!! ;-)

[xeron]

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

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

[Thomas]

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.

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.

Of course, because BlizKick loads all ROM and patches into RAM, you can use as much storage as you want for BlizKick's image. There is an extra parameter you need to set in order to use more memory than the 512KB a Kickstart ROM chip has (and needs).

IIRC the BlizKick docs also was the place where was described why it is so difficult to make a new Kickstart ROM out of all the improvements added to new OS versions. It is much easiser to just unstall some reset-proof modules like BlizKick does.

Bye,
Thomas

[olegil]

Thomas wrote:

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.

No, but there is room for what is important, the rest can be loaded from disk.

I'm running kickstart 3.9 on my A1200. I haven't burned it to a flashrom yet, because I never have enough time for all my projects. But the image works fine in UAE and on real Amigas.

I would love to get a patched ROM up and going for my WinUAE setup here.  Ever since my A3000/CSPPC died, I've wanted to try this but could not find a way to make it work.  So far I've tried what is mentioned in the BlizKick docs (got the Rom Update broken out into separate files), but the applypatch program won't apply them to the rom image.  How did you get it to work?

[KennyR]

I would say that emulators don't really need the enhanced routines in a patched ROM much. In fact the emulator is probably more stable without them.

They do if you are booting from an old HD that was set up originally on a real Amiga, with all those hardware limitations.  :-)

As it is I'm running OS3.9 (with BoingBag2) installed.  Even though it may not need some of that stuff, it still does a reboot to load a lot of the ROM patches from the update.  If possible I'd like to get rid of that requirement by loading a patched ROM directly instead.

[MikesterBrau]

   I believe that last "official" Kickstart  ROM was 3.2 and it was only in the Walker and never released to the public.  The 3.2 rom was 1 1MB chip rather than 2 512k chips and had support for 1 extra custom chip (forgot the name) and had a slight fix for larger hard drives  (4gb partitions and 9GB overall size) and an improved Setpatch, as well as a cdrom file system (borrowed and modified from cd32) and the frame work for a future super IO type setup.  I think after all was said and done only 16k was left to load anything from software (rom space wise).   Feel free to correct me if I am a bit off but that is what I recall.  

[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.