DISCLAIMER
  As this program is public domain, the author is not at all liable for any
problems you may have when using it or any problems it may cause. I do NOT
recommend using exclusively the 3.0 kickstart on the A3000, as 3.0 does not
work 100% correctly on ECS machines. I do not recommend upgrading your boot
partition to 3.0. Install the 3.0 workbench on a separate partition so you
can use either 3.0 or 2.0. Edit the beginning of your boot disk's startup-sequence
to automatically transfer control to the 3.0 partition if the 3.0 kickstart is
in use. DO NOT USE THIS PROGRAM IF YOU DO NOT UNDERSTAND THE DOCUMENTATION
BELOW ABOUT MEMORY MAPS AND ROMTAGMEM. IF YOUR ROMTAGMEM AND SKICK ARGUMENTS
ARE NOT CORRECT FOR YOUR CONFIGURATION YOUR SYSTEM COULD APPEAR TO WORK,
BUT HAVE PROBLEMS WHEN TOO MUCH MEMORY IS IN USE.


  This program lets you use non-A3000 kickstart images on the A3000. What it does
is it allows you to keep certain specified resident modules (such as the scsi.device)
through an skick reset. keepres takes as many arguments as you want. They should
be the EXACT names of the resident modules you want to survive the reboot. I have
found that "keepres scsi.device" provides the best results for kicking to an 
A1200 39.106 image. Anyway, the way this program works, it requires that both
the A3000 2.04 SuperKickStart and the skicked ROM be in memory at the same time.
Make sure you have enough memory to allow this. I wouldn't recommend using this
program with less than 6 Megs, as the extra 512k of memory used would cause 
significant problems with todays memory-hungry applications. 
  In general, you will want to use keepres in combination with skick and RomTagMem,
which are both available on aminet. skick does the actual re-kicking, and RomTagMem
allows you add motherboard fastmem to the system (A3000 motherboard memory does not
autoconfigure). ALWAYS run keepres BEFORE RomTagMem and skick, or it may prevent 
any run before it from operating correctly. 
My SuperKickStart A3000 has a Memory Map like this (from Sys:tools/showconfig)
RAM:    Node type $a, Attributes $105 (FAST), at $7c00000-$7f7ffff (3.5 meg)
        Node type $a, Attributes $303 (CHIP), at $400-$1fffff (~2.0 meg)

In addition, 2.04 kickstart is located from $7f80000 to $7ffffff
Anyway, I recommend putting your 3.0 soft-kick immediately below the SuperKickstart
memory, in this case at $7f00000. Then tell RomTagMem to use the remaining memory
below that (in this case $7c00000-$7efffff  or $300000 bytes, hence for this
system the RomTagMem line is RomTagMem 7c00000 300000 5 5 and the skick
line is skick kickstarts/39106.A1200 ADR 7f00000 FORCE

--- BE WARNED --- The addresses described above apply to my A3000. You should
use showconfig to find out your memory configuration. It may, for example, be 
different if you have more or less memory than I have.

For a complete usage example, see the includes "runskick"
script file.

This system also works for softkicking an A500/2000 2.04 ROM. Not very useful really,
but it can be used for testing.


BUGS
   For some reason, the 39.106 kickstart doesn't survive a reboot. 
(37.175 A500 images work fine through reboots). 
keepres adds $7000000 to each of the resident structure addresses.
This will definitely NOT work on a non-superkickstart machine.
I'm not sure whether or not this is absolutely necessary. Non
superkickstart users might want to try removing this and recompiling.
One of the reboot-survivable memory blocks allocated is much bigger
than needed. This is because it getting allocated into very low memory 
and was being clobbered during the reset before the KickMemPtr allocations
were done. If you have problems getting this to work, you can try increasing
further the size of the allocations of the reboot-survivable memory blocks.


  -Steve Holland sdh4@cornell.edu 2/5/94