»

[freqmax]

amigaksi, It's not necessary to provide the bits. But rather one can provide a script that will automatically copy the existing ROMs into a file. Which is then compressed and processed to files (.hex?) ready for burning EPROMs with.

[save2600]

R
save2600:
did you read your complete emails?

Hi Ratte:

Had to do a little investigating, but yeah - finally tracked it down. Kickwork - WOW, you pulled another rabbit out of your hat!

-seems to only work with my MiniMegs external 2MB expansion
-does not work with my A2091 and its 2mb of memory

...does the A2091 map its memory different or what? When plugged in,
the screen flashes red and constantly resets itself. Even after about 10
minutes. When I replace the A2091 with the other ram card, the screen
never turns red. Instead, flashes different colours for about 5 mins and
then finishes booting.

Not a complaint, but just wondering: why so long for it to boot? Is it 'cuz
of all the decrunching?

I'd really like a 3.1 software solution to work with my A2091 if at all
possible. As I mentioned before, TwinKick will go into constant reset mode too when the A2091 is plugged in and after I've tried disabling autoboot, slower drive, etc. :-(

LMK if you need some beer zapped your way or maybe something
along the lines of a PayPal donation to help in the quest of getting it to work!

[freqmax]

A2091
"Full-length Zorro-II DMA SCSI hard drive controller that was originally introduced with the A2000HD."

[save2600]

So... does DMA mean that it doesn't place or map the RAM where Kickwork, Twinkick and the like expect it to be?

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

[save2600]

Originally Posted by 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.

Thanks Ratte. Good idea, but I just tried it with no luck. Was even thinking I could build a switch and in-between resets, switch her to the full 2mb, but all the A1000 wants to do is constantly reset after loading KS 1.3. That's without a HD connected. If a HD is connected, it wants to boot straight away after loading KS 1.3. Looks like I am DJBase bound again for a KS adapter :-)