Hypothetical Kickstart ideas

[Ratte]

Twinkick "3.9"
KickWork3.1
KickTOS
 :-)

[Ratte]

Kickwork is a complete 512KB 3.1ROM crunched with LZMA down under the 256KB WOM limit.
The 256KB includes the crunched rom and some decrunching code.
The Kickstart itself is modified with an enhanced version of Pirus Kickwork-Patch.

... Its a Kick3.1 + WB3.1 on one disk for the A1000 ...

save2600 wrote:
And about the e-mail... are you xxxxxxx_xxxxx@xxx.xx? If so, yes - I got that, but haven't had time to play around with 'em yet. I did reply with a thanks. If that's not you, then no, I have not received it.  

[Ratte]

details about kickwork

the crunched 256kb are loaded to the wom
decrunching a 512kb (executable) rom-image to fastmem
same as twinkick, but without kick1.3
but it is able to repair the romimage in fastmem if some kind of code or a systemcrash destroys the rom
the "kickwork"-patch is added for fun only and has nothing to do with the lzma-compressed kick3.1

save2600:
did you read your complete emails?

[Ratte]

amigaksi wrote:
Another useful item for A1000 users would be to compress the 256K kickstart into the bootstrap ROM space and decompress that into the WOM upon power-up.  Using a pair of 27512 EPROMs to replace the bootstrap ROMs would give you 128KB so compress the 256K Kickstart into less than 128KB (and decompressor also would have to fit into that space).

Perhaps, someone who has the copyrights to those bootstrap ROMs and Kickstarts could do it.

its easier to add an rom-socket to the a1000
< link >

[Ratte]

Its related to the configchain.
Twinkick (& Kickwork) "needs" a memory-expansion as first expansion.
The A2091 is configured as a "hdd-controller" first and then as a "memory-expansion" in a second step (and thats to late for Twinkick).

You can try a workaround, but i cant promise that it works.
(Its just an idea ...)

Set the a2091 memory-jumper to "0kb" and give it a try.