Need suggestions for Kickflash board.

[motorollin]

ral-clan wrote:
I don't want to screw things up.

You won't - you can always disable the flash ROM in order to erase and start again.

ral-clan wrote:
- What files from the OS3.9 Boingbags 1 and 2 do I need to put on the Kickflash?

Just put the BB2 ROM Update file (the whole thing) in to the KickFlash, then either delete the file from DEVS: or modify your setpatch line to stop it loading the ROM Updates.

ral-clan wrote:
- I use SCSI and have heard there's an updated SCSI device in OS3.9, in what directory would I find this to install it on the kickflash?

It's in the ROM Update.

ral-clan wrote:
- Once I've put the OS3.9 ROM update and SCSI update on the kickflash, how do I make sure my startup-sequence doesn't try to re-update these files (i.e. how do I disable it in the startup sequence)?  I'm guessing this is done in the SETPATCH command, but I don't exactly how that command works.

See above - either delete the file, or add the switch to the SetPatch line to make it ignore the ROM Update. Can't remember what it is, so type "setpatch ?" in to a shell to see the syntax. It's something like "NOROMUPDATE".

ral-clan wrote:
- After my Amiga is booted, is there any way to verify that the above patches are working (have been installed) from the kickflash during boot?

Type "version" in to a shell. If you see 45.something, then it has successfully applied the ROM Update.

ral-clan wrote:
- What other modules can I put on the kickflash?  I know of a NoClick module so far, but that's it. (I assume there is no 3.9 kickstart image yet).

Any BlizKick module! Also commands which have a resident tag and are "ROM-able" will work. As for the 3.9 KickStart image, it is entirely possible to build one, but there's no point really with the KickFlash since it has space for the 3.9 ROM Update.

ral-clan wrote:
Lastly, I assume I should disable any utility in the startup sequence that copies kickstart to RAM, as that would interfere with the kickflash's function, correct?

Correct.


[EDIT]
A few changes...
[/EDIT]

--
moto

[motorollin]

Do you have a 3.1 ROM chip in your Amiga? If so then the KickFlash will realise this and not use the contents of the flash ROM (in other words, it will still be using the original ROM chip). In my case I had to load the 3.1 ROM image in to a hex editor and change the version to something newer so that when the KickFlash compared it to the ROM chip it thought that the version in flash was newer, and used it. The alternative to this rather complicated solution would be to put 3.0 ROM chips in the Amiga and a 3.1 image in the KickFlash.

[EDIT]
Just re-read your post and this doesn't seem to be related to your problem, since the ROM updates do work. Left the original post there for information, but I don't think it will help you in this case.
[/EDIT]

--
moto

[motorollin]

ral-clan wrote:
I assume renaming it to "ROM UPDATE *DISABLED*" will also work.

I don't know actually. Depends on whether SetPatch looks for a specific file, or scans DEVS: for ROM Updates and applies them regardless of the name. If you don't want to delete it, you could move it to Storage.

ral-clan wrote:
Sorry, I don't know what a Blizkick module is, nor a command with a resident tag.

BlizKick is a utility which softkicks a ROM image (without a KickFlash). It can also include modules, such as the NoClick module you mentioned. A command with a resident tag is basically one which can be stored in memory instead of on disk. Most commands and utilities will mention in their readme if they can be made resident.

ral-clan wrote:
I assume Blizkick has something to do with Blizzard accelerators.  If so can these utilities still be used with Amigas not installed with a Blizzard accelerator?

Not sure, but it doesn't matter since you're using a KickFlash.

ral-clan wrote:
Does "resident tag" mean a utility that can survive warm re-start of the Amiga?  Other than "noclick" are there any great "must install" utils like this that would be useful with the Kickflash?

I'm not sure whether it will survive a warm reboot, but since it's in your KickFlash you don't need to worry, since the KickFlash will take care of making it resident at each boot. There are lots of BlizKick modules on Aminet. Also, if there are any utilities you use regularly, check their readme to see if they can be made resident.

--
moto